[a06lp]

are you sure the "resetting devicepath" in my post doesn't work?
I don't know how to check this, which key is it?

also, what is the effect of not resseting devicepath?
because my install seemed to go quite fine... (other probs, but unrelated to this)

This post has been edited by a06lp: 09 January 2005 - 12:50 PM

[evilvoice]

positive it doesnt reset the devicepath...ill have to find the key...and pyron posted that it is a good idea to set it back to the default value AFTER windows is installed. Altho since you dont run setup.exe in your presetup.cmd, resetting the devicepath (and it actually working) would result in windows only looking at the inf folder, so in your case, its prolly good that it doesnt work like its supposed to.

EDIT: this is the key

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion]
"DevicePath"=

[Bâshrat the Sneaky]

@a06lp: thank you! I've read the entire topic just now, and I was going to test ile5's fix myself. Thanks to you I won't have to do that. (again a confirmation that it's working...) So I will use ile5's fix in the next release of my DriverPacks.

[a06lp]

@evilvoice:

Quote

if you run setdevicepatch %systemroot%\inf, it just adds %systemroot%\inf to the end of what is already in the reg key (which is %CDDRIVE%\OEM\drivers), if you dont believe me, go look at the key

I'm going to have to disagree. I did a full clean install, and I just looked at my registry, and my
"DevicePath" = %Systemroot%\Inf
Did you ACTUALLY test it? Because I did, and that's what shows... so it DOES work.

@Bâshrat the Sneaky:
You're very welcome. Though I should thank YOU for all your help!
I figured I'd read through it all, ask my questions, and then post a WORKING SOLUTION.
Ideally, we could update that first post and replace it with my post, so no one else gets mislead.

[edit]
PS - I am doing ANOTHER clean install sometime in the next few days.
I'm sure it still works fine, but I will post more results again.

[evilvoice]

I did an install in vmware, whats really funny is that %systemroot%\inf isnt in my devicepath UNTIL I run setdevicepath %systemroot%\inf...and when I go look at the key, it has a whole huge string and voila, at the end is %systemroot%\inf...whats even funnier is I delete the key before running setdevicepath using reg delete.

[a06lp]

i dont know, maybe its a vmware problem?
it works for me, and i'll do another test sometime in the next few days, and ill post results.

[evilvoice]

ok, i see now, you actually have setdevicepath reset the key DURING windows setup...I dont have mine running until AFTER windows setup, like when the computer is shutting down...hmm, Ill have to change my presetup.cmd to reflect your change and then I guess itll be fixed...windows may have a problem resetting it when its trying to restart. I am actually going to use your method for another thing - reseting driverp policy back to what windows wants it as. I was having the hardest time getting that to work, but MAYBE if I run it when runonceex is executed in windows setup, it will work...and yes, runonceex DOES get executed during windows setup..I dunno the exact time but its after installing drivers.

[a06lp]

well, i was just saying my method works.

[mediapla]

Hallo, maybe im a newbie, but i have found and tested some interesting things. So i install my "drivers from CD" without (!!!) "patched" XP files and it runs very well. The way is the detachedprogram line in winnt.sif. There i start a cmd file (is copied on textmode setup to HDD) that runs on t39, search for the CD/DVD drive and runs the there the needed 7zip.exe File.(I have a desktop and a notebook archiv). That file is expanded to HDD and MUST have the same path like OEMPNPDriverspath in winnt.sif. You dont see any DOS Window - thanks to cmdow. I have to support many configurations(PC-Tech), so my driverpack is 253MB(packed) and it expands a few minutes. But it runs very well, all PnP Drivers are installed (the inf Versions), testet from Celeron 1300 - 3,4GHz Pentium machines also on various HDs (40-250GB). Id never thought, that it is so easy to install. Because i have a multiboot DVD with more than 30 XP versions (preactivated manufacturer versions, Home/Pro/MCE) - i need the space . In earlier times i used the method with a own $OEM$ and other subdirs for each version, but that cost too much space...so i tried a other way and it runs very fine.

[a06lp]

I just completed my second real-world test of my method (described here), and, once again, it worked perfectly!

Also, in this test I tried new types of folder names ("Dell TrueMobile" as opposed to my old "DellTM", and "Uniden WLAN" as opposed to my old "WLAN"). Spaces are allowed, and the method still works perfectly!

I updated my guide to reflect this.

PS - evilvoice: Just as in my first test, my "DevicePath" = %Systemroot%\Inf

[evilvoice]

yes yes yes I told ya I misread the thing...didnt notice you run setdevicepath to reset itself during runonceex...

