1 Reply by severach

(5 replies, posted in DriverPack Sound)

I have the same problem with a Dell D620. It is a SigmaTel High Definition Audio CODEC even though HWIDS doesn't list it as that. Here are the HWIDS after the right driver has been installed.

=========== 
PCI Devices 
=========== 
PCI\VEN_10DE&DEV_01D7&SUBSYS_01C21028&REV_A1\4&1C9EC085&0&0008: NVIDIA Quadro NVS 110M
PCI\VEN_1217&DEV_6972&SUBSYS_01C21028&REV_40\4&2FE911E8&0&08F0: O2Micro OZ6912 CardBus Controller
PCI\VEN_14E4&DEV_1600&SUBSYS_01C21028&REV_02\4&378EDFA4&0&00E2: Broadcom NetXtreme 57xx Gigabit Controller
PCI\VEN_14E4&DEV_4311&SUBSYS_00071028&REV_01\4&360A6DE&0&00E1: Dell Wireless 1390 WLAN Mini-Card
PCI\VEN_8086&DEV_2448&SUBSYS_00000000&REV_E1\3&61AAA01&0&F0 : Intel(R) 82801 PCI Bridge - 2448
PCI\VEN_8086&DEV_27A0&SUBSYS_00000000&REV_03\3&61AAA01&0&00 : Mobile Intel(R) 945GM/GU/PM/GMS/940GML/943GML and Intel(R) 945GT Express Processor to DRAM Controller - 27A0
PCI\VEN_8086&DEV_27A1&SUBSYS_00000000&REV_03\3&61AAA01&0&08 : Mobile Intel(R) 945GM/GU/PM/GMS/940GML/943GML and Intel(R) 945GT Express PCI Express Root Port - 27A1
PCI\VEN_8086&DEV_27B9&SUBSYS_00000000&REV_01\3&61AAA01&0&F8 : Intel(R) 82801GBM (ICH7-M/U) LPC Interface Controller - 27B9
PCI\VEN_8086&DEV_27C4&SUBSYS_01C21028&REV_01\3&61AAA01&0&FA : Intel(R) 82801GBM/GHM (ICH7-M Family) Serial ATA Storage Controller - 27C4
PCI\VEN_8086&DEV_27C8&SUBSYS_01C21028&REV_01\3&61AAA01&0&E8 : Intel(R) 82801G (ICH7 Family) USB Universal Host Controller - 27C8
PCI\VEN_8086&DEV_27C9&SUBSYS_01C21028&REV_01\3&61AAA01&0&E9 : Intel(R) 82801G (ICH7 Family) USB Universal Host Controller - 27C9
PCI\VEN_8086&DEV_27CA&SUBSYS_01C21028&REV_01\3&61AAA01&0&EA : Intel(R) 82801G (ICH7 Family) USB Universal Host Controller - 27CA
PCI\VEN_8086&DEV_27CB&SUBSYS_01C21028&REV_01\3&61AAA01&0&EB : Intel(R) 82801G (ICH7 Family) USB Universal Host Controller - 27CB
PCI\VEN_8086&DEV_27CC&SUBSYS_01C21028&REV_01\3&61AAA01&0&EF : Intel(R) 82801G (ICH7 Family) USB2 Enhanced Host Controller - 27CC
PCI\VEN_8086&DEV_27D0&SUBSYS_00000000&REV_01\3&61AAA01&0&E0 : Intel(R) 82801G (ICH7 Family) PCI Express Root Port - 27D0
PCI\VEN_8086&DEV_27D2&SUBSYS_00000000&REV_01\3&61AAA01&0&E1 : Intel(R) 82801G (ICH7 Family) PCI Express Root Port - 27D2
PCI\VEN_8086&DEV_27D4&SUBSYS_00000000&REV_01\3&61AAA01&0&E2 : Intel(R) 82801G (ICH7 Family) PCI Express Root Port - 27D4
PCI\VEN_8086&DEV_27D8&SUBSYS_01C21028&REV_01\3&61AAA01&0&D8 : Microsoft UAA Bus Driver for High Definition Audio
PCI\VEN_8086&DEV_27DA&SUBSYS_01C21028&REV_01\3&61AAA01&0&FB : Intel(R) 82801G (ICH7 Family) SMBus Controller - 27DA
19 matching device(s) found.
 
