I had to uninstall VTMB and re-install it. When trying to execute the patch, it says it's already installed and can't be installed again. Here's what I tried:
Uninstalling the game, deleting all folders, rebooting, installing the game, trying the patch.
I'm no stranger to the regisry; I guess I need to know what flag was set so I can go and unset it.
Thanks!
Bill
can't re-apply patch 1.2
- yrthwyndandfyre
- Posts: 786
- Joined: Tue Feb 15, 2005 2:30 am
- Location: 100 Miles up the butt of the world
- Contact:
[QUOTE=billko]I'm no stranger to the regisry; I guess I need to know what flag was set so I can go and unset it.
[/QUOTE]
Setting the Version back to 1.0 should do the trick.
[/QUOTE]
Setting the Version back to 1.0 should do the trick.
Sic gorgiamos allos subjectatos nunc
(The Addams family motto: Gladly we feast on those who would subdue us)
Do not meddle in the affairs of Dragons, for you are crunchy, and good with Ketchup.
(The Addams family motto: Gladly we feast on those who would subdue us)
Do not meddle in the affairs of Dragons, for you are crunchy, and good with Ketchup.
Since it was the last thing loaded onto my computer, I used a system restore point directly before I had installed it. That worked.
Interestingly enough, qafter re-installing the game + patch, I noticed in HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall, there were actually TWO entries for the game - a version 1.0 and a version 1.2. Maybe manually deleting the 1.2 entry after uninstalling the game in the normal fashion will work.
Bill
Strange though - I see no mention of that problem anywhere, so I assume something unique happened on my computer to cause this...
Thanks for replying!
Interestingly enough, qafter re-installing the game + patch, I noticed in HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall, there were actually TWO entries for the game - a version 1.0 and a version 1.2. Maybe manually deleting the 1.2 entry after uninstalling the game in the normal fashion will work.
Bill
Strange though - I see no mention of that problem anywhere, so I assume something unique happened on my computer to cause this...
Thanks for replying!