Here’s what happened to me:
In October ’06, I installed FSX Deluxe on to my existing XP Pro Sempron 3400+ 1GB RAM machine that had been running for about 1 year with loads of anti-virus software, spam ware, Nero and other rubbish. It installed no problem at all.
This weekend, I installed a new IDE hard drive and did a completely new installation of XP Pro Media Centre Edition and did all the Windows Updates, I also installed MS Office, a Garmin GPS program, AVG Free Anti-Virus, but no Nero or CD/DVD burning software. The original hard drive remains in the machine on a different IDE cable and has been reformatted as an NTFS disc with no operating system.
So I tried to install FSX using the same DVD’s and DVD-RAM drive that I used in October and got the dreaded Error 1335. I looked here at this forum and tried the following:
1. Cleaning the DVD
2. Copying the DVD’s to the hard drive then installing
3. Copying the Cab files individually to the hard drive then installing
4. Replacing the Cab files through Windows Explorer part way through the installation each time it errors
5. Copying and trying to install to different combinations of hard drives within the machine
And still Error 1335 - Sometimes on Cab1 and sometimes on Cab 2
So I looked on Microsoft help and followed their instructions for installing problematic games all the way through, up to and including point 7 and still Error 1335. Look at: http://support.microsoft.com/kb/258496
So I looked around and found an old post about how to install Microsoft Money with Error 1335 – they seamed to indicate that you should set up a clean boot using msconfig in the run command (as Method 3 in the above Microsoft help page) BUT ALSO:
From System Configuration Utility (same place where you set up clean boot above), go to the BOOT.INI tab then ‘Advanced Options’ Select the /MAXMEM Option and enter a value that is much less than the RAM installed in your PC.
For example, my PC is 1GB RAM so MAXMEN initial shows up as about ‘1056’ (I assume this means 1.056GB’ish).
I set the MAXMEN to 256, rebooted and reinstalled – this time I got to Cab7 before Error 1335.
Then I set MAXMEN to 200, rebooted and reinstalled FSX, this time I got to Cab12 before Error 1335
Then I set MAXMEN to 150, rebooted and YES YES YES – it installed – slowly, but it installed.
Do not then forget to set Configuration Utility back to normal boot and remove the MAXMEM Setting (and reboot).
Here’s my idea why it works:
Error 1335 occurs because all the little files that make up FSX come off the DVD faster than the PC can write them to the hard drive, so you get Error 1335. When I installed it last year, my PC was so full of rubbish and back-ground programs that it was running slow and so the data was coming off the DVD slower and everything was OK.
Now all the rubbish has gone, the PC is running faster, but cannot process the data from DVD to IDE quick enough. I think MAXMEN sets the maximum amount of RAM that Windows can access. By setting it to 150, Windows can only access the first 150MB of RAM, this slows the PC down (you will notice how slow FSX Installation actually runs under this setting) and probably also increases disc caching. By slowing the PC down, you slow down the speed that the files come off the DVD drive and therefore the PC/IDE is able to keep up with the write speed.
I hope this helps somebody.