Patrician II v1.1 (English) fixed exe problems (?)
 

When i start a new game the screen gets corrupted after about 1 minute! Is it a problem with the fixed exe's or with the official us patch to v1.1 (wrong version patched)?

I know that some versions of Patrician II doesn't require the v1.1 patch...

I tried both Patrician II v1.1 (English) fixed exe/No CD posted in GCW recently.

Has anyone else the same problem?

Same problem here
 

I feel your pain. I really do!!! I can't get the game to run for more than about 5 min before it crashes with weird horizontal lines or just a blue/black screen. Tell me about your computer. Maybe it is a similar hardware prob. I have a Sony Vaio laptop with an ATI rage 8mb video card. I've tried everything I can think of. I'll post more info for you when I can. Let me know if you figure it out. I'm in touch with the developer about it. Send me your e-mail address or just watch this thread and I'll get you info if and when I get it.

Mark
flightgamer********com

I guess that one of two things happen:

a) Since the original version 1.0 works fine and some versions (international) don't require the 1.1 patch, a patch applied to a wrong game version is causing the horizontal lines on screen...

or...


b) The fixed exe files are not fully cracked (another protection layer maybe?) and that is causing the problem... Since it happens only when you play a game for a couple of minutes i believe that this is the most probable explanation...

I have a Voodoo 3000 and no graphic problems with any game so far...

Any news on this?

Is it a DirectX problem or a problem with the fixed exe?

GCS
 

I'm back to using the CD with no patch or crack and it works. Stability seemed to increase when I upgraded my via chipset drivers and went back to default video drivers. Good luck...
Mark W

You mean you are using version 1.0?

That works fine for me too! The problem appears when i update to v1.1 and use a fixed exe.

The protection changed with patch 1.1 that's why i suspect that this is causing the problem... and not DirectX!