DriverPacks.net Forum - Potential bug with driver signing repression v2

Re: Potential bug with driver signing repression v2

null@example.com (mr_smartepants) — Sun, 01 Mar 2009 17:49:26 +0000

To be honest, KTD is just a waste of space. I never use it.
It causes too many problems in my experience.
SAD on the other hand is just awesome! Not perfect, but getting there.

Re: Potential bug with driver signing repression v2

null@example.com (jdub) — Sun, 01 Mar 2009 16:14:06 +0000

I know but I wanted to check to be sure that's what was causing problems, isn't SAD the stand alone drivers project? How would that affect KTD?

In any case I've since built another one with it disabled and everything installed fine.

Re: Potential bug with driver signing repression v2

null@example.com (OverFlow) — Sun, 01 Mar 2009 16:12:34 +0000

LOL... yeah you did

Re: Potential bug with driver signing repression v2

null@example.com (mr_smartepants) — Sun, 01 Mar 2009 16:03:17 +0000

OverFlow wrote:

Don't enable KTD... it is not needed and has been replaced by SAD

Geez, didn't I just say that?
http://forum.driverpacks.net/viewtopic. … 661#p29661

Re: Potential bug with driver signing repression v2

null@example.com (OverFlow) — Sun, 01 Mar 2009 15:55:19 +0000

Don't enable KTD... it is not needed and has been replaced by SAD

Re: Potential bug with driver signing repression v2

null@example.com (jdub) — Sun, 01 Mar 2009 03:05:29 +0000

I just built a new disc from scratch and when I integrated Bâshrat the Sneaky it completed in 2 seconds - which made me go "huh" so I ran it again and it took 12 seconds... which sounded better to me so I burned it and it did that thing again with the driver warning and the little counter (number of times warning box closed 300+) I had ktd enabled

heres the log: DPs_BASE.log (7 KB)

Re: Potential bug with driver signing repression v2

null@example.com (jdub) — Sat, 28 Feb 2009 23:38:34 +0000

Edit: figured out the problem, I had both 803 and 902 in my driverpacks folder, dpbase must default to the older version for whatever reason while checking the newer one against the update checker... a little wonky, maybe a bug.

Re: Potential bug with driver signing repression v2

null@example.com (mr_smartepants) — Sat, 28 Feb 2009 23:31:08 +0000

Current DriverPack Chipset is 9.02, not 8.03 as in your log. That should fix your USB issue and possibly your IDE problem.
Sigmatel is always a bitch. Your best bet for that is to get the driver directly from the Dell support site.

Re: Potential bug with driver signing repression v2

null@example.com (jdub) — Sat, 28 Feb 2009 22:32:05 +0000

Took awhile to finish, started at 4:42 and ended around 5:15, not bad though. There were problems. I left the disable driver signing checking option in nLite on (meaning it DID disable SFC) and this time the warning boxes didnt come up. so go figure.

Drivers that successfully installed:
-videocard ati mobility radeon 9000 (5/3/2006)
-Broadcom 570x Gigabit Integrated Controller
-Intel Pro 2200BG wireless

Failed:
-Sigmatel audio controller
-IDE ATA controller (both the primary/secondary and the intel listing show they're using the 2001 microsoft driver)

Shouldn't sound B and mass storage (or maybe chipset) have taken care of those 2?
Also the usb stick (ocz diesel 16gb) that ive been using to xfer stuff like drivers etc detected but didnt install on the laptop, instead a yellow ! came up in device manager next to it and only after going through "update driver" did it install =/

HWIDs.txt - in case anyones wondering. I cant figure out how to link to dells support page but its an inspiron 600m laptop.

Re: Potential bug with driver signing repression v2

null@example.com (mr_smartepants) — Sat, 28 Feb 2009 21:58:02 +0000

Looks good to me. Let us know how it turns out.

Potential bug with driver signing repression v2

null@example.com (jdub) — Sat, 28 Feb 2009 21:40:29 +0000

Thought it best to make a new post to avoid confusion, ignore the last one or if you're an admin please delete it.

I started with an OEM copy of xp pro with sp2 integrated. I dont know how to identify its exact license. It's volume title is VX2POEM_EN and its 586mb, maybe someone recognizes it. I mounted it in daemon tools and extracted to a new folder

Fired up nLite and slipstreamed sp3. - recieved a warning that hotfixes were present and they would be deleted, hit ok.

Then Added ryanVM's 1.0.3 post sp3 update pack along with the directX9c addon

No drivers were integrated for the sake of bug detection - though I'd like to add a few (touch point, modem etc)

Misc tweaks/settings - Heres the nLite configuration file: Last_Session.ini (13 KB) - the installation was reduced by 154mb for a total size of 479mb

RVM 1.5.4_b09 to integrate OEMSCAN_1.4.1_MR_SMARTEPANTS_ADDON_MULTIOEM_1.8.07.7z - Heres the ini for that integrator.ini (406 B)
I was tempted to check "optimize system files" but thought better of it. Heres the log: RVM_Integrator_1_5_4_b09.log (3 KB)

I deleted DPBase to avoid confusion/problems. DPs_BASE.ini (2 KB) and DPs_BASE.log (7 KB)
Using DriverPacks Base 8.12.4 I integrated the following packs:
Chipset, Graphics C, LAN, Masstorage, Sound B, and Wlan - all the latest versions

Created the image with nLite (left the create iso page open the whole time) and burned with nero with verification on. It burned fine. Beginning install now.