OT. New computer - need to access old computer

Be great if you could, though if I finally master this VNC business I should be all right (until the next hard disk failure).

The programs are Adobe Premiere Pro (upgraded from version 6), Namo Webeditor 6 (upgraded from 5) and Quickbooks 6 (various non-numbered patches).

Adobe might be helpful, but QB6 is very old and no longer supported, and Namo are Korean (I think) and never answer emails.

It's made worse by the fact that I lost emails at one point, and original disks are in storage and inaccessible.

What I really need is a method to hack the registry.

Regards

G

In the absence of any other way of reinstalling from CDs I would urge you to consider the VM route.

- You get the old computer running in a window
- You can back up the whole thing just by copying a file
- You can free up the physical space taken by the old one
- You don't need to reinstall anything
- You can set it up so that it can access all the data on the new one.

George, you have a PM.

There are some nice tools on www.sysinternals.com
There's a registry viewer and file viewer that show what keys and things are being accessed by any (or all) applications.

Some applications are stupid and just put the keys in a simple file. If the software is worth its salt then the key will be encrypted somehow.

And Googling, there are packages that will show you the product key:
http://www.nsauditor.com/product_key_finder.html
(Premier and Quickbooks included )

And this: http://www.adobeforums.com/webx?14@@.3c053074

There are also some MS tools at www.nirsoft.net

Hope that helps!
Matt

Thank you, Matt. I think I will persevere for the moment (when I have a few moments, or rather, a couple of hours) with getting UVNC to work.

Then, at leisure, I will try and find out how to get the progs onto the new pc. The drive on the old one is more than three years old now, and won't last for ever.

Thanks very much to all who have made suggestions.

G

PS: I hate new computers. It always takes a month or more to get them working properly.

Update.

Well I fnally got it working with Tight VNC (having also tried Ultra and Real).

I settled on Tight because it had proper documentation, unlike the others.

However, the reason for the failure to work was that I also have another (proprietary) VNC prog on the computer, installed so that I can access a PC at a client's office in London. It is dedicated to the client's system, and no use for my local network.

Despite turning the client's VNC off, the various new VNC progs failed to work. I discovered eventually that the router stores the VNC information somehow, and refuses to allow another VNC instance to operate. The trick is to switch off the router, and start again.

Nowhere, in any forum or documentation, did I find any reference to this.

Anyway, it's working now, and thanks again for all the suggestions.

G