Jump to content
Sign in to follow this  
Jayhawk

This patch thing......

Recommended Posts

Hi all,

after trying everything mentioned in the various FAQ's, I still can't patch my (original) European Version (1.00).

My system specs are:

AMD T-Bird 1GHz

Abit KT7 Raid (Via 133 Chipset) Board (latest 4in1 drivers; 4.37)

786 MB RAM

Geforce 2 Ti 64MB DDR (Det 23.11 Drivers)

SB Live

30 GB Harddisk

4 GB Harddisk

Win2K Pro (SP2)

CDRom

CR RW

The "funny" thing is: I already had OFP installed and patched up to 1.27 beta - twice, both under Win 98 SE and Win2k. When I got my Geforce card, I reinstalled OFP, but since then I can't apply any patches anymore.

I uninstalled OFP, searched the Registry for any traces left, deleted the content of the WINDOWS\Temp folder, and rebooted. After a clean OFP install I reboot my system again, check the installation with CheckOFP_1_20, and get error messages, normally with DTA or DTA3D.pbo errors. I manually copy those files from the CD into the folders, check with CheckOFP, and ususally, after several tries, it finally says "no errors found".

*BUT* when I start the patching process (with 1.20), after a while I get an error message saying something about a checksum error, usually caused by 1985.pbo, or DTA.pbo (Phase 1).

Since it didn't happen before (I bought OFP when it came out here in Europe, and had no problems with it except for the last two months or so), and the only hardware changes I made during all that time was additional memory (512 MB), and this Geforce card. Other games (like Ghost recon, Falcon4) run pretty smooth, and I had no trouble installing those.

The burning software I was using, Win On CD, was installed before I bought OFP, and when I reinstalled OFP due to my upgrade from Win 98 to 2K, reinstalled it again, without it affecting OFP.

Same with the 4 in 1 drivers. Before all that hassle with OFP started, I wasn't even aware that my Mainboard was such a piece of crap and needed a BIOS upgrade and/or latest VIA drivers. I was running the default BIOS and the drivers that came with the installation CD.

Can anybody here help me please, 'cause I have no clue what else to do short of throwing this damn PC out of the window???

Share this post


Link to post
Share on other sites

Have you tried fully uninstalling all CD burn software, such as yours, Nero, CloneCD, etc., before patching OFP?

Share this post


Link to post
Share on other sites

Well, yes, as far as I could find its traces in the registry.

The eerie part is that OFP did run perfectly well in the past, with WinOnCD installed.

Maybe I'll reinstall WinOnCD, and try to find what it does change in the registry, then try to delete all those entries??

Or do I really have to completely format my harddisk and do a fresh install of Windows? Oh nooooooo confused.gif

Or could it be the CD itself??? As far as I can see there are some (rather tiny) scratches on it (but not really obvious ones; the CD doesn't look worse than any of my other ones)...

Share this post


Link to post
Share on other sites

Don't worry: the cd-rom (notice the 'rom' part) 'specification' includes an error-correction system. Basicly, a cd-rom contains both data bits and error-detection/correction bits. Eventhough it cannot always correct faulty bits (bits which can either not be read or could be read but turned out to be faulty), it can detect them. If you try to copy a file from a cdrom to you harddrive, and the file contains an error (at least one bit that cannot be read), then the cdrom will send a signal, which in the end let's windows know that something went wrong, and windows will then abort copying the file.

Share this post


Link to post
Share on other sites

Well, this is the error message I get when I try to install patch 1.20:

Verifying Operation Flashpoint, version 1.00...

Operation Flashpoint: Updating version 1.00 to version 1.20...

Some error occurred during patch installation.

Patch file is probably dammaged. You may need to download it again.

Error in file CAMPAIGNS\1985.pbo, phase 1.

And this is the textfile from the 1.20 patch directory:

File C:\Program Files\Codemasters\OperationFlashpoint\CAMPAIGNS\1985.PBO.tmp: bad checksum: 175443255 (expected=175443839)

Share this post


Link to post
Share on other sites

Are you overclocked at all? If you are...go back to non-overclocked settings. I had a KT133 board but I couldnt remember if they had the option to switch between using a 133mhz bus or a 100mhz bus. If it has the option to switch down to the 100mhz bus, try that. It's odd, but I have a KT266A, and I had to (and still have to) switch my board down to the 100mhz FSB to patch/install OFP, but I can switch it back up to 133mhz after I patch it with no problems, I am even running overclocked at 148mhz FSB stable.

If that doesnt work, try disabling Ultra DMA on your hard drive (through the BIOS) and try it. VIA chipsets seem to not get along very well with OFP in the installing/patch process.

I'll check and see about your board, that SB Live! might be giving you some problems, you might just need to move it to another slot and see...sometimes the slots share IRQ's with something its not supposed to share it with and data gets corrupted very easily.

Share this post


Link to post
Share on other sites

Hi 14th Boscoh,

well, I'm not overclocked, my FSB is set to 100.

My SB Live! card is in PCI slot 4, my Ethernetcard in slot 5 (Geforce is AGP), no other cards installed (slots 1, 2, 3 and 6 are empty)........

.......BUT, I just found out that my Geforce card, my SB card, my Ethernetcard, the USB-Controllers and my RAID-Controller all share the same IRQ - IRQ 11 that is. I suspect (well, I remember that I read it somewhere) that Windows 2000 assigns them?? Could that be the problem? If so, how do I manually assign IRQ's, and how do I know what IRQ should go with what Hardware??

Well, I guess I'll try disabling UDMA in the BIOS now, and see if that'll help.

Thnx.

Avonlady,

well, I flashed the BIOS, I installed latest 4 in 1 drivers, and since reinstalling WIN 2K I never had burner software installed, so nothing there.

The only thing I didn't do was to update the ASPI-layer, since there's none installed on my system (I d/l that ASPIcheck-tool, and it didn't find any)?? sad.gif

Share this post


Link to post
Share on other sites

Sorry it took me so long to respond...I have been super busy. The way to keep Win2k from assigning those IRQ's automatically is to reformat your hard drive, and before you reinstall Win2k, go into your bios and disable ACPI, It should be under PCI/PNP Configuration or Power Settings...im not sure if the KT7 had that option available, but I want to say that it didnt. ACPI is what Windows uses to map more than one device to an IRQ. Its not so much a problem on Win ME or earlier, but on XP and 2k, it can start to be a problem.

Share this post


Link to post
Share on other sites

</span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Quote (Jayhawk @ Feb. 17 2002,20:15)</td></tr><tr><td id="QUOTE">The only thing I didn't do was to update the ASPI-layer, since there's none installed on my system (I d/l that ASPIcheck-tool, and it didn't find any)??  sad.gif<span id='postcolor'>

Have you tried this utility? It's the one I mention on The FAQ's ASPI item that was supplied by Placebo.

Also note the item's menion of FORCEASPI. From what I've seen, even if it's not there, it should be or else there could be potential problems.

Keep in mind that the folks who delved into this didn't do so for OFP. They discovered other technical problems when ASPI wasn't present or was not upgraded.

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×