Corrupted EXE on clean install

[Eihort]

I purchased the downloadable version of Flaming Cliffs

and am unable to start it. The StarForce program keeps

telling me that the exe is corrupted and to reinstall.

I've done that three times (installing Lock On from

the original disc, patching up to 1.02 and then

installing the FC installer) and keep getting the same

error. Any ideas on how to get around Starfarce?

[504 Wolverine]

Hi there.

 

A few ideas here to try and help you.

 

1. It was recommended by the devs to install the add-on (1.1) to a fresh install of Lock-On (either 1.0 or 1.01 depending upon the age of your original disc). though lots of people patched from 1.02 and have not reported any problems but you never know.

 

2. The installer for 1.1 might have been corrupted during download. I would try another download to see if this was the problem.

 

3. Starforce cannot be "got" around. If you install everything in the right order you should have no problems. Install the original, then 1.1 then the 1.11 patch and then reinstall any burner programs (i.e. Nero etc), this will ensure that the burner programs will work.

 

Don't believe any of the hype about starforce, the majority of the problems that it is being blamed on was also pinned on safedisc when it first came out. Safedisc is used on the original version of Lock-on.

 

Any more problems don't be afraid to ask. We are always willing to help on these forums. Hope these ideas help.

[Alfa]

I purchased the downloadable version of Flaming Cliffs

and am unable to start it. The StarForce program keeps

telling me that the exe is corrupted and to reinstall.

I've done that three times (installing Lock On from

the original disc, patching up to 1.02 and then

installing the FC installer) and keep getting the same

error. Any ideas on how to get around Starfarce?

 

Hi,

 

Like Wolverine suggested, the problem you are experiencing is most likely due to a corrupted download. Try downloading FC again and see if that takes care of the problem.

 

Cheers,

- JJ.

[Eihort]

It was a Starforce problem, and they were nice enough to provide me with a work around.

 

However, I still have another issue with Lock-On itself, so I'm going to write another thread.