zetto

Woohoo, I beat a supermod I was delaying a fresh vista reinstall waiting for SP2, but now it turns out it does not have a integrate option

well, it's public now lol

After updating SATA driver to the Dell version (which I thought I already had) I was able to install the update

Didn't work. I've updated drivers, no dice, still crashes. I decided to install updates one by one and found out that KB943899 is the culprit. It's supposed to be a reliability update! What a load of crock, it fubars my Vista installation instead of making it more 'reliable'. Jeez! Edit: I've done some research, apparently MS replaces Intel SATA AHCI driver with that update, and it crashes on reboot on notebook drives (dell in particular). WTF was MS thinking when designing such an update?

Thanks for the suggestion. It's a Dell notebook, and all drivers installed are from Dell web-site, except for graphics, which is nvidia (I have nvidia graphics chipset, 8400gs). I guess I could swap back to dell nvidia driver and see what happens Hopefully, it'll fix the problem

any suggestions for a fix? I had another go at these updates, still have the problem. Even safe mode bluescreens and reboots. WTF did MS do this time?

I've installed these updates w/o a problem but computer won't go back to windows after reboot... Flashes blue screen at Vista load screen and instantly reboots itself. Had to use Vista CD to roll back the changes to get back in

I've run repair before going into safe mode, so I've killed all the updates... Not sure if I want to try to install them before more ppl install them. If it's widespread issues, we'll hear more of it

On my Dell, I don't have much crap... maybe because I've reinstalled windows from scratch BTW, I don't feel either way about Vista or XP, both serve me well

Hey there, did anyone else experience crash with Vista at boot? I've installed today's updates, and after rebooting the system, I found that vista would not load, no matter what. It flashes a blue screen during load (fraction of a second, couldn't read the error message) and then reboots the computer. The only way to get back in is to roll back the updates using Vista CD repair function. I have Vista Home premium (dell notebook). Any suggestions?

Thanks op! Although a little bit of constructive criticism - I'm sure this method works for you but for others, with other Intel chipsets and drivers this may not be the best way. Also, note that this works for RAID setup just as well for the ACHI setup. In my case, I had raid and modified the hardware ids to match the ones in the driver's txtsetup.oem file (I did keep everything else the same). So, with the latest F6 Intel driver, I have the following: PCI\VEN_8086&DEV_2822&CC_0104 = "iaStor" PCI\VEN_8086&DEV_2821&CC_0106 = "iaStor" PCI\VEN_8086&DEV_2682&CC_0104 = "iaStor" PCI\VEN_8086&DEV_2681&CC_0106 = "iaStor" PCI\VEN_8086&DEV_27C3&CC_0104 = "iaStor" PCI\VEN_8086&DEV_27C6&CC_0104 = "iaStor" PCI\VEN_8086&DEV_27C1&CC_0106 = "iaStor" PCI\VEN_8086&DEV_27C5&CC_0106 = "iaStor" PCI\VEN_8086&DEV_2652&CC_0104 = "iaStor" PCI\VEN_8086&DEV_2652&CC_0106 = "iaStor" PCI\VEN_8086&DEV_2653&CC_0106 = "iaStor" Worked for me, on Asus P5W DH mobo with Intel 975 chipset (ICH7). Might help those, who had errors with the ops suggested setup.

http://www.bit-tech.net/feature/47/4

actually, Nvidia's SLI is a different technology from Alienware's implementation. Alienware works with ANY pci-e videocard, and it's a external solution (i dunno, some adapter or something); while Nvidia's SLI is native. Appears, all latest gen pci-e nvidia videocards (6800 & new 6600) include sli connector. By default, nvidia's solution is better because there is less overhead, and it will work with any mobo that has 2 pci-e slots but with future ones only (like nforce 4). Right now, only high-end intel server mobo has those 2 slots. Hopefully, early next year u would be able to afford cheapo sli with 2 6600's that would yield 512mb videomemory and about 16-18k in 3dmark03. with 6800 it'd be faster but much more expensive Oh, and doesn't this belong in a different forum?

Time to update the slipstream guide - Service Pack for Office 2003 has been released!!!

Hey, now that the final DirectX 9.0c has been released, how do we get it to install silently? Any suggestion? Do we need to hex-mod it again, or some switches would work with it? thanks!

Woohoo.. Aaron is back, he'll straighten out all those MS guys Anyways, any word on when a REAL fix for IE vulnerability will be out?

Hehe, valiant effort XtremeMac. On my part, I should say it's a brilliant idea. I am trying to rebuild my unattended winxp cd and in dire need of a good, all-inclusive list of all WORKING reg tweaks. Thanks a lot, and all the best of luck.

Just tried it now, it's back up I dunno for how long tho

I was using Unnattended WinXP installation guide today, and all of sudden it dissapeared. I can't go there, when I do I get "file not found" error. When I tried the frontpage link, it just kicks me back to the Msfn.org frontpage. Same thing happens when I am trying to open Win2k3 guide for conversion (don't need it but it behaves the same way). Basically, it appears that *.msfn.org sites have dissapeared Any ideas if they gonna be back up, and is yes, when? Thanks!

