Please post the HWID of that GPU (check my sig for a tool).

Topic closed, if you wish to continue the discussion, please do so in the other thread.

It'd be very helpful if you could post the filenames of the 3rd party DriverPacks you're using.

Good of you that you submitted it at the bugtracker wink It's fixed in 6.06.1!

What's the file encoding for your original SVCPACK.IN_? Please send it to me so I can try to reproduce and fix this.

1,731

(1 replies, posted in Other)

Thank you for showing your appreciation smile

True, but are there versions in other languages?

It's language independant. Or at least that's what I've been told. I think the other languages will only affect the name of the device in the device manager and the registry imports it does (which I do NOT apply, since they're not necessary).

Already submitted to the bugtracker and already fixed! wink

Bug #60.

Topic closed.

Please post a screenshot of your '3rd party DriverPacks' directory AND post your DPs_BASE.ini and DPs_BASE.log (inside CODE tags of course).

Siginet wrote:

It has been reported. wink

I don't see it in the bugtracker? :s I've submitted it myself: bug #67.

Could you please ATTACH your \I386\txtsetup.sif file at the bugtracker? Thanks!

Correct. That's AutoIt syntax... sad Please submit a bug to the bugtracker immediately next time! wink

Fixed in 6.06.1.

marzsyndrome wrote:

You don't think it could be anything to do with the WMP hotfix, or even the WMP11 beta, surely??? =S

Might have to test anothe reinstallation at some point then and see if the icon appears afterwards.

That's very probable.

The QuickStream Cache will have an enormous effect on the slipstream time when you're using method 1: the first time it compresses the DriverPacks to the cache, the second time it will only have to copy them from there. That's why it will only take about a minute, perhaps two, to slipstream all the DriverPacks when using method 1.

When using method 2 and QSC, the QSC will only be relevant for DriverPack MassStorage text mode drivers. It will shave off a full minute of the slipstreaming though. Method 2 will then take about 1 minute.

All these numbers are applicable when using ALL (official) DriverPacks.

Please post your slipstream log (DPs_BASE.log).

Could somebody please (FINALLY by the way...) post his/her finishing log? (%SystemDrive%\DPs_fnsh.log)? I don't understand why no one has thought of that, if you know the installation itself isn't working...

Did anyone get the CCP/CCC installed?

I STRONGLY doubt that this is related to the DriverPacks in any way. My guess is that it's caused by a certain hotfix?

From the changelog of DriverPacks BASE 6.06:

-[slipstreamer] KB883667 support (Windows XP SP1 and SP2, non-MCE)

newdev.dll is a file that's necessary in this hotfix. This hotfix prevents the monitor driver pop-up during the installation, which happened in some cases.

Well they should be expanded then, or renamed to .dll! Maybe that's the cause...

Very well, then this will be fixed in 6.06.1! Thanks for your help, sadicq! wink smile

1,747

(76 replies, posted in DriverPack Mass Storage)

Very interesting, hmaster10. If somebody could confirm this, I'll make this a guideline. Did you base this method on someone else's? If so, please provide the source.

And you were also able to reproduce the scrambled fonts??? Just to make sure that this DOES solve the problem...

That's an error in the file compression code, apparently. I've tested that thoroughly though :s. This implies that you're using method 1, so if you want to get it running immediately, use method 2.

Could you please post the filenames of all 3rd party DriverPacks you're using? Thanks.

A topic that describes the same issue already exists: right here! wink

Topic closed.

EDIT:

Multi-language support will be added later! wink