Topic: [SLV] Win2K BSOD 0X7B PCI\VEN_1002&DEV_4390&SUBSYS_B0021458

Blue screen on Windows 2000 at boot
Stop: 0X0000007B (0XF601F84C, 0XC0000034, 0X00000000, 0X00000000)
INACCESSABLE_BOOT_DEVICE

Some background (how I got to this error)

I was running a triple boot machine, Win2k, WinXP, and Fedora 11.  It was an ASUS K8V-SE Deluxe motherboard (VIA chipset), AMD-64 processor and Nvidia 5300 Video card.  It had 4 drives, 2 PATA drives with the systems on the first drive (/dev/sda), data on 2nd (/dev/sda2).  There were also two SATA drives on a Promise controller (onboard) containing data.  All of the systems could R/W the SATA partitions.  I decided to build a new replacement system using a Gigabyte GA-MA770T-UD3P motherboard (AMD chipset), AMD Phenom X2 cpu, and ATI Radeon HD 4650 Video card.

The new machine only supports SATA drives, so I used two new SATA drives.  First I booted the old machine with a Fedora Live CD and created mount points for all of the partitions.  I then copied each of the partitions from the PATA drives to a backup drive using "rsync -Pavx --delete /src/ /backup/dest".  Next I booted up the new machine using the Fedora Live CD.  I created partitions on the new SATA drive (/dev/sda) that matched the partition layout of the old PATA drive.  The Windows partitions were left as FAT32 format of 30GB each.  The Fedora partitions were EXT3.  I formatted and labeled all of the partitions using Fedora.  Again I mounted the backup drive and used "rsync -Pavx --delete /backup/src/ /dest" to copy the old contents to the new disks.  Partition 2 had Win2k and was the boot partition and partition 5 had WinXP.  I rebooted the machine using a win98 startup disk (yes windows 98 SE actually) and typed "fdisk /mbr" at the prompt to write the windows bootstrap to the disk.  I understand you can boot to the console on a windows install CD and use the "fixboot" command, but I have never tried it.  I rebooted and got the windows prompt and selected WinXP and using F8, started it in safe mode.  WinXP booted and I installed the drivers from Gigabyte for the motherboard, sound, ethernet, etc.  After a bunch of reboots and of course reregistering with M$, I had a working WinXP system.  I fixed Fedora next by using an install DVD.  I booted it up and selected "recover" mode.  Mounted the root and boot partitions and ran "grub-install hd0" to install grub.  I rebooted and had my old grub menu back.  Fedora liked the new system and ran fine.  I do not remember any issues.  I can see all of the partitions from Fedora.  Last I tried to boot windows 2k and get the stop code above.  It seems to know nothing about the new SATA drives

I could not use drivers on a floppy because Gigabyte did not supply drivers for Win2k, only WinXP and Vista.  I downloaded and built UBCD4WIN 3.5 and tried the plugin to write the SATA drivers to the Win2k system, but it did not work.  I downloaded and built a Win2k system with SP4 and all the latest updates using HFSLIP (http://www.vorck.com/windows/2ksp5.html).  When booting the install CD, the drive information is incorrect and the installer can not find a valid Win2k partition.  So I figured I needed more drivers, so I came to DriverPacks.  I used the Win2KSP4+ CD and created a new CD with the DrivePacks added.  With the MassStorage V9.01 I get a message "file ahci7xx.sys is currupted" and dies.  I tried to remove some of the drivers following directions from another thread on this forum, but I got the same problem.  The last thing tried was using MassStorage V9.06r1 and with it I get the message "file ahcix86.sys is corrupt" and dies.  I even tried installing VirtualBox and creating a new Win2k guest, but it dies with the same corrupt file error.

So, I am running out of ideas.  How can I get the required drivers for Win2k installed so I can boot from the SATA drive into Win2k?  I think this board needs the AM1 driver.  Below is the Hardware info and log files.  I hope someone can help.

Jim

HWIDs

=========== 
PCI Devices 
=========== 
PCI\VEN_1002&DEV_4383&SUBSYS_A0221458&REV_00\3&61AAA01&0&A2 : Microsoft UAA Bus Driver for High Definition Audio
PCI\VEN_1002&DEV_4384&SUBSYS_00000000&REV_00\3&61AAA01&0&A4 : PCI standard PCI-to-PCI bridge
PCI\VEN_1002&DEV_4385&SUBSYS_43851458&REV_3C\3&61AAA01&0&A0 : ATI SMBus
PCI\VEN_1002&DEV_4390&SUBSYS_B0021458&REV_00\3&61AAA01&0&88 : Standard Dual Channel PCI IDE Controller
PCI\VEN_1002&DEV_4396&SUBSYS_50041458&REV_00\3&61AAA01&0&92 : Standard Enhanced PCI to USB Host Controller
PCI\VEN_1002&DEV_4396&SUBSYS_50041458&REV_00\3&61AAA01&0&9A : Standard Enhanced PCI to USB Host Controller
PCI\VEN_1002&DEV_4397&SUBSYS_50041458&REV_00\3&61AAA01&0&90 : Standard OpenHCD USB Host Controller
PCI\VEN_1002&DEV_4397&SUBSYS_50041458&REV_00\3&61AAA01&0&98 : Standard OpenHCD USB Host Controller
PCI\VEN_1002&DEV_4398&SUBSYS_50041458&REV_00\3&61AAA01&0&91 : Standard OpenHCD USB Host Controller
PCI\VEN_1002&DEV_4398&SUBSYS_50041458&REV_00\3&61AAA01&0&99 : Standard OpenHCD USB Host Controller
PCI\VEN_1002&DEV_4399&SUBSYS_50041458&REV_00\3&61AAA01&0&A5 : Standard OpenHCD USB Host Controller
PCI\VEN_1002&DEV_439C&SUBSYS_50021458&REV_00\3&61AAA01&0&A1 : Standard Dual Channel PCI IDE Controller
PCI\VEN_1002&DEV_439D&SUBSYS_00000000&REV_00\3&61AAA01&0&A3 : PCI standard ISA bridge
PCI\VEN_1002&DEV_5957&SUBSYS_00000000&REV_00\3&61AAA01&0&00 : PCI standard host CPU bridge
PCI\VEN_1002&DEV_5978&SUBSYS_00000000&REV_00\3&61AAA01&0&10 : PCI standard PCI-to-PCI bridge
PCI\VEN_1002&DEV_597F&SUBSYS_00000000&REV_00\3&61AAA01&0&50 : PCI standard PCI-to-PCI bridge
PCI\VEN_1002&DEV_9498&SUBSYS_20021787&REV_00\4&D8B142A&0&0010: ATI Radeon HD 4650
PCI\VEN_1002&DEV_AA38&SUBSYS_AA381787&REV_00\4&D8B142A&0&0110: Microsoft UAA Bus Driver for High Definition Audio
PCI\VEN_1022&DEV_1200&SUBSYS_00000000&REV_00\3&61AAA01&0&C0 : PCI standard host CPU bridge
PCI\VEN_1022&DEV_1201&SUBSYS_00000000&REV_00\3&61AAA01&0&C1 : PCI standard host CPU bridge
PCI\VEN_1022&DEV_1202&SUBSYS_00000000&REV_00\3&61AAA01&0&C2 : PCI standard host CPU bridge
PCI\VEN_1022&DEV_1203&SUBSYS_00000000&REV_00\3&61AAA01&0&C3 : PCI standard host CPU bridge
PCI\VEN_1022&DEV_1204&SUBSYS_00000000&REV_00\3&61AAA01&0&C4 : PCI standard host CPU bridge
PCI\VEN_104C&DEV_8024&SUBSYS_10001458&REV_00\4&CC5B14E&0&70A4: Texas Instruments OHCI Compliant IEEE 1394 Host Controller
PCI\VEN_10EC&DEV_8168&SUBSYS_E0001458&REV_02\4&29D96644&0&0050: Realtek RTL8168/8111 PCI-E Gigabit Ethernet NIC
PCI\VEN_14F1&DEV_8800&SUBSYS_6613107D&REV_05\4&CC5B14E&0&30A4: WinFast TV2000 XP Expert WDM Video Capture.(NTSC)
26 matching device(s) found.
 
=========== 
USB Devices 
=========== 
USB\ROOT_HUB\4&2163B286&0                                   : USB Root Hub
USB\ROOT_HUB\4&362114AD&0                                   : USB Root Hub
USB\ROOT_HUB\4&3735426B&0                                   : USB Root Hub
USB\ROOT_HUB\4&78963DC&0                                    : USB Root Hub
USB\ROOT_HUB\4&89D919A&0                                    : USB Root Hub
USB\ROOT_HUB20\4&25568EAF&0                                 : USB Root Hub
USB\ROOT_HUB20\4&29D1E53&0                                  : USB Root Hub
7 matching device(s) found.
 
============= 
Input Devices 
============= 
No matching devices found.
 
============ 
ACPI Devices 
============ 
ACPI\AUTHENTICAMD_-_X86_FAMILY_16_MODEL_4\_0                : AMD Phenom(tm) II X4 B50 Processor
ACPI\AUTHENTICAMD_-_X86_FAMILY_16_MODEL_4\_1                : AMD Phenom(tm) II X4 B50 Processor
ACPI\AUTHENTICAMD_-_X86_FAMILY_16_MODEL_4\_2                : AMD Phenom(tm) II X4 B50 Processor
ACPI\AUTHENTICAMD_-_X86_FAMILY_16_MODEL_4\_3                : AMD Phenom(tm) II X4 B50 Processor
ACPI\FIXEDBUTTON\2&DABA3FF&0                                : ACPI Fixed Feature Button
ACPI\PNP0000\4&345537B0&0                                   : Programmable interrupt controller
ACPI\PNP0100\4&345537B0&0                                   : System timer
ACPI\PNP0103\4&345537B0&0                                   : High precision event timer
ACPI\PNP0200\4&345537B0&0                                   : Direct memory access controller
ACPI\PNP0303\3&61AAA01&0                                    : Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
ACPI\PNP0400\3&61AAA01&0                                    : Printer Port (LPT1)
ACPI\PNP0501\1                                              : Communications Port (COM1)
ACPI\PNP0800\4&345537B0&0                                   : System speaker
ACPI\PNP0A03\2&DABA3FF&0                                    : PCI bus
ACPI\PNP0A06\3&5A8C0991&0                                   : Extended IO Bus
ACPI\PNP0B00\4&345537B0&0                                   : System CMOS/real time clock
ACPI\PNP0C01\2&DABA3FF&0                                    : System board
ACPI\PNP0C02\1                                              : Motherboard resources
ACPI\PNP0C02\3                                              : Motherboard resources
ACPI\PNP0C02\4                                              : Motherboard resources
ACPI\PNP0C04\4&345537B0&0                                   : Numeric data processor
ACPI\PNP0C0C\2&DABA3FF&0                                    : ACPI Power Button
ACPI\PNP0C14\0                                              : Microsoft Windows Management Interface for ACPI
ACPI\PNP0F13\3&61AAA01&0                                    : PS/2 Compatible Mouse
ACPI\PNPA000\4&410D8FBB&0                                   : VAXSCSI Controller
ACPI_HAL\PNP0C08\0                                          : Microsoft ACPI-Compliant System
ROOT\ACPI_HAL\0000                                          : ACPI Multiprocessor PC
27 matching device(s) found.
 
============ 
 HDA Audio 
============ 
HDAUDIO\FUNC_01&VEN_1002&DEV_AA01&SUBSYS_00AA0100&REV_1001\5&63D7F82&3&0001: ATI Function Driver for High Definition Audio - ATI AA01
HDAUDIO\FUNC_01&VEN_10EC&DEV_0888&SUBSYS_1458E601&REV_1000\4&126B8476&3&0001: Realtek High Definition Audio
2 matching device(s) found.
 
============ 
RAID Devices 
============ 
PCI\VEN_1002&DEV_4390&SUBSYS_B0021458&REV_00\3&61AAA01&0&88
    Name: Standard Dual Channel PCI IDE Controller
    Hardware ID's:
        PCI\VEN_1002&DEV_4390&SUBSYS_B0021458&REV_00
        PCI\VEN_1002&DEV_4390&SUBSYS_B0021458
        PCI\VEN_1002&DEV_4390&CC_01018F
        PCI\VEN_1002&DEV_4390&CC_0101
    Compatible ID's:
        PCI\VEN_1002&DEV_4390&REV_00
        PCI\VEN_1002&DEV_4390
        PCI\VEN_1002&CC_01018F
        PCI\VEN_1002&CC_0101
        PCI\VEN_1002
        PCI\CC_01018F
        PCI\CC_0101
PCI\VEN_1002&DEV_439C&SUBSYS_50021458&REV_00\3&61AAA01&0&A1
    Name: Standard Dual Channel PCI IDE Controller
    Hardware ID's:
        PCI\VEN_1002&DEV_439C&SUBSYS_50021458&REV_00
        PCI\VEN_1002&DEV_439C&SUBSYS_50021458
        PCI\VEN_1002&DEV_439C&CC_01018A
        PCI\VEN_1002&DEV_439C&CC_0101
    Compatible ID's:
        PCI\VEN_1002&DEV_439C&REV_00
        PCI\VEN_1002&DEV_439C
        PCI\VEN_1002&CC_01018A
        PCI\VEN_1002&CC_0101
        PCI\VEN_1002
        PCI\CC_01018A
        PCI\CC_0101
2 matching device(s) found.

Log files-----------

2009-07-12 14:08:29 : <INIT> DriverPacks BASE 8.12.5 initialized.
2009-07-12 14:08:29 : <INIT> Host environment: WIN_2000 Service Pack 4 on X86 CPU.
2009-07-12 14:08:29 : <INIT> Created temporary working directory.
2009-07-12 14:08:29 : <INIT> Imported proxy settings from Internet Explorer.
2009-07-12 14:08:29 : <INIT> Start scanning for DriverPacks for the wnt5_x86-32 platform.
2009-07-12 14:08:29 : <INIT> 	Detected DriverPack Chipset 902!
2009-07-12 14:08:29 : <INIT> 	Detected DriverPack CPU 804!
2009-07-12 14:08:29 : <INIT> 	Detected DriverPack Graphics A 906!
2009-07-12 14:08:29 : <INIT> 	Detected DriverPack LAN 8121!
2009-07-12 14:08:29 : <INIT> 	Detected DriverPack MassStorage 901!
2009-07-12 14:08:29 : <INIT> 	Detected DriverPack MassStorage 90111!
2009-07-12 14:08:29 : <INIT> 	Detected DriverPack MassStorage 906r1!
2009-07-12 14:08:29 : <INIT> 	Could not detect any 3rd party DriverPacks for wnt5_x86-32.
2009-07-12 14:08:29 : <INIT> 	Finished scanning.
2009-07-12 14:08:29 : <INIT> Detected settings file "D:\DrivePacks\DPs_BASE.ini".
2009-07-12 14:08:30 : <INIT> Windows 2000 Professional -  SP4 detected.
2009-07-12 14:08:30 : <INIT> [Settings]\DPsMethod not specified: default (2) was set.
2009-07-12 14:08:30 : <INIT> [Settings]\finisherMethod not specified: default (GUIRunOnce) was set.
2009-07-12 14:08:30 : <INIT> [OptionalSettings]\KTD not specified: default (none) was set.
2009-07-12 14:08:30 : <INIT> [OptionalSettings]\QSC not specified: default (yes) was set.
2009-07-12 14:08:30 : <INIT> [OptionalSettingsOther]\ATI_cpl not specified: default (None) was set.
2009-07-12 14:08:30 : <INIT> [OptionalSettingsOther]\Nvidia_cpl not specified: default (None) was set.
2009-07-12 14:08:30 : <INIT> wnt5_x86-32_disc is the selected installation platform .
2009-07-12 14:08:30 : <INIT> Imported settings from settings file.
2009-07-12 14:08:30 : <GUI>  Initialized GUI.
2009-07-12 14:08:30 : <GUI>  Created a list of all available language files.
2009-07-12 14:08:30 : <GUI>  Set the last used language, English, as the GUI language.
2009-07-12 14:08:35 : <GUI>  Windows 2000 Professional -  SP4 detected.
2009-07-12 14:08:35 : <GUI>  wnt5_x86-32_disc is the selected installation platform .
2009-07-12 14:08:58 : <GUI>  Refreshed UpdateChecker with success.
2009-07-12 14:09:12 : <GUI>  Saved settings!
2009-07-12 14:09:12 : <GUI>  Closed GUI.
2009-07-12 14:09:12 : <SEL>  Selected module: mod_slip_w2k_x86-32_disc_m2.
2009-07-12 14:09:13 : <PREP> Removed all attributes from \I386.
2009-07-12 14:09:14 : <PREP> Deleted old DriverPacks.
2009-07-12 14:09:14 : <PREP> Deleting old method 2 related files.
2009-07-12 14:09:14 : <PREP> Deleted \OEM\bin\DevPath.exe.
2009-07-12 14:09:14 : <PREP> Deleted \OEM\*.ins.
2009-07-12 14:09:14 : <PREP> Deleted \OEM\bin\7-zip32.dll.
2009-07-12 14:09:14 : <PREP> Deleted \OEM\bin\DPsFnshr.7z.
2009-07-12 14:09:14 : <PREP> Deleted \OEM\bin\DPsFnshr.ini.
2009-07-12 14:09:14 : <PREP> Deleted \OEM\bin\un7zip.exe.
2009-07-12 14:09:14 : <PREP> Deleted \OEM\DP_Install_Tool.cmd.
2009-07-12 14:09:14 : <PREP> Deleted \OEM\DPINST.exe.
2009-07-12 14:09:14 : <PREP> Deleted \OEM\DPInst.xml.
2009-07-12 14:09:14 : <PREP> Deleted \OEM\bin
2009-07-12 14:09:14 : <PREP> Deleted \OEM
2009-07-12 14:09:14 : <PREP> Restored \I386\winnt.sif.
2009-07-12 14:09:14 : <PREP> Restored \I386\txtsetup.sif.
2009-07-12 14:09:14 : <PREP> Restored \I386\dosnet.inf.
2009-07-12 14:09:14 : <PREP> D:\HFSLIP\SOURCE\I386\DriverPack_MassStorage_wnt5_x86-32.ini
2009-07-12 14:09:14 : <PREP> Restored \I386\adpu160m.SY_.
2009-07-12 14:09:15 : <PREP> Restored \I386\cpqarry2.SY_.
2009-07-12 14:09:15 : <PREP> Restored \I386\mraid35x.SY_.
2009-07-12 14:09:15 : <PREP> Restored \I386\dac960nt.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\3wareDrv.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\3waregsm.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\3wDrv100.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\aec6210.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\aec6260.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\aec6280.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\aec68x5.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\aec6880.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\aec6897.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\aec67160.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\aec671x.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\aar81xx.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\aar1210.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\DPTI2O.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\adpu320.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\a320raid.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\cda1000.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\ADP3132.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\aacsas.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\aac.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\amdide.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\amdide1.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\ahci7xx.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\ahci6xx.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\arcm_x86.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\atiide2k.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\m5228.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\m5281.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\m5287.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\m5288.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\m5289.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\cercsr6.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\msasdell.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\hpt3xx.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\rr174xp.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\hpt374.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\hptmvK.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\hptmv6.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\rr232x.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\2310_00.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\rr172x.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\hptiop.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\iastor55.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\iastor70.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\iastor78.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\iastor86.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\raidsrc.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\ipsraidn.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\nfrdx960.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\adp94xx.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\inic162x.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\iteraid.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\jraid.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\MegaIDE.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\MegaINTL.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\dac2w2k.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\megasas.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\megasr2k.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\symmpi2k.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\Mraid2k.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\mv61xx.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\mv614x.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\mvsata.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\mv64xx.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\nvgts5.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\nvrd325.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\nvgts6.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\nvatabus.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\nvraid.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\fst376kk.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\ide376kk.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\fasttk2k.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\fast2k2k.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\s150sx8.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\fastsxkk.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\sptrak.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\ulsata.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\ulsata2.SY_.
2009-07-12 14:09:15 : <PREP> Deleted \I386\ultra.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\fttxr52P.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\prfsx42k.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\FTTXR5_O.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\ql2100.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\ql2200.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\ql12160.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\si3114r5.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\3124r5A.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\3124R5A2.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\3132R5C.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\3132R5C2.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\3132R5C3.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\3132R5C4.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\3132R5C5.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\pnp649r.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\pnp680r.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\3112Rx47.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\si3114r.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\si3124r.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\ASH1205.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\pnp680.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\si3531.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\SI3112.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\si3114.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\si3124.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\SI3132B.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\SI3132B2.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\SI3132B3.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\SI3132B4.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\SI3132B5.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\SISRAID.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\SISRAID1.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\SISRAID2.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\SISRAIDX.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\SISRAID4.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\siside.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\viamraid.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\VIAPDSK.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\viaide.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\VMSCSI.SY_.
2009-07-12 14:09:16 : <PREP> Deleted \I386\DriverPack_MassStorage_wnt5_x86-32.ini.
2009-07-12 14:09:16 : <PREP> Deleted old DriverPack MassStorage text mode drivers.
2009-07-12 14:09:16 : <PREP> Deleted \I386\presetup.cmd.
2009-07-12 14:09:16 : <PREP> Restored original setup: method 2 was used previously.
2009-07-12 14:09:16 : <PREP> Verified method 2 references don't exist in txtsetup.sif or dosnet.inf.
2009-07-12 14:09:21 : <SLIP> Extracted DriverPack MassStorage to a temporary working directory.
2009-07-12 14:09:21 : <SLIP> D:\DrivePacks\tmp\DPMtmp\DriverPack_MassStorage_wnt5_x86-32.ini
2009-07-12 14:09:22 : <SLIP> Processing the files now. This may take a minute.
2009-07-12 14:09:41 : <SLIP> Created QuickStream Cache for DriverPack MassStorage text mode drivers.
2009-07-12 14:09:42 : <SLIP> Slipstreamed DP MassStorage text mode drivers using QuickStream Cache.
2009-07-12 14:09:42 : <SLIP> txtsetup.sif Backed-up Successfully
2009-07-12 14:09:42 : <SLIP> dosnet.inf Backed-up Successfully
2009-07-12 14:09:43 : <SLIP> Removed entries from \I386\txtsetup.sif that will be updated.
2009-07-12 14:09:43 : <SLIP> Removed entries from \I386\dosnet.inf that will be updated.
2009-07-12 14:10:06 : <SLIP> Updated \I386\dosnet.inf and \I386\txtsetup.sif to support DP MassStorage text mode drivers.
2009-07-12 14:10:06 : <SLIP> Created necessary directory structure for method 2.
2009-07-12 14:10:09 : <SLIP> Copying files necessary for method 2.
2009-07-12 14:10:09 : <SLIP> Extracted additional files necessary for method 2.
2009-07-12 14:10:09 : <SLIP> expanded setup.ex_ to setuporg.exe
2009-07-12 14:10:09 : <SLIP> SETUP.EX_ Backed-up Successfully
2009-07-12 14:10:09 : <SLIP> Compressed setup.exe to SETUP.EX_.
2009-07-12 14:10:09 : <SLIP> Method 2 setup.ex_ installed
2009-07-12 14:10:09 : <SLIP> Created \I386\presetup.cmd file.
2009-07-12 14:10:09 : <SLIP> Updated \I386\txtsetup.sif to support method 2.
2009-07-12 14:10:09 : <SLIP> Updated \I386\dosnet.inf to support method 2.
2009-07-12 14:10:09 : <SLIP> Copied DriverPack Chipset to \OEM.
2009-07-12 14:10:09 : <SLIP> Copied DriverPack CPU to \OEM.
2009-07-12 14:10:12 : <SLIP> Copied DriverPack Graphics A to \OEM.
2009-07-12 14:10:13 : <SLIP> Copied DriverPack LAN to \OEM.
2009-07-12 14:10:13 : <SLIP> Copied DriverPack MassStorage to \OEM.
2009-07-12 14:10:13 : <SLIP> Copied DriverPacks to \OEM.
2009-07-12 14:10:13 : <SLIP> Will not slipstream KB888111 because no Sound DriverPack is being slipstreamed
2009-07-12 14:10:13 : <SLIP> WINNT.SIF Backed-up Successfully
2009-07-12 14:10:13 : <SLIP> Updated \I386\winnt.sif to support method 2.
2009-07-12 14:10:13 : <SLIP> Updated DPsFnshr.ini to disable KTD.
2009-07-12 14:10:13 : <SLIP> Updated \I386\winnt.sif's GUIRunOnce section.
2009-07-12 14:10:13 : <SLIP> DP_Install_Tool was copied successfully
2009-07-12 14:10:13 : <SLIP> Slipstream finished in 41 seconds.
2009-07-12 14:11:21 : <CLNP> Temporary working directory successfully deleted.
- = DriverPacks BASE ini settings used = -
[General]
; preferred language
prefLang	= "English"
; yes/no, enable or disable the wizard-style buttons, if not specified: yes
wizardButtons	= "yes"
; yes/no, enable or disable the GUI, if not specified: yes
GUI		= "yes"


[Settings]
; disc/bartpe/multibootDisc
instPlatform	= "disc"
; trailing backslash is allowed, but not necessary
location	= "D:\HFSLIP\SOURCE"
; none/all/select, if select, specify them below, if not specified: all
DriverPacks	= "select"
; 1/2, method to install the DriverPacks, if not specified: 2
DPsMethod	= "2"
; GUIRunOnce/RunOnceEx/custom, if not specified: GUIRunOnce
finisherMethod	= "GUIRunOnce"


; this section is optional!
[OptionalSettings]
; none/all/select/paths/patterns, enable or disable Keep The Drivers (KTD) , if not specified: none
KTD		= "false"
; <path>, to specify a custom KTD cache location, if not specified: default (%SystemRoot%\DriverPacks)
KTDlocation	= "%SystemRoot%\DriverPacks"
; yes/no, enable or disable QuickStream Cache (QSC), if not specified: yes
QSC		= "yes"


; you should only add this section if you've set [Settings]\DriverPacks to "select"
[SelectDriverPacks]
DP_Chipset	= "yes"
DP_CPU		= "yes"
DP_Graphics_A	= "yes"
DP_LAN		= "yes"
DP_MassStorage	= "yes"
DP_MassStorage_textmode = "yes"
2009-07-12 14:11:21 : <CLNP> Create a DPs_Base.log backup @ D:\DrivePacks\LogFiles\DPs_BASE_09-07-12_14-11.log
2009-07-12 14:11:21 : <CLNP> Program terminated.

Re: [SLV] Win2K BSOD 0X7B PCI\VEN_1002&DEV_4390&SUBSYS_B0021458

Most BIOS have an IDE compatability setting for their SATA controllers.  Have you tried that?

Driverpacks officially supports XP only.  AFAIK no XP driver will function on Win2k.  There are the beginnings of support for both Vista and Win7 but none for Win2k.

In the runup to Win7 this fall I'm expecting that both XP and Vista will be rapidly abandoned except for hard core enthusiasts.  The immediate effect of this will be the loss of driver support as you are seeing.  Win2k being 3 years older than XP is already in that position.

If you really want to run XP and Win2k on modern hardware, I would encourage you to explore the possibilities of hosting both of those OSs on Fedora under a virtualization product like VirtualBox.  In your case, the immediate benefit of VB is to present a standardized and simplified set of virtual devices and drivers to the hosted operating systems.  Another upside is more precide control of disk space and a vastly simplified boot arrangement.

If you can't stomach Fedora as your primary OS, you can virtualize Win2k and Fedora under XP (and Vista and Win7).  Or under OS/X if you lean that way.

But sorry to say I believe that the days of being able to boot reasonably modern hardware into Win2k are coming to an end.

Last edited by newsposter (2009-07-28 17:05:29)

Re: [SLV] Win2K BSOD 0X7B PCI\VEN_1002&DEV_4390&SUBSYS_B0021458

Excellent first post!
Welcome to DriverPacks!
I edited your title to be more descriptive and added code tags to the post.

newsposter wrote:

Driverpacks officially supports XP only.  AFAIK no XP driver will function on Win2k.

That's not true.  Granted, the bulk of our drivers are oriented for XP, but many pull double-duty and work with Win2k.
JakeLD just built a new dpms release candidate that addresses your issue (maybe).  Can you test?

Fixed
-Changed [AM] & [AM1] sections to fix a BSOD with AMD IDE driver (cfp)

http://driverpacks.sytes.net/driverpack … 2_907r2.7z

If that doesn't work, newsposter is right I fear.  Win2k is beyond it's end-of-life, so your best bet is to run it in VirtualBox when needed.  Otherwise you can run Win2k on your older system where it was perfectly happy.

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!

Re: [SLV] Win2K BSOD 0X7B PCI\VEN_1002&DEV_4390&SUBSYS_B0021458

azcoder wrote:

It had 4 drives

Which drives and sizes did you used?

Which mass storage windows drivers did you used in the past?

Did you set EnableBigLBA at Win2k?

azcoder wrote:

I used two new SATA drives.

Which drives and sizes do you use now?

azcoder wrote:

I downloaded and built UBCD4WIN 3.5 and tried the plugin to write the SATA drivers to the Win2k system, but it did not work.

How did you called fix_hdc? Did you offer proper Win2k source files? Be aware, this won't set EnableBigLBA. Integrate this manually.

azcoder wrote:

I downloaded and built a Win2k system with SP4 and all the latest updates using HFSLIP (http://www.vorck.com/windows/2ksp5.html).  When booting the install CD, the drive information is incorrect and the installer can not find a valid Win2k partition.

Does this approach set EnableBigLBA at Win2k install CD? Add the setting to setupreg.hiv.


azcoder wrote:

============
RAID Devices
============
PCI\VEN_1002&DEV_4390&SUBSYS_B0021458&REV_00\3&61AAA01&0&88
    Name: Standard Dual Channel PCI IDE Controller
    Hardware ID's:
        PCI\VEN_1002&DEV_4390&SUBSYS_B0021458&REV_00
        PCI\VEN_1002&DEV_4390&SUBSYS_B0021458
        PCI\VEN_1002&DEV_4390&CC_01018F
        PCI\VEN_1002&DEV_4390&CC_0101
    Compatible ID's:
        PCI\VEN_1002&DEV_4390&REV_00
        PCI\VEN_1002&DEV_4390
        PCI\VEN_1002&CC_01018F
        PCI\VEN_1002&CC_0101
        PCI\VEN_1002
        PCI\CC_01018F
        PCI\CC_0101
PCI\VEN_1002&DEV_439C&SUBSYS_50021458&REV_00\3&61AAA01&0&A1
    Name: Standard Dual Channel PCI IDE Controller
    Hardware ID's:
        PCI\VEN_1002&DEV_439C&SUBSYS_50021458&REV_00
        PCI\VEN_1002&DEV_439C&SUBSYS_50021458
        PCI\VEN_1002&DEV_439C&CC_01018A
        PCI\VEN_1002&DEV_439C&CC_0101
    Compatible ID's:
        PCI\VEN_1002&DEV_439C&REV_00
        PCI\VEN_1002&DEV_439C
        PCI\VEN_1002&CC_01018A
        PCI\VEN_1002&CC_0101
        PCI\VEN_1002
        PCI\CC_01018A
        PCI\CC_0101
2 matching device(s) found.

This is SATA drives at IDE emulation mode. Default 2000 and XP pciide.sys sould support this.
There are no addional mass storage drivers required.
Default Win2k fails at big drives, atapi.sys requires EnableBigLBA.

Addional Win2k drivers maybe nice, to circumvent EnableBigLBA requirement.

Re: [SLV] Win2K BSOD 0X7B PCI\VEN_1002&DEV_4390&SUBSYS_B0021458

newsposter wrote:

Most BIOS have an IDE compatability setting for their SATA controllers.  Have you tried that?

If you really want to run XP and Win2k on modern hardware, I would encourage you to explore the possibilities of hosting both of those OSs on Fedora under a virtualization product like VirtualBox.  In your case, the immediate benefit of VB is to present a standardized and simplified set of virtual devices and drivers to the hosted operating systems.  Another upside is more precide control of disk space and a vastly simplified boot arrangement.

I have my bios set to IDE compatibility.

As for VirtualBox, maybe I did not make myself clear in my message.  I installed VirtualBox on both WinXP and Fedora 11 and created a Win2k guest.  I tried to install the Win2kSP4+ w/DriverPacks and I get the error:

The file ahcix86.sys is corrupted.
Press any key to continue.

That is the same message I get booting the Win2k install CD on the real machine.  So VirtualBox is just a handy way to test for me.  It will not allow me to install Win2k.  WinXP w/sp3 installs without a problem.

The real problem is, how do I add the required drivers to the installed Win2k installation so it can be booted?

Re: [SLV] Win2K BSOD 0X7B PCI\VEN_1002&DEV_4390&SUBSYS_B0021458

cdob asked about the drives:
The old IDE drives were 160 GB each and the SATA drives were 400 GB each.  The new drives are also 400 GB SATA drives.  My initial message stated the old controllers were VIA and Promise.  The new one is AMD.  Win2k was happy before seeing the IDE and SATA drives.

cdob wrote:

Did you set EnableBigLBA at Win2k?

I have no idea what you are talking about.  Could you please provide some detail about where this is located and how I might set it or see if it is set.

cdob wrote:

How did you called fix_hdc? Did you offer proper Win2k source files? Be aware, this won't set EnableBigLBA. Integrate this manually.

I booted the UBCD4WIN CD and selected Programs->Registry Tools->FIX_hdc->fix hard disk controller.  This did not work for me.  How do I set EnableBigLBA manually?  Where?  Could you explain this please?

Re: [SLV] Win2K BSOD 0X7B PCI\VEN_1002&DEV_4390&SUBSYS_B0021458

mr_smartepants wrote:

JakeLD just built a new dpms release candidate that addresses your issue (maybe).  Can you test?

I tried the new dpms at http://driverpacks.sytes.net/driverpack … 2_907r3.7z and it gives me the exact message as the 906r1 version. I get the error:

The file ahcix86.sys is corrupted.
Press any key to continue.

Is there any way to get past this error so I can actually get a driver installed?  As far as VirtualBox goes, it gets the same error.  I only tried VirtualBox to see if I could get a working system and then copy it back to my Win2k on the real harddrive.  I need a real install to run one of my applications that uses custom PCI hardware/drivers.  At some point in the future this application will be certified for newer versions of Windows, but it is a long process.  The application is 120,000 lines of C++ code and uses custom PCI device drivers, so this is not a thing that can be done overnight.

So, the problem is still to figure out what drivers are required for the new hardware and figure out how to actually get them installed.  What method may have the greatest chance of success?

Re: [SLV] Win2K BSOD 0X7B PCI\VEN_1002&DEV_4390&SUBSYS_B0021458

OK, sounds to me like ahcix86.sys is being called inappropriately.  JakeLD would know more about this than I.
As to VirtualBox, if you have the latest version installed (3.0.2), click on "Settings" then "Hard Disks" tab on the left, then uncheck "Enable additional controller" and see if that helps.  At the very least, you should be able to install Win2k in VirtualBox and get your code sorted.

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!

Re: [SLV] Win2K BSOD 0X7B PCI\VEN_1002&DEV_4390&SUBSYS_B0021458

whoops, my bad re win2k and xp (and server 2003) drivers.  Serves me right for posting at 2 AM after a hard day of hammering Server 2008 update concepts into noobs heads at work.

Again, sorry 'bout that.

Re: [SLV] Win2K BSOD 0X7B PCI\VEN_1002&DEV_4390&SUBSYS_B0021458

Back to the matter at hand...

By any chance do you have sata pass-through enabled for your win2k or xp virtual machines?

Set up your system bios (the real system) to whatever is best for Fedora, don't worry about anything related to virtualbox

Get Fedora running as well as you possibly can.  Then lets start kicking win2k and xp into submission as VMs.

Last edited by newsposter (2009-07-29 08:34:59)

Re: [SLV] Win2K BSOD 0X7B PCI\VEN_1002&DEV_4390&SUBSYS_B0021458

azcoder wrote:

The old IDE drives were 160 GB each and the SATA drives were 400 GB each.  The new drives are also 400 GB SATA drives.  My initial message stated the old controllers were VIA and Promise.  The new one is AMD.  Win2k was happy before seeing the IDE and SATA drives.

Drives are greater 128 GB. Win2k dosn't support this devices out of the box.
Yes, I understand the old hardware. But this dosn't clarify used drivers.
Again the question: which driver did you used previously?
Did you used default Win2k drivers? Did you used atapi.sys ?
Did you added massstorage drivers?

Can you upload your system reg file? Be aware this may contain private data.

Run a search machine, keyword: EnableBigLBA

http://support.microsoft.com/kb/305098/

As for Win2k installation media: http://www.msfn.org/board/index.php?showtopic=75713

Re: [SLV] Win2K BSOD 0X7B PCI\VEN_1002&DEV_4390&SUBSYS_B0021458

mr_smartepants wrote:

OK, sounds to me like ahcix86.sys is being called inappropriately.  JakeLD would know more about this than I.
As to VirtualBox, if you have the latest version installed (3.0.2), click on "Settings" then "Hard Disks" tab on the left, then uncheck "Enable additional controller" and see if that helps.  At the very least, you should be able to install Win2k in VirtualBox and get your code sorted.

I am using the latest version 3.0.2.  The "Enable additional controller' is NOT checked.  The default controller type is PIIX4.  Other types are PIIX3 and ICH6.  I tried them all.  None of these work.  I get the same file corruption error.  I went back to the original Win2K install CD.  It gets about 2/3rds of the way through driver installation and restarts, over and over.  It is after several screen flashes.  I do not want to spend time on debugging VirtualBox install errors, I just want to get the installed version of Win2k to boot.

Re: [SLV] Win2K BSOD 0X7B PCI\VEN_1002&DEV_4390&SUBSYS_B0021458

newsposter wrote:

Back to the matter at hand...

By any chance do you have sata pass-through enabled for your win2k or xp virtual machines?

Set up your system bios (the real system) to whatever is best for Fedora, don't worry about anything related to virtualbox

Get Fedora running as well as you possibly can.  Then lets start kicking win2k and xp into submission as VMs.

Sata pass-through is not enabled in VirtualBox.  I am thinking this is the setting noted in mr_smaretpants message "Enable additional controller".

The Bios is set for IDE compatibility.

Fedora 11 works fine with this mode.  I can install  WinXp w/SP3 in VirtualBox with no problem.  It is only Win2k that does not work.  I really do not want to debug VirtualBox with this hardware, just the installed Win2k system.  Other suggestions?

Re: [SLV] Win2K BSOD 0X7B PCI\VEN_1002&DEV_4390&SUBSYS_B0021458

cdob wrote:

Again the question: which driver did you used previously?
Did you used default Win2k drivers? Did you used atapi.sys ?
Did you added massstorage drivers?

Can you upload your system reg file? Be aware this may contain private data.

Well I rechecked the disk sizes on the old system, and the old system disk was 120 GB, not 160 GB.  Only the 2nd IDE drive was 160 GB.  I checked the drivers the best I could and it seemed that because I was using the non-raid mode of the VIA and Promise controllers, the SP4 default drivers used were atapi.sys (5.0.2195.6699), pciide.sys (5.0.2195.6655), and pciidex.sys (5..9.2195.6672).  I did not use any of the MassStorage drivers on the old system.  I checked the old win2k system, and there is no EnableBigLBA parameter in the registery.  I also checked the current running WinXP, and it has the parameter, but it was set to 0.  Not sure why it works if what you say is true.  I modified the /i386/hivesft.inf to set the parameter, but I still get the corrupt file error.  I have not modified my current win2k registery to add the parameter.  What utility do you suggest I use?  I can not use regedit because I can not boot the system.

I can send you the reg file if you think you can modify it.  Tell me how, and I can make the change.  Please continue with the suggestions.

Jim

Re: [SLV] Win2K BSOD 0X7B PCI\VEN_1002&DEV_4390&SUBSYS_B0021458

are you running the VMs on real disk partitions or VHD images?

Re: [SLV] Win2K BSOD 0X7B PCI\VEN_1002&DEV_4390&SUBSYS_B0021458

azcoder wrote:

the old system disk was 120 GB, not 160 GB.  Only the 2nd IDE drive was 160 GB.

Do you remember listed disk size at disk management?
Did you get around 130 GB or around 150 GB for 2nd IDE drive?

Did you used directory name \winnt at Win2k?

Does exist a file \winnt\system32\config\fix_hdc.log at new SATA drive?
Post the contents.

azcoder wrote:

I checked the old win2k system, and there is no EnableBigLBA parameter in the registery.

Then atapi.sys won't use the whole IDE drive.

azcoder wrote:

I also checked the current running WinXP, and it has the parameter, but it was set to 0.

XP is not 2K. XP dosn't use this setting anymore.

azcoder wrote:

I modified the /i386/hivesft.inf to set the parameter, but I still get the corrupt file error.

First you have to change setupreg.hiv at installation CD.

azcoder wrote:

I have not modified my current win2k registery to add the parameter.  What utility do you suggest I use?  I can not use regedit because I can not boot the system.

Yes, use regedit. Boot XP or UBCD4Win, run regedit.
Select the following subkey: HKEY_LOCAL_MACHINE
Click Load Hive from the Registry menu
open file \winnt\system32\config\system
Type name system_win2k for the hive you are loading
Make the necessary changes to the registry hive.
Select system_win2k and click Unload Hive from the Registry menu

Re: [SLV] Win2K BSOD 0X7B PCI\VEN_1002&DEV_4390&SUBSYS_B0021458

newsposter wrote:

are you running the VMs on real disk partitions or VHD images?

I am using a VHD, a disk_C.vdi file.

Re: [SLV] Win2K BSOD 0X7B PCI\VEN_1002&DEV_4390&SUBSYS_B0021458

cdob wrote:

Do you remember listed disk size at disk management?
Did you get around 130 GB or around 150 GB for 2nd IDE drive?

Did you used directory name \winnt at Win2k?

Does exist a file \winnt\system32\config\fix_hdc.log at new SATA drive?

I really do not remember what the disk manager said the size was.  I think it stated the real size.  The windows partitions were in the first 70 GB of the drive, with Linux using the upper parts.  I could have easily missed the sizing mismatch.

The Win2k directory is /windows, not /winnt.

After running the FIX_hdc from UBCD4Win v3.5, I had a file FIX_hdc.log and a file system_hdc.  I reinitialized my win2k partition back to the backup saved state, so these got removed.

cdob wrote:

Yes, use regedit. Boot XP or UBCD4Win, run regedit.
Select the following subkey: HKEY_LOCAL_MACHINE
Click Load Hive from the Registry menu
open file \winnt\system32\config\system
Type name system_win2k for the hive you are loading
Make the necessary changes to the registry hive.
Select system_win2k and click Unload Hive from the Registry menu

That is good to know.  I made the registery changes and I still get the same stop code.  Are you sure atapi.sys is the correct driver for my hardware.  The DriverPacks entry amdhdc.inf for AM1 is the one for my hardware.  I think it uses AmdIde.sys.  Is there a way to just install this driver?  Maybe using the same method in UBCD4WIN for the plugin that does FIX_hdc?  Can I install the amdide.sys driver manually by copying the files and making registry changes?  How?

Re: [SLV] Win2K BSOD 0X7B PCI\VEN_1002&DEV_4390&SUBSYS_B0021458

azcoder wrote:

I reinitialized my win2k partition back to the backup saved state, so these got removed.

That's sad news. I didn't exptected this.

azcoder wrote:

I made the registery changes and I still get the same stop code.

There are more settings required. Run fix_hdc too. Catch whole output text, post text. And post fix_hdc.log.

Are you sure atapi.sys is the correct driver for my hardware.

Yes, default driver does support a SB710. Dosn't XP use atapi.sys too?

The DriverPacks entry amdhdc.inf for AM1 is the one for my hardware.  I think it uses AmdIde.sys.

This is a second possibility. Sometimes a manufacturer adds features like hotplug, not supported by default ms drivers.

Is there a way to just install this driver?  Maybe using the same method in UBCD4WIN for the plugin that does FIX_hdc?

Use fix_hdc too.
Create a win2k installation CD, add drivers. Boot the CD. Press F10 at F6 message. Does recovery console list drives?
Boot UBCD4Win. Run "fix_hdc -?" to list options.
Set your win2k installation media as source media.

Re: [SLV] Win2K BSOD 0X7B PCI\VEN_1002&DEV_4390&SUBSYS_B0021458

cdob wrote:
azcoder wrote:

I reinitialized my win2k partition back to the backup saved state, so these got removed.

That's sad news. I didn't exptected this.

That was not a bad thing.  It returned me back to a known state after all the attempts to get things working.

cdob wrote:

There are more settings required. Run fix_hdc too. Catch whole output text, post text. And post fix_hdc.log.

I made registry change to support 48 bit addressing and I still got the stop error.  I then booted UBCD4Win and ran FIX_hdc.  I have attached the log file at the end of this message.  It seems like only the intelide.sys driver got updated.  This is an AMD system.  At the same time I copied the AmdIde.sys file to windows/system32/drivers, Amdhdc.inf to windows/inf/oem15.inf and windows/inf/Amdhdc.inf, and AmdHDC.cat to windows/inf/catalog directories.  And rebooted into safe mode....

There was no abort this time?  I know before I had tried FIX_hdc and the registry fix together and I still got the stop error.  This time I did not.  Not sure if the oem15 change was part of the fix.   Moving on, I was able to install the driver for the disk (AmdIde.sys) for both controllers and get the system to reboot in regular mode.  I was able to install the Ethernet controller driver by copying the Gigabyte CD to the hard drive.  I am unable to find a driver for the cdrom (vaxscsi.sys on winXP) that will allow me to read either of my cdroms.  I also copied and unzipped the DriverPacks to see if I can find more drivers to install.  The one real pain is the video driver for the Radeon HD 4650.  The DrivePacks video A1 directory has the driver (ati2mtag.sys), but it will not install.  The subsys value is different.  So I am stuck with 640x480 by 16 colors!


cdob wrote:

Create a win2k installation CD, add drivers. Boot the CD. Press F10 at F6 message. Does recovery console list drives?
Boot UBCD4Win. Run "fix_hdc -?" to list options.
Set your win2k installation media as source media.

I think you ment F6 at F6 message.  It said -none- were found.  If I do not hit F6 I get the error:

The file ahcix86.sys is corrupted.
Press any key to continue.

This is something wrong with the DrivePacks I think.

I made a lot of progress today.  Thanks for your help and understanding.  I really need to figure out how to install the WinXP driver for the video card.  I added the PCI definition to the list in the inf file, but it was still a no go.  Please take a look at the CX_80257.inf or CX_80264.inf files (Graphics_A) to see how I might change them for Win2k.  I still have several devices still needing drivers, but I will attack them one at a time.

Thanks again,

Jim


Change to registry for 48 bit support:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\atapi\Parameters]
"EnableBigLba"=dword:00000001


FIX_hdc.log --------

Wed 07/29/2009 10:41:17.84 
 
devcon hwids PCI\CC_01* 

PCI\VEN_1002&DEV_4390&SUBSYS_B0021458&REV_00\3&61AAA01&0&88
    Name: IDE Controller
    Hardware ID's:
        PCI\VEN_1002&DEV_4390&SUBSYS_B0021458&REV_00
        PCI\VEN_1002&DEV_4390&SUBSYS_B0021458
        PCI\VEN_1002&DEV_4390&CC_01018F
        PCI\VEN_1002&DEV_4390&CC_0101
    Compatible ID's:
        PCI\VEN_1002&DEV_4390&REV_00
        PCI\VEN_1002&DEV_4390
        PCI\VEN_1002&CC_01018F
        PCI\VEN_1002&CC_0101
        PCI\VEN_1002
        PCI\CC_01018F
        PCI\CC_0101
PCI\VEN_1002&DEV_439C&SUBSYS_50021458&REV_00\3&61AAA01&0&A1
    Name: IDE Controller
    Hardware ID's:
        PCI\VEN_1002&DEV_439C&SUBSYS_50021458&REV_00
        PCI\VEN_1002&DEV_439C&SUBSYS_50021458
        PCI\VEN_1002&DEV_439C&CC_01018A
        PCI\VEN_1002&DEV_439C&CC_0101
    Compatible ID's:
        PCI\VEN_1002&DEV_439C&REV_00
        PCI\VEN_1002&DEV_439C
        PCI\VEN_1002&CC_01018A
        PCI\VEN_1002&CC_0101
        PCI\VEN_1002
        PCI\CC_01018A
        PCI\CC_0101
2 matching device(s) found.
 
 
Importing B:\fix_hdc.reg: 
REGEDIT4

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\primary_ide_channel]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\secondary_ide_channel]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\*pnp0600]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\*azt0502]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\gendisk]
"ClassGUID"="{4D36E967-E325-11CE-BFC1-08002BE10318}"
"Service"="disk"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#cc_0101]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&cc_0101]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Services\atapi]
"ErrorControl"=dword:00000001
"Group"="SCSI miniport"
"Start"=dword:00000000
"Tag"=dword:00000019
"Type"=dword:00000001
"DisplayName"="Standard IDE/ESDI Hard Disk Controller"
"ImagePath"="system32\\drivers\\atapi.sys"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Services\IntelIde]
"ErrorControl"=dword:00000001
"Group"="System Bus Extender"
"Start"=dword:00000000
"Tag"=dword:00000004
"Type"=dword:00000001
"ImagePath"="system32\\drivers\\intelide.sys"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Services\PCIIde]
"ErrorControl"=dword:00000001
"Group"="System Bus Extender"
"Start"=dword:00000000
"Tag"=dword:00000003
"Type"=dword:00000001
"ImagePath"="system32\\drivers\\pciide.sys"

