If you use the Package and Deployment Wizard included in VB 6.0 and create a Dependency File, you will have a list of the needed files for any VB program (some programs may require different DLLs than others).
If your application is a relatively simple one then the dependent files in C:\Program Files\Microsoft Visual Studio\VB98\Wizards\PDWizard\Redist, plus msvbvm60.dll from Windows\System32 may satisfy its needs and you may be able to compile a redist package on XP which will be compatible with and run on Win95.
Problems arise with an install package developed on a late version of Windows when it is run on early versions of Windows if you redistribute dlls for the late version which are not compatible with earlier versions. In essense this means all the dependent files you redistribute should be compatible with the earliest version of windows you must cater for.
In practice if you want to ensure that the program will run on an earlier version of Windows you need to have a machine running that OS as a test bed. Once you have determined the correct set of dependent files to redistribute you will be able to compile the installation package on a machine running any version of Windows9+.
most of the above are Windows 2000 era versions and represent the newest versions (I have found) which remain compatible with Win 95. You should be distributing these or earlier versions.
I loaded the default files as you have listed above. These files have newer dates on them though. When I tried to run it on a Win95 system I got an ActiveX not found error. Does anyone know if this is an easy fix?
Problems arise with an install package developed on a late version of Windows when it is run on early versions of Windows if you redistribute dlls for the late version which are not compatible with earlier versions....
...You should be distributing these or earlier versions.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.