26 Reply by LeveL

(3 replies, posted in 3rd Party DriverPacks)

I wasn't doing it as a CAB file, I was simply making a "3rd Party Driverpack"
out of DRIVER.CAB by extracting the files to this folder:

D\3\XP\*.* <-------- DRIVER.CAB files

Then compressing that D folder and calling it :

DP_ALLXP_wnt5_x86-32_01.7z

Then stripping all the drivers from Windows in nLite except SCSI/RAID

This takes DRIVER.CAB down toabout 12Mb, its still there with some drivers in it.

So DRIVER.CAB was originally 80Mb, if you extract it and 7-Zip it you save about 23Mb.

But it doesn't work, at least not for the sound drivers in XP anyway.

Go to forum: 3rd Party DriverPacks

27 Reply by LeveL

(3 replies, posted in 3rd Party DriverPacks)

Hmmm, I tried this and it doesn't work, the sound drivers don't install.

How come its always sound drivers that seem to be the problem? Not with this
pack I just mean in general?! ALWAYS the sound drivers sad

Go to forum: 3rd Party DriverPacks

28 Topic by LeveL

(3 replies, posted in 3rd Party DriverPacks)

I just recompressed DRIVER.CAB with 7-Zip on Ultra...

Original DRIVER.CAB file = 77.5Mb

7-Zipped DRIVER.CAB = 54.6Mb

I just extracted the files to: D\3\XP\[files]

So you can save a lot of space IF this works, I don't see why it won't?

I would use nLite and just strip out every single driver from XP.

BUT - what about the SCSI/RAID drivers in XP? Arn't those needed at the text mode stage?

This would be great if it works because it saves almost 23Mb but you lose... nothing!

Go to forum: 3rd Party DriverPacks

29 Reply by LeveL

(4 replies, posted in DriverPack Sound)

Thanks dude!

Well, I didn't really want to remove any drivers, so instead, I have
made a simple AutoIt script that runs just before DPsFnshr.exe that
goes like this:

WinWait, Error, You have previously installed drivers without rebooting
WinActivate, Error, You have previously installed drivers without rebooting
Send, {ENTER}

The only thing I could find on Google related to this error "You have previously
installed drivers without rebooting" was to do with Audigy cards on Vista.

I don't think anyone here has ever reported this happening, I guess it must
be because I am using Server 2003.

Can't believe the work that has gone into these driverpacks, plus all the work
it must be listing everything as well... its insane!

Go to forum: DriverPack Sound

30 Reply by LeveL

(6 replies, posted in 3rd Party DriverPacks)

Cheers.

The problem with this modem is, it always was a horrible modem,
with buggy drivers. Even though the latest drivers do have CAT files
with them, I still get it asking "Are you sure you want to continue"
because the files are not signed, hmmmm...

I have deleted the drivers I had, I have re-installed Windows again
without those drivers, sorry. (blush.gif)

So, this modem... it has drivers then it has the "driver update patch" too
and that patch does not have any INF files with it, or SYS files either, so
it doesn't replace anything, I am not sure what it even does, this modem
just stinks!

Maybe its just because I am doing all this on Server 2003 and not XP.

Go to forum: 3rd Party DriverPacks

31 Topic by LeveL

(4 replies, posted in DriverPack Sound)

When DpsFnshr.exe is running I get this message:

Error
You have previously installed drivers without rebooting. Please reboot and try again

I open Task Manager and the file CT2APXX.exe is running.

It is my "Creative Soundblaster Live! Value" card. The drivers for this are
being installed twice by the look of it because the drivers install no problem.

I used Agent Ransack to search both "Sound A" and "Sound B" for the term
"Creative SB Live! Value" and only found this term appearing in the following
two folders in Sound A. I noticed that in "Sound A" these 2 folders have exactly
the same amount of files and folders:

D\S\CR\1 (371 Files / 81 Folders)
D\S\CR\2 (371 Files / 81 Folders)

But the folder sizes are slightly different: folder 1 is 83.1Mb and folder 2 is 83.4Mb.

So all I am asking is what IS the difference between these 2 folders?

They both seem to have Live! and Audigy driver icon files and look the same to me!

Is it safe to remove folder 2? Will the DpsFnshr still work if I repack the driverpack
without that D\S\CR\2 folder?

Go to forum: DriverPack Sound

32 Topic by LeveL

(6 replies, posted in 3rd Party DriverPacks)

I have included the 3rd Party Driverpack:

DP_Broadband_wnt5_x86-32_60831.7z

I have an Alcatel Modem, the drivers for this are here:

C:\D\3\B\T\A\

The files for this device are:

alca98ln.sys
alcacr95.sys
alcacrnt.sys
alcalan.cat
alcan5ln.sys
alcan5wn.sys
alcandis.inf
alcastw.inf
alcaudsl.sys
alcawan.cat
alcawh95.sys
alcawhnt.sys
alcstusb.cat
dragdiag.exe
phonebook.ini
stci.dll
stdialup.exe
valcacr.vxd

But I am getting a message popping up that says:

"Windows could not load the installer for SpeedTouchUSBModem.
Contact your hardware vendor for assistance."

Here is the failure in my C:\WINDOWS\SetupLog.log - this is all on one line not three lines! -->

04/13/2007 02:44:05,d:\nt\base\ntsetup\syssetup\syspnp.c,5070,,SETUP:
SetupCommitFileQueue(c:\d\3\b\t\a\alcastw.inf) failed while installing Class.
Error = 1223, Device = SpeedTouch ADSL Modem

As you can see there, the problem is with the file alcastw.inf

What should I do just completely leave that "A" folder out of the Broadband pack?

Then of course the drivers wouldn't install but lol, they arn't anyway.

