Bâshrat the Sneaky

i like this idea <{POST_SNAPBACK}> Me too I'd even say that it's GENIOUS!

Almost none... Some things were broken... The main reason for so drastically changing the batch files (their structure & calls) is because of the new KtD feature. Now in the .13 release there will also be support for RogueSpear's suggested alternative hybrid method, which will be named M3. In general, everything is working fine now (however it's broken in .12...) I did all THEORETICAL tests, no more problems. I say theoretical, because I did not have the chance to do a real test! Everything will be online within the hour now! Please clarify your 'museum-remark', I don't understand much of that oh-so-strange formulated sentence... Sorry

Nice one! But I don't understand why you posted this here instead of in the DriverPacks General Discussion Forum? When you got it bug-free, I'll try to implement everything into the standard DriverPacks BASE! Nice work

And the txtsetup.sif file would always be on the ROOT of a partition? Is that so?

Eh... much work? Run an executable like this: SetupCopyOEMInf.exe %SystemDrive%\Drivers\Monitor , where you've put all your monitor drivers in that folder. IMHO that's not much work AT ALL. Just run it from GUIRunOnce/RunOnceEx and it should work...

Hi, I need a tool (CLI utility is just fine too) that is capable of extracting SZDD archives. Searching the net got me nowhere... Thanks in advance!

Well, that's why there's nearly no difference: 99.99% of the consumer pc's ARE x86 CPU's.... EDIT: sorry BAM, forgot to reply to your post... <offtopic> Yes, it was fun, but there were too many museums on the agenda IMO... </offtopic> You're not out of line, but it's just too much work for now... But I'm getting really close to get everything very stable, with the help of all you here. IF it will be added, it will not be before July.

erm?

Wrong forum... Moved. SOME will work, in fact probably most, but certainly not all. EDIT: After months of no reply of the topic starter, this topic is closed. The question was answered anyway.

OK, the release won't be for tonight. But I have been cleaning up the structure etcetera. More things are automated now and for example it's now relatively easy to change the default directory where the DriverPacks should be extracted to (during setup). I can almost guarantee you that DPs BASE V5.04.13 and DP MassStorage V5.04.2 will be online tomorrow!

The root is indeed the lowest level, the lowest folder of your UWXPCD. By UWXPCD we mean here, as erik_demon said, the 'local source', also called a 'share' by some. No offense, but maybe you should first read the tutorial, or at least first get familar with 'the unattended Windows XP stuff'... I hope it's easy enough for you EDIT: I don't mean the tutorial, but my DriverPacks... edited because you could misunderstand me! Please also note that there should be NO SPACES in your path, which there are now... (C:\Documents_______and_________Settings\Sorin\blabla...). Use a folder like C:\BTSDP.

Thank you very much But the problem is already solved by including another, newer ASUS Promise 376/378 driver. At least, in theory it should work for your controller too. In fact the one included ATM too, but. Let's first give the current one a try (not yet released, please wait for DPs BASE V5.04.13 and DP MassStorage V5.02)

@DigeratiPrime: thank you very much: your controller confirms the one mark49 posted So I think it's safe to assume that the hwid PCI\VEN_105A&DEV_3373&SUBSYS_80F51043 is the one for the Promise Fasttrak 378 controller on the ASUS K8V SE Deluxe board. But for now, I've switched ALL Promise Fasttrak 376 & 378 controllers to this newer driver. I *do* have it however added to slipstream_DPM.cmd as a remark, for (possible) future enhancements. Thanks to the both of you . The new versions of DP MassStorage and DPs BASE will support it.

You can use WinInstall LE 2003 to convert ANY installation to an .msi installation. I hope this helps...

An exact list would help indeed. I assume you're talking about the driver in D\G\M\2?

@RogueSpear: and what possible newer NIC drivers could that be? (no offense, just asking, if you know some I'll add them )

How many apps are you installing? What apps? Probably you can reduce some in size... Or CAB some more things... Welcome!

The one in [sourceDiskFiles]. But I think we'll have to move on to [sourceDisksFiles.x86] when 64-bit Windows with support for AMD64 and IA64 will be released... Are you sure BOTH are added by the DPs BASE? That's quite impossible... There are no references to [sourceDiskFiles.x86] afaik. In the past they were there, but not anymore...

@McDanger: did you read my previous post???

Added viaidexp.sys and other version of fasttx2k.sys for the Promise 376/378. Where did you get ulsata.sys, mark49? @DigeratiPrime: yours is for tomorrow!

awtch... you're right, this is the oh-so-famous issue that we're having thanks to Promise. Thanks again, Promise! :angry Please use Everest Home Edition or anything else to determine your hwid and please post it afterwards.

Just DON'T choose the 'Keep the drivers' option (yes, I know, it's broken in the current version... please have some patience!)

OK, I've been working on the DPs BASE for the past two hours now, and so far these changes: -all bugs should be fixed. -the KtD function is unified. -the KtD function AND the DriverPacks cleanup are now integrated into the CPLs batch. -experimental support for method 3. Any other (special) requests? EDIT: that's also why from now on, when using KtD + M2/M3, SetupCopyOemInf.exe will be executed at GUIRunOnce, just as it was the case for KtD + M1. Therefor, it should work just fine for M2 (and M3 of course) as well from now on!

I guess that's IcemanND's point... :whistle Some stuff is still being executed at svcpack.inf (T-12), while drivers get installed MUCH earlier (T-34/T-32). Why don't you just try my method?

I know, I'm working on a new version.