DriverPacks.net Forum - OPEN: BUG during installing NFORCE4 CHIPSET

Re: OPEN: BUG during installing NFORCE4 CHIPSET

null@example.com (shaz) — Sun, 02 Jul 2006 22:33:23 +0000

Hey Bashrat could u add the new NFORCE4 drivers v9.16 in the driverspacks (LAN: Chipset; Mass_storage; etc)

http://download.nvidia.com/Windows/nFor … l_whql.exe

Thanx

Re: OPEN: BUG during installing NFORCE4 CHIPSET

null@example.com (Helmi) — Sat, 01 Jul 2006 07:51:02 +0000

shaz wrote:

Please look in the hwids in your driverpack if there is an error.
Hello bashrat i have request not to use "cmdow.exe" anymore, because this files is being blocked by many antivirus software. So this command doesn't work properly in your batchfiles.

You only need to exclude the file in your AV software.
Once you've done that (and don't change paths of where the DriverPacks are located) it should not bother you ever again.

It doesn't for me any longer at least so it was just a minor hassle (and a big bigger confusion because of a possible infection, but we already cleared that ).

Re: OPEN: BUG during installing NFORCE4 CHIPSET

null@example.com (muiz) — Sat, 01 Jul 2006 00:15:03 +0000

BÃ¢shrat the Sneaky wrote:

muiz wrote:
sommetimes a nforce4 chip needs older driver , i already told bashrat ( long time ago )
That 'sometimes' is VERY hard to detect. Do you still remember the mobo for which this was the case?

yep i also sended you the hwids

Re: OPEN: BUG during installing NFORCE4 CHIPSET

null@example.com (shaz) — Fri, 30 Jun 2006 21:04:24 +0000

Please look in the hwids in your driverpack if there is an error.

Hello bashrat i have request not to use "cmdow.exe" anymore, because this files is being blocked by many antivirus software. So this command doesn't work properly in your batchfiles.

Re: OPEN: BUG during installing NFORCE4 CHIPSET

null@example.com (shaz) — Fri, 30 Jun 2006 21:00:38 +0000

===========
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_8023&SUBSYS_808B1043&REV_00\4&13699180&0&5848: Texas Instruments OHCI Compliant IEEE 1394 Host Controller
PCI\VEN_10DE&DEV_0050&SUBSYS_00000000&REV_A3\3&2411E6FE&0&08: PCI standard ISA bridge
PCI\VEN_10DE&DEV_0052&SUBSYS_815A1043&REV_A2\3&2411E6FE&0&09: NVIDIA nForce PCI System Management
PCI\VEN_10DE&DEV_0053&SUBSYS_815A1043&REV_F2\3&2411E6FE&0&30: NVIDIA nForce4 Parallel ATA Controller
PCI\VEN_10DE&DEV_0054&SUBSYS_815A1043&REV_F3\3&2411E6FE&0&38: NVIDIA nForce4 Serial ATA Controller
PCI\VEN_10DE&DEV_0055&SUBSYS_815A1043&REV_F3\3&2411E6FE&0&40: NVIDIA nForce4 Serial ATA Controller
PCI\VEN_10DE&DEV_0057&SUBSYS_81411043&REV_A3\3&2411E6FE&0&50: NVIDIA Network Bus Enumerator
PCI\VEN_10DE&DEV_0059&SUBSYS_812A1043&REV_A2\3&2411E6FE&0&20: Realtek AC'97 Audio
PCI\VEN_10DE&DEV_005A&SUBSYS_815A1043&REV_A2\3&2411E6FE&0&10: Standard OpenHCD USB Host-controller
PCI\VEN_10DE&DEV_005B&SUBSYS_815A1043&REV_A3\3&2411E6FE&0&11: Standard Enhanced PCI naar USB-hostcontroller
PCI\VEN_10DE&DEV_005C&SUBSYS_00000000&REV_A2\3&2411E6FE&0&48: PCI standard PCI-to-PCI bridge
PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&2411E6FE&0&58: nForce4 PCI-Express Root Port
PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&2411E6FE&0&60: nForce4 PCI-Express Root Port
PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&2411E6FE&0&68: nForce4 PCI-Express Root Port
PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&2411E6FE&0&70: nForce4 PCI-Express Root Port
PCI\VEN_10DE&DEV_005E&SUBSYS_815A1043&REV_A3\3&2411E6FE&0&00: nForce4 HyperTransport Bridge
PCI\VEN_10DE&DEV_0140&SUBSYS_81CF1043&REV_A2\4&243D7BD0&0&0070: NVIDIA GeForce 6600 GT
21 matching device(s) found.

===========
USB devices
===========

USB\ROOT_HUB\4&35297846&0 : USB-hoofdhub
USB\ROOT_HUB20\4&1E67B15B&0 : USB-hoofdhub
USB\VID_046D&PID_08AD\5&36C701F9&0&4 : Logitech QuickCam Communicate STX
USB\VID_046D&PID_08AD&MI_00\6&99C786&1&0000 : Logitech QuickCam Communicate STX
USB\VID_046D&PID_08AD&MI_01\6&99C786&1&0001 : Logitech Mic (Communicate STX)
USB\VID_046D&PID_C505\5&36C701F9&0&2 : Samengesteld USB-apparaat
USB\VID_046D&PID_C505&MI_00\6&268F6001&0&0000 : USB-HID
USB\VID_046D&PID_C505&MI_01\6&268F6001&0&0001 : USB-HID
8 matching device(s) found.

Re: OPEN: BUG during installing NFORCE4 CHIPSET

null@example.com (Wim Leers) — Thu, 29 Jun 2006 07:23:44 +0000

muiz wrote:

sommetimes a nforce4 chip needs older driver , i already told bashrat ( long time ago )

That 'sometimes' is VERY hard to detect. Do you still remember the mobo for which this was the case?

Re: OPEN: BUG during installing NFORCE4 CHIPSET

null@example.com (muiz_old) — Thu, 29 Jun 2006 00:57:34 +0000

sommetimes a nforce4 chip needs older driver , i already told bashrat ( long time ago )

Re: OPEN: BUG during installing NFORCE4 CHIPSET

null@example.com (Wim Leers) — Wed, 28 Jun 2006 09:03:25 +0000

The AMD K8 CPU driver was NOT installed?

Could you please post your HWIDs? Check my sig for a tool to get them.

OPEN: BUG during installing NFORCE4 CHIPSET

null@example.com (shaz) — Tue, 27 Jun 2006 21:58:13 +0000

When Windows XP loads at the first time, the system continuously restarts at the Windows Logo. This is caused by the driverpack. Safe mode is working, but there is no hardware profile loaded in the safe mode.
You can see also that there are a few batch files from the driverpack still available at the %systemdrive% that hasn't been executed during installing. Something has gone wrong there...

You have to install for example amd64 v1.3.1 driver in safe mode to get everything right. After the next restarts everythings works perfectly. I think this problem caused by an mistake in the batch files relating to Nforce4 chipset and an AMD64 CPU.

When you install Windows without the driverpack everything is working perfectly and there is no continuously restart at the Windows Logo.

Please fix the problem.

Thank you...