If I click OK to the message "Windows could not load the installer for SpeedTouchUSBModem."
it instantly brings up the found new hardware wizard saying there is a problem with the device
and I have to then install the drivers the normal way, when doing this, it pops up the message
"Windows could not load the installer for SpeedTouchUSBModem." about three times but the
drivers do install eventually.

Go to forum: 3rd Party DriverPacks

33 Reply by LeveL

(9 replies, posted in DriverPack Sound)

Method 1 does work but I am including so many driverpacks - about 25 driverpacks
in total, so theres no way of doing it, because of the 4096 character limit.

I tried to install the driver from the command line like this:

rundll32.exe setupapi,InstallHinfSection DefaultInstall 132 .\wdma_ens.inf

Even THAT doesn't work.

And yet I can install it in Device Manager manually. Oh man this is just sick!

I have been trying for about 4 or 5 days.

Heres the INF file wdma_ens.inf, can it be hacked somehow?......

[Version]
Signature="$CHICAGO$"
Class=MEDIA
ClassGUID={4d36e96c-e325-11ce-bfc1-08002be10318}
provider=%MSFT%
LayoutFile=layout.inf
DriverVer =07/01/2001,5.1.2535.0

[Manufacturer]
%MfgName%=CREATIVE

;; Mechanism for excluding drivers from the "Add New Hardware" list.
[ControlFlags]

ExcludeFromSelect = *

[CREATIVE]

%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371                   ; generic Concert AC97 PCI board
%ES1370.DeviceDesc%=ES1370,PCI\VEN_1274&DEV_5000                   ; Concert AC97 PCI board
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880                   ; generic 5880

;Intel
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_42498086   ; Intel BI440ZX
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_424c8086   ; Intel BL440ZX
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_425a8086   ; Intel BZ440ZX
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_43418086   ; Intel Cayman
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_43328086   ; Intel Cayman 2
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_43438086   ; Intel Cape Cod
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_45418086   ; Intel Easton
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_46498086   ; Intel Fire Island
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_464a8086   ; Intel FJ440ZX
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_47428086   ; Intel Garibaldi
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_4D4F8086   ; Intel Monteal
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_4f438086   ; Intel OC440LX
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_52438086   ; Intel RC440BX
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_53548086   ; Intel Stornaway
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_53528086   ; Intel SunRiver
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_56438086   ; Intel Vancouver
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_57538086   ; Intel WS440BX


%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_13711274   ; Concert AC97 PCI board
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_58801274   ; 5880
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_20001274   ; 5880
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_80011274   ; retail 5880 4 channel


;A-Trend
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_10011563   ; A-Trend
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_10021563   ; A-Trend
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_10031563   ; A-Trend
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_10041563   ; A-Trend
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_10051563   ; A-Trend
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_74601563   ; A-Trend 7060

; Compaq
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_B1A70E11   ; Compaq /w PS
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_B1BF0E11   ; Compaq /w PS
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_00240E11
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_00250E11
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_00260E11
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_00270E11
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_00280E11
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_00290E11
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_002A0E11
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_002B0E11
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_002C0E11
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_002D0E11

;Chaintech
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_2001270F   ; ChainTech 6CTR
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_2002270F   ; ChainTech 6BTA3
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_2001270F   ; ChainTech 6CTR
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_2200270F   ; ChainTech 6WTX
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_2200270F   ; ChainTech 6WTX
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_3000270F   ; ChainTech 6WSV
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_3100270F   ; ChainTech 6WIV2
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_3102270F   ; ChainTech 6WIV
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_7040270F   ; ChainTech 6ATA4
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_7060270F   ; ChainTech 6ASA2
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_7160270F   ; ChainTech 6AIA4
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_7040270F   ; ChainTech 6ATA4

;FIC
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_99021509   ; FIC KW11
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_99031509   ; FIC KW31
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_99041509   ; FIC KA11
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_99051509   ; FIC KC13
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_99201509   ; FIC FA11
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_99211509   ; FIC FS11
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_99221509   ; FIC FS31
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_99201509   ; FIC FA11
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_99211509   ; FIC FS11
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_99221509   ; FIC FS31

;Gateway
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_8054107B   ; Gateway Tabor2

;Gigabyte
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_20601458   ; Gigabyte 6VX7-4
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_20611458   ; Gigabyte 6VM7-4X
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_20621458   ; Gigabyte 6VX7-4
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_20631458   ; Gigabyte 6VM7-4X
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_20641458   ; Gigabyte 6VX7-4
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_20651458   ; Gigabyte 6VM7-4X
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_20661458   ; Gigabyte 6VX7-4
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_20671458   ; Gigabyte 6VM7-4X
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_20681458   ; Gigabyte 6VX7-4
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_20691458   ; Gigabyte 6VM7-4X
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_206A1458   ; Gigabyte 6VX7-4
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_206B1458   ; Gigabyte 6VM7-4X
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_206C1458   ; Gigabyte 6VX7-4
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_206D1458   ; Gigabyte 6VM7-4X
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_206E1458   ; Gigabyte 6VX7-4
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_206F1458   ; Gigabyte 6VM7-4X
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_20601458   ; Gigabyte 6VX7-4
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_20611458   ; Gigabyte 6VM7-4X
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_20621458   ; Gigabyte 6VX7-4
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_20631458   ; Gigabyte 6VM7-4X
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_20641458   ; Gigabyte 6VX7-4
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_20651458   ; Gigabyte 6VM7-4X
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_20661458   ; Gigabyte 6VX7-4
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_20671458   ; Gigabyte 6VM7-4X
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_20681458   ; Gigabyte 6VX7-4
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_20691458   ; Gigabyte 6VM7-4X
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_206A1458   ; Gigabyte 6VX7-4
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_206B1458   ; Gigabyte 6VM7-4X
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_206C1458   ; Gigabyte 6VX7-4
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_206D1458   ; Gigabyte 6VM7-4X
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_206E1458   ; Gigabyte 6VX7-4
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_206F1458   ; Gigabyte 6VM7-4X

