John B.
john at winhaven.net
Thu Oct 16 12:30:43 CDT 2003
Richard: In my Wise installation scripts I check whether or not the target system is a 9x based OS or NT based OS and depending on the condition install different files (if they are needed). WinNT comes with certain OLE files pre-installed in the SYSTEM32 directory. These files are: COMPOBJ.DLL OLE2.DLL OLE2DISP.DLL OLE2NLS.DLL STORAGE.DLL TYPELIB.DLL STDOLE.TLB Win9x use files of the same name, but the files are very different. They are not guaranteed to be pre-installed. On those operating systems, the files are located in the SYSTEM directory. If you are running WinNT, you will find that you have TWO copies of each of these files, one in the SYSTEM32 directory and one in the SYSTEM directory. Because WinNT loads files from the SYSTEM32 directory before it loads files from the SYSTEM drectory, NT itself always uses the files in the SYSTEM32 directory. If you are building your distribution disks on a WinNT machine, be sure that you select the files from the SYSTEM directory and not the files from the SYSTEM32 directory. If you install the SYSTEM32 files onto a Win9x machine, you will corrupt the OLE subsystem and render it inoperative. You must also be careful that your installation program handles the case of an NT target machine properly. It should either: 1) Not install the above listed files at all. WindowsNT will have its own set pre-installed. 2) Install the files to the SYSTEM instead of the SYSTEM32 directory. NT ignores these files at runtime since it has its own set in the SYSTEM32 directory (which it gives priority to). Things You Should *NEVER* Do 1) In no case should you unconditionally overwrite the OLE DLLs in the SYSTEM32 directory with the ones from the SYSTEM directory. This will corrupt NT and you will need to manually delete all of those files and reinstall or repair NT. 2) Do not install the OLE files taken from the SYSTEM32 directory on to a Win9x machine. Install the ones from the SYSTEM directory instead. HTH John B. > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Griffiths, > Richard > Sent: Thursday, October 16, 2003 3:50 AM > To: 'AccessD at databaseadvisors.com' > Subject: [AccessD] Access Packaging (VB packaging) > > > Hi Group > > A colleague has raised a point and I wonder whether anyone in > this list has > any experience or knowledge of this. > > My colleague has suggested that there is (maybe) a problem when packaging > Access systems (and VB) (say using Package Wizard, althought the logic > could be applied to any packaging software) in that if the package is > created under XP then the various dll's and so on packaged are those > designed for XP - and that these may vary, in some cases, to > those packaged > when creating a package under NT or Win 98. So that.... > > Package Under XP....Deploy XP >> OK > Package Under XP....Deploy Win 98/95...possible problems. > > I must admit I did have a problem with one user (win 95) when the > application did not work properly (lots of strange things - compile errors > etc) on their machine - yet it worked ok on others - I think the package > was created under XP - so this may support the above argument. As a > precaution I now package my apps under win 98 (but this is a pain > on my dual > boot machine having to boot/reboot/test/repackage to correct then > /boot/reboot/test and so on) > > Has anyone come across this. > > Many thanks in advance > > Richard > > _______________________________________________ > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > >