RyanVM

You really need to provide more information if you want good help. I'm guessing you mean that you're loading the drivers from a floppy and are not directly integrating them into the CD, correct? If so, you need to read the MSFN Unattended Guide more carefully. http://unattended.msfn.org/unattended.xp/view/web/19/Basically, like the copy/paste I did says, you can't use OEMPreinstall=Yes in your winnt.sif and load drivers from a floppy. It's a topic which has probably been covered more times than any other single topic in this forum, so do try and search more in the future

That's but a small selection of the unreleased hotfixes . And indeed, you were correct that this is not the right thread for it

I highly doubt it, since MS has shifted so many resources to getting Vista out the door.

Here's a more useful link: http://www.marvell.com/drivers/upload/yk51x86_v85153.zip

http://unattended.msfn.org/

When I reported the issue to MS, I was informed that the fixed mshtml.dll would appear in the next IE cumulative update scheduled for April at the latest. So give it a couple weeks

Not soon enough

I like to keep XPero on his toes B)

I was only able to get 1.14 through WU

jdoe - do you have any idea why CABs created with CAB tool cause 7zip to error out when attempting to extract them? I'm inclined to say it's an issue with 7zip since no other programs have issues with them, but I'd be interested to hear your take on it.

That should work fine

See my reply to your post on my forums. http://www.ryanvm.net/forum/viewtopic.php?t=1790 (BTW, you do realize that it's kinda pointless posting the same question in both forums since it's pretty much the same readers in both...?)

Don't integrate KB912945. It's a known issue discussed in Hulk's thread at the top of the forum.

I'm sure KBxxxxxx.exe /integrate is an officially supported method

And with all the useful information you posted, you're sure to get immediate help!

My aren't you a perceptive one

Hmm, isn't MS releasing new security updates this week? http://www.ryanvm.net/msfn/faq.html#nextversion

Except that the very first post said he was looking for a way to directly integrate the file into the CD. He wasn't looking to do it after the fact...

What the hell are you talking about? He wanted it directly integrated into his CD, which is exactly what we told him how to do. And what we showed him how to do does have the systemwide ramification of requiring WFP to be disabled. Seriously, did you even read the first post?

This thread will probably make you guys' lives much easier http://www.ryanvm.net/forum/viewtopic.php?t=1653

Man, I remember that driver causing problems back when I was still doing RAID/SATA driver packs...

It's absolutely related. What he's recommending is a method where you don't even have to replace your original ntoskrnl.exe. You can just rename the modified one to something like purdykrn.exe and call that from boot.ini instead of ntoskrnl.exe. The advantage to it is that all it takes is one change to boot.ini and you're back on the original one again in case anything breaks.

If you integrate it with the Update Pack, you shouldn't even need the [drivercab_move] entries, since the Update Pack takes care of that for you

If WFP is disabled it should work. I still say you're better off just making yourself a custom addon pack, though. It would literally take 5min and would be a completely permanent setup from the getgo.

See if this site helps: http://msdn.microsoft.com/library/default....b9d8dbb.xml.asp