Re: [SLV] Win2K BSOD 0X7B PCI\VEN_1002&DEV_4390&SUBSYS_B0021458

azcoder wrote:

The one real pain is the video driver for the Radeon HD 4650. 
...
I really need to figure out how to install the WinXP driver for the video card.

This is off-topic for this thread.  Please open a new thread in the correct area and post your HWID list, DPs_BASE.log, & DPsFnshr.log.  I'm certain that's directly supported in the latest DriverPack Graphics A.  I'll have a look.

azcoder wrote:

Please take a look at the CX_80257.inf or CX_80264.inf files (Graphics_A) to see how I might change them for Win2k.

That's not going to happen.  At least not from me nor in the near future.  I just don't have the time.  ATI only supports W2k up to Radeon x850, that's 4 generations behind your card.  You can download the ATI w2k drivers and have a look at the .inf differences and try it yourself.

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!

Re: [SLV] Win2K BSOD 0X7B PCI\VEN_1002&DEV_4390&SUBSYS_B0021458

azcoder wrote:

I made registry change to support 48 bit addressing and I still got the stop error.  I then booted UBCD4Win and ran FIX_hdc.

That's windows default driver with EnableBigLBA.

It seems like only the intelide.sys driver got updated.

This is not true. Most likely there are more settings updated.

