While trying to uninstall 2xDVD5 version the setup returned error and there is no possibility to reinstall game. Any sugestions?

Delete the registry key and then reinstall ;)

This is more about bug reporting and fixing installer than manual fixing registry, but thanx :p

this is an error that you got, for me all works fine (install-uninstall) no need to fix anything.
if you don't like it, simple... don't use it

Actually... This "bug" (Rather a feature) is somewhat REQUIRED.
If I remember well, these InnoSetup custom installers use the game's registry keys to detect if it's installed or not. It's a surprise that autorun haven't enabled UNINSTALL instead of INSTALL this time...

Anyway, in all (or nearly all) times it happens with Peterf's conversion, it's because people FORGET to uninstall the game after test the installer. But sometimes even the original installer left some "leftovers" to be manually deleted. So it's recommended you:
- Use Revo Uninstaller or similat tool to uninstall the game, instead of the original uninstaller;
- Use cCleaner's registry cleaner to temove these "registry" leftovers;
- And, for games with .MSI (Or .MSI-based) installers, The Windows Installer Clean Up is what you need.



Alternatively, buy a DVD9 Media and do the backup. Lot less hassle, much more easier. ¬¬

Hang loose guyz. I've reported some issue to help you make the installer more reliable on particular case but you clamored and accused me of bad intention. Over and out.

I dont see how you think they are accusing you of bad intention?

You asked a question "how to reinstall" and Peter told you how "by deleting the registry key".

and you didnt say in your original post that you were 'bug reporting'.

And Killer's post was very helpful in my opinion.

Killer told you what the 'bug' is, why it can happen and how to fix it.

The possibility was, that maybe it is not actually a 'bug', but a feature of the installer, and the reason that feature did not work as expected for you is because 'maybe' you had not un-installed the game correctly?

Because this is a public forum the info Peter and Killer have provided may not only help you, it may also help other users who may experience the same problem as you. ;)

In my case it seems to be another reason of this error. I've uninstalled the game by original setup before installing the conversion, moreover i cleaned the leftovers with soft from KillerOh's post, and after reinstalling the game this problem comes back.

Although KillerOh's post clarifid the reason of occuring this error, at last he sad: "Alternatively, buy a DVD9 Media and do the backup"... Yeah, right... If i'm here it means i _DON'T_ want to archive on DVD9. The same peterf1999's advice: "if you don't like it, simple... don't use it". The problem is i like your job and want it to be perfect throughout.

Moreover i used to wander the forums so long to say half of people isn't astute enough to modify registry or, what is worse, to use cCleaner or another similar soft. Another ones will get an idea to clean registry without such "revealing" advice. So i've thought more about fixing some scripts than improvise one-time solution ("if you have a horrible splotch on your tablecloth then try to... set there a vase with flowers" ;P). Furthermore the KillerOh's post proves, this is a wider problem and pobably will return in next conversions.

I thank Grumpy to show that actually neither me nor peter are pointing BAMsE for bad intentioning. However, as I said before, all the times that happened, it was because the game wasn't fully uninstaled, or due to some random error during uninstall. It was... "never" a kind of fail from peterf's installes.

BTW... not "his" installers after all...
Considering the "ammount" of code changing required to turn a "custom installer for (The intended game here)" to a "custom installer for (Your game here)"... as long as Peterf haven't messed with "uninstall" settings (As I suppose these are handled by Inno Setup itself, with no need to do "special codes", other than changing the uninstall window), there should be no problem with the uninstaller itself.

However, one have to admit: The "don't like then don't use" answer, plus the fact "his" installers are "closed-source" don't help us not even a little. Plus, if the uninstall issue isn't TRULLY related to the registry keys (As BAMsE said), then:
I **SUPPOSE** this is the reason of the problem. Even because original game installers uses the info from windows registry to "know" if a game is installed or not. That's how an autorun menu "knows" how to enable//disable the "install", "play" and "uninstall" buttons when the game is installed or not, or how an original installer asks to UNINSTALL a game if it's already installed in your system - Something that Inno installers doesn't seem to do.

