And what tagfile can I then use to detect Sereby's UpdatePack? I AM using 'Serepack.inf' as a tagfile.

Use the 'Custom' Finishing Method, and you'll be presented a dialog that explains you which files must be executed, to finish the installation of the DriverPacks using any other script or program (in this case using WPI).

Which version of DriverPack Chipset are you using? You must be using the latest version, the old one isn't compatile anymore with the new DriverPacks BASE! wink

OK, problem solved!

The problem was that mgadallah had compressed the DP_* directory instead of the 'D' directory and therefore it was extracted to the %SystemDrive%\DP_* directories instead of to %SystemDrive%\D.

He will be posting his experiences soon, he said to me.

There are some cleanup issues, but those DP_* dirs cannot exist. That MUST be a mistake on your behalf. Could you please post a screenshot in which you show the content of both your 'DriverPacks' and your '3rd party DriverPacks' dirs? And your log file would be very handy as well.

Please post yur HWIDs, check my sig for a tool!

How long did you let it run? It CAN be running for quite some time...

Oh yes, forgot to make that remark: DON'T MESS WITH DRIVERPACK MASSSTORAGE! wink Thanks, RogueSpear smile

This is indeed possible wink

This should work just fine. Just note that the following hotfixes will be unslipstreamed and then slipstreamed again by the DriverPacks BASE:
-KB883667 (monitor driver popup during setup)
-KB888111 (HDA)
-KB913425 (latest portcls.sys)

EXCEPT for when Sereby's or RyanVM's UpdatePack is detected.

1,711

(7 replies, posted in Other)

Obviously spam indeed tongue.

First ban ever smile lol. Topic closed.

Newdev.dll is the file necessary for KB883667 wink (Added in 6.06.) It's strange that the file doesn't exist... you did check for newdev.dl_, and not newdev.dll, I hope? And does anyone else have the same problem?

Your proposed solution will work by the way wink

1,713

(11 replies, posted in Feature Requests)

It will be implemented, was already on my todo list. It will be implemented nLite-alike, though without the progress bar probably... or perhaps not, I haven't had the time to look into that yet.

Forgot to close this topic... the bug has been fixed, as you can see in that other topic covering the same problem. And I see you (the topic started) has already found it, so that shouldn't be a problem smile

Topic closed!

1,715

(21 replies, posted in Installation Platforms)

Siginet wrote:

It's been kinda postponed due to my pinched nerve in my neck. sad
I just had a shot in my neck the other day.  It is supposed to trey to tone the pain down... but it hasn't helped yet.  It actually made it worse.  So I can't really stay on the computer very long at a time.  Hopefully my neck pain will ease down a bit in the next couple days and I will be able to code for the next powerpacker beta.  I've just been popping in here and there... but I'm only sitting at the computer for a few mins at a time. sad

I'm sorry, forgot about that for a moment! sad

Get well soon! wink

1,716

(21 replies, posted in Installation Platforms)

Siginet wrote:

Oh... just one more...

SPAM! big_smile

LOL tongue

Any ETA for the new PowerPacker (beta?) yet?

1,717

(0 replies, posted in DriverPack Sound)

Changelog
fixed
-downdated Creative Sound Blaster Live! 5.1 (Dell) driver from 06/29/2004,5.12.01.0204 to 09/22/2003,5.12.01.0203

new
-Conexant AMC Audio HP driver
-added another SoundMAX Dell driver

updated
-Sigmatel HDA (universal driver) driver from 12/12/2005,5.10.4866.0 to 03/20/2006,5.10.4991.0

Known issues
-none

Remarks
-none

Download

1,718

(0 replies, posted in DriverPack Sound)

Changelog
updated
-Realtek AC'97 driver from 03/17/2006,5.10.00.6050 [3.85] to 05/19/2006,5.10.00.6090 [3.89]

Known issues
-none

Remarks
-none

Download

1,719

(0 replies, posted in News)

Changelog
Changed
-cmdlines.txt: "DPs_ROE.cmd" entry will now be inserted as the first entry.

New
-nothing