At the same time I copied the AmdIde.sys file to windows/system32/drivers, Amdhdc.inf to windows/inf/oem15.inf and windows/inf/Amdhdc.inf, and AmdHDC.cat to windows/inf/catalog directories.

Why do you copy these files?

And rebooted into safe mode....

There was no abort this time?

That's nice.

I know before I had tried FIX_hdc and the registry fix together and I still got the stop error. This time I did not.

I doubt amdide file copy makes a difference. Windows dosn't load drivers that early without registry settings.

I think you ment F6 at F6 message.

I mean F10, if I write F10.
If you don't understand a suggestion, don't make assumptions. Search the net for given keywords. That's: F10 revocery console

 
Most likely this driver dosn't support Win2k anymore.

Last edited by OverFlow (2009-07-31 06:36:20)

Re: [SLV] Win2K BSOD 0X7B PCI\VEN_1002&DEV_4390&SUBSYS_B0021458

cdob wrote:

I doubt amdide file copy makes a difference. Windows dosn't load drivers that early without registry settings.

You are correct!  Just to make sure, I reloaded by backup files again to the Win2k partition.  I retried your steps and documented all of the results.  It was a success again.  Thanks for the help cdob!

Here are the steps I followed to correct the Stop error:

I booted UBCD4Win version 3.5.
Run RegEdit.  Start->Programs->Registry Tools->RegEdit
Select HKEY_Local_Machine entry.
Select File->Load Hive.
Load C:\windows\system32\config\system.
Set Key Name to system_win2k.
Select system_win2k->ControlSet001->Services->atapi->Parameters.
Add New Key as a DWORD Value.
Set Key to EnableBigLba.
Modify data value to 0000 01 00 00 00.
Select system_win2k again.
Select File->Unload Hive (Select Yes to unload hive dialog).
Select File->Exit.

