1

(107 replies, posted in 3rd Party DriverPacks)

I came to this thread hoping to figure out why my Logitech USB (Wave) keyboard won't install properly via Driverpacks... but apparently I am far from the first person with this issue... sadly, I have to agree that I don't think it is worth the amount of time you would have to put in to correcting the issue... as much as I wish this weren't the case, I will have to settle for making an AutoIt script for this particular item... If the issue does get resolved that would be wonderful... but I don't wish the headache of figuring it out on anyone!

ok... well, I don't know what I did wrong... but starting over fresh... using the packs smartepants posted for me... all is working flawlessly now... thanks a bunch for all the suggestions!

damn... now I'm starting to wonder if I have hard drive going bad... as I have built two different times not changing ANYTHING in the source, using cdimage_gui and the first time I got the reboot after networking components install, the second I got a 7za.exe address violation error during the unpacking of the driverpacks part of setup... very very strange... going to run some hard drive tests I guess... argh!!!

edit: not hard drive... starting over from 0 again...

hmm... I'm beginning to wonder if maybe it is nLite and the way it "builds" the bootable ISO... is there a better more "reliable" way to build an ISO, I'm almost thinking that from one build to another I am getting some corruption during the ISO building process... this is the only other thing I can think of... I wish nLite had a "verify after build" option...

edit: nevermind... found the cdimage/cdimage_gui utility on msfn forums... going to try that instead... ::crossing fingers::

appears I was still a bit hasty in declaring "all is ok"... while setup did complete without getting stuck in a continuous loop and all "seemed" to install ok... once booted into windows for first time it did break most of the addons. I had to use "windows components" to get them installed properly, which usually when something breaks the installation of addons (inf installer "true addons") it is usually a poorly edited (on my part) inf file and will render an error which will give ma clue as to which "addon" it was whos inf I have edited and fouled up... but when I ran it this time a simply got an error that didn't give any clue to the name of the inf that produced the error and the error was something about "0xd file not found. click ok to continue, cancel to stop setup..."

so I'm going to see if I can figure out what happened... I just know that everything was working find, all addons were properly installed during installation of the previous (no DriverPacks) build... man this stuff can be frustrating sometimes... hehe...

OverFlow wrote:

We are getting close to the answer now... wink

and it's making me happy again! hehe...

guess I'll just have to use a svcpack or runonceex installer for wmp11... oh wellz...

well without wmp11 slipstreamed it worked with the older graphics a pack, so now I'm going to try one more time leaving wmp11 unslipped and use the newer graphics c pack and mass storage packs that smartepants posted for me earlier... thanks again for the suggestions guys!

well apparently I made a mistake, I doubled/triple checked and I built the wrong folder as ISO... and older build (pre-sp3) which I have since deleted... so I am going to go back and try one more time with Graphics A version 804 and see if that takes care of it... if not I'm going to try building the ISO without WMP11 slipstreamed and see what happens...

here is my order of building my source:

SP3 + Addons = Good working installation

SP3 + Addons + WMP11Slipstreamed or WMP11 True Addon + DriverPacks = Broken installation (always right after networking components installed)

p.s. only thing I noticed is that you can't choose a control panel when using the graphics c pack... will this be changed once it's an official pack? or just an unecessary part?

seems to have worked using your suggestions mr_smartepants, thanks!!!

mr_smartepants wrote:

Yes, try the DriverPack Graphics C instead of A.
I just uploaded it.  For nvidia 6100, DriverPack Graphics C uses the rock-solid v93.71 drivers, your hwid overlaps with DriverPack Graphics A.  If DriverPack Graphics C works better for you, I'll remove the overlap for that series chipset from DriverPack Graphics A.
Don't forget to remove DriverPack Graphics A from your .ISO wink
http://driverpacks.sytes.net/driverpack … 2_811n1.7z

And dpms has been updated too.
http://driverpacks.sytes.net/driverpack … 32_810H.7z

It also wouldn't hurt to start with a fresh source. smile

Thanks I will try all of your suggestions...

damn... guess I'm going to have to wait a bit longer... maybe I should try stepping back to an older graphics driver pack?

thanks a ton... will try it out A.S.A.P.!!!

also... base v8.05 broke installation at the same point... after that happened, I tried the 8.09rc1 and got the same results...

p.s. thanks again guys!