=========== 
USB Devices 
=========== 
USB\ROOT_HUB\4&16B3F35C&0                                   : USB Root Hub
USB\ROOT_HUB\4&3357D24F&0                                   : USB Root Hub
USB\ROOT_HUB\4&529CAA5&0                                    : USB Root Hub
USB\ROOT_HUB\4&84DA6E5&0                                    : USB Root Hub
USB\ROOT_HUB20\4&167C9B3&0                                  : USB Root Hub
USB\VID_0B97&PID_7761\6&75861D2&0&3                         : Generic USB Hub
USB\VID_0B97&PID_7762\7&312B4FD&0&2                         : USB Smart Card reader
USB\VID_413C&PID_A005\5&1187D97F&0&2                        : Generic USB Hub
8 matching device(s) found.
 
============= 
Input Devices 
============= 
No matching devices found.
 
============ 
ACPI Devices 
============ 
ACPI\ACPI0003\2&DABA3FF&0                                   : Microsoft AC Adapter
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_14\_0                : Genuine Intel(R) CPU           T2500  @ 2.00GHz
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_14\_1                : Genuine Intel(R) CPU           T2500  @ 2.00GHz
ACPI\PNP0000\4&25E2FF18&0                                   : Programmable interrupt controller
ACPI\PNP0100\4&25E2FF18&0                                   : System timer
ACPI\PNP0200\4&25E2FF18&0                                   : Direct memory access controller
ACPI\PNP0303\4&25E2FF18&0                                   : Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
ACPI\PNP0501\4&25E2FF18&0                                   : Communications Port (COM1)
ACPI\PNP0800\4&25E2FF18&0                                   : System speaker
ACPI\PNP0A03\2&DABA3FF&0                                    : PCI bus
ACPI\PNP0B00\4&25E2FF18&0                                   : System CMOS/real time clock
ACPI\PNP0C01\1                                              : System board
ACPI\PNP0C01\2                                              : System board
ACPI\PNP0C01\3                                              : System board
ACPI\PNP0C01\4                                              : System board
ACPI\PNP0C01\5                                              : System board
ACPI\PNP0C04\4&25E2FF18&0                                   : Numeric data processor
ACPI\PNP0C0A\1                                              : Microsoft ACPI-Compliant Control Method Battery
ACPI\PNP0C0A\2                                              : Microsoft ACPI-Compliant Control Method Battery
ACPI\PNP0C0C\2&DABA3FF&0                                    : ACPI Power Button
ACPI\PNP0C0D\2&DABA3FF&0                                    : ACPI Lid
ACPI\PNP0C0E\2&DABA3FF&0                                    : ACPI Sleep Button
ACPI\PNP0F13\4&25E2FF18&0                                   : PS/2 Compatible Mouse
ACPI\THERMALZONE\THM_                                       : ACPI Thermal Zone
ACPI_HAL\PNP0C08\0                                          : Microsoft ACPI-Compliant System
ROOT\ACPI_HAL\0000                                          : ACPI Multiprocessor PC
26 matching device(s) found.

Go to forum: DriverPack Sound

2 Reply by severach

(4 replies, posted in Feature Requests)

OverFlow wrote:

Do you have a suggestion as to how that might be accompished?

Right now you do no error checking. You call the unpacker and take whatever it provides. You should check to see if the unpack resulted in an error and halt if so.

the packs are always changing and can be modified by the end user. if i were to write a rotine to check them against the server it would / might prevent end users from modifying packs.