;GVC
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_207714A4   ; GVC KR639
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_210514A4   ; GVC MR800
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_210714A4   ; GVC MR801
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_217214A4   ; GVC DR739


; Micron
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_18541042   ; Micron Tazer

;MSI
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_00011462   ; MSI
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_00021462   ; MSI
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_00031462   ; MSI
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_00041462   ; MSI
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_00051462   ; MSI
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_00061462   ; MSI
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_00071462   ; MSI
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_00081462   ; MSI
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_00091462   ; MSI
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_000A1462   ; MSI
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_000B1462   ; MSI
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_000C1462   ; MSI
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_000D1462   ; MSI
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_000E1462   ; MSI
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_000F1462   ; MSI
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_00101462   ; MSI
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_64701462   ; MS-6147 1.1A
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_65601462   ; MS-6156 1.10
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_66301462   ; MS-6163BX 1.0A
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_66311462   ; MS-6163VIA 1.0A
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_66321462   ; MS-6163BX 2.0A
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_66331462   ; MS-6163VIA 2.0A
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_68201462   ; MS-6182 1.00
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_68221462   ; MS-6182 1.00A
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_68301462   ; MS-6183 1.00
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_68801462   ; MS-6188 1.00 / 137x
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_69001462   ; MS-6190 1.00
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_69101462   ; MS-6191
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_69301462   ; MS-6193
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_69501462   ; MSI MS-6195
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_69901462   ; MS-6199BX 2.0A
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_69911462   ; MS-6199VIA 2.0A
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_68801462   ; MS-6188 1.00 / 5880
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_30801462   ; MSI MS-6308
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_30901462   ; MSI MS-6309
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_31801462   ; MSI MS-6318
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_00011462   ; MSI
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_00021462   ; MSI
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_00031462   ; MSI
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_00041462   ; MSI
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_00051462   ; MSI
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_00061462   ; MSI
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_00071462   ; MSI
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_00081462   ; MSI
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_00091462   ; MSI
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_000A1462   ; MSI
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_000B1462   ; MSI
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_000C1462   ; MSI
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_000D1462   ; MSI
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_000E1462   ; MSI
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_000F1462   ; MSI
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_00101462   ; MSI
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_68801462   ; MS-6188 1.00
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_68801462   ; MS-6188 1.00 / 5880
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_30801462   ; MSI MS-6308
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_30901462   ; MSI MS-6309
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_31801462   ; MSI MS-6318
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_69501462   ; MSI MS-6195

;NEC
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_80AC1033   ; NEC / 1033

;Quanta
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_8801152D   ; Quanta CP810E
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_8802152D   ; Quanta CP810
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_8803152D   ; Quanta P3810E
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_8804152D   ; Quanta P3810-S
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_8805152D   ; Quanta P3820-S
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_8809152D   ; Quanta M73
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_880B152D   ; Quanta M62
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_8811152D   ; Quanta M30
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_8811152D   ; Quanta M30
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_890A152D   ; Quanta
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_890B152D   ; Quanta
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_890C152D   ; Quanta
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_890D152D   ; Quanta
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_890E152D   ; Quanta
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_890F152D   ; Quanta
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_890A152D   ; Quanta
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_890B152D   ; Quanta
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_890C152D   ; Quanta
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_890D152D   ; Quanta
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_890E152D   ; Quanta
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_5880&SUBSYS_890F152D   ; Quanta

; Seanix
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_00014CA1   ; Seanix
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_00024CA1   ; Seanix
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_00034CA1   ; Seanix
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_00044CA1   ; Seanix
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_00054CA1   ; Seanix
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_00064CA1   ; Seanix
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_00074CA1   ; Seanix
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_00084CA1   ; Seanix
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_00094CA1   ; Seanix
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_000A4CA1   ; Seanix
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_000B4CA1   ; Seanix
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_000C4CA1   ; Seanix
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_000D4CA1   ; Seanix
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_000E4CA1   ; Seanix
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_000F4CA1   ; Seanix
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_00104CA1   ; Seanix
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_00114CA1   ; Seanix
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_00124CA1   ; Seanix
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_00134CA1   ; Seanix
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_00144CA1   ; Seanix
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_00154CA1   ; Seanix
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_00164CA1   ; Seanix
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_00174CA1   ; Seanix
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_00184CA1   ; Seanix
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_00194CA1   ; Seanix
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_001A4CA1   ; Seanix
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_001B4CA1   ; Seanix
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_001C4CA1   ; Seanix
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_001D4CA1   ; Seanix
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_001E4CA1   ; Seanix
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_001F4CA1   ; Seanix

; Sharp
%ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_180613BD   ; Sharp DJ-P/ME1



[STUB_DEVICE]

[ES1371]
Include=   ks.inf, wdmaudio.inf
Needs=     KS.Registration, WDMAUDIO.Registration
CopyFiles=ES1371.CopyList
AddReg=ES1371.AddReg

[ES1370]
Include=   ks.inf, wdmaudio.inf
Needs=     KS.Registration, WDMAUDIO.Registration
CopyFiles=ES1370.CopyList
AddReg=ES1370.AddReg

