Bâshrat the Sneaky

@Bilou_Gateaux: I agree with your last sentence

I know. But ONLY THESE TWO types of devices didn't get installed properly. That's why I mentioned them All others install without any problem... N.B.: in fact I even forgot two: sometimes USB devices didn't install properly either!

You're right :s :blink I'll put a fixed version online.

You were ABLE TO DOWNLOAD them? As I seem to have the exact same problem as you!

Well, you're correct on all statements. But what can I do about it? The only thing I can do is removing that driver... Don't blame me, but those who wrote the drivers! I'll do a hwid comparison later.

And you ARE using an ASUS A8V mobo, right?

Nope, but nVidia GeForce Go IS! Still waiting for patje's updated Mobility Modder...

@Ghostrider & BAM & possyy_99: huh? I'll check it AGAIN... :s @ZileXa: thanks, I'll update it. @S0mE0nesMiNd1: that problem has been fixed! @iwod: which method did you use? @possy_99: Is that a quote from the DriverPacks BASE V5.04.10??? @zorro1 & colinbate: working on it... @bledd: the drivers that are included by default in Windows aren't included in the DriverPacks @mickmack & Astalavista & sixpack: thanks EDIT: @colinbate: huh? It IS online... Are you very sure, do you still have that error?

It's 7:05 AM here, have to get ready for school, so I can't post complete replies. But ... DID YOU GUYS USE THE LATEST DRIVERPACKS???? That's OBLIGATED!!!

lol In fact I wasn't But now it REALLY is working P.S.: next time I'll really tease

Thanks for that info! Very useful! Now I *probably* will do the update... I say probably, not for sure. And won't be for the next week I think, but I can do it within 2 weeks... (quite busy now...)

Fixed... sorry

DriverPack WLAN V5.04.3 Download @larciel: those are for the next version... thanks

DriverPack Sound B V5.04.3 Download

DriverPack Sound A V5.04.2 Download

DriverPack MassStorage V5.04.1 Download

DriverPack Graphics A V5.04.1 Download

DriverPack Graphics A V5.04.3 Download

BTS DriverPacks BASE V5.04.10 Download Changelog: V5.04.10 (19 Apr 05) -New: [DPB] option to keep the drivers in Windows [EXPERIMENTAL]. Thanks to schalti and again Pyron! -New: [DPB] Fedit.exe instead of AddLine.exe and RemoveAll.exe. Credits go again to djbe for this extremely useful utility! -Changed: [DPB] main folder name to save space in the OemPnPDriversPath. -Fixed: [DPM] missing entry for aliide.sys in txtsetup.sif, the very last error related to aliide.sys! -Fixed: [DPM] dosnet.inf [FloppyFiles.2] patching, solves a rare problem. I tested method 2 and I *think* everything works fine. For some odd reason my complete unattended Windows installation crashed: it installed smoothly, with no problems, but then all of a sudden it started again at T-39 (I last checked at T-22). After a reset, all I got was a black screen... (this was supposed to be my custom, fresh installed Windows...) Many thanks to djbe for Fedit.exe and to schalti and Pyron for SetupCopyOEMInf.exe! EDIT: You MUST update to the latest versions of all DriverPacks in order to use the DriverPacks BASE V5.04.10!!!

Yes, it is just normal... I should post an FAQ article...

The same date, of course..

Yes, that's correct. Is fixed in the next version, that I still have to test.

eh :blink That's more likely than a complete version mismatch, yes. I'll fix it in the next version!

OK, I told you guys I'd put V5.04.10 online tonight. In fact I CAN, but I WON'T, simply because I haven't had the chance to do ANY test with it... not much has changed, except the necessary changes from DP to D in all batch files. You might consider this a 'big' change, though. So the release will be for tomorrow then! (I hope so at least...)

Well you're the only one with this problem for now... At least for erik_demon it works fine, so I have absolutely no clue what could be causing this! Sorry...