We don't need that kind of checking. Just check each file you unpack for an unpack error. 7zip tells you when there is an unpack error. BASE just doesn't check for it.

I belive it is the users responsibility to verify thier downloads. that is why we put thier sizes on the website.

The computer corrupted them without changing their sizes. There are too many things in the world for users to check them all. BASE needs to do the checking.

Helmi wrote:

7Zip does have the option to check an archive for consistency.

Yes, that's how I found the problem.

Of course, it would be nice having BASE doing this automatically

Try "imperative". Only a few minutes of coding cuts into the problems.

It only involves a very few mouse-clicks (mark all files, right-click and select verify archives).

It involves a lot of mouse clicks since most people do not install 7zip.

OTOH, corrupted DLs are very few and far between

That's why it's so important that BASE check for damaged files when unpacking. I'm not going to check every archive for errors when 99.99% of them come through perfectly. BASE can check them every time without wasting the users time.

If you'd rather I can post what I was going to write originally and let you figure out what the problem is.

"Driverpacks mass storage is broken again. I get a VIBUS.SYS corrupted on boot."

Go to forum: Feature Requests

3 Topic by severach

(4 replies, posted in Feature Requests)

I had some 7z files get corrupted. BASE unpacked the corrupted parts as 0 length files, CAB'd them up, and wrote them to the disk image without any  error message. I had to work backwards from disks that don't boot, 71 and 72 byte CAB files on the disk and in the QSC, and into the 7z files to find out what was wrong. Firefox was able to pull good second copies out of it's cache so my computer corrupted the files during the copy. Should you ever post a damaged file, a lot of bad disks will be created without any warning.

Bad archive detection needs to be added as soon as possible. You might see a nice drop in the complaint level.

Go to forum: Feature Requests

4 Reply by severach

(4 replies, posted in DriverPack Graphics)

When the Windows Installer selects a fully functional Microsoft video driver, XP starts in 640x480 on the first boot then asks to be raised to 800x600. A downloaded video driver automatically bumps the resolution above 640x480 without asking on reboot. The automatically selected resolution may be 800x600, 1024x768, or higher, but not necessarily the highest mode because there are too many monitor and card combinations that report impossibly high values. The refresh rate is usually the highest reported for tube monitors or the lowest reported for LCD monitors. ATI, nVidia, and Intel installers all work this way and must work this way to minimize complaints that the driver didn't solve the bad resolution and colors problem and it's handy because it's one less setting that needs to be twiddled. I can't remember any driver brand that does not bump the resolution without asking if the previous was 640x480 or unknown.

Question: If the Windows Installer selects a Driverpacks video driver which are exactly the same as the drivers we download, does XP automatically start in a mode higher than 640x480 or does it start in 640x480 and ask to be raised?

The video problems on the first boot means that a Driverpacks video driver does not start at 640x480 and ask to be raised. Since the drivers are unmodified from the download distribution it is no surprise that they automatically bump the resolution above 640x480 even when they are installed by the Windows Installer supplied by DriverPacks. If you happen to have a bad monitor you'll only see "unsupported mode" until you use F8-VGA mode.

Microsoft must have thought that broken monitors were common enough that they hacked all the video drivers they supply to block the mode bump on boot to ensure they boot at 640x480, then ask the user to raise it to 800x600. My broken monitor which isn't broken is Compaq 15" LCD cycled out of use by a large corporate buyer, which should make it obvious why Microsoft is so careful switching away from 640x480 even though any monitor used with XP should support 800x600. Since Microsoft doesn't write the drivers but instead gets them from the OEMs, there must be an INF setting that blocks this automatic resolution bump. To make Driverpacks video drivers as reliable as the Microsoft video drivers this hack needs to be duplicated.

