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?

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

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.

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

Why do you copy these files?

That's nice.

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

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 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.

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.

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.

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!

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"

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

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

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

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

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

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.

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.

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?

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

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

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.

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

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

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

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

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

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?

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.

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