RyanVM

I wish there was a way to archive the files being used in OEMPnPDriversPath. I've got a section of monitor drivers that's almost 1100 files (yet only 3.5MB). I haven't tried it yet, but I have this sinking feeling that copying all those files to the hard drive is going to take a year.

I think you can only launch one command via cmdlines.txt, though. In other word, call a batch file which calls the other jobs.

Forgive me if this is a dumb question, but have you tried this in your winnt.sif file? [unattended]DriverSigningPolicy=IgnoreIt doesn't solve loosing the digital signatures, but it would at least tell Windows setup to ignore them . Of course, I have no idea how sysprep works, so I don't know if that works or not. Forgive me if I'm wrong .

Sadly I agree that trial and error probably is the best bet

I don't know about that . I just try to make life easier for the people who've made my life easier already .

Your 875P chipset has native SATA RAID support built into it. You should be able to enable that function in your BIOS. Myself and one other person have both tested the driver pack with the 875P's RAID controller successfully (I'm typing this message on that very system). I still don't understand why you're creating a RAID array for three different drives. There will be very little if any performance gain (maybe even a performance loss!), since the array will be limited in size to the smallest drive and in speed to the slowest drive. It seems like a TOTAL waste to me. If I were you, I'd put your SATA drive on the Intel 875P SATA controller (not in a RAID array) and the other two IDE drives on other IDE channels.

Try using the ICH5R SATA controller and see what happens. Support for the Promise 378 controller was a bit of a hack job and may not work quite correctly.

on the root drive (IE, C:\Drivers)

OK guys, I'm not sure what happened, but it works now. Somehow, not defining ANY imagepath did it...

That looks like a good thing to try.

Yet another new error message! C:\Documents and Settings\Administrator>net start winrtSystem error 123 has occurred. The filename, directory name, or volume label syntax is incorrect.I don't think it likes me .

Hey, that OEMPnPDriversPath string looks familiar! And if it's not rebooting, I'd say it's VERY likely that it's never getting to the driver deletion part of the batch file either (BTW, why do you have it trying to delete that folder twice in a row?). I still think you're best off putting a pause before and after each step to see where it's dying. EDIT: Are you sure that that batch file is even executing at all?

Well, that gave me a new error message C:\Documents and Settings\Administrator>net start WinRTSystem error 3 has occurred. The system cannot find the path specified.

Yes, the first code block was a direct copy/paste from the event viewer. It's a REG_EXPAND_SZ value, and double \\'s didn't seem to change anything. This is what I get if I try to start the service via command prompt: C:\Documents and Settings\Administrator>net start WinRTSystem error 2 has occurred. The system cannot find the file specified.

Are you sure it's getting that far and the batch file isn't quitting before it gets to that point? Try putting a series of pauses in there so you can verify its progress. I use this command and it's always worked fine, so I don't know why else yours wouldn't be working. rd /s/q %systemdrive%\Drivers

Basically, I've got a batch file which patches txtsetup.sif and dosnet.inf to add support for extra RAID controllers. Right now, I'm adding the entries by having the batch file pull values from a separate text file and I want to put those values in the batch file instead to effectively remove the middle man. I'm pretty sure spaces at the end of the line don't matter in txtsetup.sif (since there's a crap ton of lines with spaces at the end by default), but I'm not sure about dosnet.inf.

Worked like a charm. Most interesting . I wonder why the second example worked without the comma, though (there was still a number before the redirect). EDIT: And having a space at the end of each line shouldn't make a difference in either dosnet.inf or txtsetup.sif, right?

Also note that if we do a batch like this, the same problem occurs: echo hi>>blah.txtecho 3ware78k = 3wdrv100.sys,4>>blah.txtecho hi>>blah.txtHowever, if the comma is removed from line 2, it works fine.

If I do: echo hi>>blah.txtecho 3waregsm.sys = 1,,,,,,4_,4,1,,,1,4>>blah.txtecho hi>>blah.txtAll you end up with is a blah.txt that looks like: hihiI've narrowed it down to the commas causing the problems.

I've noticed while working on a batch file which writes to a text file with the echo command that commas in a line seem to throw a wrench in the process (ends up writing an empty line). The weird thing is that if you run the same command without writing to a file, commas don't bother the echo command at all. Is there some kind of flag that needs to go in front of the comma so it will be written to a file?

Is it OK to have multiple sections of the same name in an INF file such as dosnet.inf?

And at that point, you're better off just using the MS-supplied tools for creating a winnt.sif file

Does anybody here have experience registering a service on WinXP? At my workplace, we have some hardware that's controlled by proprietary controller board. It uses a driver file WinRT.sys which needs to be loaded as a service when Windows loads. Here's where things get complicated. I've got an INI file that came with the driver (along with the exe regini for loading what's in it into the registry). When I run the program to load the registry entries, all appears OK. I copied the WinRT.sys file into system32\drivers (which is the path referenced by the ImagePath key). The service is registered, but whenever Windows tries to start the service, I get this error: The WinRT service failed to start due to the following error: The system cannot find the file specified.The sad part is that this exact method worked in the past just fine. For reference, here are the entries being imported into the registry: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinRT]"Type"=dword:00000001"Start"=dword:00000002"ErrorControl"=dword:00000001"Group"="Extended Base""ImagePath"=hex(2):73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,64,00,\ 72,00,69,00,76,00,65,00,72,00,73,00,5c,00,57,00,69,00,6e,00,52,00,54,00,2e,\ 00,73,00,79,00,73,00,00,00"Description"="Nanomover Stage Control""DisplayName"="WinRT" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinRT\WinRTdev0][HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinRT\WinRTdev0\Parameters][HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinRT\WinRTdev0\Parameters\Section0]"IoPortAddress"=dword:00000300"IoPortCount"=dword:0000001fThe image path there is an expanded string with the value "system32\drivers\WinRT.sys" (which is exactly where that file is). The sad thing is that I'm looking at other entries for system drivers and they all look the exact same Anybody have an idea?

What controller is your boot drive hooked up to?

does this line, "SuperHidden"=dword:00000000 should be '0' or '1'? It's correct how he had it. AND OMG, IT WORKS!