[FireGeier]

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

[maxXPsoft]

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

Quote

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

but i'll check it out soon.

[FireGeier]

Quote

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

[maxXPsoft]

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 *

[FireGeier]

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

[maxXPsoft]

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

[FireGeier]

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

[maxXPsoft]

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.

[maxXPsoft]

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!!!

[FireGeier]

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

[maxXPsoft]

well several Installs later it won't put the ctrl panel for my Vid driver into the display properties using this method but it does add it in the taskbar.
Now a new twist
I left the xml on root of dvd and didn't use %configsetroot% on anything only the <UseConfigurationSet>true and it copied down the whole DVD to Windows\configsetroot folder. ??

When you think you understand whats going on and make a minor change and MS throws curve balls at you.
Back to the drawing board

This post has been edited by maxXPsoft: 24 February 2007 - 08:13 AM

[Dobby]

Did you still have an entry for PnPCustomizations? Just a guess.

[Dobby]

Could someone enlighten me as to the official documentation for this so called configsetroot. I cannot find any info about it and if I try to create a distribution share the PnPCustomizations section ends up containing the path to the configset on my local machine. How is that supposed to work? Does it somehow magically replace that path with the configsetroot path when running PE?

[Dobby]

Well I'll be a *think of something bizzare/funny/ironic*!!

Tried the configuration set thing again and checked the resulting Autounattend.xml file and hey presto there's that %configsetroot% everyone has been banging on about. Shame Windows SIM copies the entire path instead of just the relevant part. Well I guess I won't need to do it again now I know what it should look like although I could swear I tried it before.

Just need to figure out how to sort the Wireless Lan now. Sorry to hear all the woes about this configsetroot but I think it's what I need as I want to have a base DVD image and put all the apps and drivers onto the usb drive. I'm sure I'll be back later with my own sob story when I find it's not working the way I want!

[maxXPsoft]

Using <UseConfigurationSet>true</UseConfigurationSet> under <component name="Microsoft-Windows-Setup"
and leaving the AutoUnattend.xml on root of drive will copy the whole dvd to what I said in Windows, sorta like the I386 of past.
Who wants that? Takes longer to install and everything.
+ side = Using that the OEMs get copied down.

BTW, If you place your AutoUnattend.xml on a USB stick it copies the whole Dir to Windows\Configsetroot.
Not sure about sub folders as when I had that on my floppy there were no Subs

Whats the alternative?
Everything you would place in OEMs just mountrw the image and copy it all over to correct dirs
Remove <UseConfigurationSet>true</UseConfigurationSet> setting and leave the xml on root and
NO Windows\Configsetroot folder

[urie]

maxXPsoft, on Feb 25 2007, 05:47 PM, said:

Using <UseConfigurationSet>true</UseConfigurationSet> under <component name="Microsoft-Windows-Setup"
and leaving the AutoUnattend.xml on root of drive will copy the whole dvd to what I said in Windows, sorta like the I386 of past.
Who wants that? Takes longer to install and everything.
+ side = Using that the OEMs get copied down.

BTW, If you place your AutoUnattend.xml on a USB stick it copies the whole Dir to Windows\Configsetroot.
Not sure about sub folders as when I had that on my floppy there were no Subs

Whats the alternative?
Everything you would place in OEMs just mountrw the image and copy it all over to correct dirs
Remove <UseConfigurationSet>true</UseConfigurationSet> setting and leave the xml on root and
NO Windows\Configsetroot folder

Hey Maxx, just got you message will talk tommorrow but does this mean your are adding $OEM$ to wim file or just folders couse i know we $OEM$ working before last october. P.S. MSFN is still playing up for me dont know whay to problems on other forums:((

[maxXPsoft]

I see someone still hungup on Configsetroot instead of trying to move forward.
To go where no man or woman has gone before, to discover new and exotic lands and meet exciting and new people and .......

NO Windows\Configsetroot folder
NO whole DVD copy

Drivers
FireGeier's method in this post with a little MaxXP twist of course
No file needed on root of Dvd, just a path and its all fine

[FireGeier]

Thanks, for confirmation maxXP!

You can use the same method for your applications setup. I call a SetAppsRoot.cmd during specialize pass, which will set an AppsRoot variable using setx -m. It will put the variable in the machine environment and it will stay there as long till you remove it.

So you can install drivers and applications from where ever you want during any further passes.

Note:
If you install drivers in these later passes you will be prompted if you do not use signed drivers.

So my recommendation is, install as many drivers as possible during PE pass - only possible for inf-Drivers.
Install exe-drivers during audit-mode - but take care that they are signed or you need to have a workaraound for the prompt.

Regards,
Martin

[maxXPsoft]

no file i mean i set the For cmd like this
DO IF EXIST %%i:\sources\pnpDrivers SET DriversRoot=%%i:
with my pnpDrivers folder with all sub folders in the sources folder and then all you need is
%DriversRoot%\sources\pnpDrivers
Yep only .inf in that pass but work's ok.

[FireGeier]

Quote

no file i mean i set the For cmd like this
DO IF EXIST %%i:\sources\pnpDrivers SET DriversRoot=%%i:

You're rigth maxXP, this is working as good and may be a bit "simpler".

Note:
I've found out a little problem that might come up using this method during PE pass. Some Friends told me, that they've had problems using this method. The "funny" thing was, that the Autounattend.xml was detecteted on the stick by Setup, but the DriversRoot Variable was not set before. So I've had the idea that this could be a timing problem and at least it was.

So what happend on their system?
It's very easy. The SetDriversRoot.cmd was finished already before PE Enviroment had seted up the USB-Stick.

Workaround:
If you should have the same problem on your system, all you need to do is: Loop the SetDriversRoot.cmd like this:

@ECHO OFF
SET DriversRoot=NULL

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

:StartSetup
ECHO DriversRoot=%DriversRoot%
X:\setup.exe

Regards,
Martin

This post has been edited by FireGeier: 26 March 2007 - 03:26 AM