Bâshrat the Sneaky

Edit: small fix in the code caused by my stupidity ← Maybe this is my bad, but IMO this won't work failproof... This would be alot better: REM ### If KB888111 is slipstreamed, it will be deleted, UNLESS the .cat file is detected in the SVCPACK folder. ### %INE% I386\SVCPACK\KB888111.ca? ( %IE% I386\portcls.sys DEL /Q I386\portcls.sys %IE% I386\hdaprop.dl_ DEL /Q I386\hdaprop.dl_ %IE% I386\hdashcut.ex_ DEL /Q I386\hdashcut.ex_ %IE% I386\hdaudbus.in_ DEL /Q I386\hdaudbus.in_ %IE% I386\hdaudbus.sy_ DEL /Q I386\hdaudbus.sy_ %IE% I386\hdaudio.in_ DEL /Q I386\hdaudio.in_ %IE% I386\hdaudio.sy_ DEL /Q I386\hdaudio.sy_ %IE% I386\hdaudres.dl_ DEL /Q I386\hdaudres.dl_ ) Note the question mark, that way it will work for both a compressed and a non-compressed .cat file. EDIT: You may be wondering why I didn't include that .cat file? The answer is very simple: RyanVM is just including it for completeness, it does not protect the KB888111 hotfix files anyway (thank you again, RyanVM for that info ). This code is more effective, yet easier

You must be right, Nazgul! d0ublezer0, could you please post your ORIGINAL txtsetup.sif and dosnet.inf files? Without them I'm afraid I won't be able to track down the exact cause of this bug...

**** that's possible! Didn't think take note of that one! I'll try to figure out a solution. So I suggest you rebuild your entire UWXPCD for now...

Eh that means your txtsetup.sif/dosnet.inf file(s) didn't get re-updated. Did you mess with the txtsetup.old/dosnet.old file(s)? If not... then this is a new bug in Fedit...

Please try to extract data1.cab, using the i6comp CLI tool. It *might* be in here!

I just tested and I don't have that problem... Are you sure you have updated correctly to DPs BASE V5.05.2? P.S.: did you copy Fedit.exe to %SystemRoot%\system32? If so, it will be using this one instead of the one I provide!!!

Those are default.

Well, if my DriverPacks didn't work for you, that means that your HWID has a different SUBSYS ID then the other VIA VT8237 controllers on ASUS boards. PLEASE post your HWID! You can obtain it with Everest Home Edition. If you need more info, do a quick search with this board's search engine or with google

Did you read the guide?

Eh.. odd story... that's the least I can say I think. But I doubt it has to do *anything* with my DriverPacks... the structure of Windows XP RUS won't be any different than the English version... And if it didn't work... what method did you use and what (possible) errors did you get?

@hammermtl: use Everest Home Edition, or devcon.exe or... use the search function (or google) @BAM: checked and that driver was missing indeed! P.S.: Fujitsu-Siemens has got a whole collection of yet unsupported cards I think... :s But I won't add all of them untill: a) I get bored as never before, B) I get paid for doing this insane job or c) my life depends on it: I'm being threatened to death. @mark49: it's really become time that you maintain your posts better, mark49. No offense, but that sentence doesn't make much sense to me... @what3v3r: what soundcard? I can't help you if you don't give me that information!

Try checking the following folders after you STARTED setup, but not finished/continued it: %temp% %WinDir%\Downloaded Installations\* (it might have a name like '{abcd-1234-wxyz-7890}')

Method 3 is a hybrid method that combines method 1 and 2. You can find more info about it in this thread Method 3 is still considered to be in the experimental status. I don't remember exactly what that was all about... But I do remember that it wasn't full mobility support! I promise that there will be ATI Mobility support in the next version of DP Graphics A, though it might be limited support.

Use START /WAIT. Like this: start /wait %systemdrive%\Install\Apps\GrabIT\GrabIt152b.exe /verysilent Please use CODE tags next time!

That's just a shortened (read: optimized) version of what he has

This one should be working :s. Could you please post the HWID of that soundcard?

Why not use the built-in RunOnceEx functionality?

I *hope* (sorry ) that your files were corrupt... If we'd be back at the aliide.sys error...

Hmm... And why exactly would you want to creat a UWXPCD from VMWare? The only reasons I can think of ... you're running VMWare from Longhorn? On condition VMWare CAN run from Longhorn. Anyway, besides that, it's very strange that it isn't working properly! :s Does ANYONE else have the same problem?

Eh... is that Windows 98? Yes it is, isn't it? It's possible that ROBOCOPY isn't working properly on that OS... Just retried on my own system and I can confirm that I do *NOT* have that problem.

I can host it too if you want. 214 KB... even with 10 000 downloads monthly that would only be 2GB of traffic... Let me know something if you want it! (I noticed you got several other offers )

@Siginet: thanks, please mail me that, that could be a temporary solution! @Cartoonite: the first bug: that would amaze me. EDIT: as I said that it would amaze me, I tested it for myself: Method 2, GUIRunOnce for the finish off, DriverPacks BASe V5.05.2, no winnt.sif present. I get this: ;Generated by Bashrat the Sneaky's DriverPacks BASE [Data] MsDosInitiated = "No" [Unattended] OemPreinstall = "Yes" [GUIRunOnce] command9 = "%SystemDrive%\D\BTS_DPs_finish.cmd" And the second one... you're wrong about that: from BTS_DPs_finish.cmd: SET DPDIR=%SystemDrive%\D ... IF EXIST %DPDIR%\BTS_DPs_cleanup.cmd START %DPDIR%\BTS_DPs_cleanup.cmd

This is quite normal... maybe you could hack some files (I think I've once seen something similar to this before), but wouldn't that require more time than just clicking 'OK'?

I see you automated nearly everything with the info I sent you Thanks again, djbe, for the wonderful tool you made!

BTS DriverPacks BASE V5.05.2 Supported devices. Changelog: V5.05.2 (13 May 05) -Improved: [DPB] BTS_DPs_auto.example.cmd: now it can be run stand-alone. -Fixed: [DPB] slipstream_DPM.cmd: ASH1205.sys error when using winnt.exe/winnt32.exe to initiate setup. -Fixed: [DPB] Fedit.exe: the problems with Fedit.exe (current version: 1.2.2.3) -Fixed: [DPB] RUN_ME.cmd: the problem with the cleanup batch file not being executed. -Fixed: [DPB] RUN_ME.cmd: the problem with the erroneus REG ADD command in BTS_DPs_ROE.cmd. -Fixed: [DPB] RUN_ME.cmd: all method 3 related bugs should be fixed now. -Fixed: [DPB] RUN_ME.cmd: M1 folder was left. -Fixed: [DPB] RUN_ME.cmd: several other bugfixes. -Fixed: [DPB] RUN_ME.cmd: OemPnPDriversPath was erroneus. -Fixed: [DPB] RUN_ME.cmd: KB888111 not being slipstreamed when using method 3. Download Known issues -Minor bug: [DPB] all methods, RunOnceEx: it would be better if BTS_DPs_ROE.cmd would be listed as the FIRST entry under [COMMANDS] in cmdlines.txt, but for now this is impossible with Fedit.exe (it doesn't accept the parameters given), so for now it will be listed as the last one... -Bug: [DPB] all methods: in winnt.sif: if a section is being updated with new and/or updated entries, it will add a new section if the cases of the sectionname aren't identical.