Page 1 of 1

Zero Edit Fails after SWB2 Re-install.

Posted: Sat Feb 13, 2010 1:14 pm
by Ace_Azzameen_5
Original Post (No longer Applicable)
Hidden/Spoiler:
I've gotten back into SWBF2, mostly single player and modding. Today I pulled out the DVD so I could install and play online (CD Key needs to be installed to the registry).
Unfortunately the installation programs giving me that 'cyclic redundancy check' error and quits before finishing the install.
Could somebody send me a .reg file, or tell me the name of the key where the CD key is stored so I can add it manually?

HKEY_LOCAL_MACHINE\Software\Lucasarts\Star Wars Battlefront II\????? Should be where to find it.
or
HKEY_LOCAL_MACHINE\Software\Lucasarts\Star Wars Battlefront II\1.0\ ?????

In the mean time I'll keep looking for registry back ups.

If you send me a .reg file, remember to edit out at least the 4 middle characters of your CD key.

P.S.
Possibly as a direct result of this failed install, Zeroedit started giving the runtime error. Go figure.

Thanks.

Re: Zero Edit Fails after SWB2 Re-install.

Posted: Mon Feb 15, 2010 11:13 am
by Coley
Shouldn´t that be in the modding-topic? :?

Re: Zero Edit Fails after SWB2 Re-install.

Posted: Mon Feb 15, 2010 12:26 pm
by mswf
No. This falls under both categories, but this forum is a better choice because it isn't a modding error.

Re:

Posted: Sun Feb 21, 2010 9:42 pm
by Ace_Azzameen_5
lol I weighed the options far too long.

Anyway....ZE's back!

Original Thread Title: Zero Edit Fails after SWB2 Re-install.
New Thread Title: Zero Edit Fails after Monitor change

Long story short, i switched monitors and switched back....and now it works.
I can't at the moment but maybe someone should test the effects of switching to a different monitor without updating drivers etc and see what that does to Zeroedit...

And it worked on the one monitor before btw...
Finickity little thing it is....

Re: Zero Edit Fails after SWB2 Re-install.

Posted: Mon Feb 22, 2010 12:47 am
by 501st_commander
switching monitors?

O.o

thats odd.. its most likely the moniter driver.