Add the XP sound drivers to Server 2003?

[LeveL]

On Microsoft's own website on a page about troubleshooting

the audio in Server 2003 it says:

A sound driver may not be installed. Windows Server 2003 includes a limited list of sound drivers.

Yes it does, because with XP in VMware, the sound driver is fine, it installs,

but with Server 2003 it does not work, where Microsoft say "Windows Server

2003 includes a limited list of sound drivers" I think they mean it is VERY

limited.

Is there any way to add the drivers for sound that are in XP to Server 2003?

Where would I start? I know you can't just throw them into DRIVER.CAB

because those files are all listed in INF files so if the XP sound drivers were

inside the Server 2003 DRIVER.CAB, it wouldn't make any difference! Or so

thats how I understand it, to be honest I really don't understand it, thats why

I am asking!

I know I could just use Bashrat The Sneaky driverpacks but the sound drivers

alone are 100Mb... far far too big! I only want to add the core sound drivers that

are obviously in XP (because they work in VMware) but not in Server 2003.

Strange thing is, on my real system the sound drivers do install for my onboard

sound, but its VMware where I want them working. I installed the Creative sound

driver in VMware and it added these files to C:\WINDOWS\system32\drivers\ --->

As you can see from the descriptions, it is not totally obvious what are sound

drivers and what arn't! They don't have sound driver-ish names. The real kicker

is... none of these files, not a single one, even exists in the Windows XP source

folder!

Please tell me someone has made a simple add-on for these drivers?!

Because DRIVER.CAB in Windows XP contains thousands and thousands of files,

no way am I reading through 1000's of file descriptions!

Edited March 22, 2007 by LeveL

[ricktendo]

You could make your own small personal driverpack http://forum.driverpacks.net/viewtopic.php?id=279

Use IcemanND Driver Backup tool to extract the driver files from your XP Install http://www.msfn.org/board/index.php?showtopic=83960

Install XP and the driver for your sound card and use the Driver Backup to extract those XP Sound drivers.

Then simply use DPs Base to slipstream your personal DriverPack into your 2k3 CD

[LeveL]

Thanks... I have tried something else, I have got to test it yet though:

1 - Extracted DRIVER.CAB from Windows XP into a folder "XP\DRIVER"

2 - Extracted DRIVER.CAB from Windows Server 2003 into a folder "2003\DRIVER"

3 - Opened both folders side by side.

4 - Scrolled to the bottom of the "2003\DRIVER" folder.

5 - Copied all the files from the "XP\DRIVER" folder into the "2003\DRIVER" folder, overwriting nothing.

6 - Copied all the added files from the bottom of the "2003\DRIVER" into another folder.

This turns out to be 351 files!

DRIVER.CAB on Server 2003 as standard = 55.4Mb

DRIVER.CAB on XP as standard = 60.4Mb

When I recabbed the "hybrid" drivers (2003 with added XP drivers) with

Power Archiver - my DRIVER.CAB is now 80.0Mb. So there are a lot of

drivers in XP that are not in 2003 - and vice versa!

I will just have to test it to see, because what i said before about those

drivers all being listed... they are not listed anywhere as far as I know, it

would be nice if Windows just dealt with the device installations seperately

and managed to use "whatever" drivers are in DRIVER.CAB.

Its not just sound drivers - the following drivers are also included with XP that are not in Server 2003:

Adaptec SCSI Miniport

AdvanSys SCSI Card Driver

Compaq Drivers (tons of those!)

Creative SB Live! Adapter Driver

Creative SB Live! Interface Driver

ESS Technology Audio Driver

Hewlett-Packard ScanJet 2100C/3300C/4200 Device Driver

Modem Drivers (tons of!)

U.S. Robotics

That is just a fraction of whats added in the "hybrid" DRIVER.CAB!

[softice]

vmware use Creative AudioPCI (ES1371), it needed 2 files.

1, expand wdma_ens.in_ from \i386 of xp disk, to wdma_ens.inf.

2, extract es1371mp.sys from driver.cab.

[LeveL]

Thanks, but I want to add ALL the drivers from XP into it, somehow.

Well everything I said in post #3 has not worked.

I guess the drivers in the CAB file are listed somewhere huh.

Time to start f**king about adding 351 lines of code to

some f**king INF file somewhere.

OMFG the files ARE listed, in TXTSETUP.SIF under [sourceDisksFiles]

So yeah, now I have got to add the 350 lines of code to that... Microsoft, why do you

make it so difficult?

Edited March 23, 2007 by LeveL

[softice]

The main point is that you didn't copy *.inf from xp to 2003. Driver.cab have none of inf files.

The driver list is generated by inf file.

You can copy all in_ to 2003 cd:

copy x:\i386\*.in_ y:\i386

or you can expand all in_ to inf folder of current win2003.

Edited March 23, 2007 by softice

[LeveL]

So you mean... all those *.IN_ files in XP have drivers listed?

I am looking in TXTSETUP.SIF and it has listed every file that is

