[RyanVM]

WinRAR SFX Windows GUI module extracting at the T39 mark prior to device detection running as the DetachedProgram in winnt.sif.

Attached File(s)

•  virtualpc.PNG (75.09K)
  Number of downloads: 519

[edmoncu]

oh i see... i stand myself corrected then.

[Bâshrat the Sneaky]

RyanVM, on May 21 2004, 06:39 PM, said:

WinRAR SFX Windows GUI module extracting at the T39 mark prior to device detection running as the DetachedProgram in winnt.sif.

And you didn't use any switches??? I can't get it to work with the normal GUI :'(

[edmoncu]

same here... that is when i use the detachedprogram method (as well as via presetup.cmd).

anyway, i tried complimenting the execution of the sfx-rar archive with /S on the arguments.

[GuiUnattended]
    AdminPassword=*
    EncryptedAdminPassword=NO
    OEMSkipRegional=1
    TimeZone=215
    OemSkipWelcome=1
    DetachedProgram="%systemdrive%\others\drivers.exe"
    Arguments="/s"

[Bâshrat the Sneaky]

edmoncu, on May 22 2004, 02:06 PM, said:

same here... that is when i use the detachedprogram method (as well as via presetup.cmd).

anyway, i tried complimenting the execution of the sfx-rar archive with /S on the arguments.

[GuiUnattended]
    AdminPassword=*
    EncryptedAdminPassword=NO
    OEMSkipRegional=1
    TimeZone=215
    OemSkipWelcome=1
    DetachedProgram="%systemdrive%\others\drivers.exe"
    Arguments="/s"

I tried it too like that, with normal GUI.

What module did you use and did it work with the /S switch?

[edmoncu]

i tried the Default.sfx module. although when i tried running it using the WinCon.sfx module, i got no problem decompressing it at any situation... though i have lesser control over it than Default.sfx.

[RyanVM]

RyanVM, on May 7 2004, 09:25 AM, said:

For those using WinRAR to achieve this, this is my method for creating an SFX archive that worked.  RAR up the subdirectories within your Drivers folder (I personally do it with the best compression and as a solid archive and it got a 5:1 compression ratio).  Make it self extracting, but don't worry about any SFX options for the time being.  Once the archive is created, add a comment to the archive (a shortcut to this is Alt+M) with this info in it:

;The comment below contains SFX script commands

Path=%systemdrive%\Drivers
SavePath
Silent=2
Overwrite=1

