Bâshrat the Sneaky

BTS DriverPacks BASE V5.04.6 Download All bugs are fixed + some improvements Changelog: V5.04.6 (07 Apr 05) -Changed: unified batch file for ALL control panels! (Note: the current DriverPacks still contain there own cpl batch files. These will simply be ignored!) -Changed: default tagfile for method 2, to get default support for Multi-Boot CDs/DVDs. -Fixed: automatical removal of the KB888111 hotfix. -Fixed: portcls.sys (part of the KB888111 hotfix) wasn't copied when using DP Sound A. -Fixed: method selection was completely messed up, lots of errors occurred because of it... -Fixed: ATI FireGL controlpanel

... and the new version is there

I already included a HP driver... **** man, how many different SoundMAX drivers are there? Please provide me with a downloadlink after your (99% chance) successful test!

@Rickie: link not working

Topic title changed, was against the rules. Also I chose a better topic title.

Sry muiz, I looked over that one. I'm adding something new (in fact a change) to V5.04.6: unified control panels batch file. This way you guys will be able to easily edit it. And I won't have to release a new DP just for a changed batch file... I hope you guys like this change...

I can't find it... I WISH I had SLI Use RegShot or RegSnap to determine the changes in the registry after enabling/disabling it.

Then add them to drvindex.inf as well. Didn't you get any error?

Isn't it the software that activates it?

The controlpanels batchfiles must be executed at the first Windows boot. This can however also be imported using cmdlines.txt. Don't forget to add the cleanup (deleting %SystemDrive%\DP). Those are the only references in the winnt.sif, please try without them and let me know. EDIT: topic moved to correct forum.

@muiz: sry forgot about that, I'll check it now, I'll edit this post in a few minutes. EDIT: now WTF is that... you seem to be the one with the most odd errors!!! To be honest, I have absolutely no idea... maybe it's because of too many erroneus slipstreams because of the bugs in the unfixed version of V5.04.5.... Try V5.04.6 later today. @erik_demon: may god bless you! Thanks @A|ex: check the fixed version 1 page back. Or wait some time for V5.04.6 (it will be released tonight).

*maybe* it fixes that too. Not sure about that though.

OK... Then try to disable the VIAMRAID controller in your BIOS, instead of removing those lines. However you can also remove the lines if you prefer that.

@Yzöwl: we're trying to get it to work for the DriverPacks, that's why it's here

No it ISN'T right. The file should be copied from the KB888111 folder to the I386 folder! Doing tests on this issue and then I'll upload V5.04.6

Please *attach* your winnt.sif file. Are you very sure it's popping up that window because it can't FIND the required driver or is it because the driver isn't WHQL SIGNED?

You'll also have to add it to dosnet.inf to get it to work with BartPE or network installations

So you got it all figured out, or do you still have some issues???

@Yzöwl: please use the fixed version that I posted on the previous page There this problem is fixed. @Ghostrider: huhhhhh? Now what's that? :s Are you sure everything went right? I think you're quite familiar with this process? Please check if everything in the OEM folder is ok... I did a test installation with this yesterday without any problems :s

Yes, I also thought of that... But then again, you can adapt this method so much that it works totally different and then it won't work like that But... that would be rather rare... So I'll change the default one to \OEM.

Thank you for testing and confirming Another bug fixed

They both leave files? I've just integrated it for someone with remote assistance and it worked flawlessy... method 2... You have to download the fix, paste it in the DPs BASE folder and overwrite the old file. Then you have to start again from step 1

oh... wel that's what I asked several posts ago, but I didn't get the answer... I asked if you were talking about the MassStorage section of the winnt.sif file, no answer, so I supposed it was a 'yes'... I don't know about that file... Never seen it. Please start a new topic in the DriverPacks General Discussion and attach that sysprep.inf file, with the system-default examples included.

I think you still didn't get what I'm saying. Currently the ASUS driver *IS* being used, I'm trying to avoid using it because that driver only works on ASUS mobo's.

Fixed version posted. Please post next time in the main thread. Topic closed!