=========== 
PCI Devices 
=========== 
PCI\VEN_1022&DEV_1100&SUBSYS_00000000&REV_00\3&2411E6FE&0&C0: PCI standard host CPU bridge
PCI\VEN_1022&DEV_1101&SUBSYS_00000000&REV_00\3&2411E6FE&0&C1: PCI standard host CPU bridge
PCI\VEN_1022&DEV_1102&SUBSYS_00000000&REV_00\3&2411E6FE&0&C2: PCI standard host CPU bridge
PCI\VEN_1022&DEV_1103&SUBSYS_00000000&REV_00\3&2411E6FE&0&C3: PCI standard host CPU bridge
PCI\VEN_10DE&DEV_0242&SUBSYS_D0001458&REV_A2\3&2411E6FE&0&28: NVIDIA GeForce 6100
PCI\VEN_10DE&DEV_0260&SUBSYS_00000000&REV_A2\3&2411E6FE&0&50: PCI standard ISA bridge
PCI\VEN_10DE&DEV_0264&SUBSYS_02641458&REV_A2\3&2411E6FE&0&51: NVIDIA nForce PCI System Management
PCI\VEN_10DE&DEV_0265&SUBSYS_B0001458&REV_A1\3&2411E6FE&0&68: Standard Dual Channel PCI IDE Controller
PCI\VEN_10DE&DEV_0266&SUBSYS_B0021458&REV_A1\3&2411E6FE&0&70: NVIDIA nForce 430/410 Serial ATA Controller
PCI\VEN_10DE&DEV_0267&SUBSYS_B0031458&REV_A1\3&2411E6FE&0&78: NVIDIA nForce 430/410 Serial ATA Controller
PCI\VEN_10DE&DEV_0269&SUBSYS_E0001458&REV_A1\3&2411E6FE&0&A0: NVIDIA Network Bus Enumerator
PCI\VEN_10DE&DEV_026D&SUBSYS_50041458&REV_A2\3&2411E6FE&0&58: Standard OpenHCD USB Host Controller
PCI\VEN_10DE&DEV_026E&SUBSYS_50041458&REV_A2\3&2411E6FE&0&59: Standard Enhanced PCI to USB Host Controller
PCI\VEN_10DE&DEV_026F&SUBSYS_00000000&REV_A2\3&2411E6FE&0&80: PCI standard PCI-to-PCI bridge
PCI\VEN_10DE&DEV_0270&SUBSYS_50011458&REV_A2\3&2411E6FE&0&48: nForce Memory Controller
PCI\VEN_10DE&DEV_0272&SUBSYS_02641458&REV_A2\3&2411E6FE&0&52: nForce Memory Controller
PCI\VEN_10DE&DEV_027E&SUBSYS_50001458&REV_A2\3&2411E6FE&0&07: nForce Memory Controller
PCI\VEN_10DE&DEV_027F&SUBSYS_50001458&REV_A2\3&2411E6FE&0&06: nForce Memory Controller
PCI\VEN_10DE&DEV_02F1&SUBSYS_50001458&REV_A2\3&2411E6FE&0&00: PCI standard RAM Controller
PCI\VEN_10DE&DEV_02F8&SUBSYS_50001458&REV_A2\3&2411E6FE&0&03: nForce Memory Controller
PCI\VEN_10DE&DEV_02F9&SUBSYS_50001458&REV_A2\3&2411E6FE&0&04: nForce Memory Controller
PCI\VEN_10DE&DEV_02FA&SUBSYS_50001458&REV_A2\3&2411E6FE&0&01: nForce HyperTransport Bridge
PCI\VEN_10DE&DEV_02FB&SUBSYS_00000000&REV_A1\3&2411E6FE&0&20: PCI standard PCI-to-PCI bridge
PCI\VEN_10DE&DEV_02FD&SUBSYS_00000000&REV_A1\3&2411E6FE&0&18: PCI standard PCI-to-PCI bridge
PCI\VEN_10DE&DEV_02FE&SUBSYS_50001458&REV_A2\3&2411E6FE&0&02: nForce Memory Controller
PCI\VEN_10DE&DEV_02FF&SUBSYS_50001458&REV_A2\3&2411E6FE&0&05: nForce Memory Controller
PCI\VEN_1106&DEV_3044&SUBSYS_10001458&REV_80\4&DC268A3&0&7080: VIA OHCI Compliant IEEE 1394 Host Controller
PCI\VEN_1412&DEV_1712&SUBSYS_1138153B&REV_02\4&DC268A3&0&3880: DMX 6fire 24/96
PCI\VEN_1412&DEV_1724&SUBSYS_36301412&REV_01\4&DC268A3&0&3080: M-Audio Revolution
PCI\VEN_14F1&DEV_8880&SUBSYS_78010070&REV_0F\4&59B10B8&0&0018: Multimedia Video Controller
30 matching device(s) found.
 