[ES1371.Interfaces]
AddInterface=%KSCATEGORY_AUDIO%,%KSNAME_Wave%,       W_ES1371.Interface.Wave
AddInterface=%KSCATEGORY_RENDER%,%KSNAME_Wave%,      W_ES1371.Interface.Wave
AddInterface=%KSCATEGORY_CAPTURE%,%KSNAME_Wave%,     W_ES1371.Interface.Wave
AddInterface=%KSCATEGORY_AUDIO%,%KSNAME_Topology%,   W_ES1371.Interface.Topology
AddInterface=%KSCATEGORY_TOPOLOGY%,%KSNAME_Topology%,W_ES1371.Interface.Topology
AddInterface=%KSCATEGORY_AUDIO%,%KSNAME_UART%,       W_ES1371.Interface.UART
AddInterface=%KSCATEGORY_RENDER%,%KSNAME_UART%,      W_ES1371.Interface.UART
AddInterface=%KSCATEGORY_CAPTURE%,%KSNAME_UART%,     W_ES1371.Interface.UART

[ES1370.Interfaces]
AddInterface=%KSCATEGORY_AUDIO%,%KSNAME_Wave%,       W_ES1370.Interface.Wave
AddInterface=%KSCATEGORY_RENDER%,%KSNAME_Wave%,      W_ES1370.Interface.Wave
AddInterface=%KSCATEGORY_CAPTURE%,%KSNAME_Wave%,     W_ES1370.Interface.Wave
AddInterface=%KSCATEGORY_AUDIO%,%KSNAME_Topology%,   W_ES1370.Interface.Topology
AddInterface=%KSCATEGORY_TOPOLOGY%,%KSNAME_Topology%,W_ES1370.Interface.Topology
AddInterface=%KSCATEGORY_AUDIO%,%KSNAME_UART%,       W_ES1370.Interface.UART
AddInterface=%KSCATEGORY_RENDER%,%KSNAME_UART%,      W_ES1370.Interface.UART
AddInterface=%KSCATEGORY_CAPTURE%,%KSNAME_UART%,     W_ES1370.Interface.UART

[W_ES1371.Interface.Wave]
AddReg=W_ES1371.Interface.Wave.AddReg

[W_ES1371.Interface.Wave.AddReg]
HKR,,FriendlyName,,%W_ES1371.Wave.szPname%
HKR,,CLSID,,%Proxy.CLSID%

[W_ES1370.Interface.Wave]
AddReg=W_ES1370.Interface.Wave.AddReg

[W_ES1370.Interface.Wave.AddReg]
HKR,,FriendlyName,,%W_ES1370.Wave.szPname%
HKR,,CLSID,,%Proxy.CLSID%

[W_ES1371.Interface.Topology]
AddReg=W_ES1371.Interface.Topo.AddReg

;; warning!! must be "Topo" because "Topology" is too long
[W_ES1371.Interface.Topo.AddReg]
HKR,,FriendlyName,,%W_ES1371.Topology.szPname%

[W_ES1370.Interface.Topology]
AddReg=W_ES1370.Interface.Topo.AddReg

;; warning!! must be "Topo" because "Topology" is too long
[W_ES1370.Interface.Topo.AddReg]
HKR,,FriendlyName,,%W_ES1370.Topology.szPname%

[W_ES1371.Interface.UART]
AddReg=W_ES1371.I.UART.AddReg

[W_ES1371.I.UART.AddReg]
HKR,,FriendlyName,,%W_ES1371.UART.szPname%
HKR,,CLSID,,%Proxy.CLSID%

[W_ES1370.Interface.UART]
AddReg=W_ES1370.I.UART.AddReg

[W_ES1370.I.UART.AddReg]
HKR,,FriendlyName,,%W_ES1370.UART.szPname%
HKR,,CLSID,,%Proxy.CLSID%

[ES1371.AddReg]
HKR,,AssociatedFilters,,"wdmaud,swmidi,redbook"
HKR,,Driver,,es1371mp.sys
HKR,,NTMPDriver,,"es1371mp.sys,sbemul.sys"

HKR,Drivers,SubClasses,,"wave,midi,mixer,aux"

HKR,Drivers\wave\wdmaud.drv, Driver,,wdmaud.drv
HKR,Drivers\midi\wdmaud.drv, Driver,,wdmaud.drv
HKR,Drivers\mixer\wdmaud.drv,Driver,,wdmaud.drv
HKR,Drivers\aux\wdmaud.drv,Driver,,wdmaud.drv

HKR,Drivers\wave\wdmaud.drv, Description,,%*ES1371.DeviceDesc%
HKR,Drivers\midi\wdmaud.drv, Description,,%*ES1371.DeviceDesc%
HKR,Drivers\mixer\wdmaud.drv,Description,,%*ES1371.DeviceDesc%
HKR,Drivers\aux\wdmaud.drv,Description,,%*ES1371.DeviceDesc%

[ES1370.AddReg]
HKR,,AssociatedFilters,,"wdmaud,swmidi,redbook"
HKR,,Driver,,es1370mp.sys
HKR,,NTMPDriver,,"es1370mp.sys,sbemul.sys"

HKR,Drivers,SubClasses,,"wave,midi,mixer,aux"

HKR,Drivers\wave\wdmaud.drv, Driver,,wdmaud.drv
HKR,Drivers\midi\wdmaud.drv, Driver,,wdmaud.drv
HKR,Drivers\mixer\wdmaud.drv,Driver,,wdmaud.drv
HKR,Drivers\aux\wdmaud.drv,Driver,,wdmaud.drv

HKR,Drivers\wave\wdmaud.drv, Description,,%*ES1370.DeviceDesc%
HKR,Drivers\midi\wdmaud.drv, Description,,%*ES1370.DeviceDesc%
HKR,Drivers\mixer\wdmaud.drv,Description,,%*ES1370.DeviceDesc%
HKR,Drivers\aux\wdmaud.drv,Description,,%*ES1370.DeviceDesc%

