Bâshrat the Sneaky

Please post here your problems/questions related to DriverPack Sound A V5.03.1!

DriverPack LAN V5.05.1 Supported devices. Changelog: V5.05.1 (08 May 05) -Updated: Marvell Yukon driver from 04/01/2005, 8.25.1.3 to 04/18/2005, 8.26.2.3 -Updated: Realtek 8139(A/B/C/D/8130)/810X/8169/8169S(B)/8110S(B) driver from 12/02/2004,5.620.1202.2004 [6.20] to 04/18/2005,5.621.0304.2005 [6.21] Download

Even in the title of THIS topic you can see the issue: immediately after a bracket ([) a capital character becomes a small one... Not an important bug, but rather annoying...

Please post here your problems/questions related to DriverPack MassStorage V5.03!

Let's discuss here how we could solve this... I think the only solution is to add ALL SoundMAX drivers; for the next release of DriverPack Sound B I've planned to add: -ADI SoundMAX -Dell SoundMAX -Intel SoundMAX Let's hope that will solve everything

The solution: 1) use the viamraid.sys driver for the 'general hwid' (that is, without 'SUBSYS'); 2) use the viasraid.sys driver for the special ASUS cases, pointing to their 'specific hwids' (WITH 'SUBSYS').

The solution: 1) include the SiI3114r5 driver; 2) list the SiI3114r5 driver EARLIER than the SiI3114r driver in the txtsetup.sif file.

Let's discuss here how we could solve this... EDIT: The solution: 1) use only 2 different 'cases' in the txtsetup.sif file instead of 1 per hwid; 2) use the newest driver (the one with the filter driver (nvcchflt.sys), this solved many problems.

DriverPack Graphics A V5.04.3 Download

What will be in the next version of MassStorage: nothing yet...Suggestions are welcome!P.S.: yes, this is the new style: not one topic for everything, but multiple, then it won't get as messy as before

DriverPack Sound A V5.05 Supported devices. Changelog: V5.04.2 (08 May 05) -Updated: Realtek AC'97 (ALC-101/201/202/203/250/650/655/658/850) from 03/25/2005,5.10.00.5820 [3.71] to 04/19/2005,5.10.00.5830 [3.72] -Updated: Realtek HD Audio (ALC880, ALC882, ALC260, ALC861) from 03/23/2005, 5.10.0.5122 [1.18a] to 04/15/2005, 5.10.0.5123 [1.19] Download

Still on the to-do list... I will post some info later today.

This is the script that I use. It searches the folder %FOLDER% recursively @ECHO OFF COLOR FC TITLE Compressing all drivers... if %1.==Sub. goto %2 SET FOLDER=YOURFOLDER FOR /R %FOLDER% %%a IN (*.*) DO (call %0 Sub makeIt "%%a") REM commands after compressing come here goto EXIT :makeIt setlocal for %%a in (%3) do set naam=%%~nxa for %%a in (%3) do set pad=%%~dpa if /I %naam:~-1%==_ goto end if /I %naam:~-3%==cat goto end if /I %naam:~-3%==inf goto end if /I %naam:~-3%==cmd goto end if /I "%naam%"=="somefile.exe" goto end ECHO. ECHO Compressing %naam%... set naam=%naam:~0,-1%_ MAKECAB /D CompressionType=LZX /D CompressionMemory=21 %3 "%naam%" > NUL DEL /F /Q %3 move "%naam%" "%pad%%naam%" endlocal goto end :EXIT EXIT :end the IF /I blabla things are exclusions; files that should NOT be compressed EDIT: some vars are in Dutch naam=name=filename pad=path BTW... the cabbed file is placed in the same folder as the original one, the original one is being deleted (deleted by 'DEL /F /Q %3')

Building Your Own DriverPack EDIT: updated the link: the tutorial has been moved to the uAwiki! I'll leave this topic open for suggestions!

hehe nice answer, Wraight

Thanks, jaxflmax I've been planning to add support for multiboot discs for some time now, but never really had the chance to because: nobody did _really_ know how to do it AND because I never used multiboot discs.j So please let me get this straight: you've put the OEM folder at the root of your multiboot disc, while the other files are simply put where they should: in the I386 folder. Is that ALL you did? (of course put the necessary files also in the (possible) other Windows XP shares)

256 for Windows 2000 4096 for Windows XP

I think this must be a name length issue... Please try this: replace VIARAID_VT3149_XP by VT3149

****... Why would ATI do that? Byebye Unified Driver Architecture...

I'll make a short tutorial The last week it's been asked alot, so I guess it's sort of a 'need' of the users of my DriverPacks

Hi danard, I did NOT replace the drivers in driver.cab, I ONLY replaced the driver in the I386 directory. Maybe that's the problem... But RyanVM once did the same with the ultra.sys driver (Promise Ultra controller), so I guess it *should* work, however, I cannot really test that part here. The '4 VS 3' part: I don't remember that by heart, I'll look it up, but I doubt this will make any difference. (Wasn't it '3' for a driver that's originally included in the Win XP disc, and a '4' for a driver you added (and that's compressed)?)

rcordorica, thanks for your testing, but I'd like to ask you to test one more thing: *remove* the nvraid.sys and nvatabus.sys entries in your txtsetup.sif file (so setup won't recognise them), and then try again with the NVRAID disabled. If THEN you will still get a BSOD, then there's a problem with the SiI3114r.sys driver

@gpwolfe: please post the hardwareIDs of both your nVRAID and SiI3114r controllers!

You should be SEARCHING the forums instead of bumping this topic! The optimising thing: the first paragraph says 'Defragment your pc'. Well.. that's not an optimisation for a 'music production pc', but for _every_ pc... You should know how to do that and if not, I'm sure you will find on the net (even in Windows help). Integrating drivers etc. : READ THE GUIDE!!!!!! Is this so difficult? Read, read, test, read, test, read, test, test, search, test, search, test and THEN you can ask! the guide: http://unattended.msfn.org

Hey, that's funny Didn't know that! Thanks