NT 4 sp4 Program won't run with Windows XP

January 21, 2011 at 17:44:49
Specs: Windows NT 4.0, Pentium II 350 MHz

I have this program that runs on a Windows NT4.0 machine. I tried copying it to a Windows XP machine, but there it doesn't even start up.
It either generates the following message: Run-time error '429' ActiveX component can't create object or shows the graphic interface with non functional buttons.
The program is used to calculates input given to different MS Access 97 database and then generate output with in pre determined ranges. It also uses a wide variety of "obsolete" file extensions like: zzqs, sav, GID, PAK, ttt,isu and bin.
Eversince the original installation CD is un-usable, the only option I have is to copy all files in the program file folder and everything else that's related to it and paste it into the Program files folder on my other computer.
Is there any one out there that can give me a clue of how to solve this problem.
(Maybe I overlooked something while copying the files or something else, that for some of you is obvious, but not for someone who uses the program only to work with.)

Thanking you in anticipation.


See More: NT 4 sp4 Program wont run with Windows XP

Report •


#1
January 21, 2011 at 18:08:50

Just copying programme files from one computer to another very rarely works. You have to run the installation disk as this will set up entries in the registry. There may also be DLL files in the Windows\Ssytem32 folder that may be needed.

ActiveX component can't create object is a good indication that an Active X control is not properly registered and therefor your application cannot find it.

Trying to get round those problems without the installation disk would be a difficult job for somebody who knew exactly what they were doing. For you it may well be impossible. Someone that knows about these things could look at the Windows\System32 folder and make an educated guess as to which files are needed and through a process of trial and error get the application working but it is a long drawn out process,

Getting another copy of the installation disk may be your only practical solution.

Stuart


Report •

#2
January 21, 2011 at 20:01:04

Turn the system into a virtual machine then fix the hal then it may run on the xp.

Why did it take me over a year to phone in a problem to ATT?


Report •

#3
January 22, 2011 at 04:10:40

The HAL (Hardware Abstraction Layer) has nothing to do with it. That's an Operating System function as far as I can see the OS is working perfectly.

The problem is the lack of an installation disks for the application in question. That will be a problem even if the OP wanted to reinstall the application on a Windows NT system.

Stuart


Report •

Related Solutions

#4
January 22, 2011 at 09:45:59

StuartS,

Eversince the original installation disk is not working anymore (damaged) and the one person who wrote the program is no longer among us, I guess I have no other option left but to try, find and fix everything that is linked with the program in the registry and the Windows\system (32) folders.
If you have any tips as for where to look or what actions to take/avoid, I would be grateful to hear them.

Fyi, the program is used to calculate various gas pressures based on input from laboratorium analysis. Each main component exists of around 10 other components, each with their own specific P-V diagram. The program calculates the percentage of each component and then calculates the pressure of the mixture at any given temperature, based on the newly calculated mixture.
It has already been suggested to try and build an Excel spreadsheet, but I highly doubt it if anyone without not only knowledge of programming, but also good knowledge of Chemistry/thermodynamics will be able to build anything close to the program we (I) work with.


Report •

#5
January 22, 2011 at 10:35:45

All I can suggest is that you look for files that might be associated with the application. DLL files, OCX files if it is using VB or VBA then try registering them manually.

You can do this by using regsrvr32 which can be found in the Windows\system folder,

Type Regsvr32 /? at a command prompt to see the options. It is normally used from a command prompt.

As I said, it could be a long drawn out process with no guarantee of success but if it is the only option you have to try.

Installing MS Access 95 on Windows XP should help a lot if you have access to it.

Good luck.

Stuart


Report •

#6
January 23, 2011 at 01:10:08

I think you are headed down a dead end road almost any NT 4.0 program is not going to work in XP Windows, I mean you can take a hard drive that has NT installed on it attach it as a slave drive boot into XP and 90 percent of any programs inside the WINNT directory structure i.e. SYSTEM32 and all the other folders there next to nothing will run on XP. Trust me I tried extensively to trick or rather hack QuickView from NT and the windows 98se Version in to working on XP I never found a way. I copied DLLs I hex edited locations of dependencies in the DLLs and EXE everything short of hacking the registry that well is for the experienced a very sensitive job and mostly is avoided. I don't touch the registry unless I know the changes have proven results that I can look at and see that someone else has done it before me. If you plan to break new ground be sure to get Virtual PC 2007 for XP install it and create a virtual XP inside there then mess with the registry. That is the safe way, I still don't think it'll do any good though. Best Of Luck..

