On Saturday, 12/13/14, I upgraded my computer from: (updated from original submission to reflect additonal actions to repair)
350 w Powersupply
AMD A6,2200 with 2.1 Ghz processer mounted on Asus A75 MB
using 8 Meg of memory (2x4.0 sticks) feeding an NVidia GTX 550ti
and a pair of 7200 rpm Drives; C: 340 Gig / E: 250 Gig.
Monitors: 21" Dell / 18" Westinghouse
Ad Aware is only virus prot on system; zero issues; never had conflict since closed beta began
>> This was giving me a solid framerate in combat of 25; dipping to 20.
to:
550 w Powersupply
AMD A8 3780 with 3.0 Ghz processer mounted on Asus A75 MB
upgraded to 16 Meg of memory (4x4.0 sticks) ~ all matching kingston
feeding an EVGA GTX 760 with 2 gig and the same 2 drives
Monitors: Dual 24" Dell 1920x1080's
Have Ad Aware turned off to get the file downloaded; making sure that it's not blocking anything.
>>>>
Got the "FRead did not read the expected numbe rof byte from file. Only 128 of 0 bytes read"
Read Forum Stuff; Took Corrective Action. No Success.
Restarted the computer; tried again - same result.
Read More Forum Stuff.
Ran the repair tool; fixed the errors (it said that mismatched files were the issue; referred to PAK files).
restarted the machine and ran the game. Now the error reads: "Missing PAK file ERROR"
restarted again. Same "Missing PAK" error.
Re-Ran the repair tool. It referenced the same mismatched files and reloaded lots of *.PAK files
Same error; wont run. So many people experiencing similar issues. Decided to Delete game and do fresh reload.
At completion of download and at some partially complet get the #MD5 error (read lots about that on the Forums)
Downloaded 8x times changing various things.
* * * U P D A T E * * *
Finally removed the additional 8 Gig of RAM that I had added and *poof*; the #MD5 error is gone and the game downloaded and now runs slick and at framerates 3x my original with no stability issues.
I want to thank the community and the nice folks at PGI for helping so much with this issue. Go Pro.
its a tragedy that there still is no "answer on why the #MD5 error is taking out a bunch of our installs and killing our game time... people just go off quietly and play another game or find their own answers.
Edited by Gofer, 17 December 2014 - 01:43 PM.