Alright, when I followed intel chipset instructions, it worked. Anyways, I have the following 3 folders: 1) $OEM$\$$\INF which contains 4 files: 865.inf, ich5core.inf, ich5ide.inf, ich5usb.inf 2) $OEM$\$1\Drivers\IntelINF with 865.inf, ich5core.inf, ich5ide.inf, ich5usb.inf; and 865.cat, ich5core.cat, ich5ide.cat, ich5usb.cat 3) $OEM$\$1\Drivers\IntelRAID with iaStor.cat; iaStor.inf; iaStor.sys; TXTSETUP.OEM The major hurdle was unpacking and choosing appropriate files from several folders contained in the driver package. Make sure you choose the ones appropriate for your chipset (that's probably why you had computer constantly rebooting - wrong drivers). Lastly, I had to add the following 2 lines to winnt.sif [unattended] section DriverSigningPolicy=Ignore OemPnPDriversPath="DRIVERS\INTELINF" I think that was enough for my silent installation to recognise and format raid0 without reverting to F6 floppy disk setup. But it was a long while ago, so I might have forgotten a couple details, so read up some more. Good luck!

Check out this: General Intel info for setting up Raid on their chipsets http://support.intel.com/support/chipsets/iaa_raid/ Specific info for unattended setup of Raid (i.e., no need to press F6 during install) http://support.intel.com/support/chipsets/.../unattended.htm

Yeah, it'd be nice if someone looked into updating the first post in this thread. I know Aaron is not around, maybe one of the other admins could do it? Thanks!

This new critical update (June 9, 2004), 839643 for DirectX is not installing on my computer for some reason. I have DirectX 9.0b and I d/led the hotfix from MS site: http://www.microsoft.com/downloads/details...&displaylang=en When I try to run the above hotfix, it tells me there was an error and that my computer did not meet some requirements. The log file says: "SOFTWARE\Microsoft\DirectX\Version is Not Equal To Specified Value" Can someone tell me what is going on here? EDIT: I check registry, DirectX version value is 4.09.00.0902, same as reported by DXDiag. I am also running plain WinXP, with Service pack 1 etc... EDIT2: Nevermind, I figured it out. There 2 updates for 839643, one is called WindowsXP-KB839643-x86-ENU.EXE and the other DirectX90-KB839643-x86-ENU.EXE . I was able to install the latter without any problem, but I am curious as to why does MS provide 2 hotfixes for the same problem? Can someone clarify which one of them should be in the integrated hotfix collection on the WinXP unattended CD?

Well, I got a couple of those new Hitachi 7k250 (160 Sata) last october and setup a raid0 striped. Works like a charm until today. A few hours ago, during HD-intensive operation Windows crashes, saying something about kernel - the blue SoD flashed so quickly, I did not have a chance to read it all. After that, computer reboots and fails to find one of the Raid0 drives. I tried to resetting BIOS, reconnecting all connectors, cleaning the internals, even shaking the drives (yes, that desperate) to no avail. The Intel Raid bios report one of the drives missing (says drive 1 is missing, drive 0 is OK), and fails to initialize the Raid0. I have no idea how to proceeed. Luckily, I did make a backup relatively recently, but I did lose some important stuff I was doing the last couple of weeks. To make story short, I would greatly appreciate any kind of ideas or suggestions on how to handle this. This is actually the first time an actively used HD dies on me, even though I owned PCs for the last 10 years, and had about a dozen of different HDs, so I have no idea about how to proceed from now. Thanks a lot guys!

All these are on the first post in this thread... gotta read it all