1 Reply by dummy1

(7 replies, posted in Feedback and Support - DriverPacks Base)

I'm sorry. I don't mean to seem like I am hammering on you, personally. I know you must have done a lot of work to get Driverpacks to where it is now. It simply falls apart for me, though. And my primary job is dad, not computer guru.


.....



AH-ha. I looked at the VID and the PID for the Zyxel G-220 and they do not match the only WLAN *.inf with the word 'Zyxel' in it. This would explain why at least, windows cannot find the drivers for the Zyxel in the driverpack - they do not appear to be there.

Most wounds are self-inflicted.

.....

I'm going to do one more build, and just update this last post instead of ranting on or making like I'm talking to myself (which is not a bad thing).

I hope to get this fixed in the next ten minutes.

.....

Did it! Whoohoo. Man, the weight is off my shoulders. The other guy has his disk now. :whew: That teaches me.

Go to forum: Feedback and Support - DriverPacks Base

2 Reply by dummy1

(7 replies, posted in Feedback and Support - DriverPacks Base)

No. That last time did not work. This has already cost me a weeks worth of bits of free time away from my kid and wife. It's my fault for thinking there was a simple way to add drivers to the XP installation disk and hand it over to the customer, whom I'm doing it for as a favor, because no amount of phony money in the whole world is worth in trade getting me away from my very real family.

It seems this worked better in the past. Is the addition of more drivers in the last year or so, that has made Method One not work anymore for all driver packs inclusive?


....


Sorry. I can't get this to work. If you have a really simple step-by-step tutorial: Bring disk, add drivers, wa-la! Then I'm all ears.

Umm. the last statement I can't figure out a way to rephrase sounded a bit too bitter so it's edited out.

Go to forum: Feedback and Support - DriverPacks Base

3 Reply by dummy1

(7 replies, posted in Feedback and Support - DriverPacks Base)

P.S. No offense to all your work you take great pride in, I'm sure. I would not be pursuing this normally as I am already very busy; it's all a bit of a pain in the ass for me, I've been struggling with making this disk for a week. I would just add the drivers normally for myself.

But..

I have a customer who will understand and expects this disk: put the disk in and XP loads with the drivers. I am only deleting the winnt.sif, because the install should be as vanilla as possible, with the addition of the valuable driver packs.

Be careful, most wounds are self-inflicted.

Go to forum: Feedback and Support - DriverPacks Base

4 Reply by dummy1

(7 replies, posted in Feedback and Support - DriverPacks Base)

It kinda works and it kinda does not work. Whatever happens at the end, the drivers may be copied into the installation drive by the setup process, but then %KTD% appears and there is no system-wide definition of what the value of %KTD% is: it's undefined. So the installation has no idea where the drivers are for anything installed after the desktop comes up.

I tried throwing it out. I did a fourth or fifth try, this really aught to be easy now -  I've got a vanilla XP SP3 disk and I want to add all the drivers.

Method 1 does not work because of the 4096 limitation. Too many drivers, so we can forget about that.

Method 2 does not appear to work because, while drivers may be loaded (okay so that works), they are not available afterwards for additional hardware.

Maybe I'm asking too much?

I think the availability afterwards is the hang-up, and specifically the undefined system variable %KTD%.

I did try the 'SAD' method, with compressed drivers being in a folder, then putting the folder onto the ISO and burning it.

When XP setup completes, I plug in a WLAN stick. It searches for the drivers, including the DVD drive. Even though the CAB compressed versions of the drivers are on there, and windows should see those, it doesn't. It's an older Zyxel stick.

EDIT found the problem with the zyxel stick below.

Go to forum: Feedback and Support - DriverPacks Base

5 Reply by dummy1

(7 replies, posted in Feedback and Support - DriverPacks Base)

Oh please forgive my newbie-ness.

I just realized I am using Driverpacks Base 8.05. Apparently I updated all the driverpacks, while forgetting to update base.

My bad. Have a nice day!

Go to forum: Feedback and Support - DriverPacks Base

6 Reply by dummy1

(7 replies, posted in Feedback and Support - DriverPacks Base)

Hate to be a pest:

I deleted windows xp, and from the working folder I deleted the Windows XP installation copy. I re-extracted the vanilla from the ISO. I did another DriverPacks process:

This time I selected Method 2, KTD ALL drivers, and deleted the winnt.sif.

NOW I got to see the finisher process in-action, as it 'reset' the registry entries over one-thousand times, and so-on.

Yet, when it was done, at the Start Menu, trying to add a piece of hardware, again it cannot find the drivers.

The KTD folder exists, but HKLM\Software\Microsoft\Windows\Currentversion has %SystemRoot%\Inf;%KTD%\C\A1;%KTD%\C\A2... so -on

If I open a CMD prompt, and type SET, there is no environment variable called KTD defined.

Go to forum: Feedback and Support - DriverPacks Base

7 Topic by dummy1

(7 replies, posted in Feedback and Support - DriverPacks Base)

I have a vanilla XPSP3 CD.

I grabbed all the latest driverpacks, including base 8.05.

I ran Base on it, and choose the options Method 2, and KTD ALL.

When all was said, and done, the install had a %SystemRoot%\DriverPacks folder, C:\WINDOWS\DriverPacks,

and navigating to HKLM\SW\Microsoft\Windows\CurrentVersion, DevicePath shows %SystemRoot%\Inf;%KTD%\C... and so on.

But running CMD and typing SET (enter), the value KTD is not defined. Plugging in a 1.5 yr old zyxel USB wlan stick after the install, it can't find the drivers, although they exist in the DriverPacks folder.

?

Go to forum: Feedback and Support - DriverPacks Base