Fixed (bug ID's from bugtracker)
- 0000067: [slipstreamer] Windows 2000: when KB888111 is slipstreamed: hdaudres.dll entry is corrupted or missing (BashratTheSneaky)
- 0000065: [slipstreamer] M1, only DP M text mode: Critical Error: "Could not extract bin\finish.7z to $OEM$\$1" (BashratTheSneaky)
- 0000068: [slipstreamer] Windows 2000: QL2100.sys is deleted (BashratTheSneaky)
- 0000069: [slipstreamer] Files without extension crash (BashratTheSneaky)
- 0000066: [slipstreamer] DPS_fnsh.cmd: missing a "(" in the cleanup section (BashratTheSneaky)
- 0000064: [GUI] [OptionalSettingsOther] allways ATI_cpl = "CCC" (BashratTheSneaky)
- 0000061: [slipstreamer] ATI CCC/CCP selection: settings saved but not imported (BashratTheSneaky)
- 0000060: [GUI] "Next" button on QuickStream Cache page doesn't go anywhere (BashratTheSneaky)
- various small bugs

Known issues
-[GUI] When doing the following sequence: UpdateChecker -> Overview -> UpdateChecker, there's a GUI bug
-[slipstreamer] DriverPack MassStorage text mode doesn't work properly when using Windows 2000 (NTLDR missing error)
-[slipstreamer] multiboot support is not yet operational

Remarks
-Documentation later! Just use it as-is now. It's all pretty self-explanatory...
-You have to rename the DriverPacks! An example: "DriverPack_Graphics_A_V603.7z" must be renamed to "DP_Graphics_A_wnt5_x86-32_603.7z". If you download any DriverPack now, they will already have the correct names.
-You should slipstream the new DriverPacks in a fresh source!
-This version may still contain bugs, but it should be VERY FEW!

Download

I think I've found the cause. I add this line for KB888111 (and several others) in Windows 2000, XP and Server 2003:

hdaudres.dll = 100,,,,,,,2,0,0

The '100' means it's a file that was added by a ServicePack (ANY SP), and that it wasn't included in the RTM version. I didn't do any further investigation regarding this: I assumed this '100' value would work on all Windows NT 5 platforms. But it does not.
It seems that for Windows 2000, the value '2' is used. It's fixed in the next version of the DriverPacks BASE! wink So just for the record, what should be added when using Windows 2000 is the following:

hdaudres.dll = 2,,,,,,,2,0,0

1,721

(88 replies, posted in Feature Requests)

That WILL be figured out smile Not the time for that now though (blame those useless exams tongue :lol)!

1,722

(21 replies, posted in Installation Platforms)

No more spamming, Siginet! mad :lol

ontopic:
Well, inhib, as you may have noticed, the DriverPacks BASE isn't built by batch files anymore... so no more dumb .cmd file to provide partial multiboot support. There IS built-in support for multiboot discs, but there's three big BUT's:

BUT #1: it's not yet integrated in the GUI! It will be after my exams. Please check the docs\reference.ini file for details on how to use multi-boot mode.

BUT #2: it's not yet verified to be working (lack of multiboot users to test it).

BUT #3: it's not yet available for the regular users. Only for those calling the application in API mode (so far only Siginet's PowerPacker uses the multi-boot mode).

So I'm afraid you'll have to patient for a while, until Siginet is finished or until I've implemented it (after my exams, after June 22). Sorry!

@clubcj: that would require that you always have the previously used version. Or it would imply that I'd have to create incremental updates for all previous versions. Don't think so tongue (if I'd do that, I wouldn't have a life left...). In the future (not the very close one) you will be able to select any particular driver, and therefore there won't be 'DriverPacks' anymore, at least in the current meaning of the word. Those DriverPacks would then simply be repackaged drivers, one by one instead of grouped by device type. And Siginet's remark is also very relevant. It'd really make things more complex than necessary.

1,724

(88 replies, posted in Feature Requests)

Vista WILL be supported. But not just yet, first get all Windows XP platforms working wink

razormoon wrote:

What is newdev.dll by the way? Sometimes it shows up in txtsetup.sif, sometimes it doesn't. Same with dosnet.inf.

It's for KB883667, which has been added in the latest version.

Is that with the same OS that it sometimes gets slipstreamed and sometimes not? It's a hotfix solely for Windows XP SP1 or SP2.