Serious Help Needed on Setup

[Catrina]

I have a major problem.

I changed the setup1.exe and compiled an application using it. I mistakenly left a stop statement in it. When I tried to run the setup, I got the error "Stop Statement Found", so I took all the stops out and compiled again. I put this new setup1.exe in the PDWizard directory and repackaged my application. But I am still getting the error on the machine I tried to install on originally. The install works fine on my machine, but even when I use the original setup1.exe that came with VB, I still get the same error on the original machine.

I am assuming that the first install stored the setup with the stop in it someplace and it is continuing to use it. I have deleted all setup1.exe from the machine, and cleared the Windows\temp files, I don't know what else to do.

I have to get this working today. Any help would be greatly appreciated.

Thanks
Catrina

 

[CCLINT]

Are you sure that when/after recompiling Setup1.EXE that the new version was placed into the PDWizard Folder and not the PDWizard\Setup1 folder? (some VB updates the default folder to compile the Setup1.exe into was PDWizard\Setup1 and not PDWizard)

The P&D Wizard will only use the Setup1.exe located in the PDWizard, not the PDWizard\Setup1 folder. And naturally if you compiled the exe into the Setup1 folder, and didn't copy it to the PDWizard folder, the P&D Wizard will still be using the old one.
[/b][/i][/u]*******************************************************[sub]
General remarks:
If this post contains any suggestions for the use or distribution of code, components or files of any sort, it is still your responsibility to assure that you have the proper license and distribution rights to do so!

 

[willrae]

I'm sure I placed setup1.exe in PdWizard. Service Pack 5 fixed the problem, (touch wood)

 

[CCLINT]

Then that (what I mentioned) is probably where the problem was. It couldn't be much else.... [/b][/i][/u]*******************************************************[sub]
General remarks:
If this post contains any suggestions for the use or distribution of code, components or files of any sort, it is still your responsibility to assure that you have the proper license and distribution rights to do so!