in DRIVER.CAB.

So I will have to do this:

1 - Open the folder with the 351 added files (those are in the DRIVER.CAB for XP but not in Server 2003)

2 - Open a new notepad TXT file and call it "OMFG I can't believe I am doing this.txt"

3 - Copy the name of the first of the 351 files.

4 - Open my XP TXTSETUP.SIF file and Ctrl+F for that file.

5 - Once I find it, copy the whole line it is on and add it to the new

text file, of course also noting the [sections] it appears in as I do it.

This is an INCREDIBLE amount of work.

I could always work on one letter a day and it will take about a month to do

it and even then, its not guaranteed to work, or is it?

You said the files are also listed in INF files! This is a nightmare, why can't

JERKOFF MICROSOFT just put the drivers in there in the first place?!

[LeveL]

As a famous prophet once said:

"F**K THIS FOR A GAME OF SOLDIERS"

I wonder if theres some way to slipstream these drivers with BTS, HFSLIP or nLite?

How are any of those programs going to know the comma's and numbers its supposed to have?

For example:

3cwmcru.sys = 1,,,,,,,,3,3

a3d.dll = 1,,,,,,,2,3,3

a3dapi.dll = 1,,,,,,,2,3,3

acerscad.dll = 1,,,,,,,,3,3

adm8511.sys = 1,,,,,,,,3,3,,1,4

adm8810.sys = 1,,,,,,,,3,3

adm8820.sys = 1,,,,,,,,3,3

adm8830.sys = 1,,,,,,,,3,3

aha154x.sys = 1,,,,,,4_,4,1,,,1,4

alifir.sys = 1,,,,,,,,3,3

amb8002.sys = 1,,,,,,,,3,3,,1,4

amsint.sys = 1,,,,,,4_,4,1,,,1,4

apmbatt.sys = 1,,,,,,,4,1,1

That is just the first 13 files out of 351 files.

Some files appear under multiple sections:

[sourceDisksFiles]

[sourceDisksFiles.x86]

[Files.DeleteOnUpgrade]

[HardwareIdsDatabase]

[sCSI.Load]

And MANY MANY more!

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

You know it would actually probably be quicker to hand code a program all of its own

that searches TXTSETUP.SIF for these lines, adds them to a new TXT file under the correct

sections and so on.

351 files, its too much work to do by hand.

Edited March 26, 2007 by LeveL

[softice]

For exmple, driver of ES1371 contained two files,wdma_ens.inf andes1371mp.sys. But you only copyed es1371mp.sys, so win2003 lost the driver information from wdma_ens.inf.

In my opinion, follow the step below here:

1, ex, all files of win2003 are located in x:\win2003\, create folder "x:\win2003\$OEM$\$1\drivers\plus\".

2, copy all the files(those are in the DRIVER.CAB for XP but not in Server 2003) to x:\win2003\$OEM$\$1\drivers\plus\

3, expand all the files(those are in the \i386\*.in_ for XP but not in Server 2003) to x:\win2003\$OEM$\$1\drivers\plus\

4, edit winnt.sif, add this information

[unattended]

OemPreinstall=Yes

OemPnPDriversPath="drivers\plus"

Edited March 23, 2007 by softice

[softice]

Only the device used in textmode setup, and it's driver information must add in to txtsetup.sif. exmple, SCSI, SATA...

VGA, soundcard,etc, are noneeded.

[LeveL]

For exmple, driver of ES1371 contained two files,wdma_ens.inf andes1371mp.sys. But you only copyed es1371mp.sys, so win2003 lost the driver information from wdma_ens.inf.

In my opinion, follow the step below here:

1, ex, all files of win2003 are located in x:\win2003\, create folder "x:\win2003\$OEM$\$1\drivers\plus\".

2, copy all the files(those are in the DRIVER.CAB for XP but not in Server 2003) to x:\win2003\$OEM$\$1\drivers\plus\

3, expand all the files(those are in the \i386\*.in_ for XP but not in Server 2003) to x:\win2003\$OEM$\$1\drivers\plus\

4, edit winnt.sif, add this information

[unattended]

OemPreinstall=Yes

OemPnPDriversPath="drivers\plus"

Wow - this seems like a very quick and easy fix, thanks... but my main problem

is that I don't have the 50Mb spare needed to store these driver files. I guess if

I strip out the UDDI service (33Mb) and a few other things, like Printer drivers

(another 33Mb) I can fit all these files on the CD.

So I should search the XP I386 folder for ".IN_" and use whatever *.IN_

files are not on Server 2003? OK, I think I understand this, those IN_

files need to be uncabbed and PUT WITH the driver files... it seems to

be quite straightforward.

Only the device used in textmode setup, and it's driver information must add in to txtsetup.sif. exmple, SCSI, SATA...

VGA, soundcard,etc, are noneeded.

Yeah the [sCSI.Load] section etc - but why are all these driver files (from inside

DRIVER.CAB) all listed in TXTSETUP.SIF?

