Thought I would give this a quick look but on startup I get an error message that the source text of the license agreement was changed and it won't continue

WOW!!!! This is AWESOME... not only have you managed to get the packs final but being able to install my .NET with the DP will allow me to clean up some of my custom RunOnceEx items and some scripts I did... I have some work to do today lol... I will be installing three to four different laptops today with your new work and I will report back THANKS

153

(5 replies, posted in News)

Just wanted to take a moment and wish everyone a great day and a Happy Thanksgiving!!! Thank You for this awesome forum!!!

compstuff wrote:
mr_smartepants wrote:
compstuff wrote:

when I manually deleted it after "unlocking" the file handle, the service failed

Whoa!  If the file is still in use after a restart and the service fails when it's deleted then we have another problem.

I did this 2x and had the same result each time...

Well I actually tried this again since I am doing other testing and yes it happened a 3rd time so it is consistent

mr_smartepants wrote:
compstuff wrote:

when I manually deleted it after "unlocking" the file handle, the service failed

Whoa!  If the file is still in use after a restart and the service fails when it's deleted then we have another problem.

I did this 2x and had the same result each time...

mr_smartepants wrote:

No need to merge them.  Check the SHA1 hashes of both .inf and check for matches in either of the .cat files.  You might be able to put both .infs in the same folder and maintain signing (renaming an .inf doesn't affect it's hash).

Is the Thumbprint sha1 of the cat file supposed to match the sha1 of the corresponding inf? IF it is then none of these match up on the files I have... so I am confused roll

mr_smartepants wrote:

This is an old bug where DriverPacks Finisher can't delete files that are in use.  That's why DriverPacks Finisher creates a reg entry to clean up after itself after the next reboot.

I know from the finisher log that it states it added a reg entry for the cleanup but it still didn't delete the D directory, plus when I manually deleted it after "unlocking" the file handle, the service failed so thats why I checked the reg for the entry and had to change it from the D folder to the proper programs folder. I will run a small reg file during my cleanup which will handle this in the meantime but thats not the real fix

I just ran another test and noticed and odd issue... the audio works but the install leaves the D folders in the root with the stacsv.exe in it and the actual service is registered and running from that location... I was able to create a reg mod but why would it  do that?

Well after a really hectic week I am back at this issue... your help was actually dead accurate... it IS the O2 Micro... here is the link and I have already tested it on the laptop and it works:

http://support.us.dell.com/support/down … eid=292566

I am analyzing the inf files to see about updating the pack but am a little confused:

O2SDDISK.INF Misc_wnt5_x86-32_90909

; O2SDDISK.INF, O2Micro SD Disk Device INF file
; Copyright (c) 1997-2007 O2Micro Corp.

[Version]
Signature   = "$Windows NT$"
Class       = DiskDrive
ClassGuid   = {4D36E967-E325-11CE-BFC1-08002BE10318}
Provider    = %O2Micro%
DriverVer   = 03/16/2007,5.1.2600.2180
Catalogfile = o2sddisk.cat

[Manufacturer]
%O2Micro% = O2SDDISK

[O2SDDISK]
; customize the hwid to match SCSI INQUIRY data
%O2SDD.DeviceDesc% = DriverInstall, SCSI\DiskO2Micro_SD______________0001

[DriverInstall.NT]
Include = disk.inf
Needs   = expect_surprise_removal_disk_install.NT

[DriverInstall.NT.Services]
Needs   = expect_surprise_removal_disk_install.NT.Services

[DriverInstall.NT.HW]
Needs   = expect_surprise_removal_disk_install.NT.HW

[Strings]
O2Micro          = "O2Micro"
O2SDD.DeviceDesc = "O2Micro SD Disk Device"

O2SDDISK.INF Dell Update

; O2SDDISK.INF, O2Micro SD Disk Device INF file
; Copyright (c) 1997-2008 O2Micro Corp.

[Version]
Signature   = "$Windows NT$"
Class       = DiskDrive
ClassGuid   = {4D36E967-E325-11CE-BFC1-08002BE10318}
Provider    = %O2Micro%
DriverVer   = 08/04/2004,5.1.2600.5512
Catalogfile = o2sddisk.cat

[Manufacturer]
%O2Micro% = O2SDDISK

[O2SDDISK]
; customize the hwid to match SCSI INQUIRY data
%O2SDD.DeviceDesc% = DriverInstall, SCSI\DiskO2Micro_SD______________0001
%O2MMC.DeviceDesc% = DriverInstall, SCSI\DiskO2Micro_MMC_____________0001

[DriverInstall.NT]
Include = disk.inf
Needs   = expect_surprise_removal_disk_install.NT

[DriverInstall.NT.Services]
Needs   = expect_surprise_removal_disk_install.NT.Services

[DriverInstall.NT.HW]
Needs   = expect_surprise_removal_disk_install.NT.HW

[Strings]
O2Micro          = "O2Micro"
O2SDD.DeviceDesc = "O2Micro SD Disk Device"
O2MMC.DeviceDesc = "O2Micro MMC Disk Device"