WINNT.SIF is a good idea and might work for the above but there's a place where it won't work. The resolution for the Windows Installer may be locked but the refresh rate is not. I installed onto a Compaq laptop and when the DriverPacks video driver was installed the refresh rate was bumped to the max. The screen became fuzzy but was still readable for the remainder of the install. The first boot chose a higher resolution which had a more appropriate refresh. Other installs may not be so lucky and WINNT.SIF won't help here because it was never expected that any video driver available to the Windows Installer would up and change the refresh rate without being asked to.

The block resolution change on boot setting needs to be found and applied. Any video brand that Microsoft has ever included should have the setting ready and waiting. Brands that Microsoft have not badgered into compliance may not have a setting available.

Go to forum: DriverPack Graphics

5 Topic by severach

(4 replies, posted in DriverPack Graphics)

All too often the video driver will choose the highest possible mode, something like 1900x1600 @ 105Hz making it impossible to complete setup with a monitor that reports capabilities that it doesn't actually have. The lowest possible video mode should be chosen. Let the user choose a higher mode later.

Go to forum: DriverPack Graphics

6 Reply by severach

(1 replies, posted in DriverPack Mass Storage)

I suspect your message actually said 'LSI_SAS.sys'. A search up this.

http://forum.driverpacks.net/viewtopic.php?id=1468

It is being worked on.

Go to forum: DriverPack Mass Storage

7 Reply by severach

(13 replies, posted in Software)

Shouldn't this thread be moved to DriverPack MassStorage.

I wrote an XP Home CD from DP_MassStorage_wnt5_x86-32_7091.7z and got this ATIIDE.sys error. With Windows 2000 down from LSI_SAS.SYS and XP Home down from ATIIDE.sys I'm scrambling for an old version but that anti leecher keeps getting in the way. Maybe I can find a way around it...

coolAll your files are belong to us.

Go to forum: Software

8 Reply by severach

(17 replies, posted in DriverPack Mass Storage)

I wrote disks with and without QSC and Windows 2000 halted with this error. The file is there. The CAB is not damaged and compares exactly with the original. Anyone know why the Windows installer can't continue after getting this harmless error?

edit: DP_MassStorage_wnt5_x86-32_7091.7z; Windows 2000 Pro OEM

Go to forum: DriverPack Mass Storage

9 Reply by severach

(8 replies, posted in Site & Forum Issues And Feedback)

No need for DP_BASE to learn how to handle torrents as it's kind of a major operaton to implement. All it needs to know is how to download torrent files and submit them to your normal torrent client.

Go to forum: Site & Forum Issues And Feedback

10 Reply by severach

(15 replies, posted in Frequently Asked Questions)

Dumping a KTD on an already installed Windows wouldn't be much use to me. I'd much rather have an executable like DP_BASE scan my hardware and perform all upgrades.

KTD would be a poor testbed because it would be rarely used. The way I want it would be an excellent testbed since it would get used all the time.

For example, say a DP install crashes. The solution is to install from a non DP enhanced media and install all the drivers after Windows gets up and running. The end result would be exactly the same and hopefully the malfunctioning driver would be easy to identify.

Driverpacks is too good to limit it to new installs from custom media.

Go to forum: Frequently Asked Questions

11 Reply by severach

(8 replies, posted in DriverPack Sound)

I have the same problem with a Latitude D620. Neither the SIGMATEL STAC 92XX C-Major HD Audio nor the O2Micro OZ77C6 USB CCID SmartCard Controller were recognized.

