DriverPacks.net Forum - Parity Error on First Boot

Re: Parity Error on First Boot

2007-06-20T12:45:36Z

My current solution is to create a slipstream without the graphics driverpack included. It's the only way it will work, even on other machines...

...Dell

Re: Parity Error on First Boot

2007-06-20T12:37:52Z

Yeah. I tried it again with the newer DriverPacks Graphics 'A' and during my RunOnceEx routine a 'found new hardware' box pops up for the geforce go 7300 (rebranded as a Quadro 110). Really frustrating!

edit: Actually I noticed that if I reboot during the installation when it restarts it doesn't re-extract the driver packs. My sound isn't working either... Maybe it's why it worked this time, though

Re: Parity Error on First Boot

2007-06-20T04:51:19Z

Yes, I can verify that the release DP Graphics_A does not support an older HP notebook with Geforce Go 420 video.

PCI\VEN_10DE&DEV_0176&SUBSYS_006D103C&REV_A3\4&2655A04&0&0058: NVIDIA GeForce4 420 Go 32M

Last night, the installer hangs at T-34 "Installing Devices" with the card listed in the pnplog.txt file as the source of the hang.

Re: Parity Error on First Boot

2007-06-19T21:45:49Z

hi helmi
I just looked, and the lines ruudboek added to NV4_go.inf back then are not in the current release.

%NVIDIA_G72.DEV_01DA.1% = nv4_WSApps_mobile, PCI\VEN_10DE&DEV_01D7&SUBSYS_01C21028
%NVIDIA_G72.DEV_01DA.1% = nv4_WSApps_mobile, PCI\VEN_10DE&DEV_01D7&SUBSYS_01CC1028
%NVIDIA_G72.DEV_01DB.1% = nv4_WSApps_mobile, PCI\VEN_10DE&DEV_01D8&SUBSYS_01CC1028

Re: Parity Error on First Boot

2007-06-19T21:06:34Z

Maybe these special Dell drivers could somehow be included in DriverPack Graphics A (if it's only the INF it shouldn't take up too much space)...
I'm still perplexed it will cause such a serious error instead of simply not installing the GFX driver and be done with that (what you'll ususally get if a special INF is required).
But that's Dell for you, I guess...

Re: Parity Error on First Boot

2007-06-19T15:55:55Z

I just installed it on the same machine without Graphics Driver Pack A and it worked beautifully (if you don't count the graphics )

I am going to try it again with the most recent release to see if the same problem happens. If it does I will post back here.

Re: Parity Error on First Boot

2007-06-19T12:20:28Z

I remember a similar error with the Quadro, even posted here on these boards: http://forum.driverpacks.net/viewtopic.php?id=1195

It's because it's a Dell and the drivers are 'special' somehow. Something about a relabeled .inf. Anyways - I'm going to make an install DVD without the Graphics A package and see if it works.

The problem with this is I work in a tech department that deals exclusively with Dell so it's not going to go away if I ignore it on one machine. Maybe I'll keep a flash drive with the current forceware drivers on it for install after the Unattended OS finishes

Re: Parity Error on First Boot

2007-06-18T19:37:27Z

If any quirks happen during a Win installation (or that of any OS basically), I can only recommend to reinstal that OS right away.
This is in no way restricted to an nlited or BASE'd installation CD but also to the original installation medium.
Windows installs are very sensitive towards RAM timings, voltage and OC'ing (the latter two also applying to the CPU) so you should revert back to BIOS defaults (maybe not even using the "performance" or "optimized" settings) for the installation - all changes can be undone once it has been successfully installed.

As you tested the DVD (and not the ISO) in VPC already, I think we can outrule a bad burn.

Also make sure to disable any "virus protection" in the BIOS, that will ususally prevent anything from writing (properly) to the MBR which could result in such strange behaviour.

Parity Error on First Boot

2007-06-18T19:17:05Z

I'm getting a parity check\error BSOD on first boot using an unattended DVD.

I used nlite and then driverpacks. (the version I am using is about one week old)

The computer is a Dell D820 with a Quadro graphics chipset. I say that because during the 'installing devices' section the screen went crazy and the driver obviously installed incorrectly. On reboot, the BSOD happened after the windows loading screen.

This DVD worked in Virtual PC 2007