The registry is now changed for 48 bit support:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\atapi\Parameters]
"EnableBigLba"=dword:00000001

The next operation is to run the plugin FIX_hdc.
Select Start->Programs->Registry Tools->FIX_hdc->fix hard disk controller.
Select <M> Update MassStorage drivers.
Hit any key to continue and reboot into Window 2000.

Here is the console output from Fix_hdc:

 fix_hdc:  Fix for some Stop 0x0000007B Errors
 based on http://support.microsoft.com/kb/314082/
 Remember other hardware differences can cause stop 0x7b too.

 First backup data yourself.
 This comes with ABSOLUTELY NO WARRANTY.

 TargetRoot: C:\WINDOWS

 Backup does not exist and will be created.

 (M) Update MassStorage drivers
 (T) Set TargetRoot
 (0) Do nothing and exit

 Your choice ? M
creating backup of C:\WINDOWS\system32\config\SYSTEM
        1 file(s) copied.

Create MassStorage HardwareID log file C:\WINDOWS\system32\config\fix_hdc.log

ControlSet "ControlSet001" used.


IDE controller found. Add additional files.
Microsoft (R) File Expansion Utility  Version 5.1.2600.0
Copyright (C) Microsoft Corp 1990-1999.  All rights reserved.

Copying x:\i386\system32\drivers\intelide.sys to c:\windows\system32\drivers\int
elide.sys.
x:\i386\system32\drivers\intelide.sys: 5504 bytes copied.


Importing registry file "B:\fix_hdc.reg"

Fix_hdc finished. Good luck.

Press any key to continue . . .

And the FIX_hdc.log file contents:

Thu 07/30/2009 10:22:39.29 
 
devcon hwids PCI\CC_01* 

PCI\VEN_1002&DEV_4390&SUBSYS_B0021458&REV_00\3&61AAA01&0&88
    Name: IDE Controller
    Hardware ID's:
        PCI\VEN_1002&DEV_4390&SUBSYS_B0021458&REV_00
        PCI\VEN_1002&DEV_4390&SUBSYS_B0021458
        PCI\VEN_1002&DEV_4390&CC_01018F
        PCI\VEN_1002&DEV_4390&CC_0101
    Compatible ID's:
        PCI\VEN_1002&DEV_4390&REV_00
        PCI\VEN_1002&DEV_4390
        PCI\VEN_1002&CC_01018F
        PCI\VEN_1002&CC_0101
        PCI\VEN_1002
        PCI\CC_01018F
        PCI\CC_0101
PCI\VEN_1002&DEV_439C&SUBSYS_50021458&REV_00\3&61AAA01&0&A1
    Name: IDE Controller
    Hardware ID's:
        PCI\VEN_1002&DEV_439C&SUBSYS_50021458&REV_00
        PCI\VEN_1002&DEV_439C&SUBSYS_50021458
        PCI\VEN_1002&DEV_439C&CC_01018A
        PCI\VEN_1002&DEV_439C&CC_0101
    Compatible ID's:
        PCI\VEN_1002&DEV_439C&REV_00
        PCI\VEN_1002&DEV_439C
        PCI\VEN_1002&CC_01018A
        PCI\VEN_1002&CC_0101
        PCI\VEN_1002
        PCI\CC_01018A
        PCI\CC_0101
