supersheep

Actually, just found it. The attached zip has the files you need. 1) Copy contents of 2003 CD to your machine. 2) Unzip the "newtree.zip" from here, and make sure you extract with subfolders turned on. 3) You'll see that newtree has an $OEM folder, and a i386 folder. Move these folders into the folder that contains the Windows 2003 CD - $OEM won't exist, but i386 will. 4) Open nLite, target the Windows 2003 folder, and just create a bootable ISO. 5) Burn it. 6) Boot your Powervault from it using an external CD-ROM drive - you don't need to press F6 or anything, the gd31244.sys will load automagically. This definitely works on a Powervault 745N, with an Intel GD31244 SATA controller. Good luck! newtree.zip

No problem - I'll need to dig out the image I used, which is at work, but I'll get back to you with the modified files you need. Our Powervault is now running vanilla Windows 2003, installed last week, so I can testify that it does work (eventually)!

Since this thread is Google indexed, I'll provide the solution to this one.. The GD31244 drivers have a broken txtsetup.oem. For some reason this breaks the nLite integration - and the driver never gets loaded. What I did: 1) Rewrote the txtsetup.oem with the write hardware ID, included the catalog file, etc. according to these MSDN docs - http://msdn.microsoft.com/en-us/library/ms794587.aspx. I can upload it if required. 2) Integrated this according to the OEM preinstall method listed in the article I linked to previously. I have a better link somewhere to the article that helped me through it - I'll edit this post to include it. 3) Used nLite to generate a bootable CD *only* from my modified install. The driver gets loaded in textmode setup and I can see all the volumes. (Incidentally, this is for an install on a Powervault 745N, using a USB CD-ROM drive, which has an Intel GD31244 SATA controller - index this, Google!)

I've found this about integrating textmode drivers using Unattended, OEM style:- http://www.windowsnetworking.com/articles_...nded-Setup.html Before I start on the massive process of doing this, do you know if this kind of thing is successful? Thanks for your help, btw! I noticed this thread has been indexed by google as the only sensible result for nLite and this particular controller.

Weirdly enough, adding one of those INFs, then attempting to add the other, results in nLite saying that the driver has already been included. The "press S" bit I'm referring to occurs well after the F6 prompt - just prior to selecting a HD to install to. If I don't select a mass storage driver and try to install, I get an error about Windows not having any drives to install to. I'm absolutely stumped. I've poked around in txtsetup.sif, and I can see the drivers in there, but I have absolutely no idea what the lines referring to them mean. The gd31244.sys line appears twice, though - once with a bunch of commas and the number 1984, the other line has a lot more numbers in it, one of them being 4_ (reference to disk 4?) Cheers for the suggestions, but I don't seem to be getting anywhere at all - running nLite under 2k3 makes no difference, nor can I see why it should. Using "multiple driver folder" only results in one driver being available for integration, as above. Is anyone able to interpret txtsetup.sif files?

Hi all, I've been trying to integrate some drivers for a SATA chipset - Intel GD32144 - that our server uses. I'm installing Server 2003 SP2 (Volume License version). I integrated the drivers okay (textmode), but Windows setup doesn't automatically detect the chipset. It asks me to press S to install additional mass storage devices - if I press S I can see "Intel SATA GD32144 Miniport" in the list, but when I select it, it asks me to insert Windows Server 2003 Setup DISK #4! I don't have a disk 4! Leaving the disk in doesn't work. What the hell is going on here? Why does it want Disk 4? Attached is the Last Session.ini for the integration, and a zip of the drivers. LAST_SESSION.INI Drvr_1150.zip