And going back to the time where I did some custom menus, plus the code Skeraxe sent to me in that times and the fact that these peterf's installers always were "Registry-sensitive", that should be no surprise if peter's installer uses the regkeys for "uninstall" features, like it uses to the "autorun" features ("Uninstall" is disabled in my PC, as I don't have the game).




Don't get me wrong, people, it's just an opinion.
And yes, I'd like to see these peter's codes, and even that he stop sending pre-compiled installers, but the codes to be compiled instead (Like he did sometime ago). So people can do the needed tweaks by their own, or wait for someone with more free time to do these... with no need to asking to peter to do everything everytime and all... Whatever.

OK, OK... At the first sorry for this mess, at the "second first" i know where the problem is. Nobody's noticed the error window isn't black like the rest of Inno Setup? I've realized that todey, checked the "unins000.exe" file and bingo! It comes from original setup, not Inno. During the instalation of conversion Inno creates its own "unins000.exe" and "unins000.dat", but the first one is created at the beginning, the last one at the end of process. Meanwhile Inno moves files from DVD which contains:
so also the original "unins000.exe" (which overwrites this made by Inno at the beginning) and "unins000.dat" (which is overwriten by this made by Inno at the end). As a result in installation dir there is original .exe and Inno's .dat

BTW: i'd like to compile peterf1999's installers myself and don't need to ask him for doing e.g. 2xDVD instead 1xDVD (as here i did).

...

Lemme see if I understand...
You mean that your uninstaller haven't worked properly because the "unins000.exe" comes from... A-HEM... your game folder... and was included along the game files when you did the conversion?

...


And then you talk THIS about us!





Allright, people... some TRUE words of advise...
Everytime you do these "peterf" conversions:

1. Install the game.
   For STEAM releases, it's interesting to apply patches and the like.
   
2. Make a BACKUP of the game folder. It'll help you a lot!
3. Read the conversion
   
4. READ the conversion
   
5. READ THE CONVERSION
   
6. Do the conversion just after understand all the steps, but this time, ignore all and every "uninstall"-related files.
   Mainly "unins000.exe" and "unins000.dat", as the new setup will create them for you.
   
7. Uninstall the game before testing your all new installer.
   Try these software if "uninstall" becomes your enemy (Or just use them):
   • Revo Uninstaller or similar tool will uninstall the game with original installer AND remove all leftovers - Even if uninstaller fails;
   • cCleaner's registry cleaner to remove any "registry" leftovers;
   • for games with .MSI (Or .MSI-based) installers, The Windows Installer Clean Up is what you need.
8. test BOTH install and uninstall features from your the new installer.
   But just to be safe, install it in ANY ANOTHER FOLDER.
   DO NOT use neither the "default" one provided by the setup, nor the "previous" folder where it was installed.
   
9. • Conversion is working? Good! BURN TO HELL!
   • Conversion is NOT working? Now you know why you did a "BACKUP". ;)

Now we'll live in Peace of (Insert your god here. If none, well... live in peace. ;))... Amen.

Yes KillerOh, you understand quite well. But only deads don't make mistakes. I've made tens of conversions and never failed, until now. So yes, it's my blame, but when I've said the uninstaller returned an error, nobody took pains to read what this error means. Nobody realized such error even don't exist in Inno. Instead, you said I should take the conversion what it is, although error clearly sad there is a problem with generated uninstall script. However, one conclusion could be drawn: "take the conversion as is, because peterf1999 can't be wrong". And now one love fella :o

Quite true. ;)

Actually... NOT QUITE...

**MAYBE** the "utCompiledCode record" don't register as an error in normal Inno setup installers (Like the ones we can do with the Inno's Wizard assistent and no much "cosmetics", just simple and plain code), and in fact, there's no "utcompiledcode" word avaliable in Inno Setup manual.

HOWEVER, in several Inno Setup installers, it seems to happen when there's an OLD unins000.exe/dat. Examples for "known" software are WinVista//Seven codecs (Despite I always thought they were MSI-installers ONLY), Spyware Doctor and Any Flv Player 2.2.1, to quote some. Here's a google search. =3

It looks like "peterf" installers aren't the only ones with this error, and unfortunately, the "avaliable" solution for these above was to:
- Delete the "unins000" files
- And re-install in the same folder

Yet, it's "no good" for his custom installers: Unless you know which regkey the autorun reads to his "enable//disable buttons" feature for a manual remotion or try a "Brute-force uninstall" (Like Revo Uninstaller in extensive mode or manual deletion + CCleaner or any another reg cleaner), you'll be UNABLE to re-install it. After all, for these custom installers, the autorun menu IS the setup!

As you noticed in your PREVIOUS post, this is NOT an error with the generated script itself, but with how you did the conversion. Even because the way Inno Setup installers generates their uninstall files are "by design" (The way it works with "peterf" installer is the very same with all and every another Inno Setup installer).

Plus, despite the thanks I gave to peterf for... "his" installers, he never ever explained a bit of the codes, and after he said that "it's not his work", it just make me mad as hell with him and his "closed-source setups".
Everything nice he did for "Several-DVD9-2-Several-DVD5", like these setups, are ONLY with him. So ONLY him can fix the mess, yet he doesn't seem to be fully interested to neither share his knowledge nor that much interested to fix the mess. Yener90, for the other hand... And his scripts are also top-quality!

Due to this, we're all "doomed" to "take the conversion as is, because peterf1999(...)" stands correct. Yes, we're pretty dommed... ¬¬

NEVER include the unins*.exe or unins*.dat files from a previuosly installed game, when doing ANY DVD9 to DVD5 conversion. Move those files out of game dir, do the conversion with the rest of the games files, then move them back & uninstall normally. Then test the DVD5 Conversion ISO's for install / Uninstall. Never had an issue yet, but havent done this conversion as yet. Still working on another project.

Yes, I know peter has been very reluctant lately to post the full details of his latest conversions & hasnt responded much to questions regarding his conversions. He may be away, will just have to wait & see if he responds.

I've never seen steam games with those files :confused: