1 Reply by rdsok

(36 replies, posted in DriverPack Sound)

BhaGwaN,

Overflow was most certainly NOT being insulting .... you had been asked to provide specific information that was linked to twice already when you called him insulting... and yet you had still not provided that information which is plainly spelled out in the post you were linked to.

You have yet to provide any of the information that has now been mentioned numerous times now. You have only been rude to those that have simply been asking for your information in order to assist you.

I must say that if ignorance is bliss... then BhaGwaN, you my friend must be ecstatic considering the posts you have made.

It is either time for you to wake up and provide the information you have repeatedly been asked to provide... or stop posting because otherwise without that info it is a waste of everyone's time.

I would also recommend that you appologize to Overflow for the ignorance you have so obviously now shown upto this point and for you suggesting that him having to point what you have done incorrectly up to this point is somehow insulting to you...

Go to forum: DriverPack Sound

2 Reply by rdsok

(36 replies, posted in DriverPack Mass Storage)

You bet... I just noticed that I showed using the Sound A DP... actually that wasn't part of the build I did... I had it downloaded but not selected and had inadvertantly left that one in the list..

Go to forum: DriverPack Mass Storage

3 Reply by rdsok

(36 replies, posted in DriverPack Mass Storage)

CD Build with XP Pro SP2
MB - Giga-byte GA-M51GM-S2G
CPU - AMD Sempron64 2800+ AM2
MEM - 1024Mb ( 128Mb shared video )

Base 7.05.2
Chipset 7.10.1
CPU 7.04.1
Graphics C 7.09.1
LAN 7.10.1
MassStorage 7.11_nightly
Sound A 7.11!
Textmode - yes

Settings
Type - disc
DPsMethod - 2
Finisher - GUIRunOnce
KTD - false
QSC - no


=========== 
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_104C&DEV_8024&SUBSYS_10001458&REV_00\4&DC268A3&0&7080: Texas Instruments OHCI Compliant IEEE 1394 Host Controller
PCI\VEN_10DE&DEV_0242&SUBSYS_D0001458&REV_A2\3&2411E6FE&0&28: NVIDIA GeForce 6100
PCI\VEN_10DE&DEV_0260&SUBSYS_00000000&REV_A3\3&2411E6FE&0&50: PCI standard ISA bridge
PCI\VEN_10DE&DEV_0264&SUBSYS_02641458&REV_A3\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: Standard Dual Channel PCI IDE Controller
PCI\VEN_10DE&DEV_0267&SUBSYS_B0021458&REV_A1\3&2411E6FE&0&78: Standard Dual Channel PCI IDE Controller
PCI\VEN_10DE&DEV_0269&SUBSYS_E0001458&REV_A3\3&2411E6FE&0&A0: NVIDIA Network Bus Enumerator
PCI\VEN_10DE&DEV_026C&SUBSYS_A0021458&REV_A2\3&2411E6FE&0&81: Microsoft UAA Bus Driver for High Definition Audio
PCI\VEN_10DE&DEV_026D&SUBSYS_50041458&REV_A3\3&2411E6FE&0&58: Standard OpenHCD USB Host Controller
PCI\VEN_10DE&DEV_026E&SUBSYS_50041458&REV_A3\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: PCI standard RAM Controller
PCI\VEN_10DE&DEV_0272&SUBSYS_02641458&REV_A3\3&2411E6FE&0&52: PCI standard RAM Controller
PCI\VEN_10DE&DEV_027E&SUBSYS_50001458&REV_A2\3&2411E6FE&0&07: PCI standard RAM Controller
PCI\VEN_10DE&DEV_027F&SUBSYS_50001458&REV_A2\3&2411E6FE&0&06: PCI standard RAM 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: PCI standard RAM Controller
PCI\VEN_10DE&DEV_02F9&SUBSYS_50001458&REV_A2\3&2411E6FE&0&04: PCI standard RAM Controller
PCI\VEN_10DE&DEV_02FA&SUBSYS_50001458&REV_A2\3&2411E6FE&0&01: PCI standard RAM Controller
PCI\VEN_10DE&DEV_02FE&SUBSYS_50001458&REV_A2\3&2411E6FE&0&02: PCI standard RAM Controller
PCI\VEN_10DE&DEV_02FF&SUBSYS_50001458&REV_A2\3&2411E6FE&0&05: PCI standard RAM Controller
26 matching device(s) found.
 
 
=========== 
USB devices 
=========== 
 
USB\ROOT_HUB\4&12BE9683&0                                   : USB Root Hub
USB\ROOT_HUB20\4&282DDEF6&2                                 : USB Root Hub
USB\VID_058F&PID_9254\5&34D1FB39&0&4                        : Generic USB Hub
USB\VID_058F&PID_9360\2004888                               : USB Mass Storage Device
USBSTOR\DISK&VEN_GENERIC&PROD_USB_CF_READER&REV_1.01\2004888&1: Generic USB CF Reader USB Device
USBSTOR\DISK&VEN_GENERIC&PROD_USB_MS_READER&REV_1.03\2004888&3: Generic USB MS Reader USB Device
USBSTOR\DISK&VEN_GENERIC&PROD_USB_SD_READER&REV_1.00\2004888&0: Generic USB SD Reader USB Device
USBSTOR\DISK&VEN_GENERIC&PROD_USB_SM_READER&REV_1.02\2004888&2: Generic USB SM Reader USB Device
8 matching device(s) found.

No problems found.... The created CD boots fine... XP Pro installed with the included drivers without any problems.

Go to forum: DriverPack Mass Storage

4 Reply by rdsok

(23 replies, posted in DriverPack Chipset)

muiz wrote:

And??

As I stated... I'm now in the middle of beta testing for the next release of UBCD4Win which is critical to get released soon. The UBCD4Win testing must come first even though the drivers are also important also.

I did do some preliminary tests with just the latest chipset drivers ( DP_Chipset_wnt5_x86-32_7051.7z )... but as long as the HIDCLASS.SYS that is included in the AU folder gets parsed into the INF file there will be certain systems that have trouble. This isn't the one that is normally used with XP so certain USB devices will fail as I've reported already.

I'll discuss this with Overflow when I get more time to devote to the drivers. At that time, I"ll also see if the video and other drivers that were not previously supported are working now or not. From the changelog that was posted, it doesn't appear that they were added.

Go to forum: DriverPack Chipset

5 Reply by rdsok

(23 replies, posted in DriverPack Chipset)

Debugger wrote:

rdsok
Try to disable LAN, Sound, Internal VGA in BIOS to prevent of BSOD. Try to disable in bios all, what you can smile.

I won't be able to disable VGA... can't read braille... lol


I am also not going to be able to get back to this testing soon, I'm now in the middle of beta testing the next release of UBCD4Win which is critical to get released soon. When I do get back to this... I'll also test with the latest 705 releases.

Note: ... I suspect the MB that you had tested on was a differnet revision... the board I'm using is rev 2.1... I know for a fact that the VGA driver is different from the v1 release... the rev 1 driver would not load on a rev 2x MB. I found this out after replacing an older board with a newer rev after the original was killed from a power surge.

Go to forum: DriverPack Chipset

6 Reply by rdsok

(23 replies, posted in DriverPack Chipset)

jtdoom wrote:

hi
I looked at my backups and found a chipset 702 nightly

I will upload it to OLD, just in case you want this.

I'm not sure that will matter Jaak, as I stated, the hwid's my hardware has are different that what even the current nightly has...

But thanks for the offer,

Randy

Go to forum: DriverPack Chipset

7 Reply by rdsok

(23 replies, posted in DriverPack Chipset)

Debugger wrote:

rdsok
I'm confused again... HIDCLASS.SYS file don't mentioned in any inf file... how you fond out this file? :-[]

I looked in the folder and it was among the drivers listed. Should this file NOT be copied, after all it is included in with the files?

You are incorrect that the file isn't listed in an INF but this is probably because I'm working with an alpha build that Overflow is working on to allow integration of the driverpacks into BartPE builds. A BartPE build requires additional INF's that tell it what files are needed to be copied to the build. A BartPE build also requires that the drivers that are added are already in place because these are running from read only ( CD ) media.

Again, this isn't about that file really, even though it is causing an issue and may need to be addressed. The only thing that the BSOD has done was point out that this boards drivers were not supported. I even believe that the issue can probably be avoided if the proper drivers are added in the first place so the generic ones do not get used. The current DP's do not directly support the hwid's that this board has. I can probably create my own third party DP, but that would do nothing to help the community which is what I thought the point of reporting missing drivers was for.

Go to forum: DriverPack Chipset

8 Reply by rdsok

(23 replies, posted in DriverPack Chipset)

PS... OverFlow said he was unable to find the hwid's that I posted here... so the request for the drivers to support this board should still stand even though I've isolated the file that causes issues... I agree with him that if the proper hwid isn't matched, that the issue is likely caused by a generic driver getting loaded... at least that makes sense to me.

Go to forum: DriverPack Chipset

9 Reply by rdsok

(23 replies, posted in DriverPack Chipset)

The trouble is caused by the HIDCLASS.SYS file.

Go to forum: DriverPack Chipset

10 Reply by rdsok

(23 replies, posted in DriverPack Chipset)

I had planned to test the AU folder futher, it just got too late for me to do it last night.

I believe the reason that those two LOG files are the same is from what I described about the basic PNP detection that a PE build does. It isn't a full hwpnp scan.. it only does select devices at first. While I didn't compare the LOG files because it was getting late, that is why I included each one that I did, I suspected the two you mentioned would be the same.

TIP... the fastest way to isolate the trouble is not to test one at a time but to divide them into groups. For instance, the AU folder currently has 10 INF files total... test the first 5, then the second 5 and depending on which group BSOD's, then split that group up... say test 2 then 3... until you finally work down to the one INF that causes it.

Go to forum: DriverPack Chipset

11 Reply by rdsok

(23 replies, posted in DriverPack Chipset)

Debugger,

Ok.. here are some testing results for this issue.

Overflow was able to provide the older DP_Chipset_wnt5_x86-32_612 and this also produces a BSOD... so all of the following tests were done with the latest nightly I had which was the DP_Chipset_wnt5_x86-32_7056.

The BSOD error code...

A typical IRQ_NOT_LESS_OR_EQUAL error that is common with driver issues.

STOP 0x0000000A ( 0xFFFFFFD4, 0x00000002, 0x00000001, 0x8043026D )


I've also got several SETUPAPI.LOG files so you can choose which or all of them that may be of use in this issue... http://www.rdsok.net/chipset/setupapi.7z

I've isolated the chipset folder that causes the issue to show up but I didn't isolate which file may be the cause in that folder. The folder that causes the BSOD to happen is the AU folder. The 7z file contains 3 different log files.

setupapi_AU_only.log  - This one causes the BSOD but only had the AU folder included in build.

setupapi_no_AU.log  - This contains all folders EXCEPT the AU folder and doesn't BSOD.

setupapi_all.log - This contains all folders ( including AU ) and causes a BSOD.


Since I'm not sure how familiar you are with a PE build like I'm doing using UBCD4Win verses a full XP build... let me point out some differences. A PE boot doesn't perform a complete PnP initialization... it only does the basic devices. What I am doing after the boot process is then to force a complete HWPnP detection... this is when I see the BSOD. Because of these differences, it is easy to see why the DP you tested with worked ok for you... yet still produced a BSOD for me... the OS does act and react slightly different than a normal XP build.

Overflow and I were speculating about the cause of the BSOD when I first mentioned it to him. I believe what he said may have a good reason for a cause... that the dev ID's aren't matched exactly so a generic match is made instead causing it. Of course this speculation has yet to be proven... but my test results do appear to help support it.

Go to forum: DriverPack Chipset

12 Reply by rdsok

(23 replies, posted in DriverPack Chipset)

Debugger,

Since it is what is available... I'll first test with the DP_Chipset_wnt5_x86-32_703.7z to see if it makes a difference. Then I'll test the DP_Chipset_wnt5_x86-32_7056 version and isolate which part of the set appears to be causing the issue, this type of testing I can certainly do easily even if it takes some time. Of course I will also post the info you requested as well.


In order to isolate the trouble, last night I already tested with just the N subfolder-inf set and this alone did not produce the BSOD. Tonight I'll start by removing just one subfolder-inf set at a time and see if I can find which one may be affecting it.

Go to forum: DriverPack Chipset

13 Reply by rdsok

(23 replies, posted in DriverPack Chipset)

Debbugger,

I'm sorry to have to ask this one but...