Since the INQUIRY data and the Strings from the 90909 pack are included in the update do I just replace the inf?

O2MDDISK.INF Misc_wnt5_x86-32_90909

; O2MDDISK.INF, O2Micro O2Media Disk Device INF file
; Copyright (c) 1997-2007 O2Micro Corp.

[Version]
Signature   = "$Windows NT$"
Class       = DiskDrive
ClassGuid   = {4D36E967-E325-11CE-BFC1-08002BE10318}
Provider    = %O2Micro%
DriverVer   = 04/04/2007,5.1.2600.2180
Catalogfile = o2mddisk.cat

[Manufacturer]
%O2Micro% = O2MDDISK

[O2MDDISK]
;Customize the hwid to match SCSI INQUIRY data
%O2MDD.DeviceDesc% = DriverInstall, SCSI\DiskO2Micro_O2Media_________0001

[DriverInstall.NT]
Include = disk.inf
Needs   = expect_surprise_removal_disk_install.NT

[DriverInstall.NT.Services]
Needs   = expect_surprise_removal_disk_install.NT.Services

[DriverInstall.NT.HW]
Needs   = expect_surprise_removal_disk_install.NT.HW

[Strings]
O2Micro          = "O2Micro"
O2MDD.DeviceDesc = "O2Micro FlashMedia Disk Device"

O2MDDISK.INF Dell Update

; O2MDDISK.INF, O2Micro O2Media Disk Device INF file
; Copyright (c) 1997-2008 O2Micro Corp.

[Version]
Signature   = "$Windows NT$"
Class       = DiskDrive
ClassGuid   = {4D36E967-E325-11CE-BFC1-08002BE10318}
Provider    = %O2Micro%
DriverVer   = 08/04/2004,5.1.2600.5512
Catalogfile = o2mddisk.cat

[Manufacturer]
%O2Micro% = O2MDDISK

[O2MDDISK]
;Customize the hwid to match SCSI INQUIRY data
%O2MS.DeviceDesc%    = DriverInstall, SCSI\DiskO2Micro_MS/MSPRO________0001
%O2XD.DeviceDesc%    = DriverInstall, SCSI\DiskO2Micro_xDPicture_______0001

[DriverInstall.NT]
Include = disk.inf
Needs   = expect_surprise_removal_disk_install.NT

[DriverInstall.NT.Services]
Needs   = expect_surprise_removal_disk_install.NT.Services

[DriverInstall.NT.HW]
Needs   = expect_surprise_removal_disk_install.NT.HW

[Strings]
O2Micro          = "O2Micro"
O2MS.DeviceDesc = "O2Micro MS/PRO Disk Device"
O2XD.DeviceDesc = "O2Micro xDPicture Disk Device"

Do I combine the [O2MDDISK] and [Strings] items to create a new inf or does that screw up the signature?

Major... I customized the pack to experiment by making the following changes and it seemed to work but I am still experimenting:

Changed:
Removed SG\7
SG\9
IDT High Definition Audio CODEC Driver Disk Driver Ver=02/23/2009,6.10.0.6159 to 01/29/2009,5.10.0.6147 for V1520

http://support.dell.com/support/downloa … eid=298625

I decided to try the Intel updater program from the link above and it ran and produced the following logs but I still have the Device Manger error:

http://www.mediafire.com/?sharekey=80f1 … bfb1230ce0

Well there still is no Joy in Mass driver Land sad

The install finished but I still get an error in Device Manager... as much as I hate to admit it I am losing this battle and I am taking the gun back out... along with a bottle of wine :-)

Here are the logs and HWID's:

http://www.mediafire.com/?sharekey=80f1 … e4ff677d52

OK I put the gun away for the time being since it turns out I had a bad burn... go figure... in the middle of all this frustration to get a bad burn must be a test of my patience LOL

OH MAN I am ready to shoot myself yikes

I tried to create a simple mass storage pack to test out on the Vostro 1520 that I am having problems with and I got the perc2.sys error... I downloaded the Matrix Storage Manager from http://downloadcenter.intel.com/Detail_ … p;lang=eng and created  asingle folder with the files and also created:

DriverPack_MassStorage_wnt5_x86-32.ini

[DriverPack]
platform="wnt5_x86-32"
name="MassStorage"
; version 911intel02
classes="hdc,SCSIAdapter"
rootdir="D\M"
driverCount=

