as for that quadro, it sat here waiting on my hard drive.
(mind you, I think that the quadro is something Muiz can handle with a lot more expertise.)

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.

Please keep in mind that rdsok is testing BARTPE support, not a normall install.

This changes everything.

I believe that HIDCLASS.SYS is copied by the coinstaller so it wont be in an inf file.
Pebuilder support is still at alpha stage for this pack and is expected to be buggy at best.

For those that don't know, for a standard bartpe to work, all added drivers are expanded to their respective folders at build time, not boot time, this is why pebuilder support is taking so long to complete. Nore info will follow as time allows.

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

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.

mass needs added minimum and lan will remain as a problem till i get a little farther on the support of that

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

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

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.

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.