=========== 
USB Devices 
=========== 
USB\ROOT_HUB\4&354DBDA&0                                    : USB Root Hub
USB\ROOT_HUB20\4&346B7D9E&0                                 : USB Root Hub
USB\VID_046D&PID_C317\5&21302E94&0&3                        : USB Composite Device
USB\VID_046D&PID_C317&MI_00\6&1BC86E07&0&0000               : USB Human Interface Device
USB\VID_046D&PID_C317&MI_01\6&1BC86E07&0&0001               : USB Human Interface Device
USB\VID_0A4D&PID_008E\5&21302E94&0&4                        : USB Composite Device
USB\VID_0A4D&PID_008E&MI_00\6&11300480&0&0000               : USB Audio Device
USB\VID_0A4D&PID_00F1\5&21302E94&0&2                        : USB Composite Device
USB\VID_0A4D&PID_00F1&MI_00\6&35E5A49A&0&0000               : USB Audio Device
9 matching device(s) found.
 
============= 
Input Devices 
============= 
HID\VID_046D&PID_C317&MI_00\7&312ACAE1&0&0000               : Logitech HID-Compliant Keyboard
HID\VID_046D&PID_C317&MI_01&COL01\7&19673E9C&0&0000         : Logitech HID Keyboard Power Key
HID\VID_046D&PID_C317&MI_01&COL02\7&19673E9C&0&0001         : Logitech HID Keyboard Consumer Controls
3 matching device(s) found.
 
============ 
ACPI Devices 
============ 
ACPI\AUTHENTICAMD_-_X86_FAMILY_15_MODEL_35\_0               : AMD Athlon(tm) 64 X2 Dual Core Processor 4400+
ACPI\AUTHENTICAMD_-_X86_FAMILY_15_MODEL_35\_1               : AMD Athlon(tm) 64 X2 Dual Core Processor 4400+
ACPI\FIXEDBUTTON\2&DABA3FF&0                                : ACPI Fixed Feature Button
ACPI\NVRAIDBUS\3&2411E6FE&0                                 : NVIDIA nForce(tm) RAID Class Controller
ACPI\PNP0000\3&2411E6FE&0                                   : Programmable interrupt controller
ACPI\PNP0100\3&2411E6FE&0                                   : System timer
ACPI\PNP0200\3&2411E6FE&0                                   : Direct memory access controller
ACPI\PNP0401\3&2411E6FE&0                                   : ECP Printer Port (LPT1)
ACPI\PNP0501\1                                              : Communications Port (COM1)
ACPI\PNP0700\3&2411E6FE&0                                   : Standard floppy disk controller
ACPI\PNP0800\3&2411E6FE&0                                   : System speaker
ACPI\PNP0A06\3&473F1A46&0                                   : Extended IO Bus
ACPI\PNP0A08\1                                              : PCI bus
ACPI\PNP0B00\3&2411E6FE&0                                   : System CMOS/real time clock
ACPI\PNP0C01\2&DABA3FF&0                                    : System board
ACPI\PNP0C02\1                                              : Motherboard resources
ACPI\PNP0C02\5                                              : Motherboard resources
ACPI\PNP0C04\3&2411E6FE&0                                   : Numeric data processor
ACPI\PNP0C0C\2&DABA3FF&0                                    : ACPI Power Button
ACPI\PNP0F13\3&2411E6FE&0                                   : PS/2 Compatible Mouse
ACPI_HAL\PNP0C08\0                                          : Microsoft ACPI-Compliant System
ROOT\ACPI_HAL\0000                                          : ACPI Multiprocessor PC
22 matching device(s) found.

This may be my fault... here is what happens

windows xp pro (sp3) setup gets to installing the networking components, actually it finishes installing networking components and then just before starting the "copy files" part of setup it then reboots and restarts setup gets to that point and reboots again...

this only happens after using the DriverPacks slipstreamer...

here is the log...
http://pursuit4perfection.biz/files/DPs … _00-08.log

please let me know what other info/logs you may need... thanks!

oh... this may be relevant... or not...

this is an unattended disc built from an sp0 disc with sp3 slipstreamed then a post sp3 update pack slipstreamed with a number of program addons including ie7 and wmp11...etc... but I built an iso before doing the driver pack slipstreaming and tested it, and everything installed and booted as it should have and I had no issues until running the DPsBase and building that ISO...

also using all main DriverPacks (except for graphics b&c) and a couple or 3rd party DriverPacks...
DP_Chipset_wnt5_x86-32_803.7z
DP_CPU_wnt5_x86-32_804.7z
DP_Graphics_A_wnt5_x86-32_8102.7z
DP_LAN_wnt5_x86-32_8053.7z
DP_MassStorage_wnt5_x86-32_805.7z
DP_Sound_A_wnt5_x86-32_805.7z
DP_Sound_B_wnt5_x86-32_805.7z
DP_WLAN_wnt5_x86-32_806.7z

