Gosh method and txtsetup.sif: recovery console installation impossible

[cyberyeye]

Hi

I used gosh method (winnt32 /noreboot) form making my boot folder, I put txtsetup.sif & winnt.sif into their respective boot folder; and deleted txtsetup.sif & winnt.sif from "i386".

Everything is working fine excepting Unattended installation of Recovery console (in runonceex stage).

Probleme is IF txtsetup.sif is NOT present into "i386" -> recovery console install don't find txtsetup.sif and can't install it, error msg (popup) appear and I can indicate path of txtsetup.sif (boot folder/txtsetup.sif).

I wonder if anybody has a solution for this ?

My dir structure: 3 boot folder pointing to the same I386 dir; I use different txtsetup.sif and winnt.sif in each boot folder.

/

/Setup/XPUA/$OEM$/$1/D --->(Driverspack by bashrat)

/Setup/XPUA/$OEM$/$1/install/runonceex.cmd

/Setup/XPUA/i386 ---> (no winnt.sif and txtsetup.sif inside!)

/XPCL -> boot files gosh method (redirect to /Setup/XPUA)

/XPNL/txtsetup.sif (original from i386) install NOT unattended

/XPCL/SYSTEM32

/XPNL -> boot files gosh method (redirect to /Setup/XPUA)

/XPNL/txtsetup.sif (same ver as XPCL txtsetup.sif) + winnt.sif (no btpack/oempnp, etc...)

/XPNL/SYSTEM32

/XPUA -> boot files gosh method (redirect to /Setup/XPUA)

/XPNL/txtsetup.sif (driverpacked) + and winnt.sif fully modified for driverspack etc...

/XPUA/SYSTEM32

So I386 doesn't contains any txtsetup.sif or winnt.sif, these files are on their respective boot folder. But when i call these cmdcons with cmdline in my Runonceex:

%cdrom%\Setup\XPUA\i386\winnt32 /cmdcons /unattend

Setup don't find txtsetup.sif (don't remember the exact msg but "don't find txtsetup.sif" blabla) I can "Browse" for indicate the path of txtsetup.sif (pointing to boot folder/txtsetup.sif) so install resume and finish...

IF i put txtsetup.sif into /Setup/XPUA/i386, no error msg appear during (runonceex) installation of recovery cons. RC is installed well unattended. But "my" txtsetup.sif had differents content (XPUA has driverpack; XPCL and XPNL has the original txtsetup.sif from XP) so i'd really like to use "external" txtsetup.sif...

So my real question is... Is there any method or trick to bypass this problem ?

Edited December 5, 2005 by cyberyeye

[Pantner]

ok,i admint, i don't know much about these multi-boot disks and stuff...

maybe if you change the txtsetup.sif to be something like txt1.sif txt2.sif and txt3.sif, for each respecting Windows copies

and then go into the setupldr.bin file using a hex editor and change all the txtsetup.sif to the corrosponding new files...

just an idea, havn't put it to work yet, but i am semi interested to see if it works as i may need to the same thing...

and, have a look through your boot directory, there may be other files that need hexediting

[cyberyeye]

Hum... I admit I don' try what you mean..., I mean hexedit "somefiles in bootfolder" for changing path to txtsetup.sif, of course I used the hexedit method for changing path in setupldr.bin and modifiying Textsetup.sif (SetupSourcePath).

But the problem is not to install windows (in my case), install went fine, no pb ! Excepting when installing recovery console with "winnt32 /cmdcons /unattended" without putting txtsetup.sif into windows\system32, bring an error msg blabla don't find txtsetup.sif....

I mean "winnt32" is winnt32.exe located into "systemdrive" (let's say generally C drive) \windows\system32\winnt32.exe"

or in: DVD\I386 path\winnt32.exe

So I don't think boot folder is used by commandline: winnt32 /cmdcons /unattended; because winnt32 is not present in boot folder but in windows\system32 or dvd\I386 folder.

I think and hope there's a solution like adding a switch to the commandline something like this:

winnt32 /cmdcons /unattended /L:%path%\txtsetup.sif

Unfortunatly I've never see anything like this (i've search a lot on google, msdn forum... i've found nothing), maybe there's an undocumented "winnt32 switch" but I never find it.

Maybe there's another "trick" to do ? But I never find it, that's why I post here... because here there are many really good poweruser of multiboot technics ^^

Any other idea or trick around there ?

Edited December 8, 2005 by cyberyeye