I'm a brand new user.

I did a straight build of v3.06.

On two different machines, I booted to the built CD and attempted to "Launch the Ultimate Boot CD for Windows". Starts CD, begins loading and about halfway through the progress bar it shows the following error message.

The file aic78xx.sys is corrupted.

Press any key to continue.

(Followed by "setup failed", etc.)


Now, this was only a baseline test, so I did NOT F6 in any drivers. However, both of these machines have RAID C: drives. Both are Intel mobo controllers, though years different. One machine happens to have C: at RAID 0 and the other at RAID 1.

I haven't yet tried to F6 in the RAID drivers because, of course, I can never find the damn floppies that I so carefully tucked away - somewhere.

I have a couple questions:

1. Am I guessing correctly that F6'ing the RAID drivers will resolve the issue?
2. Is this desireable behavior?

I don't want to have to build a system-specific CD for every machine. Many machines I see have RAID drives, but I often don't know that when I first see them. In fact, I'm never "prepared" with an appropriate driver floppy. Usually, I first run basic hardware tests and isolate a problem - then scramble to find an appropriate driver.

I'm thinking that two changes might be desirable:

1. On the initial Boot options screen, do NOT automatically initiate a a default Boot.
2. Find a way to "slow down" the F6 opportunity?

The initial boot screen defaults to the Ultimate Boot CD for Windows. If no selection is made, that Boot is started after a slight delay. The result is the subject error message. MY assumption was that the CD was bad, so I built another. The current behavior does not lead to an intuitively obvious conclusion about what the problem is.

Since I have the attention span of a gnat, the F6 prompt is always a problem for me. The phone rings, an e-mail comes in, the sun shines - whatever - and I always miss it. 'Twoould be nice to have it wait for a positive response; but that's Windows problem, right?

Just thought I'd ask . . .


Jim Maher

What version and SP level of Windows are you building from?

What type of source is it... OEM, Retail etc...

Is it one supplied by your computer manufactorer and if so which one?

Did you slipstream any service packs or other updates to your windows source?

Source is Microsoft. Specifically, Action Pack distribution of XP Pro / SP1 AND a separate SP2 CD. both CDs copied to disk for build.

So, yes, I slipstreamed SP2 with the SP1 base. And, no, I didn't include any other updates.

BTW, the same failure occurred on a third system, a very generic Dell 2400. So, its not RAID related.

I do note that the UBCD4Win-delivered version of this driver is different (newer and smaller) than the version extant on one of the failing systems.







Jim Maher

Check your download's MD5 hash to verify that it is ok... start with a fresh build... something is corrupted in the other one. No one else is reporting the issue so its something with that build or set of source files.

As another idea/directions... test your ISO in a virtual machine... this can tell you if your CD media make be having an issue