No need to distribute VB runtime files?

[Uncle Mike]

I have a VB6 app that folks have been downloading for several years (a reactor simulator at my website, www.acme-nuclear.com) without any installation issues.

I use INNO Setup to create my setup file and I distribute the 6 VB runtime files to {sys}. I have tested my app under Vista, but recently a Vista user reported an error during install saying stdole2.tlb could not be registered due to an error accessing the OLE registry.

Question: Can I avoid runtime file install issues by simply NOT distributing the runtime files – as long as I don’t claim my app will run under older OS’s?

While searching the web, I see that several folks state that the VB runtime files come with ME, W2K, XP and Vista by default.

Thanks

[RobDog888]

Welcome to the Forums.

You always have to distribute runtime files as there is no guarentee that a system will have everything your app requires.

[randem]

Since you use Inno Setup, there are several things you need to know about installation. You don't need to distribute, I should say you NEVER distribute the VB runtime files to Vista. Vista has it's own versions and you will be corrupting Vista. On all other OS's you should distribute the VB runtime files.

Please read Installation Problems

[Uncle Mike]

OK, Thanks for the quick reply.

I will distribute the runtime files to all except Vista.

I assume I'll be able to review the Inno Setup help and find the exact syntax used to include earlier OS's while excluding Vista (VB runtime files as well as any other files I shouldn't distribute to Vista).

Thanks again

[Uncle Mike]

I searched and searched and could not fine a way for INNO Setup to only distribute a file if the user doesn't have Vista. Seems like it would be a common issue (??)

I guess I'll have visitors to my site download one setup file if they'll be installing on Vista or later (one without distribution of VB runtime files) and another for earlier OS's. Seems like a poor work-around.

Mike

[randem]

It is a VERY poor work around. There are scripts out there that do that. I know for I provide some of them With ********** and Inno Setup provides some too.
From **********

Source: e:\server data\randem\develop\vb 6 redist files\msvbvm60.dll; DestDir: ; Flags:  ignoreversion; OnlyBelowVersion: 0,6
Source: e:\server data\randem\develop\vb 6 redist files\oleaut32.dll; DestDir: ; Flags:  ignoreversion; OnlyBelowVersion: 0,6
Source: e:\server data\randem\develop\vb 6 redist files\olepro32.dll; DestDir: ; Flags:  ignoreversion; OnlyBelowVersion: 0,6
Source: e:\server data\randem\develop\vb 6 redist files\asycfilt.dll; DestDir: ; Flags:  ignoreversion; OnlyBelowVersion: 0,6
Source: e:\server data\randem\develop\vb 6 redist files\stdole2.tlb; DestDir: ; Flags:  ignoreversion; OnlyBelowVersion: 0,6
Source: e:\server data\randem\develop\vb 6 redist files\comcat.dll; DestDir: ; Flags:  ignoreversion; OnlyBelowVersion: 0,6
Source: e:\server data\randem\develop\vb 6 redist files\vb5db.dll; DestDir: ; Flags:  ignoreversion; OnlyBelowVersion: 0,6

[Uncle Mike]

The light just came on.

Thank you Randem - that is exactly what I need!

Mike

[RobDog888]

Other off topic posts moved to a new thread in General Developer forum

http://vbforums.com/showthread.php?t=492973