Bâshrat the Sneaky

Hmm... maybe these drivers aren't well coded... or not well included in the DriverPack. Are you sure there aren't any problems with either of those options?

Hmmm.... I cooperated with RyanVM on the slipstream procedure for this hotfix. It seemed the .cat file didn't protect ANY of the files it included, i.e. it only existed because a hotfix should contain a .cat file! And... could you (or anyone else of course) tell me what the version of portcls.sys is if you ONLY slipstream RyanVM's UpdatePack? I'll get in touch with RyanVM ASAP!

Hm... please post your problem in detail in the DriverPack MassStorage forum!

Fencer128, the reason for placing the portcls.sys file in the I386 dir is that is the easiest method: the original portcls.sys file is ALSO in the I386 dir and therefor I only have to rename the old portcls.sys files (to keep it as a backup) and I add this entry to dosnet.inf: [ForceCopyDriverCabFiles] "portcls.sys" That ensures it will be used. However, I strongly doubt my explanation is complete and completely correct, since I cannot seem to find the portcls.sys file in my I386 dir! :s Then why didn't setup complain?? (I used this UWXPCD IRL....)

DriverPack LAN V5.10.1 Supported devices. Changelog: V5.10.1 (12 Oct 05) -Updated: Marvell Yukon driver from 08/23/2005, 8.39.3.3 to 09/19/2005, 8.41.1.3. -Updated: Realtek 8139(A/B/C/D/8130)/810X/8169/8169S(B)/8110S(B) driver from 05/16/2005,5.621.0304.2005 [6.21] to 09/23/2005,5.635.0923.2005 [6.35]. Download

BTS DriverPacks BASE V5.10.2 Changelog: V5.10.2 (12 Oct 05) -Fixed: [DPB]: RUN_ME.cmd: KB888111 presence check was broken. V5.10.1 (02 Oct 05) -Fixed: [DPB]: M2: presetup.cmd file was missing. V5.10 (01 Oct 05) -Fixed: [DPB]: KB888111 problems when using RyanVM's UpdatePack and the DriverPacks. -Fixed: [DPB]: UpdateChecker: the DriverPacks' homepage URI has changed and therefor the UpdateChecker was broken. That's fixed in this version. -Fixed: [DPB]: all links in these offline files have been edited to point to the new DriverPacks' homepage URI and to uAwiki.org (that's the new place for the articles). Download Known issues -Bug|critical: [DPM]: nVidia nForce mass storage controllers & chipsets.

An update will be online very soon...

@Fencer128: This is what I have: SET T1=Fedit -add -once -create -f I386\DOSNET.INF -s Files -l %T1% "d1,hdaprop.dll" ... That means... it should add it only once, even if a identical entry already existed: it does NOT check if the existing entry had identical cases! @RogueSpear & Fencer128: Well, Fencer128 prooved RyanVM did NOT merge the hdaudio.sy_ file into I386\DRIVER.CAB. Are you very certain it is merged in your UWXPCD, RogueSpear? EDIT: Forgot to say I've fixed the KB888111 check issue, of course. An update will be online very soon...

Thanks, but next time please post it in the BTS DriverPacks - Supported Devices section at uAwiki.org , in your case that would have been here. Thanks. I added the reference to the Chipset on the main index, but did not know how to add the motherboard into it. No problem, I noticed your addition to the list for DriverPack LAN too, thanks again!

I haven't included any Bluetooth drivers, for now you'll have to do that yourself. As for the hotfix (that is the KB888111 hotfix): did you use DriverPack Sound A? Could you please check if the file I386\SVCPACK\KB888111.ca? exists?

It's ALOT more than just a 'PHP + MySQL version'! We all like a stable, fast and pretty site better than one with endless errors, right?

Of course! We're all human beings, right? We all face the same problems, so why not help each other?

@cybpsyc: thanks... when I downloaded the latest drivers just a couple of days ago, those weren't there yet... Can't they put it online just a... @jordi1984: thanks At least SOMEONE who enters his results in the uAwiki - where it should be entered!

Thanks, but next time please post it in the BTS DriverPacks - Supported Devices section at uAwiki.org , in your case that would have been here. Thanks.

@ZileXa: Unless you've made some modficiations to your txtsetup.sif, dosnet.inf and drvindex.inf files, you don't have to worry about anything: everything will be processed without overwriting your changes. And... Making some money out of it? How would you do that? Since you're not allowed to 'sell' your 'finished product': it's based on property of Microsoft. Personal use won't matter, but commercial will! @RogueSpear: **** you! At first, it was 'I386\SVCPACK\KB888111.ca?', but I've changed that to 'I386\SVCPACK\hdaudio.sy?' in V5.10, not noticing the SVCPACK folder! I'll fix that today... :deeply_ashamed: @RogueSpear & Fencer128: what entries are duplicate then? Fedit should remove duplicate entries!

Does your laptop have a floppy station? If yes, this is probably the easiest solution. If not, you'll have to slipstream the drivers. A tutorial can be found in this forum's "Read this first" sticky, the easiest is using my DriverPack MassStorage: check my signature.

hehe.... This seems to be the first Sound Blaster (budget Sound Blaster) that isn't included in the Audigy driver... I'll have to add a separate driver for it... when I find it. I've been looking for a while and Creative's site doesn't find anything. It's against my policy, but I'll have to use a driver from one of those driver sites, probably this one...

First of all, next time you should take care of your spelling, since your first sentence is far from correct English. You can find all answers in the here, in the tutorial at uAwiki.org. If you just don't know what GUIRunOnce or RunOnceEx are, I'd suggest you do some more reading! (GUIRunOnce and RunOnceEx )

I figured

Not enough memory! P.S.: wrong forum!

I'm sorry, but I have only returned since the end of September, and the last 1 and a half week we've had a huge amount of tests and tasks. That means ALOT less time than 1.5 months, at least for me. I will check Creative's driver tomorrow and compare your HWIDs. Promised.

Please e-mail it too BashratTheSneaky [at] gmail [dot] com.

hehe BTW, this is a problem I cannot solve, since this is related to the setup program and not to the DriverPacks.

This is VERY VERY odd. Thanks for your testing. Tomorrow, I'll do a test with all latest DriverPacks on a nForce 2 system (on a spare (old) HDD), I'm curious...!

OK, don't forget to post the results! (I'm sure you won't )