Modem Pack: No
Sound B: Both sounds were used

 
=========== 
PCI devices 
=========== 
 
 
PCI\VEN_10DE&DEV_01D7&SUBSYS_01C21028&REV_A1\4&1C9EC085&0&0008: NVIDIA Quadro NVS 110M
PCI\VEN_1217&DEV_6972&SUBSYS_01C21028&REV_40\4&2FE911E8&0&08F0: O2Micro OZ6912/601/711E0 CardBus/SmartCardBus Controller
PCI\VEN_14E4&DEV_1600&SUBSYS_01C21028&REV_02\4&378EDFA4&0&00E2: Broadcom NetXtreme 57xx Gigabit Controller
PCI\VEN_14E4&DEV_4311&SUBSYS_00071028&REV_01\4&360A6DE&0&00E1: Dell Wireless 1390 WLAN Mini-Card
PCI\VEN_8086&DEV_2448&SUBSYS_00000000&REV_E1\3&61AAA01&0&F0 : Intel(R) 82801 PCI Bridge - 2448
PCI\VEN_8086&DEV_27A0&SUBSYS_00000000&REV_03\3&61AAA01&0&00 : Mobile Intel(R) 945GM/PM/GMS/940GML/943GML and Intel(R) 945GT Express Processor to DRAM Controller - 27A0
PCI\VEN_8086&DEV_27A1&SUBSYS_00000000&REV_03\3&61AAA01&0&08 : Mobile Intel(R) 945GM/PM/GMS/940GML/943GML and Intel(R) 945GT Express PCI Express Root Port - 27A1
PCI\VEN_8086&DEV_27B9&SUBSYS_00000000&REV_01\3&61AAA01&0&F8 : Intel(R) 82801GBM (ICH7-M) LPC Interface Controller - 27B9
PCI\VEN_8086&DEV_27C4&SUBSYS_01C21028&REV_01\3&61AAA01&0&FA : Intel(R) 82801GBM/GHM (ICH7-M Family) Serial ATA Storage Controller - 27C4
PCI\VEN_8086&DEV_27C8&SUBSYS_01C21028&REV_01\3&61AAA01&0&E8 : Intel(R) 82801G (ICH7 Family) USB Universal Host Controller - 27C8
PCI\VEN_8086&DEV_27C9&SUBSYS_01C21028&REV_01\3&61AAA01&0&E9 : Intel(R) 82801G (ICH7 Family) USB Universal Host Controller - 27C9
PCI\VEN_8086&DEV_27CA&SUBSYS_01C21028&REV_01\3&61AAA01&0&EA : Intel(R) 82801G (ICH7 Family) USB Universal Host Controller - 27CA
PCI\VEN_8086&DEV_27CB&SUBSYS_01C21028&REV_01\3&61AAA01&0&EB : Intel(R) 82801G (ICH7 Family) USB Universal Host Controller - 27CB
PCI\VEN_8086&DEV_27CC&SUBSYS_01C21028&REV_01\3&61AAA01&0&EF : Intel(R) 82801G (ICH7 Family) USB2 Enhanced Host Controller - 27CC
PCI\VEN_8086&DEV_27D0&SUBSYS_00000000&REV_01\3&61AAA01&0&E0 : Intel(R) 82801G (ICH7 Family) PCI Express Root Port - 27D0
PCI\VEN_8086&DEV_27D2&SUBSYS_00000000&REV_01\3&61AAA01&0&E1 : Intel(R) 82801G (ICH7 Family) PCI Express Root Port - 27D2
PCI\VEN_8086&DEV_27D4&SUBSYS_00000000&REV_01\3&61AAA01&0&E2 : Intel(R) 82801G (ICH7 Family) PCI Express Root Port - 27D4
PCI\VEN_8086&DEV_27D8&SUBSYS_01C21028&REV_01\3&61AAA01&0&D8 : Microsoft UAA Bus Driver for High Definition Audio
PCI\VEN_8086&DEV_27DA&SUBSYS_01C21028&REV_01\3&61AAA01&0&FB : Intel(R) 82801G (ICH7 Family) SMBus Controller - 27DA
19 matching device(s) found.
 
 
=========== 
USB devices 
=========== 
 
