Can you copy a WinXP Pro registry entry into Win 7 registry

[innkeeper9]

Hello,

Background:
1. I have a program I use always, I have the install disks and can install it on Win 7 Pro x64. It is a 32 bit program. However, this program had a critical patch issued as a download way back when and this patch cannot be installed on the 7 system, because the installer is a NE (Win 3.1) 16bit. The patch is critical to the program without which it crashes every 5 to 10 minutes.
2. I put on Win 7 two programs which also only had 16bit installers, they also are 32bit and I got them to work. The solution for them was to copy the folder over from XP, click the exe and then windows gives you a window says x is missing [usually dll files] so I then copied over to the system32 and the sysWOW64 folders the missing dll files [Not sure which folder they should be in so did both]. They work a treat with no problems.

The Issue and question:
I copied and pasted this program over however, unlike the others when I click it the error message is That x is not found in the registry. So, I was wondering if it is possible to copy the existing registry file from XP to the Win 7 registry? The location on XP is the same location Win 7 gives for the missing folder and missing value.

I do understand editing registries is tricky, I've done just some basic edits and I know the first thing to do, if this is possible, is to back it up before I start.

Possible other solution? Could I install using the CDs which would put the program in the registry and then copy the folder I brought from XP over that installation and then change the registry based on the values that are in the XP registry? Though the first way would be the quickest, I don't care which I have to use as long as I can get the program running and since it is 32bit it will run once the registry issue is solved.

Thanks for any help.

Ruth

 

[MilesAhead]

It shouldn't hurt to rerun the patch on the XP machine? If that should be ok you can use RegShot to take a snapshot of the XP Registry before installing the patch. Then take another after. It will tell you what files and Registry settings were changed. If the patch only updated the exe then I would just install on W7 then copy the patched exe from the XP machine.

If you're lucky that's all you'll need.

 

[innkeeper9]

Just making sure I understand what you are saying.

1. uninstall the already patched program which should also remove the stuff from the registry
2. if the stuff is not removed from the registry what do I do?
3. if removed, then reinstall the program
4. take a picture of the registry as is before the patch
5. run the patch
6. take a new shot of the registry to see what has changed

I just want to make sure I am following your directions exactly so I get the correct results. I don't care how I have to do it and how long it takes just so I get the program on Win 7. Too bad no one thought about 16bit installers not working down the road when they first started on 32 bit programs installed with them. Not very visionary for a pretty visionary field [just kidding ]

I can tell you one thing the patch does is upgrade the program version, it goes from 2 something to 3.869

Thanks so much for the help

Ruth

 

[carwiz]

I don't think just moving registry entries will work, even if you could find them all. The installers are different and there's class IDs that have to be installed. On 64-bit machines, the 32-bit registry hives are isolated from the 64-bit hives in operation. This is because of the address limitations on 32-bit software as well as security. Windows also isolates 32-bit programs and drivers from the 64-bit counter parts. The folder named "System32" on a 64-bit machine actually contains the 64-bit software. A folder called "SysWOW64" contains the 32-bit software. It's done this way to maintain compatibility. The 32-bit software that is run on a 64-bit machine is really run in a virtual machine or in WOW (Windows on Windows) mode. This is why 32-bit software runs slower on a 64-bit machine. It's running under emulation.

 

[Pete4]

actually without trying you can't tell if it's going to work, so I would just try and see. Without going into specific details, some programs don't use the registry at all (for example portable apps) so it would be impossible to say if your program uses registry just for tracking it's folders etc. for example (should work) or uses it also for tracking illegal copies and security (won't work) etc etc. Once you find the right entries, you could just export them to file and then right click and merge on new system. Of course assume your system may get messed up totally in the process so have full back up of everything just in case. Personally I would do full disc image, good idea to have it anyway, always, besides restore point and full registry back up.

 

[innkeeper9]

Thanks Pete and everyone. I will just keep plugging away, though I'm not real knowledgeable and have to mostly check forums I did just update a 16bit installer to 32 and it worked installing the program and creating registry files. Of course, that was one of those install shield installers and some of them are fixable though the process is tedious. Then again, it gives me something to do and who knows, maybe someone will come up with an answer! I'm an optimist at heart

Ruth

 

[MilesAhead]

I wouldn't do all that uninstalling. Just take a snapshot with RegShot. Run the patch installer. Take another snapshot. Then you should have an idea what's involved. The patch installer may refuse to go because the update already happened. But it may give you the option to patch anyway.

See what happens. If you can find out what has to be set to effectively apply the patch then you'll have some idea if it's feasible.

Edit: I see now what you meant about the uninstall. To detect Registry changes there has to be a difference. You could go the uninstall route. Or you could try tools from SysInternals that monitor Registry and File actions in real time. I don't know which is easier.

 

[innkeeper9]

I'll try the SysInternals tool 1st. They have something called Process Monitor that monitors real time. If it works that's much less work for me since uninstalling and re-installing means I lose all my custom settings which I had done over the many years of using the program. But, I can do a screen capture of all the settings and use that to reset them after reinstall.

Thanks for all the help

 

[MilesAhead]

You're welcome. Let us know the resolution.

 

[innkeeper9]

A long time ago in a galaxy far away

You're welcome. Let us know the resolution.

I realize that this is way down the road from when I was trying to do this - life tends to interrupt a lot of things - but I wanted to let you know the only solution I found. It may not be the only one, but it is the only one that worked with all I tried, and it is simple, though perhaps not a solution many can or would want to use.

I purchased a Win 7 Pro 32 bit and got rid of the 64bit. So, two years later, I do have my program, Corel PhotoPaint8, Corel Draw 8 and Cored Dream 3D installed through the Windows Virtual Machine XPMode, but they run directly from Win 7 and I haven't had any problems.