[beaumar]

Hello,

Just posting this to reiterate a point that evilvoice made and that ppl may miss ( I know I almost did!):

A06LP HAS POSTED A MODIFIED PRESETUP.CMD! If you're using Method 2 with Bashrat's compressed driver packs, be SURE to add the following lines to A06lp's presetup.cmd:

REM +===============================================+
REM | If you are using compressed drivers unpack them here: |
REM |-------------------------------------------------------|
%SystemDrive%
cd \
%CDDRIVE%\OEM\bin\7za.exe x -y -aoa %CDDRIVE%\OEM\DriverPack_*.7z -o"%SYSTEMDRIVE%"

Also, as long as I'm at it, I may as well point out that if you're using Method 2 you'll need to REM out the

%CDDRIVE%\OEM\bin\SetDevicePath.exe %CDDRIVE%\OEM\drivers

line and remove the "REM" on this line:

%CDDRIVE%\OEM\bin\SetDevicePath.exe %SystemDrive%\drivers

I was *this* close to copying the presetup.cmd to my I386 dir without actually going thru it when I noticed the file size was about half the original one. I shudder to think about all the time I would have spent trying to troubleshoot this if I hadn't!

Hope I head off some potential probs for others...
As always, thx to all who put in their $.02!

[a06lp]

Ok, updated my zip to include (commented out) sections in presetup.cmd so that it can be further modified for compressed drivers, and a few other things. Same post.

The guide still follows how to install uncompressed drivers from CD, and the steps are still the same, so no one else has to worry.

This update is only for those who want to modify the files a little (and understand how to do so).
Everyone else just follow steps 1-7, and it will work.

[evilvoice]

a few updates about your script a06lp...it seems that your runonceex keys are getting set BEFORE devices are installed...I checked this while drivers were supposedly being installed by going to the registry key and it only had %systemroot%\inf in the key...no other values...I am currently looking at how to get it to take the runonceex keys and also start setup correctly, but yea, if you check the registry key, you will see what Im talking about...another note, it seems watchdriversingingpolicy.exe is never started, but that could be on my end since I had it killing itself in runonceex (which was executing before installing drivers)...but install windows one more time, and right when setup starts, hit Shift+F10 and then type taskmgr to see if watchdriversigningpolicy.exe is still running, and also type regedit and goto HKLM\Software\Microsoft\Windows\CurrentVersion and check if devicepath=something other than %systemroot%\inf

PS my script is almost exactly like yours now.

PPS Im not trying to be difficult about this, Im just hoping to come to a complete solution I am also not trying to discourage you, you found out what was giving me errors before for which I appreciate.

[Afterdawn]

Never mind

This post has been edited by Afterdawn: 17 January 2005 - 05:14 PM

[a06lp]

@evilvoice:
Before I even try what you are saying:
Have you tried to install winxp using this method in a real-world environment? or is this all VMWare speculation?

maybe some of what I posted should happen isnt happening, but at the end of the day my drivers installed.
therefore i must ask you to try it out on a real test system (or your own, with another winxp copy handy incase it doesnt work) and then post your results.

[larciel]

need help with setup

presetup.cmd file is missing

continue with normal setup?

'click yes' and it displays setuporg.exe file is missing

ran with vmware

presetup.cmd and setup.ex_ and setuporg.exe file is in i386 folder

[a06lp]

@larciel:
This sounds a LOT like new_user's post here.
Look at ile5's reply here.
Did you follow ALL the steps? 1-7?
Epecially editing "Txtsetup.sif" in i386 folder (Step 7)??

Also, you do realize that VMWare won't install your drivers, (since it doesn't really use your machine's hardware) right?

[larciel]

thanks for pointing that out

"

.
For test try to put this three files in the same directory:
- setup.exe,presetup.cmd,SetupORG.exe
("SetupORG.exe" is renamed original windows "setup.exe")
Edit presetup.cmd and leave only this:

presetup.cmd:

CODE  

if exist setup.exe ren setup.exe setupold.exe
if exist setupORG.exe ren setupORG.exe setup.exe
exit
 


Execute "setup.exe".

If "windows Xp Setup" window is pop up with "Please go to Control Panel..."
everything is fine because setup is started without parameter.

."

i emulated that. and setup only renames 'setup.exe to setupold.exe' and setuporg.exe to setup.exe and nothing happens.

txtsetup.sif has all neccessary info.

any idea ? thanks in adv

[a06lp]

have you made any other changes to your CD that may be impacting this?
do you use nlite?
i can confirm that it all works fine on my end, so there must be something different about your U-CD.