Package depoyment wizard fails on W2000

[Spinaker]

Having transferred my VB6 development program from a Win ME PC a W2000 machine I now find I cannot make the Package & Deplyment Wizard work. It hangs after I have selected the folder for the package. It works fine on the Win ME machine.
Any ideas please?

[Keithuk]

Yes, Win2k is s**t, stick to ME. I still use Win98 because of this type of problem.

When you say you've transfered VB6 development program. Do you mean just the project, so the Win2k isn't yours. This may seem a stupid question but do you have admin rights?

Try uninstalling and re-installing with Service Pack 6.0. There are plenty of links on here for that.

[Jmacp]

Try the INNO set up Package. You cam use P & D the find out what files need be include then add them to INNO.

[lintz]

I DID use P&D Wizard previously but had the same problem with Win2000 so starting using INNO and have not had a probelm since.

Jmacp is right in saying find out what files are needed in your setup via P&D then use INNO.

[Spinaker]

I have full admin rights on the W2000 PC and am keeping the old (slower) Win ME machine as backup. Downloadng the latest VB6 service packs has not helped.
I have now downloaded and installed INNO but as yet I have not worked out how to use it (not obvious to me anyway).
I guess I will have to identify the files I need from the Win ME machine since P&D does not work on W2000.
Thanks for the suggestion - I will see if I can work out how to use INNO.

[BodwadUK]

LOL WINDOWS ME.

Suprised anything works on that

[Spinaker]

Thanks guys for pointing me in the direction of INNO. Itreally does work on W2000 when I had sorted out how to use it.
The only thing I remain uncertain about is how I would have determined what dependency files are needed if I had not had access to the P&D on the old machine.
Is there an easy way of identifying what additional files are needed for a new package?

[Vishalgiri]

You can make a exe that will deploy your App as P&D does, just make a list of required OCX and dll and others install them to where they should be ...

Or use Setup Factory

[James Stanich]

Use Microsoft Visual Studio Installer. I have used it to install apps on Win 2k and XP and have not run into any problems with the installer packages... just with my applications