Just a little information on a problem I had trying to reinstall FSX.

I recently changed mother boards but kept all of my drives from my old system after I moved every thing over when I tried to start the system it got hung up in a cycle and would not boot no matter what i tried the boot sector had gotten corrupted. So I tried to repair windows XP using the install CD I have but no luck so I had to reformat my entire hard drive in order to install windows and lost my FSX instaltion.
That is when the fun begin I kept getting a error that said I had a bad file. Mind you this has nothing to do with the system reset tool although I did run it with no luck. The error code I got was 1335 I then copied the entire disk 1 to a folder on my hard drive and ran the install from that folder and still got the same error. So I then proceeded to call M$ (Microsoft) I spent the next two to three hours on the phone with them and was never able to get past the same error. What was strange was that once it got into disk two before I got the error. After doing a lot of research using Google I made some interesting discoveries I thought I would share them with every one in the case someone else has the same problem.
The first thing I found out was I use NERO and that can cause problems when trying to install FSX so I removed that but it did not help.
I then thought my DVD ROM drive was finally bitting the dust as it was at least ten to twelve years old. So I went and bought a new drive but still had the same problem
I then found out if you are installing FSX on a large hard drive that is new or nearly empty The system can have trouble keeping up as it tends to read faster than it can write and create this error message.
There is a way you can limit the amount of ram your system uses which will slow down every thing and allow you to get buy this problem. I was installing to a new 320 gig hard drive. I did not want to try that just yet so I kept looking.
I then stumbled upon a post that said to try updating the drivers for the DVD drive. I had tried to do that on my old drive but was unable to locate a driver for it as it is obsolete and no longer supported.
Since I had a new drive I honestly thought I did not need to update the drivers for it. The drive came with no driver CD just came with NERO 7 essentials. But I figured what the heck so I downloaded a driver from the manufacturer and low and behold it worked
The moral to this story is try to keep things simple even though I had a brand new drive it used a generic driver from windows and that was the problem so after you hang a new device make sure you have a proper driver for it