Printable View
i know this sounds REALLY weird.
but i decided to change the .exe name of my program, so anyway i give the user the new .exe, and when they try to run it, it activates their old install package and installs the old exe etc. how F**king weird is that.
any pointers!?
vb6 install package was an .msi made from VSI
the evil side of auto repair feature of VSI? I am not sure, but that is what it sounds like to me
Armbruster is correct, I believe! You will have to keep the old exe name. You can replace it with an updated one, but if the system detects the original exe name missing, it will reinstall it ...Quote:
Originally posted by SkiNLaB
i know this sounds REALLY weird.
but i decided to change the .exe name of my program, so anyway i give the user the new .exe, and when they try to run it, it activates their old install package and installs the old exe etc. how F**king weird is that.
any pointers!?
vb6 install package was an .msi made from VSI
argh, well thats just Farked. I've created a new install package, and im starting afresh, even though its gonna take all day to install on every computer, but so be it.
that's not too bad, at least youhave one working.
Mine doesn't work, when install the last system .dll file(I am not sure the last file is installed tomy computer or not),I was told to reboot computer for some system file is out-of-date. but afer reboot, same error come back.
I am really headache.