Jump to content

Recommended Posts

Posted

Im reading a lot in this forum about installation of compressed drivers. So i burnd my multiboot DVD with 1. DetachedProgram="%SYSTEMDRIVE%\d.exe" Arguments="-x -y -o%systemdrive%" - a 7zip selfextracting file, which extracts the compressed drivers to C:\D..... I thougt XP install (after the extraction is done)

-T39- my hardware,but it doesnt. The PnPDriverPath is in winnt.sif. Then i tried a other way - DetachedProgram=cmd.exe

Arguments="/C START %systemdrive%\detached.cmd"

-the cmd runs fine, 7zip file runs fine, but hardware dedection doesnt run. It only install the ms-drivers(but DriverSigningPolicy=Ignore). My 7zip file is very large, because i have much configurations to install. Can it be, that the extraction time is to long, and hardwarededection starts before extraction is fully done ?

Here are the cmd script, it works fine at t39

@echo off

%systemdrive%\cmdow @ /hid

FOR %%d 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 %%d\fmm4\$OEM$\$1\detached.cmd SET CDROM=%%d

start /wait %CDROM%d.exe -x -y -o%systemdrive%

EXIT

The easiest way for me (on the boot dvd are now 25 XP versions of varios PC manufacturers) was to have 1 compressed file (d.exe) in the root, that will be unpacked through T39 and after that PNP dedection/install runs. So i must have only 1 file for all versions.

Is there a other way to scan for hardware through the cmdlines.txt at T12/13, before the last boot ?

I read something about Setdevicepath and other progs, but i dont now how they work. Sorry for my bad english, hope you understand...


Posted (edited)
Im reading a lot in this forum about installation of compressed drivers. So i burnd my multiboot DVD with 1. DetachedProgram="%SYSTEMDRIVE%\d.exe" Arguments="-x -y -o%systemdrive%" - a 7zip selfextracting file, which extracts the compressed drivers to C:\D..... I thougt XP install (after the extraction is done)

-T39- my hardware,but it doesnt. The PnPDriverPath is in winnt.sif. Then i tried a other way - DetachedProgram=cmd.exe

              Arguments="/C START %systemdrive%\detached.cmd"

-the cmd runs fine, 7zip file runs fine, but hardware dedection doesnt run. It only install the ms-drivers(but DriverSigningPolicy=Ignore). My 7zip file is very large, because i have much configurations to install. Can it be, that the extraction time is to long, and hardwarededection starts before extraction is fully done ?

Here are the cmd script, it works fine at t39

@echo off

%systemdrive%\cmdow @ /hid

FOR %%d 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 %%d\fmm4\$OEM$\$1\detached.cmd SET CDROM=%%d

start /wait %CDROM%d.exe -x -y -o%systemdrive%

EXIT

The easiest way for me (on the boot dvd are now 25 XP versions of varios PC manufacturers) was to have 1 compressed file (d.exe) in the root, that will be unpacked through T39 and after that PNP dedection/install runs. So i must have only 1 file for all versions.

Is there a other way to scan for hardware through the cmdlines.txt at T12/13, before the last boot ?

I read something about  Setdevicepath and other progs, but i dont now how they work. Sorry for my bad english, hope you understand...

I'd refer you to Pyron's method. In short: it starts a fake setup, decompresses drivers, installs them, and starts the real setup! Please take a look in the Sticky at the top.

EDIT: here's the link ;)

Edited by Bâshrat the Sneaky
Posted

I have found a easy way ! In detachedprogram i run a cmd script, that search for my Install DVD/CD - than it calls a 7zip archiv from CD and extract it at T39 to the PnPDriverPath (in winnt.sif) to disk. Runs fine, all drivers are installed.....MUST NOT PATCH XP files !!!

Posted

You're not the one to invent this method. I've come up with things like that months ago, and I was not the first one either... There are soooo many methods you can combine, you can't call every variant a method... :P

But as you said, the disadvantage of this method is that if you have too many driver files to be extracted, it will take too long and not all required drivers may be installed...

That's why I linked to Pyron's method, he fixed that! You can read more about it in the link I posted 2 posts above.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...