Add the XP sound drivers to Server 2003?

[softice]

I guess DOSNET.INF and others might list driver files.

For my own sanity in case I lose my files (it has happened before, lol)

here is the [sourceDisksFiles] section of TXTSETUP.SIF. Most files

have = 1,,,,,,,,3,3 after them but not all of them.

I found DRVINDEX.INF and LAYOUT.INF include driver files list.

DRVINDEX.INF

[Version]

signature="$Windows NT$"

CabFiles=sp1,driver

[driver]

acpiec.sys

adptsf50.sys

adpu160m.sys

afcnt.sys

agcgauge.ax

---------------

LAYOUT.INF

[sourceDisksFiles]

atapi.sys = 100,,95744,,,,4_,4,0,0,,1,4

disk.sys = 100,,39936,,,,6_,4,0,0,,1,4

classpnp.sys = 100,,54784,,,,6_,4,0,0,,1,4

dmio.sys = 100,,150016,,,,4_,4,0,0,,1,4

dmload.sys = 1,,7680,,,,4_,4,0,0,,1,4

ftdisk.sys = 100,,137216,,,,3_,4,0,0,,1,4

I put es1371mp.sys into driver.cab. Then edit drvindex.inf and layout.inf, add es1371mp.sys like example. Copy inf to "\$OEM$\$$\inf\". create iso, install it. It also installed soundcard successfully.

[LeveL]

OK this is really freaking me out now...

I tried it the way you said softice, cabbing the driver files, but it didn't install the sound driver in VMware.

I put all the driver files and INF files into this folder:

I put this line in winnt.sif...

I have both these files in that DRIVER folder:

es1371mp.sys

wdma_ens.inf

It just doesn't work:

Since I did exactly what you did, what could possibly be going wrong?

Edited March 26, 2007 by LeveL

[LeveL]

Sorry, double posted.

Edited March 26, 2007 by LeveL

[softice]

You are creating ISO file and then boot from it to install windows?

"c:\driver" in vmware, check whether there.

Edited March 26, 2007 by softice

[LeveL]

You are creating ISO file and then boot from it to install windows?

"c:\driver" in vmware, check whether there.

Yes. After the install is complete, I have the folder on the C: drive...

C:\DRIVER

I chose to "re-install driver" on the Multimedia Audio Controller in Device Manager

and it will install the drivers smoothly from that "C:\DRIVER" folder! This is so wierd.

When I was doing it the other way, dumping all the files in I386, it had to be pointed

to I386 twice but this way, it is a smooth install, but still this is only AFTER Windows

has installed... its not working doing it with "OemPnPDriversPath" in WINNT.SIF.

I tried all these combinations:

OemPnPDriversPath="DRIVER"

OemPnPDriversPath=DRIVER

OemPnPDriversPath="DRIVER\"

I also tried it having the actual .SYS files (all uncabbed) in the DRIVER folder,

this won't work.

I am using bashrats Driverpacks with this but I don't see how that could stop

the install working.

Its a shame he doesn't make a XP > Server 2003 driverpack because it would

only be about 20Mb.

[softice]

This is a strange thing, I don't know where the problem lies.

[LeveL]

This is a strange thing, I don't know where the problem lies.

Me neither... heres what I am using:

Server 2003 SP2 with Bashrats Driverpacks - MassStorage, LAN, CPU, Chipset, WLAN.

Let me guess, you're not using any Bashrat Driverpacks?!

That is the only thing it can possibly be. I am not knocking Bashrat, but I

just think its conflicting somehow, I know there is a "Driver Signing Policy"

thing built into BTS driverpacks and I know it resets something in the

registry, but I dunno if this has anything to do with it.

softice you have been a great help already, I never knew I could just

cab those files... it should work but it isn't, not for me at least.

I got to get some sleep, its 4.30am here

I am going to test again tomorrow without integrating any of the Bashrat drivers.

I will post back with the results... just give up on it if you want though dude, its just

impossible it seems... if it still doesn't work without Bashrats drivers, then I dunno,

maybe I could 7-zip those driver files into one of Bashrats driverpacks, I am not sure

how it works... or use just "D" as a directory, since this is what the Bashrat drivers

unpack to and they do work, lol, one can only assume, its in VMware though so the

"hardware" inside that is limited. The only device in VMware (with or without modifying

Windows) that is not installed is that pesky Audio device.

[softice]

I am used the driver which rip form XP. I test it again through the same way, it also install the soundcard successfully.

I never knew I could just

cab those files... it should work but it isn't, not for me at least.

I use "makecab.exe" to compress the files. It located in "\windows\system32".

Open Command Prompt.

cd directory of the files, run:

makecab es1371mp.sys

If you have so many files to cab, use:

for %f in (*.*) do makecab /l b:\win2003\$oem$\$1\driver %f

Why these words in front of a few space? My winnt.sif have none of it.

I am prepared to make a test with Bashrat Driverpacks.

good night!

Edited March 26, 2007 by softice

[LeveL]

Maybe it is the spaces in front of the lines, but if it is then the only

line being affected is the OemPnPDriversPath, all the other lines

are fine.

When you integrate bashrat driverpacks, that puts a tab/space in

front of the lines it puts in, like this:

[GuiRunOnce]

[TAB --->] command9="%SystemDrive%\DPsFnshr.exe"

I am testing it again right now with no driverpacks.

[LeveL]

I got it to work - IT IS those driverpacks causing it!

I left out the driverpacks and it has installed fine!

I might pull apart those driverpacks and try to add them to the OemPnPDriverPath

I was using "Method 2" when I put the packs in. Can't believe this is why it wouldn't work.

This is from Bashrats BASE program...

Method 1: copy drivers to $OEM$\$1\, then list the directories in winnt.sif's

OemPnpDriversPath entry. The drivers will be CAB compressed.

Method 2: install a fake setup that will be executed before the real setup.

This fake setup will extract the DriverPacks from the CD/DVD to the HDD

and then update the DevicePath key in the registry.

Thats why its not working "and then update the DevicePath key in the registry"

it is not looking for "OemPnPDriversPath" if you use method 2.

I know the favoured method is method 2, I don't know why, but if I use method

1 then I can just add ";DRIVER" to the end of the line.

D4mn it - I just don't read! I should have read properly what Method 1

and Method 2 are doing!

Edited March 26, 2007 by LeveL

[softice]

OK, find out where the problem lie.

Congratulation!