[DestinationDirs]
ES1371.CopyList         = 10,system32\drivers ; %SystemRoot%\system32\drivers
ES1370.CopyList         = 10,system32\drivers ; %SystemRoot%\system32\drivers

[ES1371.CopyList]
es1371mp.sys

[ES1370.CopyList]
es1370mp.sys

;;**************** NT Install ****************

[STUB_DEVICE.NTX86]
[STUB_DEVICE.NTX86.SERVICES]
AddService=,0x2

[ES1371.NTX86]
Include=ks.inf, wdmaudio.inf
Needs=KS.Registration, WDMAUDIO.Registration
CopyFiles=ES1371.CopyList
AddReg=ES1371.AddReg

[ES1370.NTX86]
Include=ks.inf, wdmaudio.inf
Needs=KS.Registration, WDMAUDIO.Registration
CopyFiles=ES1370.CopyList
AddReg=ES1370.AddReg

[ES1371.NTX86.Interfaces]
AddInterface=%KSCATEGORY_AUDIO%,%KSNAME_Wave%,       W_ES1371.Interface.Wave
AddInterface=%KSCATEGORY_RENDER%,%KSNAME_Wave%,      W_ES1371.Interface.Wave
AddInterface=%KSCATEGORY_CAPTURE%,%KSNAME_Wave%,     W_ES1371.Interface.Wave
AddInterface=%KSCATEGORY_AUDIO%,%KSNAME_Topology%,   W_ES1371.Interface.Topology
AddInterface=%KSCATEGORY_TOPOLOGY%,%KSNAME_Topology%,W_ES1371.Interface.Topology
AddInterface=%KSCATEGORY_AUDIO%,%KSNAME_UART%,       W_ES1371.Interface.UART
AddInterface=%KSCATEGORY_RENDER%,%KSNAME_UART%,      W_ES1371.Interface.UART
AddInterface=%KSCATEGORY_CAPTURE%,%KSNAME_UART%,     W_ES1371.Interface.UART

[ES1370.NTX86.Interfaces]
AddInterface=%KSCATEGORY_AUDIO%,%KSNAME_Wave%,       W_ES1370.Interface.Wave
AddInterface=%KSCATEGORY_RENDER%,%KSNAME_Wave%,      W_ES1370.Interface.Wave
AddInterface=%KSCATEGORY_CAPTURE%,%KSNAME_Wave%,     W_ES1370.Interface.Wave
AddInterface=%KSCATEGORY_AUDIO%,%KSNAME_Topology%,   W_ES1370.Interface.Topology
AddInterface=%KSCATEGORY_TOPOLOGY%,%KSNAME_Topology%,W_ES1370.Interface.Topology
AddInterface=%KSCATEGORY_AUDIO%,%KSNAME_UART%,       W_ES1370.Interface.UART
AddInterface=%KSCATEGORY_RENDER%,%KSNAME_UART%,      W_ES1370.Interface.UART
AddInterface=%KSCATEGORY_CAPTURE%,%KSNAME_UART%,     W_ES1370.Interface.UART

[ES1371.NTX86.Services]
AddService = es1371,  0x00000002, es1371_Service_Inst

[ES1370.NTX86.Services]
AddService = ES1370,  0x00000002, ES1370_Service_Inst

[es1371_Service_Inst]
DisplayName    = %ES1371.SvcDesc%
ServiceType    = 1                  ; SERVICE_KERNEL_DRIVER
StartType      = 3                  ; SERVICE_DEMAND_START
ErrorControl   = 1                  ; SERVICE_ERROR_NORMAL
ServiceBinary  = %10%\system32\drivers\es1371mp.sys

[ES1370_Service_Inst]
DisplayName    = %ES1370.SvcDesc%
ServiceType    = 1                  ; SERVICE_KERNEL_DRIVER
StartType      = 3                  ; SERVICE_DEMAND_START
ErrorControl   = 1                  ; SERVICE_ERROR_NORMAL
ServiceBinary  = %10%\system32\drivers\ES1370MP.sys


[Strings]
MSFT="Microsoft"
MfgName="Creative Technology Ltd."
ES1371.DeviceDesc="Creative AudioPCI (ES1371,ES1373) (WDM)"
*ES1371.DeviceDesc="Creative AudioPCI (ES1371,ES1373) (WDM)"
ES1370.DeviceDesc="Creative AudioPCI (ES1370), SB PCI 64/128 (WDM)"
*ES1370.DeviceDesc="Creative AudioPCI (ES1370), SB PCI 64/128 (WDM)"
W_ES1371.Wave.szPname="Creative Sound Blaster PCI"
W_ES1371.Topology.szPname="Creative Sound Blaster PCI"
W_ES1371.UART.szPname="Creative Sound Blaster MPU-401"
W_ES1370.Wave.szPname="Creative Sound Blaster PCI"
W_ES1370.Topology.szPname="Creative Sound Blaster PCI"
W_ES1370.UART.szPname="Creative Sound Blaster MPU-401"

*MS.MPU401.DeviceDesc="Microsoft MPU Audio Driver(WDM)"

MediaCategories="SYSTEM\CurrentControlSet\Control\MediaCategories"
WDM_MIDI="WDM-based Device"

Proxy.CLSID        ="{17CCA71B-ECD7-11D0-B908-00A0C9223196}"
KSCATEGORY_AUDIO   ="{6994AD04-93EF-11D0-A3CC-00A0C9223196}"
KSCATEGORY_RENDER  ="{65E8773E-8F56-11D0-A3B9-00A0C9223196}"
KSCATEGORY_CAPTURE ="{65E8773D-8F56-11D0-A3B9-00A0C9223196}"
KSCATEGORY_TOPOLOGY="{DDA54A40-1E4C-11D1-A050-405705C10000}"

