You can not automatically update the drivers.

Your best option is:
1) extract DriverPacks
2) apply KTD
3) right click every device in the device manager and let it search for updates, it will find the updates automatically.

227

(16 replies, posted in DriverPack Sound)

lucky2007 wrote:

as I said didnt got a log, but I wil do a reinstall today or tomorow just to get the log file!

The log is in your C:\Windows directory, no longer at C:\. This was changed a couple of months ago.

You're welcome wink

So my suspicion was right smile

Kurt_Aust, could you please tell us which ones you disabled? So we can make the same changes - or changes with the same driver size. Then you won't have to bother doing this next time.

Use method 1, without KTD. Then there's less compression. But because EVERYTHING has to be copied, it's actually slower.

The only way to make it faster, is by installing through imaging software.

OverFlow wrote:
Kurt_Aust wrote:

I would suggest changing the text on the settings page to

QuickStream Cache
Enable  (recommended for Slipstream method 1)
Disable (recommended for Slipstream method 2)

I belive that is a good suggestion, and not presumptuous at all. I'll add it to 7.05.2 english version

Ill have to get with the translations team to get it fixed for the other languages

Actually it's not.

QSC is still useful for text mode MassStorage drivers. So it should stay the way it is.

Jeff, what did you change to fix this? I don't see why this error only occurs for 7.05.1, I understand you did not even touch the CAB compressing code or the code for method 1?

OverFlow wrote:

Since you are useing QSC. I wanted to make sure you knew this...

The Quick Stream Cache folder is not self maintaining.

You need to manualy delete the files in this folder anytime you switch driverpacks.

\DPs_BASE\QSC\wnt5_x86-32_uni_DP_MassStorage_*.*

if you missed this step then we dont have a valid result.

Huh? This is not true.

This is only necessary if you want to use a modified version of a DriverPack after you've slipstreamed an unmodified one. You don't have to do it every time. The QSC has a directory for each (DriverPack, DriverPack version) - pair. Hence there's no need to clear the QSC "every time".

234

(10 replies, posted in Software)

kendrahoese wrote:

im a first time buyer of a laptop that came with vista. I hate it.i was told that i could erase my whole hard drive and install xp,but i would have to find the drivers myself. could i possibly get some help

Just slipstream the DriverPacks into your XP install cd using the BASE.

Kurt, could you please try this: do a new slipstream using the newest BASE (7.05.1) with the previous MassStorage (7.04). Please post the results here. Thanks.

236

(9 replies, posted in News)

It's DriverPack, not Pack.

It's LAN, not Lan.

It's 7.05.1, not 705.1.

It's all in the details wink

@OverFlow: did you add some text mode MassStorage drivers? Did you take the Windows 2000 memory limit into account? This problem might be caused by that.

But apart from this one, all settings are documented, in the .ini files themselves!

I have never heard of "Distribution Shares", but I guess it's just a networked installation. If so, yes it works.

0x7E is often related to sound cards or hardware conflicts, IIRC.

In this case, I assume it is a driver conflict - which is a royal pain to narrow down. I suggest you start over and ONLY slipstream MassStorage. If that works, add Chipset, then Graphics A, and so on.

ATI 437A it is. That's a Silicon Image 3112 (either RAID or non-RAID) in disguise. This should be working flawlessly. Please post your DPs_BASE.log.

Please post your HWIDs. Either post your DPsFnshr.log or use the tool you can find in my signature.

lightsout wrote:
Bâshrat the Sneaky wrote:

lightsout, are you ready for some AutoIt programming?

I've used AutoIT to automate software installation, but I could give it a go.

The main thing is working out exactly how to insert drivers into the image.

Nope, that's properly documented this time smile And the snippet muiz posted (written by a friend of muiz) does it already. We just have to integrate it properly into the BASE *and* provide more options (but that's phase #2).

lightsout, are you ready for some AutoIt programming?

@-I-: The BASE was designed from the ground up to be so modular that it could support slipstreaming into ANY kind of installation for ANY version of Windows (at least any version AutoIt works under). Currently supported slipstream platforms for wnt5_x86-32: disc (the most well-known), multibootDisc and BartPE. Support for Vista is OBVIOUSLY something completely different, but it should be put in the same software, as another slipstream module.

Good job, OverFlow! smile

@ lieblingsbesuch: we assumed it was working now, because it's been months since we've had negative reports about them.

247

(2 replies, posted in News)

Well done, DriverPacks Team!!!

This is the URL the UpdateChecker requests: http://driverpacks.net/UpdateChecker.php. As you can see, everything listed there is okay... perhaps it was a temporary glimpse...

And FYI, those "Where did you get that?" messages appear if you have a version newer than the last official release version.

Then you have a problematic mass storage device. Please report this in detail in the DP MassStorage forum. Post your HWIDs and the exact product name, so we can help you further.

Ehm, the text mode MassStorage drivers always get slipstreamed the same way. It SHOULD have worked. And this is the wrong forum by the way, moving it to feedback & support.