I'm confused... you said to try DP_Chipset_wnt5_x86-32_612 to see if it resolves the issue. In the Nightlies/old area... the closest one that I see listed is a DP_Chipset_wnt5_x86-32_703.7z version ... Is this the one you mean or is there another you wish me to test with UBCD4Win?

Thanks
Randy

Go to forum: DriverPack Chipset

14 Reply by rdsok

(23 replies, posted in DriverPack Chipset)

Certainly, It will be later this evening after I get home to the system I have with that hardware... 8+ hrs. Thx.

Go to forum: DriverPack Chipset

15 Reply by rdsok

(23 replies, posted in DriverPack Chipset)

If I'm understanding debuggers post... it did add some nVidia 520 chipset items... but not the ones specific for this chipset. I could easily be incorrect since I'm not very good with drivers.

I still rebuilt my UBCD4Win using the DP_Chipset_wnt5_x86-32_7056 and the BSOD I was seeing with the previously tested chipset drivers still exist with this one. This BSOD only happens on this chipset combination on the boards I've tested this on... on a system with the 6100 / 430 chipset combination it works fine without incident.

Go to forum: DriverPack Chipset

16 Topic by rdsok

(23 replies, posted in DriverPack Chipset)

I believe this driver set is different than the nVidia that are currently supported.

Giga-byte GA-M55plus-S3G Motherboard
NVIDIA® Quadro NVS 210S + 430 chipset

http://www.gigabyte.com.tw/Support/Moth … uctID=2385

Since this is an integrated MB with video and ethernet included... I'll post my complete Hwid's that are board related...

===========
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_104C&DEV_8024&SUBSYS_10001458&REV_00\4&DC268A3&0&7080: Texas Instruments OHCI Compliant IEEE 1394 Host Controller
PCI\VEN_10DE&DEV_0245&SUBSYS_D0001458&REV_A2\3&2411E6FE&0&28: NVIDIA Quadro NVS 210S / NVIDIA GeForce 6150LE
PCI\VEN_10DE&DEV_0260&SUBSYS_00000000&REV_A3\3&2411E6FE&0&50: PCI standard ISA bridge
PCI\VEN_10DE&DEV_0264&SUBSYS_02641458&REV_A3\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_B0021458&REV_A1\3&2411E6FE&0&78: NVIDIA nForce 430/410 Serial ATA Controller
PCI\VEN_10DE&DEV_0269&SUBSYS_E0001458&REV_A3\3&2411E6FE&0&A0: NVIDIA Network Bus Enumerator
PCI\VEN_10DE&DEV_026C&SUBSYS_A0021458&REV_A2\3&2411E6FE&0&81: Microsoft UAA Bus Driver for High Definition Audio
PCI\VEN_10DE&DEV_026D&SUBSYS_50041458&REV_A3\3&2411E6FE&0&58: Standard OpenHCD USB Host Controller
PCI\VEN_10DE&DEV_026E&SUBSYS_50041458&REV_A3\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: PCI standard RAM Controller
PCI\VEN_10DE&DEV_0272&SUBSYS_02641458&REV_A3\3&2411E6FE&0&52: PCI standard RAM Controller
PCI\VEN_10DE&DEV_027E&SUBSYS_50001458&REV_A2\3&2411E6FE&0&07: PCI standard RAM Controller
PCI\VEN_10DE&DEV_027F&SUBSYS_50001458&REV_A2\3&2411E6FE&0&06: PCI standard RAM Controller
PCI\VEN_10DE&DEV_02F0&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: PCI standard RAM Controller
PCI\VEN_10DE&DEV_02F9&SUBSYS_50001458&REV_A2\3&2411E6FE&0&04: PCI standard RAM Controller
PCI\VEN_10DE&DEV_02FA&SUBSYS_50001458&REV_A2\3&2411E6FE&0&01: PCI standard RAM Controller
PCI\VEN_10DE&DEV_02FE&SUBSYS_50001458&REV_A2\3&2411E6FE&0&02: PCI standard RAM Controller
PCI\VEN_10DE&DEV_02FF&SUBSYS_50001458&REV_A2\3&2411E6FE&0&05: PCI standard RAM Controller

I'm able to do some basic testing for these if needed. Currently I'm working with Overflow to test the DP's for BartPE integration which was how I identified this issue. The Chipset drivers worked on a similar board with the 6100 - 430 combination without issues.

Go to forum: DriverPack Chipset