KSNAME_Wave="Wave"
KSNAME_UART="UART"
KSNAME_Topology="Topology"
KSNAME_Wavetable="Wavetable"

WDM.UART.szPname="SBPCI MPU-401"

ES1371.SvcDesc = "Creative AudioPCI (ES1371,ES1373) (WDM)"
ES1370.SvcDesc = "Creative AudioPCI (ES1370), SB PCI 64/128 (WDM)"

I know it fails because in setuplog.log in C:\WINDOWS I have this line:

04/09/2007 20:28:39,d:\nt\base\ntsetup\syssetup\syspnp.c,5364,,SETUP: SetupDiCallClassInstaller(DIF_INSTALLDEVICE) failed. Error = e0000217, Device = Creative Sound Blaster AudioPCI 128D (WDM)

Go to forum: DriverPack Sound

34 Reply by LeveL

(9 replies, posted in DriverPack Sound)

OverFlow wrote:

you could call the sound blaster setup program

You mean the program thats inside the C:\SBPCI folder?

When I try that, it only has a "remove" option. So I remove
it and a DLL file disappears out of that SBPCI folder. There
are only three files inside it to begin with.

The problem seems to be that the card is "half installed" because
in Device Manager you don't get a yellow triangle (not instaled)
but its a yellow circle (the device has a problem).

It is installed, half way, because you only need those two very
small files, wdma_ens.inf (26Kb) and es1371mp.sys (40Kb) to
make it work.

All I need is some way to silently install those 2 files after everything
else has finished running and it would work, I don't know of any way
(with the one INF and one SYS file) to install the driver, but I guess
there must be some way of doing that, I just haven't found out how.

Go to forum: DriverPack Sound

35 Reply by LeveL

(9 replies, posted in DriverPack Sound)

elbrute wrote:

@ Level
No, I'm installing XPsp2 on a machine with a SB PCI card.

Dave

I can't believe it, it just won't install no matter what I do.

I also do get the SBPCI folder on my C: drive.

Whats funny is, this does work if I put these two files in a folder
and do it from WINNT.SIF the old "OemPnPDriversPath" way:

wdma_ens.inf
es1371mp.sys

Thats it! It is only those 2 files! I think it is getting mixed up somewhere
you know, because there are so many sound drivers in Bashrats packs?

wdma_ens.inf is in I386, it is cabbed so its called "wdma_ens.in_" and you'd have to uncab it.
es1371mp.sys is in DRIVER.CAB, so you'd have to open that with WinRAR and drag out that one file.

So for this device ---> Creative Sound Blaster AudioPCI 128D (WDM)
this is confirmed not to work on both these setups:

1 - Windows Server 2003 installed in VMware.
2 - Windows XP with a hardware card version of the same device.

I just tested this manually installing from Device Manager and all I needed was these two files:

wdma_ens.inf (26Kb)
es1371mp.sys (40Kb)

Look at how tiny those files are and yet it just won't install with Windows when Windows installs!

AAAAAAAAAAAGH BUT WHY WHY WHY WHY WHY WHATS STOPPING IT?!?!

This is actually driving me mad. sad

Something I still want to know - is there a way, like from the command line, to install
drivers after Windows has installed? I mean a similar (or even the same) method that
Windows itself uses like the "OemPnPDriversPath" method? How does it do that? If you
do it in Windows afterwards you need to do it all through Device Manager, but I am sure
there must be some way to do it in an unattended way? Doing this would solve the
sound card problem in an instant!

Go to forum: DriverPack Sound

36 Reply by LeveL

(9 replies, posted in DriverPack Sound)

I can confirm that yes, this is the exact same driver thats in VMware:

Creative Sound Blaster AudioPCI 128D (WDM)

@ elbrute: Are you installing Windows Server 2003 in VMware?

If you are installing XP in VMware then this driver should be installed by
default, without driverpacks even needed, at least it always has done
for me.

I found this topic because I have this exact failure in my setuplog.log for Windows.

04/08/2007 22:41:20,d:\nt\base\ntsetup\syssetup\syspnp.c,5364,,SETUP: SetupDiCallClassInstaller(DIF_INSTALLDEVICE) failed. Error = e0000217, Device = Creative Sound Blaster AudioPCI 128D (WDM)

I really don't know what to do to get this sucker to install!

I used "Driver Genius professional 2007" after installing the sound driver through
Device Manager. This is the kicker - it DOES install through Device Manager, theres
no issue with it being "unsupported" because it will install the driver, with no complaints
from Windows or the drivers themselves whatsoever, if you install it afterwards through
Device Manager) the files Driver Genius Professional 2007 spat out for this device amounted
to about 14Mb of files! WHY? You only need ONE SYS FILE AND ONE INF FILE for this in XP!

However, you can put those 2 files in a 3rd party Driverpack, do it however you want,
it REFUSES to install. Honestly, I am on the verge of doing stupid s**t here like standing
on my hands whilst it installs, maybe cast a spell over it, pray for it, I dunno, I have done
everything else...

Go to forum: DriverPack Sound

37 Reply by LeveL

(9 replies, posted in DriverPack Sound)

OK... VMware and the sound driver issue...

I was just looking though my setup logs for Server 2003 and setuperr.log is
a 0Kb file - in other words there were no errors during setup. But when I search
the other setup log "setuplog.txt" for "audio" I have ONE single failure regarding
the sound device in VMware = Creative Sound Blaster AudioPCI 128D (WDM)...

The following (broken down into seperate lines, but all this is on one line).....

04/08/2007 22:41:20
d:\nt\base\ntsetup\syssetup\syspnp.c,5364,,SETUP: SetupDiCallClassInstaller(DIF_INSTALLDEVICE) failed.
Error = e0000217, Device = Creative Sound Blaster AudioPCI 128D (WDM)

