Bâshrat the Sneaky

@jeeva: a SKINNED cmd.exe? Do you have a screenshot of an example? :s

You're a 100% correct, BAM. I don't know which fool coded language detection that way, but it must be a fact that he was drunk when he did it! Currently still ~50% votes no...

LOL off-topic: have you ever seen a Chinese keyboard + Windows? It's unbelievable... They just use a English keyboard, they type some characters and then there's a pop-up with a list of possible Chinese characters. So then they have to make their choice between some... 20-30 characters again... :o RESPECT for those who know the Chinese language! on-topic (well sort of...) my Chinese is ... let's say... extremely rusty?

Eh... I screwed NONE Always used CD-RWs... now moving to DVD-RWs

Google showed NO results at all for that card :s Could you please tell me if it's a SiI3112 SATALink or a SiI3112r SATARAID? Which soundcard is that? Please check your device manager if there are any yellow exclamation marks. If not, I'm VERY happy At last one perfectly installed system (mine too, but...) I think/hope I'll get many of these reports from now on.

Well, then Windows will probably show some errors, at least if you remove some things.

Thank you, fixed now.

@erik_demon: hehe, I got some eh... info for you: The topic you link to, check the last post, Serialzs links to... a new topic with a new guide. Then read the 5th and 7th post and last but not least the 10th one. Eventually I've moved to Pyrons method because it was basically the same as Serialzs' his. But with the advantage that Pyrons was properly working... So in fact you are linking to my 'method 2' That's what I've been saying throughout this entire topic: why are you making it so difficult??? If you just remove the lines that reset the DevicePath to %SystemRoot%\Inf, you can keep on using my DriverPacks, though they will be in uncompressed form then... But what you could do is making a hybrid method: use method 1 + Pyron's method: let the presetup.cmd COPY the drivers to the harddisk. This is VERY easily done, just use method 1 and change 2 lines of the presetup.cmd. You won't have it actually 'slipstreamed' into Win XP, but it's very easy to accomplish. However, if you want to go on with the things you were working on, I won't stop you

You can remove WMP9 without problems, but you'll have to do that BEFORE you apply my DriverPacks. That's because nLite edits the txtsetup.sif, dosnet.inf and drvindex.inf files. Upgrading is easy: execute the UpdateChecker, it will automatically download and update the DriverPacks BASE files to the newest version. Then redo the entire slipstream process. If any DriverPack was slipstreamed before, it will remove them.

I will definetely NOT remove all the other languages. Why do all U.S. citizens (maybe also U.K.) that their language truly rules the world? Just CAN'T stand that... Do you really think everyone likes to have English everywhere?

Doh sorry, this isn't a DriverPacks topic... Well, when you use my DriverPacks, it's recomended to use the DriverPacks BASE to slipstream them, because then you won't have to do much (3 extremely easy steps), and since V5.04.4 I've added a feature that slipstreams KB888111 automatically.

I see I looked it up and you're right I'll add this 'optimization'

Remarks: not everything in this topic is completely new to me (and to others). To make it the 'official' way, you'll have to add entries to dosnet.inf, txtsetup.sif and drvindex.inf. (This can relatively easily be added to the current DPs BASE, as I'm already editing all these files.) About those txtsetup.sif values: it starts with 1 or 100, 1 means XP Vanilla, 100 means SP1 (maybe also SP2, so any SP?) I think the _3 is a IDE driver and the _4 is a RAID driver. Anyway, you can find lots of info at microsoft.com and gosh's site about .inf files.

Well, personally I agree with anonim1979 But I have to admit that it can be quite annoying to have the control panel in the language of your keyboard setup, while everything else is in English. It won't be too much extra work though. I'll leave this poll running for 7 or 14 days (we'll see).

@erik_demon: do you STILL have that error? I thought it'd be fixed now...

I think the drivers are identical, so I guess it should work. Please note that the nForce 4 MassStorage drivers aren't yet reported to work...

A quote from that thread: That's exactly what's integrated since DPs BASE V5.04.3 And... wrong topic

I know about that It's included in DPs BASE V5.04.4, including automatic slipstream system

BTS DriverPacks BASE V5.04.4 Download EDIT: I'll make a *second* exception and post the changelog, because the changes are worth mentioning changelog: V5.04.4 nothing except a fixed internal version number that caused too much trouble V5.04.3 (02 Apr 05) -New: automatic slipstream of the KB888111 hotfix for HD Audio compatibility (detects if it's already slipstreamed, only when using DriverPack Sound A), to make the installation of HD Audio drivers possible (currently only Realtek HD audio driver). -New: drvindex.inf patching (for DriverPack MassStorage). It also works without patching the drvindex.inf file, but this way the result is almost exactly the same as the original drivers included. -Changed: single filename for one driver. This means that I removed the specific names for specific hardwareids. This should help getting DriverPack MassStorage to work. -Fixed: aliide.sys error (experimental). -Fixed: when using method 1 and DriverPack Sound A & B, the entries in the winnt.sif file to install their control panels weren't added. EDIT2: and probably there will be some errors in txtsetup.sif. With such a large file to edit, the chance is very real that somewhere I've made a mistake (however I've TRIPLE checked). I don't have tried it yet, not enough time ATM... I will try it tomorrow... But in theory everything should work!

Doh... so easy... but strange enough it just didn't happen with method 2... Manual fix: 1. Edit the BTS_DPs_Slipstreamer_V5043.cmd 2. Search for this line: SET V=V5042 and change it to: SET V=V5043 ... or you can just wait 2 mins for V5.04.4 AGAIN a version number that I forgot to edit... :angry:

How is this possible :s I'll check it again... :'( EDIT: could you guys please specify? Method 1, of course, but did you update to the newest version? EDIT2: huh? You're right! WTF is this...

Please re-slipstream DP MassStorage using DPs BASE V5.04.3, it's got some interesting new features

BTS DriverPacks BASE V5.04.3 Download EDIT: I'll make a one time exception and post the changelog, because the changes are worth mentioning changelog: V5.04.3 (02 Apr 05) -New: automatic slipstream of the KB888111 hotfix for HD Audio compatibility (detects if it's already slipstreamed, only when using DriverPack Sound A), to make the installation of HD Audio drivers possible (currently only Realtek HD audio driver). -New: drvindex.inf patching (for DriverPack MassStorage). It also works without patching the drvindex.inf file, but this way the result is almost exactly the same as the original drivers included. -Changed: single filename for one driver. This means that I removed the specific names for specific hardwareids. This should help getting DriverPack MassStorage to work. -Fixed: aliide.sys error (experimental). -Fixed: when using method 1 and DriverPack Sound A & B, the entries in the winnt.sif file to install their control panels weren't added. EDIT2: and probably there will be some errors in txtsetup.sif. With such a large file to edit, the chance is very real that somewhere I've made a mistake (however I've TRIPLE checked). I don't have tried it yet, not enough time ATM... I will try it tomorrow... But in theory everything should work!

I think I've found the solution. If you add newer versions of the files that were originally included in Windows XP, you'll have to list them under [ForceCopyDriverCabFiles] in the dosnet.inf file! This will be included in the new version of the DriverPacks BASE that I'll upload tonight.

I'm using Firefox and can confirm that I do NOT suffer this problem...