3rd party packs:
DP_Input_wnt5_x86-32_070923.7z
DP_Misc_wnt5_x86-32_71216.7z
DP_Monitor_wnt5_x86-32_07111.7z
DP_Scanner_wnt5_x86-32_60831.7z
DP_USB_wnt5_x86-32_80224.7z
DP_Virtual_wnt5_x86-32_708.7z
DP_Broadband_wnt5_x86-32_70416.7z

again thanks for any help you may be able to lend!

O.K. so staying away from SP3 till it's fixed and public... thanks guys!

OverFlow wrote:

did you use RVM to integrate the RVM RVMUpdatePack2.1.11 (or other RVMAddons_)as well or just for the slipstream of SP3

ok used a clean sp2 source and slipped rvm update via nlite then when i tried to slip sp3 using nlite it requires you to remove previous updates to apply sp3 so you're back to not having 888111... or did you have other reasoning for asking about this?

OverFlow wrote:

did you use RVM to integrate the RVM RVMUpdatePack2.1.11 (or other RVMAddons_)as well or just for the slipstream of SP3

Is this necessary before integrating SP3? or do you think this would take care of the 888111 integration issue if we were to do the RVM update prior to slipping SP3? and eliminate the need for the 888111 addon?

I am getting the same error:

nLite SP3
nLite 888111 addon
got the missing files error

noticed that files weren't copied properly... so I manually copied the files, made sure txtsetup, dosnet, svcpack and sysoc all reflected the correct files as noted in the entries.ini of the 888111 addon...

tried slipstreaming and got the error 888111 and no SP1 or SP2 detected error, but it seemed to finish... so I burned the disk and tried an install, it seemed to install fine, but after installation complete it goes into infinite reboot after about half a second of the Windows XP loading logo screen...

what other info do you need to know so I can be of more help?

the latest version on the site for sound b is 7.10.1 and that is what I have, which according to the changelog on the page says something about removing that exe you are talking about, but must have just forgotten to update the inf...

thanks again for everything... I truly do apologize for frustrating you...

there weren't ever any hard feelings... please understand that... I realize I was late posting my logs... I apologize... and the night I tried posting them I got really frustrated because the board kept timing out and either it wouldn't post or for some reason it was causing me to double/triple post... so I gave up after posting the finisher log...

I really do appreciate EVERYONE's input as it has helped me understand some things better.

O.K. one last question... I actually have a DMX 6Fire soundcard, do I need to delete that entire section of the inf, or just the reference to the T_DMX.exe? Removing that section won't prevent it from installing the drivers I need, is all I'm asking I guess... sorry for the ignorance.

Thanks again in advance, you have been very helpful and I will certainly donate as soon as I can.

look I'm not trying to argue here, just trying to find a solution... because I get this error NO MATTER HOW DPsFnshr.exe is called, whether it's from a normal DP_BASE install. I have tried GUIRunOnce & Custom (manually double clicking the exe in windows explorer that is copied to C:\ via DP_BASE) and my script. I wasn't trying to reinvent the wheel with my script, just had it there for redundancy so it could be run if for some reason the DP_BASE didn't do it's job the first time.

I have NOT ignored ANYTHING anyone of you has said.

My main question in the first place still hasn't been answered, what "external program" is it (DPsFnshr.exe) trying to "execute"????

It isn't a matter of DPsFnshr.exe not being in the proper place as it is DPsFnshr.exe which is spitting the error...

what the point of your last comment is I have no idea as I never once said anything about being or claiming to be the first dual boot(er) here... I only stated my intentions... jeez

As I have also stated earlier in this thread DPsFnshr.exe (7.01.6) works flawlessly at finishing on this same exact source (only difference being the BASE)

as for the registry entry I know it isn't being overwritten as WPI is called @ entry 999 and I have Finisher set via BASE to be called @ 937 or whatever the default is.

IT IS RUNNING, but I get this error:
http://i7.tinypic.com/6ywjdwl.jpg

if you don't want to help, then don't I won't be offended as I have already found a temp. solution for now...

to Tiger: yes i know what you mean about the folders, that is what I had done. Put files in $OEM$\$1 but hadn't tried putting them in $OEM$\$$ (that is what I was asking about putting them in systemdrive ($OEM$\$1) or systemroot ($OEM$\$$))

Overflow: I had actually caught that :CHECK2 (:DOPNFCHECK2) error already... didn't realize I had posted that version of my script though... sorry... I'm not a script kiddie... and not asking you to debug my cmd/bat file I just posted it just an enthusiast trying to get the most out of an unattended xp cd... as I said earlier, I dual boot XP so I can have one setup isolated for audio production.

actually do you mean %systemdrive% or %systemroot%? I put it manually to %systemdrive% but not to the %systemroot%... I must have misunderstood... anyways... as noted above I have a temporary fix, but am not so sure of how good of a fix it is... don't know the differences between 7.01.6 and 7.05.2 finishers.