Pyron

It should be normal and it means that Windows sees that directory during installation, ie the DevicePath variable is correctly set. I just searched around for it a bit and found one in every singe directory beneath my drivers path, never noticed before however. But then again I don't know why your drivers are not installed. I have similar problems in vmware, in particular with the mouse driver. On a real world system all neccessary drivers get installed, so I don't care too much. -- Pyron

@serialzs: I don't know anything specific, but you can test by yourself: As soon as the GUI-mode installation starts, press shift F10 and enter taskmgr. It will not work and give you an error message. Wait for a few seconds and try again, it will work eventually. So the environment is not fully operational at that point, but I cannot say in which way exactly. BTW, I noticed you are using AutoIt v3, did you try v2? Because I am using v2, not a compiled script, but nevertheless v2 and it works in presetup.cmd. -- Pyron

@Bâshrat the Sneaky You are right, but I modified my method for compressed drivers since, but didn't write about it here, so maybe you see the irony... But it's good to see that my SetDevicePath.exe has its uses after all -- Pyron

I didn't realize that this was such a big problem... I am doing it this way for a long time now (well, with my own setup.exe), since I came to the conclusion that uncompressed drivers take too much space on my CD. -- Pyron

@swgreed: No, nothing is hardcoded in SetDevicePath.exe. It just takes a directory as first parameter, scans its structure and adds all found directories to the DevicePath regkey. So you don't have to have a specific directory layout. -- Pyron

As far as I know, you can have only one OemPnPDriversPath line in your winnt.sif, sorry. -- Pyron

I think your system is missing the HighMAT-CD-Wizard, downloadable as an optional package from Windows Update. Try installing that again. Microsoft Knowledge Base -- Pyron

Great! -- Pyron

Ah, typo... Try this: for %%i in (*.dll;*.cpl;*.exe) do makecab "%%i" pause -- Pyron

Step by step: Create an empty textfile in the directory with the cpls. Name it "createcabs.cmd". Edit it and put this into it: for "%%i" in (*.dll;*.cpl) do makecab "%%i" pause Save it. Double click it. Should work as expected. -- Pyron

How about this: for "%i" in (*.dll;*.cpl) do makecab "%i" Double the % if you are doing this from a batch file: for "%%i" in (*.dll;*.cpl) do makecab "%%i" -- Pyron

Doom3.exe gives this error when started from outside of its game dir, check your shortcut, it could be faulty. EDIT: Nevermind, just noticed on your screenshot that the pk4 files are found. -- Pyron

I had this problem once or twice. Happened to me when I upgraded a NT4 workstation. Search your registry for UpperFilters/LowerFilters in the entries for your drives and backup/delete them. That *should* help. -- Pyron

Obvious question: Is it valid? -- Pyron

Actually it is quite easy, add this to the "!custom" plugin (custom.inf): [SetValue] ; Set the boot message "txtsetup.sif", "SetupData", "loaderprompt", """Starting zabouthPE...""" -- Pyron

Sorry, but SetServicePath.exe was created under the assumption that there is a registry available at that early time. Look here, if in doubt. My whole "drivers from CD" method relies on that. -- Pyron

I hexedited dxsetup.exe at offset 0x359B and changed 0x74 to 0xEB. Then the /OPK switched worked again. Note that I have done it with the german version, but the old hacks worked for 9.0b, so you may try this. EDIT: I took the dxsetup.exe from the 9.0c redistributable -- Pyron

I assume you already created a plugin directory for your install.bat, so all you need to add to the .inf is this: [SetupReg.AddReg] 0x1, "Setup", "CmdLine", "\Programs\example\install.bat" This is how nu2menu gets started normally. I did not test it with a batchfile yet, so you may need to use cmd.exe like this: [SetupReg.AddReg] 0x1, "Setup", "CmdLine", "cmd.exe /s \Programs\example\install.bat" If in doubt, copy the original nu2menu.inf over to your new directory and change it accordingly, it is small and pretty self explanatory. NOTE: You have to comment out the last line in the nu2menu.inf, or it will override your plugin: [SetupReg.AddReg] ; Install nu2menu.exe as shell ;0x1, "Setup", "CmdLine", "\Programs\Nu2Menu\nu2menu.exe" -- Pyron

Well, the new window with the Camedia.exe-title pops up because I screw up.... You have to omit the "/WAIT" of course. Sorry, my mistake... -- Pyron

I think you will need to run it via 'start': start /WAIT camedia.exe In your example the batchfile simply waits for camedia.exe to terminate. -- Pyron