Hi.

im new to this forum and this is my first post..

so..

here comes my doubt..its like dis

i donwloaded da driver pack and i extracted dem but it appears as d/c/1/... etc..

is it suppose to be like dis?? am i suppose to do anything more??

thnx ahead..

@tom9191:

You need DriverPacks_BASE to make any of the other DriverPacks work.

Hi..its like dis..i already have da drivers pack of Bâshrat the Sneaky's DriverPacks and i extracte4d dem and wat appears is da image inn da attachment..xD

You shouldn't extract anything; DriverPacks_BASE.exe does all the work for you. Just run BASE and follow the instructions.

Outstanding work! This method is fast, easy, and effective. It works great with HFSLIP.

Thanks!

Outstanding work! This method is fast, easy, and effective. It works great with HFSLIP.

Thanks!

Glad to hear!

I've problem.....My pc reboot always after the copy of the files of windows

OK RESOLVED

Edited March 1, 200620 yr by Unlock

I've problem.....My pc reboot always after the copy of the files of windows

OK RESOLVED

...ok

new problem:

1)Start installation windows

2)start driver.cmd and I see all operation after, pc restart and blue screen

WHY?

I've many drivers for more pc in drivers directory...Is the problem it?

This would be cool as an addon pack. Has anyone tried to build one yet?

I've problem.....My pc reboot always after the copy of the files of windows

OK RESOLVED

...ok

Exactly when are you getting this problem shortly after T39?

Cheers

MC.

new problem:

1)Start installation windows

2)start driver.cmd and I see all operation after, pc restart and blue screen

WHY?

I've many drivers for more pc in drivers directory...Is the problem it?

I have same problem. I deleted the Forceware driver and everything working correctly. I think the problem appears with 8x.xx drivers only. In this weekend I will test.

Any opinion?

Joc

Solved the BSoD 0x7e: everything is working correctly with Forceware 77.72!

Joc

ok canghe forceware 8 wiht 77.72.......where found it?

Now that everything is back to batch syntax, may I submit for testing a small modification to this method?

Using it as specified in the 1st post, there may be a weak point in the way Drivers.cmd is looked for, namely the Arguments line in Winnt.sif:

Arguments="/Q /C FOR /F %I IN (%SystemRoot%\SYSTEM32\$WINNT$.INF) DO (FOR %J IN (%I$OEM$) DO (IF EXIST %J (start /min /D%J Drivers.cmd)))"

* All the lines of $WINNT$.INF are processed regardless of their relevance/risk.

* %I$OEM$ works fine for installing from CDROM but for installing using a local source (from dos, network, etc.) we need to use %I\$OEM$

I would suggest the following 3 steps:

1- put Drivers.cmd in \$OEM$\$1 instead of \$OEM$

Doing so, it will be copied to %SystemDrive% at the end of the Textmode Setup

2- Have a really simple Arguments line:

Winnt.sif

DetachedProgram = cmd.exe

Arguments = "/Q /C START /MIN %SYSTEMDRIVE%\Drivers.cmd"

3- Modify Drivers.cmd to find the exact source folder at the beginning and to remove itself at the end:

Drivers.cmd

CLS

@ECHO OFF

TITLE Drivers-from-CD Installation

color 1F

:: Set Current Drive as CD

CD /D "%~dp0"

:: Find the source (dospath) folder

FOR /F "tokens=1* delims==" %%I IN (%SystemRoot%\SYSTEM32\$WINNT$.INF) DO (IF dospath==%%I SET dosP=%%J)

::Add trailing slash for installs from local source

IF NOT %dosP:~-1%==\ SET dosP=%dosP%\

:: check for drivers existence

IF NOT EXIST "%dosP%$OEM$\SetupCopyOEMInf.exe" EXIT

:: Set $OEM$ as CD

CD /D "%dosP%$OEM$"

:: Set Drivers Location Folder

SET DRV=Drivers

...

...

...

Bulk of Drivers.cmd goes here

...

...

:: Delete Ticker File

DEL %SystemDrive%\Ticker.ncl

:: Clean myself 'cause I'm a nice little boy

DEL %SystemDrive%\Drivers.cmd

EXIT

* The FOR can now use quotes so it can properly target the folder referenced by the dospath line, at the exclusion of any other potential folder referenced by the other lines of $WINNT$.INF. Although the risk of having another $OEM$ elsewhere is low, this may avoid unexpected things to happen,

* The next line allow for use in any situation: install from CDROM and install using a local source,

* Then a control is performed,

* Eventually the current directory is set to $OEM$ and the rest of the operations can follow.

[edit]: added the 'START' command in the arguments directive, otherwise .cmd files are not processed.

Edited May 2, 200620 yr by Djé