Program installs into Win98 ok, but not Win2K or XP. Why?

[bupkus]

Program installs into Win98 ok, but not Win2K or XP. Why?

I have an old program written in the Win98 era that's no longer supported. I believe it's written in VB and uses a microsoft database engine of some kind. I would like to run it in a more stable OS, like W2Kpro or WXPpro but it doesn't seem to load all the data when I run a 'restore'. Either that or it doesn't display all the data cause one column in a form displays as empty. In either case it works ok in W98 but not an NT variant. Is there some way I can figure out what's happening?
The restore uses a .zip file I can view and see all the .mdb files inside. I can't display those file contents unless I install Access or an access viewer if MS makes one. I suppose I must install Access and try to find which file has the missing data and try to see why it never appears when run in W2k or XP.

 

[gorcorps]

Hmmm... If the program uses some kind of old school DOS to run, then XP will have many troubles with it. 2000 wasn't that bad w/ DOS though. I can't fully understand why it wouldn't run on xp or 2000 but on 98. In my experience only XP would have trouble. Wish I could help more.

 

[bupkus]

I have a setup.CFG file that appears in a directory of the above mentioned program I wish I could have analyzed. I believe it would provide the answer I'm looking for but probably needs a programmers eye. Is there a way I can attach it? Perhaps if I just copy and paste some of it. Not all the files are displayed below, but a sample of almost every category.
Question: Would W2k store system files in a different location than W98? If so could that be the source of the problem?
I don't know what this file does but it seems to be loading program files in various locations, hence the REMs.


REM: The following files are base VB system files - most applications use these.
FILE: "$winsysdir$\MSVBVM50.000", overwrite=new, From="C:\WINDOWS\SYSTEM\MSVBVM50.dll", nouninstall, register, sharedDLL

REM The following files are for the Sheridan Designer Widgets Custom Controls
FILE: "$winsysdir$\SSDOCK32.000", overwrite=new, From="C:\Windows\System\ssdock32.ocx", nouninstall, register, sharedDLL

REM: The following files are data access system files - only include these if necessary.
FILE: "C:\Program Files\Common Files\Microsoft Shared\DAO\DAO350.000", overwrite=new, From="C:\Program Files\Common Files\Microsoft Shared\DAO\DAO350.DLL", nouninstall,sharedDLL
FILE: "$winsysdir$\EXPSRV.000", overwrite=new, nouninstall, From="C:\WINDOWS\SYSTEM\Expsrv.dll",sharedDLL

REM: The following files are registered optional VB system files - they are used by your application.
FILE: "$winsysdir$\COMDLG32.000", overwrite=new, From="C:\WINDOWS\SYSTEM\COMDLG32.OCX", nouninstall, register,sharedDLL

REM: The following files are registered data access system files - only include and register these if necessary.
FILE: "$winsysdir$\REGSVR32.000", overwrite=no, From="C:\WINDOWS\SYSTEM\Regsvr32.exe", nouninstall
REGSERVER: "$winsysdir$\MSVMVB500.DLL"

REM The following files are your Database files - you will need these files.
FILE: "ACCTNO.000", overwrite=new, nouninstall, From="H:\Vb5ver40\EMPTYDAT\Acctno.mdb"

REM The following files are your VB & other application files - you will need these files.
FILE: "MAGPAPER.000", overwrite=new, From="H:\Vb5ver40\EMPTYDAT\magpaper.bmp"

REM Three steps for creating your own setup:
REM I. Go through each command in this config file and modify
REM to fit your own needs. This is done by clicking on the
REM command line and modifying the dialog box below.
REM II. In the left window, click on "File" under the
REM BASE INSTALLATION category. You will see a "Select Files"
REM button in the dialog box below. Click on it to select
REM all files that you wish to distribute, then click on OK and Add.
REM III. Select "Rebuild All" from the Build menu and choose to
REM build a single EXE or floppy diskettes. (You can also
REM select "Run" from the Build menu to test your installation.)
REM Your installation is now created. The file(s) will be saved in a
REM "Onefile" or "Disks" subdirectory under the Build directory you
REM specified in the Build dialog box.

TITLE: "Programname Setup"
SUBTITLE: "by Software Company., Ltd."
BEGINFIRSTSCREEN
Thank you for using Programname. We are confident that you will find it a valuable addition to your software library.

This program will install Programname onto your system. You will be prompted for a few bits of information - please answer the prompts when they appear. Thanks.
ENDFIRSTSCREEN
UNINSTALL: yes, makeicon, removegroup
DEFAULTDIR: "C:\Program Files\Programname", text="Programname will install onto your system in a directory. Please accept the suggested directory location and name or type in one of your own. Make certain to provide both a drive letter and the directory name."
FILE: "SETUP.000", overwrite=new, From="h:\pcinst\programname\setup.CFG"
WINITEM: "Programname", "$DEFAULTDIR$\programname.exe", "Programname", icon="$DEFAULTDIR$\programname.ico", replace
WINITEM: "Programname", "$DEFAULTDIR$\programname.hlp", "programname Help", replace
SHORTCUT: "$DEFAULTDIR$\programname.exe", "Programname", dir="$DEFAULTDIR$", icon="$DEFAULTDIR$\programname.ico"
COPY: "Utilities\Repair Databases.exe", "$DEFAULTDIR$\Repair Databases.exe"
COPY: "Utilities\FixLedger.exe", "$DEFAULTDIR$\FixLedger.exe"
COPY: "Utilities\Update Databases.exe", "$DEFAULTDIR$\Update Databases.exe"
WINITEM: "Programname\Utilities", "$DEFAULTDIR$\Repair Databases.exe", "Repair Databases", replace
WINITEM: "Programname\Utilities", "$DEFAULTDIR$\FixLedger.exe", "Re-Index Ledger", replace
WINITEM: "Programname\Utilities", "$DEFAULTDIR$\Update Databases.exe", "Update Databases", replace
BEGINLASTSCREEN
Programname has been successfully installed onto your system. To run Programname, select the icon labeled 'Programname' from the program group labeled 'Programname'. There is also an Uninstall icon selected, should you ever wish to remove Programname from your system.

Again, thank you for selecting Programname.
ENDLASTSCREEN

 

[DaveSimmons]

If all else fails: Win98 should be fine if you do a clean install and don't run any other applications. You could dual-boot or even use Virtual PC.

What makes Win98 unstable is that programs can leak memory and resources that never get recovered until you reboot, unlike 2000 and XP where memory and resources are strictly per-application and fully recovered on exit.

That, and installing and running batches of applications that each take turns messing up the DLLs in the system folder and trashing the registy.

 

[bupkus]

Thanks, but I don't want to give up. I believe the answer is somewhere in the destination folders the files are stored in. I just don't know what kind of a script file that is and what it's responsible for.

LANDesk
Here's some info I've found that IDs all but a few of these "labels".