DriverPacks.net Forum - RIS Install and method 2

Re: RIS Install and method 2

2009-03-19T21:43:46Z

OverFlow wrote:

Doh... One should not code when one is tired

Or drinking...but that's my vice...

Re: RIS Install and method 2

2009-03-19T21:28:46Z

Doh... One should not code when one is tired

Re: RIS Install and method 2

2009-03-19T16:18:09Z

Well, I also removed the move...'to'.

Re: RIS Install and method 2

2009-03-19T05:36:07Z

try it

i think "." has been an allowed Abbr. for "*.*" since at least Win 2k...

Re: RIS Install and method 2

2009-03-19T05:28:47Z

True, my code would have to scan the contents of the text file first. Not quick. But more universal.
I believe your syntax is wrong though. It should be this:

REM +==========================================================================+

If exist "%systemroot%\system32\setupold.exe" DEL /F "%systemroot%\system32\setupold.exe"
start /wait move /y "%SYSTEMDRIVE%\$win_nt$.~ls\$OEM$\$1\*" "%SYSTEMDRIVE%\"

REM +==========================================================================+

Re: RIS Install and method 2

2009-03-19T04:44:18Z

the simplest solution is to execute the single move that windows normaly would.

move %SYSTEMDRIVE%\$win_nt$.~ls\$OEM$\$1 to %SYSTEMDRIVE% and call it a day

a "move" should happen quickly enough it's not a "copy"
Then DriverPacks should continue normaly without further issues...

this would be accomplished by adding one line near the top of presetup

REM +==========================================================================+

If exist "%systemroot%\system32\setupold.exe" DEL /F "%systemroot%\system32\setupold.exe"
start /wait move /y "%SYSTEMDRIVE%\$win_nt$.~ls\$OEM$\$1\." to "%SYSTEMDRIVE%\"

REM +==========================================================================+

Re: RIS Install and method 2

2009-03-18T18:54:18Z

If it helps, here's the batch code I wrote to determine the source files installation directory for my oemscan addon. It should work for disc-based or RIS-based installs.
The below code will find the drive letter/path to the source and declare it as the string %dospath%.

:PATH
setLocal EnableDelayedExpansion

for /f "tokens=* delims= " %%a in (%systemroot%\system32\$WINNT$.INF) do (
echo %%a | find "dospath=" > nul
if not errorlevel 1 set str=%%a
)
for /f "tokens=2 delims==" %%a in ('echo !str!') do (
SET dospath=%%a
echo dospath=!dospath!
)

You could leave the OEM folder in your RIS image and just point presetup.cmd to %dospath%\OEM
Just a thought...

Re: RIS Install and method 2

2009-03-18T14:07:57Z

Aha i see didn't know that part, but whats the idea of removing the repair function when you can make the batch script do the move part for you and keep the repair function ?

Btw about the sound problem, added some commands to silently install live messenger and some other programs with GuiRunOnce, install of live messenger takes about 5 minutes on my slow test computer because it have to finish the other work with updates and driver installs before live messenger can be installed, and when its done the sound works fine, so that problem is kinda solved aswell.

EDIT : A tricky question, is Dpsfnshr hardcoded to load its dpsfnshr.ini file and the D folder from %SYSTEMDRIVE%
Tried to make presetup.cmd unpack into a seperate folder but got a error when starting the finisher saying it could not find the ini file, then i tried to move just the dpsfnshr.ini file into %SYSTEMDRIVE% but again no go, however this time it deleted the ini file after pressing ok to the error.

Re: RIS Install and method 2

2009-03-18T13:06:57Z

No...

if the unattended section is missing then the oem folder is not copied from %SYSTEMDRIVE%\$win_nt$.~ls\$OEM$\$1 to %SYSTEMDRIVE% (because this only happens for an unattended / OEM install) otherwise it is. and driverpacks will work as intended - AutoImage works. you need to copy it from $win_nt$.~ls because you altered teh winnt.sif so it is no longer an unattended install and must therefore manually force it to work, IE use the $win_nt$.~ls source instead of useing the final destination of $OEM$\$1 which is %SYSTEMDRIVE% in a normal unattended install.