There are 5 lines for "Creative Sound Blaster AudioPCI 128D (WDM)" and only one of the
lines says "failed".

I wonder if Bashrat ever did hack those drivers? (whistle.gif!)

I would certainly test them if he did.

You know whats REALLY annoying about it? You can manually install these drivers from
Device Manager so it isn't that these drivers won't work, they do definitely work because
I can install them! It does not even say the drivers are untested (like it does on XP for my
modem drivers on my real system, for example) so i am sure there is some other wierd
issue here, it is NOT because the drivers are "bad" or anything, because they DO install
and the sound does work, with not one single complaint, as long as you do it from Device
Manager afterwards, which kinda defeats the object of what this whole thing is all about huh?!

If there is some other device in VMware other than "Creative Sound Blaster AudioPCI 128D (WDM)"
then what is it?!

Go to forum: DriverPack Sound

38 Reply by LeveL

(10 replies, posted in Feedback and Support - DriverPacks Base)

Helmi wrote:
LeveL wrote:

The reason Bashrats driverpacks won't support your devices
on Server 2003 is because the native support that is in XP
for many onboard sound devices, is simply not there in
Server 2003. I guess the driverpacks BASE relies on whats
in XP.

Just a wild guess here, but could that be related to the HDA hotfix?

Many newer onboard devices are HDa now instead of the older AC'97 standard.
To get them to work (or even the device reckognized so you can install the driver) the hotfix needs to be applied first.
IDK how the situation is with Server2k3, either it requies a different hotfix or it is somehow not compatible with DriverPacks otherwise.

Its Server 2003 SP2 with all hotfixes slipstreamed into the source.

The silly thing is, I can install the XP drivers on Server 2003 if I do it the old
way - Method 1 with OemPnPDriversPath, but then I have to drastically cut
down on the driverpacks used because it goes over the 4096 character limit.

If I make a "3rd party Driverpack" it does not work. I can't work out why.

Go to forum: Feedback and Support - DriverPacks Base

39 Reply by LeveL

(58 replies, posted in 3rd Party DriverPacks)

Can't get my "3rd party DriverPack" to work on Server 2003!

Heres what I did:

Made these folders on my desktop:

XP\DRIVER_CAB
2003\DRIVER_CAB

XP\INI_CAT_INF_SYS
2003\INI_CAT_INF_SYS

1 - Extracted the Server 2003 "DRIVER.CAB" into "2003\DRIVER_CAB\"

2 - Extracted the XP "DRIVER.CAB" into "XP\DRIVER_CAB\"

3 - Searched XP/I386 for ".cat + .inf + .sys + ca_ + .in_ + .sy_" files.

4 - Extracted the cabbed files and copied the normal (uncabbed files) to: XP\INI_CAT_INF_SYS

5 - Did the same as #4 but for "2003"

6 - Copied the files from XP into the folders for Server 2003, saying "no" too overwriting,
to catch all the files that are in XP but not in Server 2003.

So, I have all the INF, CAT, SYS files that are in XP but not in Server 2003 > all in one folder...

D\3\XP\[All Files]

I make the 7-Zipped archive on "Ultra" compression, with dictionary size of 256.

I make my ISO.

I install my ISO and I can see indeed, there are 11 driverpacks! So my custom pack
is indeed extracting to the systemdrive.

sad When Windows has installed, the sound driver is not installed in VMware. Also, this
has STOPPED the network connectivity (internet) as well!

All I need to know is - is there something wrong with my folder structure?

I tried:

D\3\XP\[All Files] and also D\3\R\XP\[All Files] and nither one works.

Whats funny is on a standard install, without driverpacks, the ethernet in VMware,
with Server 2003, does work. Sound drivers never work, unless I use Method 1
and put the sound drvers in "$1\D\XPD" but forget that, my path is over 6000
characters doing it that way!

I guess I could leave out all the graphics drivers and WLAN... then maybe my path
for "OemPnPDriversPath" will be OK and I can add the XP drivers that way, I have
already tried it that way and I know it works.

Wish I could work this out, I have been trying for 2 days, ever since DriverPacks v7.04

OK heres a few things: I know for definite this is not failing because of Server 2003,
I know this because the old "OemPnPDriversPath" way of installing the sound drivers
does work, as long as the path starts with "D\XPD;" even if its well under the 4096 limit
it doesn't matter, if the XPD folder is specified at the END of that path it doesn't work, if
its specified at the beginning, it does work.

I am only talking about VMware, as a test case, because in XP the sound driver does install
in VMware, in Server 2003 it does not install the sound driver, I mean on standard installs
without driverpacks.

Heres a question then: Is there any way of installing drivers silently like this but AFTER the installation?
A way of making Windows do what it does during setup when it uses OemPnPDriversPath from WINNT.SIF
but after DpsFnshr.exe has done its work?

Its just so frustrating to know it should be working and isn't.

Sorry Bashrat, I never even keep my log file... I will make an ISO that does not remove
the log file and see....

Go to forum: 3rd Party DriverPacks

40 Topic by LeveL

(2 replies, posted in DriverPack Sound)

I can install an "untouched" Windows XP in VMware and
it will install the sound driver, I have the volume icon in
my system tray and nothing in Device Manager has any
problems.

I have slipstreamed all driverpacks including "Sound A" and
"Sound B" and now, the sound driver has not installed at all.

This was tested on:

Windows XP Professional SP2
Windows Server 2003 Enterprise SP2
Windows Server 2003 Datacenter SP2

I can understand it in Server 2003 but in XP?

I am totally perplexed by this.

