Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 

a06lp

Drivers from CD: Simple Method

Recommended Posts

tom9191    0

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..

Share this post


Link to post
Share on other sites
Guest   
Guest

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

Share this post


Link to post
Share on other sites
Unlock    0

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?

Share this post


Link to post
Share on other sites
Joc    0
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

Share this post


Link to post
Share on other sites
Djé    0

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 by Djé

Share this post


Link to post
Share on other sites

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.

×