2 matching device(s) found.
 
 
Importing B:\fix_hdc.reg: 
REGEDIT4

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\primary_ide_channel]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\secondary_ide_channel]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\*pnp0600]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\*azt0502]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\gendisk]
"ClassGUID"="{4D36E967-E325-11CE-BFC1-08002BE10318}"
"Service"="disk"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#cc_0101]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&cc_0101]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Services\atapi]
"ErrorControl"=dword:00000001
"Group"="SCSI miniport"
"Start"=dword:00000000
"Tag"=dword:00000019
"Type"=dword:00000001
"DisplayName"="Standard IDE/ESDI Hard Disk Controller"
"ImagePath"="system32\\drivers\\atapi.sys"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Services\IntelIde]
"ErrorControl"=dword:00000001
"Group"="System Bus Extender"
"Start"=dword:00000000
"Tag"=dword:00000004
"Type"=dword:00000001
"ImagePath"="system32\\drivers\\intelide.sys"

[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\Services\PCIIde]
"ErrorControl"=dword:00000001
"Group"="System Bus Extender"
"Start"=dword:00000000
"Tag"=dword:00000003
"Type"=dword:00000001
"ImagePath"="system32\\drivers\\pciide.sys"

I wish to thank everyone on this forum that helped solve this problem.  Cdob was extremely helpful and patient to my unending list of questions.  It is now time to move on to some of the other driver problems.

Jim

Re: [SLV] Win2K BSOD 0X7B PCI\VEN_1002&DEV_4390&SUBSYS_B0021458

OverFlow wrote:
MySelf wrote:
cdob wrote:

I mean F10, if I write F10.
If you don't understand a suggestion, don't make assumptions. Search the net for given keywords. That's: F10 revocery console

 
Most likely this driver dosn't support Win2k anymore.

The other possability is the limit for 2K has been breached in the new pack...

    Disableing a few drivers for win2k may also yield results...

    IE adding the line

    ms_1_exc_disableIfOS="w2k" in the mass storage INI for a few more drivers (ones you don't think you will need)

Cool Pyramid eh?

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: [SLV] Win2K BSOD 0X7B PCI\VEN_1002&DEV_4390&SUBSYS_B0021458

Thanks cdob!  I don't know what we'd do without your help.

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!