I am going to try "Method 1" instead (although then I will have to drastically
cut down on the driverpacks used, because of the 4096 character limit) and
if that doesn't work, I don't know, I just haven't got a clue what could be causing
XP to not even have its own native driver support anymore???

1 - No, I did not remove any drivers with nLite.

2 - I am using the brand new v7.04 of the driverpacks.

Go to forum: DriverPack Sound

41 Reply by LeveL

(10 replies, posted in Feedback and Support - DriverPacks Base)

Server 2003 is a pain, I can't get my third party driverpack to
install the drivers, but like MatthiasAK did - I can unpack this
and manually install the drivers via Device Manager and it
works.

The reason Bashrats driverpacks won't support your devices
on Server 2003 is because the native support that is in XP
for many onboard sound devices, is simply not there in
Server 2003. I guess the driverpacks BASE relies on whats
in XP.

Go to forum: Feedback and Support - DriverPacks Base

42 Reply by LeveL

(58 replies, posted in 3rd Party DriverPacks)

Wow, this looks incredibly easy!

Whats always been missing for me (its a specialist thing I guess) is a pack
with all the drivers that are in XP but not in Server 2003. This includes a LOT
of sound drivers, but other things like scanners and cameras too... with this
tutorial I have made a pack for Server 2003 that has all the files from XP's
DRIVER.CAB that are not in Server 2003, all the INF/INI files in XP that are
not in Server 2003 and all the CAT files... all these files, SYS, INF, INI, CAT,
EXE are all dumped into ONE folder... this folder is called "X" and goes here
like this:

D\3\R\X\[all files]

This folder is 102Mb and has 973 files inside! When it is 7-Zipped
it is only 21Mb. I can live with that... now lets see how it works...

Waaaaaaaaaaa! It didn't work.

OK now I am trying this way...

D\3\XP\[all files]

I hate Server 2003, I actually hate it. sad

Go to forum: 3rd Party DriverPacks

43 Reply by LeveL

(9 replies, posted in DriverPack Sound)

Soundblaster drivers do work on Server 2003.

I install Server 2003 in two scenarios:

1 - In VMware
2 - On my real machine.

In DRIVER.CAB for XP it contains something like 500 or 600 files that are
not in the Server 2003 DRIVER.CAB.

In VMware for example, Server 2003 Enterprise will not install the onboard Creative sound drivers,
you have to get the XP driver and it works.

On my real machine however, my onboard sound works, it is hit and miss which is why I am
opening a new topic to request... something wink

Go to forum: DriverPack Sound

44 Reply by LeveL

(15 replies, posted in Feedback and Support - DriverPacks Base)

Also getting this same error.

Line 0 (File "C:\DPsFnshr.exe"):
for $i=1 to $exceptions[0][0]
for $i=1 to $exceptions^ ERROR
Error: Subscript used with non-Array variable.

It applies to XP and Server 2003, multi boot or non multi boot.

It does not happen if you slipstream ALL driverpacks, but seems to
always happen with any combination of the others! It is driving me crazy sad

Does this shed any light on the matter:

http://www.autoitscript.com/forum/index … opic=35036

What other versions of the driverpacks BASE can I use?

I know its a v6.10 error because people have said they didnt get it with v6.08.

Go to forum: Feedback and Support - DriverPacks Base

45 Reply by LeveL

(9 replies, posted in Feedback and Support - DriverPacks Base)

Also getting this same error.

Line 0 (File "C:\DPsFnshr.exe"):
for $i=1 to $exceptions[0][0]
for $i=1 to $exceptions^ ERROR
Error: Subscript used with non-Array variable.

It applies to XP and Server 2003, multi boot or non multi boot.

It does not happen if you slipstream ALL driverpacks, but seems to
always happen with any combination of the others! It is driving me crazy sad

Does this shed any light on the matter:

http://www.autoitscript.com/forum/index … opic=35036

What other versions of the driverpacks BASE can I use?

I know its a v6.10 error because people have said they didnt get it with v6.08.

Go to forum: Feedback and Support - DriverPacks Base

46 Reply by LeveL

(8 replies, posted in Feedback and Support - DriverPacks Base)

I spoke too soon, I tried integrating 4 driverpacks - Chipset, CPU, MassStorage and LAN.

I only had those 4 driverpacks in the driverpacks folder.

I still get the same error just before Windows logs in for the first time:

Line 0 (File "C:\DPsFnshr.exe"):
for $i=1 to $exceptions[0][0]
for $i=1 to $exceptions^ ERROR
Error: Subscript used with non-Array variable.

I can't understand why I get this error! Its driving me crazy!

Go to forum: Feedback and Support - DriverPacks Base

47 Reply by LeveL

(8 replies, posted in Feedback and Support - DriverPacks Base)

I will try what you said jtdoom, indeed I did have all seven packs
in the driverpacks folder and only included certain packs, I will try
it again only including the relevent packs and if that gives this same
error I will post the log, but I have a feeling this is whats causing it,
having packs there I don't need to have, thanks for the wise words!

Go to forum: Feedback and Support - DriverPacks Base

48 Topic by LeveL

(8 replies, posted in Feedback and Support - DriverPacks Base)

Using Windows Server 2003 - full (not nLite'd) OS.

If I slipstream every driverpack, I get no problems.

If I slipstream any other combination of driverpacks, for instance
only the MassStorage pack, I get this error...

http://img407.imageshack.us/img407/7407 … rorgs7.png

This comes up just before Windows logs in for the first time.

Using the latest BASE (v6.10) to do this.

Post #9 here explains the exact same thing, but theres no replies after that...

http://forum.driverpacks.net/viewtopic.php?pid=5674

This thread explains the same thing but again, theres no solution to it...

http://forum.driverpacks.net/viewtopic.php?id=748

Go to forum: Feedback and Support - DriverPacks Base