That will tell it to extract to Drivers on root (in other words, generally C:\Drivers).  It will show an extraction progress dialog (so you can verify that it is indeed working.  Change Silent=2 to 1 if you want it to be completely hidden.  Overwrite=1 tells it to overwrite any files it comes across (not that it'll be an issue if you're doing a clean install).

So now you should have an exe (mine's called Drivers.exe and I'll be using it as an example) with the above comment in it (you can test its functionality too by double clicking and verifying that it extracts how you want it to).  Place it in your $1 folder inside $OEM$.  In the [GUIUnattended] section of winnt.sif, add the following line:

DetachedProgram="%systemdrive%\Drivers.exe"

Leave your OEMPnPDriversPath settings in winnt.sif the same as if the files were uncompressed on the CD.  They will be extracted prior to PnP device detection, so this will not be a problem.

This is exactly how I made it.

[Denney]

Hmm... don't know quite what's wrong here... wondering if someone could help me (this is my first attempt at using DetachedProgram)...

WINNT.SIF:

[GuiUnattended]
 OemSkipWelcome=1
 TimeZone=260
 DetachedProgram="%systemdrive%\MSA\DriverSetup.cmd"

DriverSetup.cmd:

@echo off

if exist D:\WIN51IP.SP2 D:\OEM\utilities\setenv -m CDROM D:
if exist E:\WIN51IP.SP2 E:\OEM\utilities\setenv -m CDROM E:
if exist F:\WIN51IP.SP2 F:\OEM\utilities\setenv -m CDROM F:
if exist G:\WIN51IP.SP2 G:\OEM\utilities\setenv -m CDROM G:
if exist H:\WIN51IP.SP2 H:\OEM\utilities\setenv -m CDROM H:
if exist I:\WIN51IP.SP2 I:\OEM\utilities\setenv -m CDROM I:
if exist J:\WIN51IP.SP2 J:\OEM\utilities\setenv -m CDROM J:
if exist K:\WIN51IP.SP2 K:\OEM\utilities\setenv -m CDROM K:
if exist L:\WIN51IP.SP2 L:\OEM\utilities\setenv -m CDROM L:

%CDROM%\OEM\utilities\cmdow @ /HID

start /wait %systemdrive%\MSA\drivers.exe

%CDROM%\OEM\utilities\setdevicepath.exe %systemdrive%\MSA\drivers

exit

For some reason that doesn't work. Can I use .cmd files from DetachedProgram?

[Bâshrat the Sneaky]

CMD is not available at that stage. You've got to use it in a special way, which I don't know anymore... Someone who remembers it?

[Denney]

FIXED IT! Never actually thought, change it from a .cmd file to a .bat file!! It works!! So simple.

It took me so long to figure that out.

.cmd is a "Windows NT Command Script" whereas .bat is an "MS-DOS Batch File".

[iSmart]

This cool method doesn't allow to install RAID or SATA/RAID drivers from floppy by pressing F6. For the first time, a driver is copied from floppy, but when the yellow marker grown up on text-mode stage, driver cannot be copied with error.

Maybe you'll release new version, Pyron?

[Denney]

In relation to my first post, I have given up on the CDROM bit... For some reason nothing will work to detect the CDROM drive at this stage (or any stage for some reason).

The "if exist" part will work but only if I use "set" rather than the "setenv" executable (but then I have to do the "if exist" part again at cmdlines). The DetectCD executable won't work either.

After a day of trying this I have given up (I still use the compressed drivers though). Just thought I'd let people know.

[bilemke]

@RaveRod

perhaps could you try setting the variable with "set" and then use the variable you just added as the input for "setenv" ?

[Alanoll]

iSmart, on Jun 26 2004, 06:52 AM, said:

This cool method doesn't allow to install RAID or SATA/RAID drivers from floppy by pressing F6. For the first time, a driver is copied from floppy, but when the yellow marker grown up on text-mode stage, driver cannot be copied with error.

Maybe you'll release new version, Pyron?

this has NOTHING to do with RAID. Sorry.


It intended solely for the purpose of not having to copy over massive amounts of drivers like for different video cards during each install, and instead use them from CD (or modify it otherwise)

RAID can NOT be done this way. the RAID drivers must be loaded during txtsetup and an entry in WINNT.SIF breaks teh F6 function. This method only STARTS AFTER textmode is done. We can't run ANYTHING DURING TXTMODE. SO the only alternatives is to NOT use a winnt.sif OR add the driver's manually to txtsetup.sif on your own, or use a drivers pack.

[edmoncu]

quick question: i heard from the early part of the thread that this *should* work with win2k... has anyone tried it with win2k?

[Pyron]

Just checked, it works.

But you need to change this line

set tagfile=\WIN51

in my example to

set tagfile=\CDROM_NT.5

Otherwise it won't find the CD and the script(s) fail, resulting in an immediate restart.

--
Pyron

[edmoncu]

wow cool! i'll try it! thanks!

[bilemke]

Alanoll, on Jun 29 2004, 11:32 PM, said:

iSmart, on Jun 26 2004, 06:52 AM, said:

This cool method doesn't allow to install RAID or SATA/RAID drivers from floppy by pressing F6. For the first time, a driver is copied from floppy, but when the yellow marker grown up on text-mode stage, driver cannot be copied with error.

Maybe you'll release new version, Pyron?

this has NOTHING to do with RAID. Sorry.


It intended solely for the purpose of not having to copy over massive amounts of drivers like for different video cards during each install, and instead use them from CD (or modify it otherwise)

RAID can NOT be done this way. the RAID drivers must be loaded during txtsetup and an entry in WINNT.SIF breaks teh F6 function. This method only STARTS AFTER textmode is done. We can't run ANYTHING DURING TXTMODE. SO the only alternatives is to NOT use a winnt.sif OR add the driver's manually to txtsetup.sif on your own, or use a drivers pack.

Actually it may, there is a small chance this could be used to make the ideal raid driver setup... One that would still allow f6. I will try to test this idea in the next 24-48 hours if i can afford the time, otherwise here it is(in case someone else wants to try).....


1. Modify txtsetup.sif similair to method in M1 setups described in thread here and Microsoft KB article here.

This should take care of text based portion of setup.

2. Follow insctuctions in this thread for using Pyron's creation. This should take of the gui portion of setup.

This would be great if it worked as it would be a truely winnt.sif free way of using raid drivers, plus be able to use f6 to load new drivers from floppy. My only concern is the difference between the two major portions of the text setup part of setup. The changes will take care of the first part (drive identifaction) and let you do partitioning.. After that, but before gui setup starts, is the potential problem.

[twindude]

have a problem......these directions are great and works but here's the problem!

Seems to get the RAID drivers to load but doesn't act as if it see's the unattend.txt
in your cmd can you set it to use something like "winn32.exe /u" so it looks for the unattend.txt ????

or some other way?

[bilemke]

@twindude

you talking to me?

If so, you can still use unattend.txt/winnt.sif.... if you want.

I am working on finding where/when in setup this info gets imported, and do it seperately.