USB\ROOT_HUB\4&16B3F35C&0                                   : USB Root Hub
USB\ROOT_HUB\4&3357D24F&0                                   : USB Root Hub
USB\ROOT_HUB\4&529CAA5&0                                    : USB Root Hub
USB\ROOT_HUB\4&84DA6E5&0                                    : USB Root Hub
USB\ROOT_HUB20\4&167C9B3&0                                  : USB Root Hub
USB\VID_0B97&PID_7761\6&75861D2&0&3                         : Generic USB Hub
USB\VID_0B97&PID_7762\7&312B4FD&0&2                         : USB Smart Card reader
USB\VID_1241&PID_1166\5&1D4952DC&0&2                        : USB Human Interface Device
USB\VID_413C&PID_A005\5&1187D97F&0&2                        : Generic USB Hub
9 matching device(s) found.

Go to forum: DriverPack Sound

12 Topic by severach

(0 replies, posted in DriverPack Mass Storage)

This model may be incorrectly reported as a P4S8000-X. A closer look at the board shows that the last digit is actually a "D".

I had to install Windows XP Pro SP2 from a non DP enhanced CD and F6 to install the storage driver downloaded from Asus to support the SATA boot drive. A DP enhanced CD blue screens shortly after the GUI setup starts. This is quite a hassle since finding a working floppy disk takes longer than building a DP enhanced CD.

All but the sound card is supported by a vanilla XP install.

 
=========== 
PCI devices 
=========== 
 
 
PCI\VEN_1039&DEV_0003&SUBSYS_00000000&REV_00\3&267A616A&0&08: SIS Processor to AGP Controller
PCI\VEN_1039&DEV_0180&SUBSYS_810E1043&REV_01\3&267A616A&0&28: SiS 180 RAID Controller
PCI\VEN_1039&DEV_0655&SUBSYS_00000000&REV_50\3&267A616A&0&00: PCI standard host CPU bridge
PCI\VEN_1039&DEV_0900&SUBSYS_80A71043&REV_91\3&267A616A&0&20: SiS 900-Based PCI Fast Ethernet Adapter
PCI\VEN_1039&DEV_0964&SUBSYS_00000000&REV_36\3&267A616A&0&10: PCI standard ISA bridge
PCI\VEN_1039&DEV_5513&SUBSYS_810E1043&REV_01\3&267A616A&0&15: SiS PCI IDE Controller
PCI\VEN_1039&DEV_7001&SUBSYS_810E1043&REV_0F\3&267A616A&0&18: SiS 7001 PCI to USB Open Host Controller
PCI\VEN_1039&DEV_7001&SUBSYS_810E1043&REV_0F\3&267A616A&0&19: SiS 7001 PCI to USB Open Host Controller
PCI\VEN_1039&DEV_7001&SUBSYS_810E1043&REV_0F\3&267A616A&0&1A: SiS 7001 PCI to USB Open Host Controller
PCI\VEN_1039&DEV_7002&SUBSYS_810E1043&REV_00\3&267A616A&0&1B: SiS PCI to USB Enhanced Host Controller
PCI\VEN_1039&DEV_7012&SUBSYS_810D1043&REV_A0\3&267A616A&0&17: Multimedia Audio Controller
PCI\VEN_10DE&DEV_0322&SUBSYS_00000000&REV_A1\4&13EB4D69&0&0008: NVIDIA GeForce FX 5200  (Microsoft Corporation)
12 matching device(s) found.
 
 
=========== 
USB devices 
=========== 
 
USB\ROOT_HUB\4&272A948&0                                    : USB Root Hub
USB\ROOT_HUB\4&2B53C2AA&0                                   : USB Root Hub
USB\ROOT_HUB\4&2EDEF877&0                                   : USB Root Hub
USB\ROOT_HUB20\4&2DEB0156&0                                 : USB Root Hub
USB\VID_154B&PID_0005\6E641B0013D6                          : USB Mass Storage Device
USBSTOR\DISK&VEN_PNY&PROD_USB_2.0_FD&REV_PMAP\6E641B0013D6&0: PNY USB 2.0 FD USB Device
6 matching device(s) found.

Go to forum: DriverPack Mass Storage