so \$OEM$\$1\OEM will be moved to %SystemDrive%\OEM and work normaly if you are doing an OEM / unattended install

If you enable the repair feature you disable the $OEM$ folders one or the other - unless someone uses adapts your method.

Re: RIS Install and method 2

2009-03-18T06:38:40Z

This has nothing todo with the repair function, like i have said before you do not need oempreinstall with ris installs, it will automatic copy the intire content of your ris image dir (i386 OEM or what ever dirs you have inside it) into %SYSTEMDRIVE%\$win_nt$.~ls\ whereever oempreinstall is on or not.
This is because during most of the gui mode setup it doesn't have acces to the install source like it would if it was a cd install.

And no the autoimage tool only fixes one thing, when slipstreaming text mode storage drivers with DB_Base only the instalation will halt before its even started. Using autoimage will fix that.
Autoimage also renames the OEM folder to $OEM$/$1 but it does not edit the presetup.cmd batch to fit any of those changes, the presetup script is made to find 7z files on the install cd's OEM dir or on your %SYSTEMDRIVE% in case its a oempreinstall and unpack then into %SYSTEMDRIVE%, for ris installs you need to make it find 7z files inside %SYSTEMDRIVE%\$win_nt$.~ls\$OEM$\$1

Re: RIS Install and method 2

2009-03-18T02:49:24Z

Just so users know this is to be used if you want to enable the repair feature.

a normal RIS install works just fine out of the box with roguespears autoimage.

These files overcome the problems created by removing the Unattended section of the winnt.sif...

Re: RIS Install and method 2

2009-03-17T13:55:39Z

Tried installing it with all updates integrated on a much faster machine today, instead of my old slow test computers, and it worked like a charm, no massive work after it was installed, and sound was on from the first boot.
It might be because the old ones i tested it on cant handle all those updates within the instalation and has to do some of them on the first boot.

Ive made a fix for ris and ris like installs so the unpacking (presetup) works (requires the driverpacks 7z files, and bin folder is inside a folder called DriverPacks in your ris image root) It will also make KTD an option with 2 links on the desktop after installing. 1 for removing the unpacked files for ktd, and one for instaling kts, and remove the instalation dirs when done.

Extract this file into your i386 folder overwriting the old one.
http://www.fileqube.com/file/Kobxtm181301
Extract these files into your /OEM/bin dir, the bin subdir DP_BASE creates inside the oem folder.
http://www.fileqube.com/file/BLZdqiA181303
Add this to your sif file instead of DPfnshr.exe
[GUIRunOnce]
command83="%SystemDrive%\fixdps.cmd"

EDIT: Just tried my theory out by setting it to install a very big package (.NET Framework 3.0 runtimes) during the windows instalation with the svcpack function, and that resulted in the same sound error on my fast pc.

Re: RIS Install and method 2

2009-03-16T16:17:13Z

Thanks for keeping us in the loop!

Re: RIS Install and method 2

2009-03-16T08:10:07Z

Found the reason why it happend, it must have something todo with either WMP11 IE7 or some of the other extra updates i had slipstreamed in.
When i make the full version with all updates from WUD that nlite can handle the machine is doing lots of work on the first boot after install, and if i wait 10 minutes that work is done and the sound comes on.
Tried to make a version today with only the ones from the WUD Critical Updates folder. Minus IE7-WindowsXP-* and msxml4-*
It doesn't do all that work on the first boot, and the sound works on first boot, i have no idea what update pack it is yet though, but must be either ie7 or wmp11

Re: RIS Install and method 2

2009-03-15T06:40:41Z

Hm well i only get that error when im using a ris image with hotfixes slipstreamed in by nlite and drivers by DP with Autoimage (in that order)
When i take a clean ris image directly from a cd and then apply DP only it works fine, sound is on when its rebooted after gui mode setup.
And there that pci modem aint installed either. It should also be noted that the error is reproduceable on ALL the computers i have tested it on, both laptops and stationary ones, with and without onboard/pci modem.
I will try it though, but i dont have any high hopes for it hehe.