http://telechargerman.tripod.com/


Report •

#7
January 23, 2011 at 06:20:51

I think you are headed down a dead end road almost any NT 4.0 program is not going to work in XP Windows,

Thats complete and utter rubbish. I have programs that were made for Windows 98, The worked fine on Windows NT and now on Windows 98. But then I still have the installation disks and that is where the problem lies,

I mean you can take a hard drive that has NT installed on it attach it as a slave drive boot into XP and 90 percent of any programs inside the WINNT directory structure directory structure i.e. SYSTEM32 and all the other folders there next to nothing will run on XP

Thats because most of the programmes in system32 are Windows NT specific and are put the during the installation. As the OP has Windows XP installed an running then that wont be a problem.

The other files that are put there by programme installation like DLLs and OXCs are likely to be identical for all version of Windows from NT onwards.

Stuart


Report •

#8
January 25, 2011 at 05:11:33

True but the guy said he doesn't have the install program and if you can't install it on XP it isn't going to work, Like you can't take the program QuickView copy it from the installed folders on NT or Windows 98 and have it work in XP Windows. Because there is no install program for it on either version of those windows that will run outside of 98 or NT 4.0 or that is installable on XP. Because Microsoft removed it from Win2k onward and there never was a user installable program for QuickView. With out an installer your chances of getting a program from NT or 98 to work on XP are complete and utter rubbish. Because There Is No Way, unless you can get Windows to install it you are out of luck. Unless you can prove me wrong and have some prof I'll never believe it.

Anyway I was just suggesting that I wouldn't waste my time on it.

http://telechargerman.tripod.com/


Report •

#9
January 25, 2011 at 05:31:44

You are missing the point obsolete. The chances of copying any programme from one computer to another without the installation disk and getting it to work are slim, regardless of which Operating System or system are involved, even if the were identical with identical hardware, The different Operating Systems is not the problem, it the lack of an installation disk.

The installation programme puts entires into registry, The fact that the OP is using two different Operating Systems is irrelevant in this case, To say the the two different operating system will stop it from working is silly.without having intimate knowledge of the application in question.

As this is a database application using MS Access there is a very good chance of it being made to work.

Stuart


Report •

#10
January 25, 2011 at 05:51:13

Okay I see what you are saying now, I am thinking about Quickview which is not really an installable program to begin with on XP, Where this Program is one that could have been installed with the installer that is no longer operable, You either need the Install Program or you need to trick windows into thinking it was installed.

I am to lazy to mess with XP's Registry if it was 98 I could and probably would do it. I am Obsolete after all.

http://telechargerman.tripod.com/


Report •

#11
January 25, 2011 at 06:36:48

I wouldn't mess with the Windows XP registry, it is far more complicated than the Windows 98 registry. You could delete whole chunks of the Windows 98 registry and it would recreate itself. Not so with Windows XP.

That is what the regsvr32 application was designed for. It can emulate some of the functions an installation application uses. In fact a lot of installation programme will actually use regsvr32 during the installation process.

Stuart


Report •

#12
January 25, 2011 at 08:02:37

I have managed to do something similar. My approach was initially on the old machine where the program was still working. I found the folder date/times for the program then searched for others with the same date/time. Complicated because other files or folders with same date/time could be something completely different. Once I had deduced the files and folders they were copied over to the new machine.

The next step was to search the registry to find associated registry entries (no mean task) then export them for import onto the new machine as reg files. This required some of the reg files to be edited to ensure that they only added the relevant information.

However, I agree with those who have already said that messing around in the registry is risky unless you are well up to it. I would always install a freebie called ERUNT first, which takes and exact copy of the registry which can be restored for restoration if things go awry. That, of course, is not much use if you goof it so badly that you can't even start Windows.

Great fun but you have to be up to it.

We all live on a ball.


Report •

#13
January 25, 2011 at 18:26:47

I use Virtual PC 2007 with XP Pro I think you have to have PRO cause that is the only XP it works with, So if I was going to hack the registry I would run my XP Virtual machine and try getting it to work there first if something goes wrong you won't lose any thing because it isn't on your actual setup it is in a virtual machine and stored in a file on your computers hard drive. Called a virtual Hard Drive.

http://telechargerman.tripod.com/


Report •


Ask Question