Question on 'default runtime files'

Started by philippe, October 26, 2011, 12:04:26 AM

Previous topic - Next topic

philippe


Randem

Aloha philippe,
 
The full version (11.0 Build 16) has been released. Download it from the website.

Randem

Remember the Unsafe.fil needs to go into the user data area for it to be used. You can put a copy in the InnoScript folder also for a backup.
 
I.E.  
 
in Vista / Windows 7
 
C:UsersYOURUSERNAMEAppDataLocalRandem SystemsInnoScriptRelease
 
In XP
 
C:Documents and SettingsYOURUSERNAMELocal SettingsApplication DataRandem SystemsInnoScriptRelease",

philippe


Randem

Ok, both have been fixed. The vbruntime files got into the unsafe file and have been removed. They got into the MDAC section... Here is an updated unsafe file list



And here is an update InnoScript exe

This takes care of the Create Script button as well as a few other things. You can look at the InnoScript history to see the changes.

InnoScript EXE
InnoScript.zip (541.8 k)

philippe

No worry...I always wondered myself if these system files still needed to be embedded since most of the default installs install most of these files anyway...But ou never know, right?

Randem

Aloha philippe,
 
I will take a look into these issues. Thanks...

philippe

Aloha,
 
With the advent of v11, it seems - if I am right - that you have somehow reduced the number of default runtime files embedded in the script..I mean, I created yesterday a brand new VB6 project for WXP and looking at the generated script, I figured that it just included msvbm60.dll and stdole.tlb whereas in previous versions it was embedding 5-6 files.
 
Is there a reason for it?
 
Another detail: using the latest 11.0.15: if you doubleclick a .pjt file from Windows Explorer, IS loads the file but disables the Create Script button from the toolbar...If you reload it from the menu, the button is then re-enabled.
 
Cheers
 
Philippe