Well I don't need to install to many drivers for my system. A Raid driver, sound driver and video. The video driver is installed at this state without the .exe certainly. So I would need to install this later. But that should not be a problem hopefully.

It's important to call a cmd to set the variable. If I try to set it directly with startnet.cmd than it does not work.

It would be usefull to have a confirmation of that procedure from others. But it works basicly here.

Martin

Edited February 2, 200719 yr by FireGeier

It's important to call a cmd to set the variable. If I try to set it directly with startnet.cmd than it does not work.

Martin

Will test here in about an hour or 2 but glad I read that first.

It seems to work, thanks!

Edited February 3, 200719 yr by nDrew

haven't tried that yet as I'm havin fits with my sata/raid on new PC but i think I have a plan to cure that soon. I'd thought Vista would recognize the Satas out there.

FireGeier

where you create that and call it right before wpeinit in startnet.cmd but fails cause

I went ahead and added an extra line

Set > A:\Set.txt where I place my xml on a: right now and the variable DriversRoot is showing up in the .txt but when wpeinit starts it sets its own variables so definitely not working here. I do the Set again after it crashes

Hello maxXPsoft!

First of all, thanks a lot for your feedback!

If you have problems to set the DriversRoot variable using startnet.cmd, than leave the startnet.cmd untouched. So the only enty in startnet.cmd is (lile it is originaly):

wpeinit

Now change the SetDriversRoot.cmd like this:

FOR %%i IN (C D E F G H I J K L N M O P Q R S T U V W X Y Z) DO IF EXIST %%i:\DriversRoot.txt SET DriversRoot=%%i:\
X:\setup.exe

Now create a new file in %windir%\system32 called winpeshl.ini:

[LaunchApp]
AppPath=%Windir%\System32\SetDriversRoot.cmd

Now it should work! Had some feedbacks from tow German guys having the same problem like you. The steps above were working for them.

I don't know, if you have a WinPE-Disk which boots you to a cmd. Than you could simple test the steps above manually, before wasting ISOs.

So far I've not had the time to find out, why it's working for me from startnet.cmd and why it's not working for some others.

Regards,

Martin

Its no problem I burn to RW and use the floppy for the xml so i can test in short time

I have winpe.chm and seen this in there

When you exit the Command Prompt window or your custom shell application, Windows PE restarts.

but i'll check it out soon.

When you exit the Command Prompt window or your custom shell application, Windows PE restarts.

That is ture, if you leaving it without calling anything else. But if you call the Vista setup.exe wihtin this cmd as last command it will not restart - it will run the setup.

I've tested that many times doing it with adapted boot.wim of Vista-DVD. I never create PE using copype.cmd so far, cause you've the srt-package-problem than.

Regards,

Martin

someone mentioned reading the reg and getting this elusive path variable, ok

the only place and I do mean 1 place that the letter of my Dvd appears in the registry during X: is at

[HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices]
"\\DosDevices\\F:"=hex:5c,00,3f,00,3f,00,5c,00,49,00,44,00,45,00,23,00,43,00,\
  64,00,52,00,6f,00,6d,00,5f,00,4e,00,45,00,43,00,5f,00,44,00,56,00,44,00,2b,\
  00,2d,00,52,00,57,00,5f,00,4e,00,44,00,2d,00,33,00,36,00,35,00,30,00,41,00,\
  5f,00,5f,00,5f,00,5f,00,5f,00,5f,00,5f,00,5f,00,5f,00,5f,00,5f,00,5f,00,5f,\
  00,5f,00,5f,00,5f,00,5f,00,5f,00,5f,00,31,00,30,00,35,00,43,00,5f,00,5f,00,\
  5f,00,5f,00,23,00,34,00,26,00,33,00,38,00,33,00,36,00,64,00,36,00,35,00,34,\
  00,26,00,30,00,26,00,30,00,2e,00,32,00,2e,00,30,00,23,00,7b,00,35,00,33,00,\
  66,00,35,00,36,00,33,00,30,00,64,00,2d,00,62,00,36,00,62,00,66,00,2d,00,31,\
  00,31,00,64,00,30,00,2d,00,39,00,34,00,66,00,32,00,2d,00,30,00,30,00,61,00,\
  30,00,63,00,39,00,31,00,65,00,66,00,62,00,38,00,62,00,7d,00

With F: being my Dvd

Done tried it, done did \\DosDevices\\ and all variations of it

X is stupid, won't search on a *

I don't think, that it's set to the registry. That would not make sense IMO, cause the registry get lost after reboot.

I think they call these information with API functions. MS will bring out a tool - SCM (System Configuration Manager) - which will make it possible to take influence of setup procedure and integrating your own scripts. I think this will be very need.

Regards,

Martin

FireGeier, No luck yet

exactly how are they calling setup adfter running the cmd?

I've tried it with /noreboot and every way I can see and it reboots after running that cmd.

Dam MS, why no DVD variable or anything. Be too easy to include that, they set configsetroot and all

well really you think of it there was no CD variable in XP, had to do it ourselves right

Do you use an "Exit" command in SetDriversRoot.cmd?

Have you tried setting "Pause" command behind X:\Setup.exe command, like this:

FOR %%i IN (C D E F G H I J K L N M O P Q R S T U V W X Y Z) DO IF EXIST %%i:\DriversRoot.txt SET DriversRoot=%%i:\

X:\setup.exe

Pause

Regards,

Martin

I did use an exit, It don't even show on screen so be no good to do a pause. Not that will matter cause can Alt Tab to it maybe. I'll leave off the exit and see.

Exit was it

For a quick test I set to show disk config

PnPIBS: Building the list of drivers in the path F:\sources\pnpDrivers ...

PnPIBS: Found the directory 1.

PnPIBS: Building the list of drivers in the path F:\sources\pnpDrivers\1 ...

I copied the log and done a set

I'll have to run full Install now and see what happens.

BTW, Don't close that cmd window. You going for a reboot!!!

Hello maxX!

That's right! You dare not use "Exit" cause batch commands a running quickly and so the "Exit" is executed already before setup.exe is started properly. My mistake. I think I have not had explained that well enough the first time.

But glad to see that you're on the right way now!

Regards,

Martin