I have slipstreamed some Bashrat drivers, my WINNT.SIF is like this:

[unattended]

UnattendMode=FullUnattended

OemSkipEula=Yes

UnattendSwitch="yes"

WaitForReboot="No"

TargetPath=\WINDOWS

DriverSigningPolicy=Ignore

NonDriverSigningPolicy=Ignore

OemPreinstall=Yes

You said do it so these lines are there:

[unattended]

OemPreinstall=Yes

OemPnPDriversPath="drivers\plus"

So the only difference is that this is added:

[unattended]

OemPnPDriversPath="drivers\plus"

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

Well OK what about this: When does this OemPnPDriversPath get read?

I mean, is it possible to add all these drivers and INF files to a 7z archive

and unpack it to "%SYSTEMDRIVE%\Drivers\Plus" at the cmdlines.txt

part of setup, will it be "unpacked in time" for the OemPnPDriversPath

to install the drivers?

If that could be done (and this is getting almost like what Bashrats driverpacks do)

then it would be excellent because those 50Mb of drivers could be 7zipped down

to only 8.90Mb

[softice]

Yeah the [sCSI.Load] section etc - but why are all these driver files (from inside

DRIVER.CAB) all listed in TXTSETUP.SIF?

Sorry, I made a mistake.

Only the device used in textmode setup, and it's driver information must add in to txtsetup.sif. exmple, SCSI, SATA...

##########

But VGA, soundcard,etc, are noneeded.

I mean, is it possible to add all these drivers and INF files to a 7z archive

and unpack it to "%SYSTEMDRIVE%\Drivers\Plus" at the cmdlines.txt

part of setup, will it be "unpacked in time" for the OemPnPDriversPath

to install the drivers?

I am not sure wether this can work correctly. You can try it.

I have another way, like this:

1, ex, all files of win2003 are located in x:\win2003\, create folder "x:\win2003\$OEM$\$$\inf\".

2, expand all the files(those are in the \i386\*.in_ for XP but not in Server 2003) to x:\win2003\$OEM$\$$\inf\

3, add all the files(those are in the DRIVER.CAB for XP but not in Server 2003) into x:\win2003\i386\driver.cab.

I have not tested it.

[LeveL]

I have another way, like this:

1, ex, all files of win2003 are located in x:\win2003\, create folder "x:\win2003\$OEM$\$$\inf\".

2, expand all the files(those are in the \i386\*.in_ for XP but not in Server 2003) to x:\win2003\$OEM$\$$\inf\

3, add all the files(those are in the DRIVER.CAB for XP but not in Server 2003) into x:\win2003\i386\driver.cab.

I have not tested it.

At the moment I am trying to unpack a folder to the C:\ drive that will

contain the driver files and INF files. I am doing this from cmdlines so

I think it might be too late. When Windows says "Setup is installing

devices such as your keyboard and mouse" I am sure thats when

other stuff like Printers, Scanners, Modems, Sound Cards get their

drivers installed, if thats the case then cmdlines runs AFTER this

so it won't work but I am testing it now.

I will try your way above if my way doesn't work out... if that doesn't

work I will have to unpack and just have the 50Mb worth of drivers

there (actually its 55Mb with the INF files) and try to strip a few things

from the install but I really didn't want to strip the OS.

EDIT: Well I ended up removing a few things with nLite, that has

freed up 50Mb of space, the drivers are all expanded now and I am trying

the OemPnPDriversPath method.

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

AAAAAAAAAGH!

It has not installed the sound drivers!

I suppose I will have to try the hard way packing them into DRIVER.CAB

and listing them all in TXTSETUP.SIF.

Edited March 23, 2007 by LeveL

[LeveL]

Dunno if this will work but I am listing the files in TXTSETUP.SIF

This is just two sections of one file!

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

Edited March 25, 2007 by LeveL

[softice]

Today, I had a test on virtual machine. It successfully install the es1371 soundcard.

1, Copy win2003 disk to b:\win2003. create folder "b:\win2003\$oem$\$1\driver"

2, Ceate a folder "b:\temp0", copy the driver files to temp0.

3, Open cmd, change folder to temp0, run command to compress files.

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

B:\temp0>makecab /l b:\win2003\$oem$\$1\driver  es1371mp.sys
Microsoft (R) Cabinet Maker - Version 5.2.3790.0
Copyright (c) Microsoft Corporation. All rights reserved..

100.00% [flushing current folder]

4, Copy inf files to "b:\win2003\$oem$\$1\driver"

5, After completing the above step, win2003 look likes:

B:\WIN2003
├─$OEM$
│  └─$1
│	  └─driver
│			  WDMA_ENS.INF
│			  es1371mp.sy_
│
└─i386
...............

6, Edit i386\winnt.sif, add this information.

[Unattended]
DriverSigningPolicy = Ignore
NonDriverSigningPolicy = Ignore
OemPnPDriversPath="Driver"

7, Make bootable cd, install windows 2003.