[i]
ms_count=1
ms_1_deviceName="Intel ESB2/ICH7/ICH8/ICH9/ICH10 SATA AHCI/RAID 8.9.0.1023"
ms_1_tag="iastor"
ms_1_sysFile="iastor.sys"
ms_1_hwids="PCI\VEN_8086&DEV_2681&CC_0106,PCI\VEN_8086&DEV_27C1&CC_0106,PCI\VEN_8086&DEV_27C5&CC_0106,PCI\VEN_8086&DEV_2821&CC_0106,PCI\VEN_8086&DEV_2829&CC_0106,PCI\VEN_8086&DEV_2922&CC_0106,PCI\VEN_8086&DEV_2929&CC_0106,PCI\VEN_8086&DEV_3A02&CC_0106,PCI\VEN_8086&DEV_3A22&CC_0106,PCI\VEN_8086&DEV_3B29&CC_0106,PCI\VEN_8086&DEV_3B2F&CC_0106,PCI\VEN_8086&DEV_3B22&CC_0106,PCI\VEN_8086&DEV_2682&CC_0104,PCI\VEN_8086&DEV_27C3&CC_0104,PCI\VEN_8086&DEV_27C6&CC_0104,PCI\VEN_8086&DEV_2822&CC_0104,PCI\VEN_8086&DEV_282A&CC_0104"
ms_1_isBusExtender=false
ms_1_exc_disableIfOS="w2k"

Where and why is the system looking for a perc2 controller???

Not making any progress here can you point me in a direction?

I tried the whole thing from scratch and yes of course it shows a device Manager error
I deleted the I5 folder and just kept I4 and that showed the same device Manager error
I tried creating a pack entry with the Dell driver and that fails completely and just keeps rebooting
SAD doesn't seem to make any changes for the installs at all

Yes I can supply logs etc but this has me spinning my wheels...

Uploaded DP_HID_wnt5_x86-32_91101.7z to 3rd Party Packs

Uploaded DP_Monitor_wnt5_x86-32_91101.7z to 3rd Party

168

(65 replies, posted in 3rd Party DriverPacks)

dell Vostro A860 Modem:

============
HDA Audio
============
HDAUDIO\FUNC_01&VEN_14F1&DEV_5051&SUBSYS_1028029A&REV_1000\4&36D388F1&0&0001: Audio Device on High Definition Audio Bus
HDAUDIO\FUNC_02&VEN_14F1&DEV_5051&SUBSYS_1028029A&REV_1000\4&36D388F1&0&0002: Modem Device on High Definition Audio Bus
2 matching device(s) found.

Dell Driver:
http://support.dell.com/support/downloa … eid=260233

Not sure how to update this pack and keep the format correct or I would... do you add a new entry and if so where or do I update the entries in the AC\05

I have made the following updates and wondered if you want me to upload the pack as a 3rd party release candidate?

Changes from 9.08.13

911D - COMPSTUFF

\S\2
Updated V13.0.4.0 to Synaptics Driver 14.0.3 08/27/2009

A3
Updated from 7.1.102.7 08/24/2007 to 7.4.102.102 03/06/2009

Would this be the right naming convention? DP_HID_wnt5_x86-32_911

The inf was a 0 byte file...

I have made the following updates and wondered if you want me to upload the pack as a 3rd party release candidate?
Changes since 9.08.130
11/16/09 - Compstuff - Replaced 0 byte nl171v.inf with correct NEC inf 07/03/2006,1.06.0703.1334
11/16/09 - Compstuff - Updated Synmaster 720N driver from 07/26/2006 ver. 2.0HC tot 03/28/2007 ver. 3.0HCr

EDIT: Would this be the right naming convention? DP_Monitor_wnt5_x86-32_911

Well I haven't been able to get this pack to work correctly for ages now and since 85% of all the systems I work on are Dells with either Synaptics or Alps I decided to break out the drivers and create separate packs. Now I have a pack for Synaptics and a packs for ALPS and of course the original pack with the updated drivers. Certainly not what I was looking for but my tests so far on three laptops have all worked, so until I have a better answer at least this resolves my problems with this.

I am having a problem with a Dell a860 installing the Blue Tooth using the 910 pack. I looked at the pack to try and update the driver but I really don't understand this pack so I couldn't.

Here are all the logs, HWID's etc including HWID's before and after installing the driver from Dell(Toshiba):
http://www.mediafire.com/?sharekey=80f1 … 2bd5edc68e

Here is the link to the actual driver:
http://support.dell.com/support/downloa … eid=265039

I have been trying a few different things to see if I could get this...

If I am wrong in any of this feel free to point it out :-)
From the HWID I found that the driver should be in the SG\9 folder so I ran a test by replacing the original driver in the folder with the one provided by Dell 01/29/2009 5.10.0.6147... then I ran the SAD
The driver didn't get updated so I decided to remove the device in Device Manager and let it try again ...when it did the new hardware wizard started and was asking for SG\7... needless to say that driver didn't work.
I manually ran the Dell driver setup which installed so I also included that log... not sure what to do from here...

OverFlow wrote:

the why is always contained in the setupapi.log and its friends wink Hint: open the windows folder and sort by time. The logs come to the top wink

I have been saving so many logs this week you would think I would have already posted them for you lol roll I will get the logs up today since I am still working and testing that system

OK here are the logs etc:
http://www.mediafire.com/?sharekey=80f1 … 60c1ce7296

175

(13 replies, posted in 3rd Party DriverPacks)

If you have any ideas I will test them this weekend to see if we can resolve this...