Skip to main content
Start a Conversation

Unsolved

This post is more than 5 years old

M

Mumford68

3 Posts

5767

April 25th, 2012 02:00

Moved Dimension 4300 HDD to 4600 now won't load OS

Hello, We have a Dimension 4300 with a 260Gb HDD. It

out a couple of weeks ago and found a 4600. I tried the 4600 and it booted up WinXp however we need the data from the 4300 HD so I put it into the 4600 and the system sees it in CMOS. However after leaving the CMOS screen it goes blank for a couple of seconds as if it is going to start loading up WinXp Home (OS same on both hard drives) but then ends up at the Windows options screen (Boot normal mode, safe mode, safe mode with prompt, etc). I have tried pretty much all the options but all that happens in a continuous loop is that the screen then goes blank for a couple of seconds and the returns to the windows options screen.

I have tried the jumpers on the old (260Gb partitioned into two sections) drive to both 'Cable select' and 'Master single' with the same results.

With the 2 drives that came with the 4600 it boots to WinXp (I have both 4600 drives out when trying to get the old drive to boot).

All the programs, data, drivers, etc I need are on that drive not too mention I cannot (even if I knew how) that the boot drive that came with the 4600 is not big enough to hold everything that is on the old 4300 drive (WD2500).

I am wondering if there is something inherent like hidden info. that the system is looking for that does not match up with the drive I put in there or if there is something stored in the MBR or something that confuses the 4600.

Any help is of course greatly appreciated. We don't have the money to take this to anyone which seems silly anyhow as one would think it wouldn't have this difficulty.

As a side note, the battery is apparently going bad in the 4600 as after you unplug the power cord and plug it back in it does not know the time or date.
Also when the 4300

out I assumed as I saw power come on but nothing on the monitor that either the PSU or CPU had gone out but now if there is no explanation of conflict or the old drive in the new (relative term) system if the HD has issue.

Frustrated as it is needed for getting on the net and such.

Again thank in advance for any suggestions and/or help,

Steve

fireberd

9 Legend

 • 

33.3K Posts

April 25th, 2012 04:00

There is different hardware between the 4300 and the 4600, thus the hard drive from the 4300 will not boot up the 4600, or if it does there will be many errors.

If you want to get the data off of the 4300's hard drive, connect the drive to the second port on the IDE ribbon data cable (not the end connector as that should be on your 4600's boot drive).  Set both drives for cable select.  Make sure your original 4600's hard drive is set as the first drive in the boot sequence in the BIOS. 

You will be able to get user data off of the old drive but you can't copy programs to the 4600.  Programs must be installed, using the program's install procedure.

Alternately, if hooking to the second hard drive port on the hard drive data cable does not work, you could temporarily use the data and power cable from the CD/DVD drive and that would allow you to copy off the user data to the 4600's hard drive.

rdunnill

6 Professor

 • 

8.8K Posts

April 25th, 2012 19:00

It's possible to run an XP "repair install" that will update the 4300 Windows instance to work with the 4600's hardware. Afterwards, it will boot.

tgsmith

2.9K Posts

April 25th, 2012 20:00

Mumford68,

First and foremost, please follow fireberd's suggestion on backing up your 4300 drive's data.

Question:  Are the 4300 and 4600 drives running the same version of XP; i.e., XP Home or XP Pro?  Also has the XP on the 4300 drive been upgraded to Windows XP SP3?

It may be possible to do a repair install of XP on the 4300 drive in the 4600 machine.  However, you must do a repair install of XP with an XP reinstallation CD having the same version and Service Pack level.  If they are not the same you must have the original Dell Reinstallation CD for Windows XP that shipped with the 4300.  With it you can slipstream SP3 onto it using Autostreamer or nLite.  Instructions on how to perform a repair install of Windows XP are here:

www.michaelstevenstech.com/XPrepairinstall.htm

The above web page includes links for obtaining XP SP3 and links for AutoStreamer.

Note:  Read the instructions fully.  Pay particular attention to the WARNINGS included in the instructions.

Hope this information helps.

speedstep

9 Legend

 • 

47K Posts

April 26th, 2012 07:00

The chipset and ICH aka Hard Drive controller are totally different thats why you get Blue screen

STOP 7B

This is well known and Documented.

Important notice for users of Windows XP with Service Pack 3 (SP3): The support for this product ends April 8, 2014. To ensure that you will receive all important security updates for Windows you need to upgrade to a later version such as Windows 7.

You receive a Stop 0x0000007B error after you move the Windows ...


You receive a Stop 0x0000007B error after you move the Windows XP system disk to another computer

This article describes how you may receive a Stop error when you try to start the Microsoft Windows XP-based backup computer after you move the system disk to a backup computer. This issue occurs when registry entries and the drivers for the mass storage controller are not installed in Windows XP. To resolve this issue, use the same hardware in the backup computer.

After you move the Microsoft Windows XP system (boot) disk to a backup computer, you may receive the following Stop error when you try to start the Windows XP-based backup computer:

STOP: 0x0000007B (0xF741B84C,0xC0000034,0x00000000,0x00000000)
INACCESSIBLE_BOOT_DEVICE
This error may occur if the registry entries and the drivers for the mass storage controller hardware in the backup computer are not installed in Windows XP.

For integrated device electronics (IDE) controllers, there are several different chip sets available, such as Intel, VIA, and Promise. Each chip set has a different Plug-n-Play identifier (PnP-ID).

The PnP-ID information of mass storage controllers for the backup computer must be in the registry before startup so that Windows XP can initialize the correct drivers.
To resolve this error, use the same hardware for the backup computer:
  • Replace the problem hardware components in the backup computer with components of the same manufacturer, make, and model as the motherboard in the computer that you are backing up.
  • If the system disk is a SCSI disk, use the same make and model of SCSI controller in the new computer.
  • If the system disk is an IDE disk, use the same kind of motherboard in the new computer, a motherboard that has the same kind of IDE chip set and the same PnP-ID as the motherboard in the computer that you are backing up.
For SCSI-based system disks, you can prime the registry and make sure that the drivers that you want are in place by installing the SCSI controller that is used by the backup computer before you transfer the system disk contents. Windows XP PnP detects the controller, sets up critical registry entries, and copies the appropriate driver.

After you see the SCSI controller in Device Manager, you can remove the alternate controller. If you have to move the system disk to another computer that has the same make and model of SCSI controller in the future, Windows XP will start successfully because Windows XP has already used that controller one time and has retained the correct configuration information.
Although Microsoft does not support this method, you can import or merge the required registry entries, and copy the drivers beforehand to support all IDE controllers that are natively supported by Windows XP. Note that although this method might enable the relocated system disk to start successfully, other hardware differences can lead to other problems.

This solution provides support for IDE controllers whose PnP-ID matches one of the PnP-IDs in the following list. However, if you want to determine beforehand the IDE controllers that are used in your current and backup computers, you can search the %SystemRoot%\Setupapi.log file for the PnP-ID that is detected while the Setup program is running.

After you determine the PnP-IDs that are used in your computers, you can choose to merge or to populate the registry with only the PnP-IDs that you need.

The following list shows the PnP-IDs of natively supported IDE controllers in Windows XP:
To import this information, follow these steps on two different test computers that exhibit the Stop 0x0000007B error after you change disks between computers. After you follow this procedure on each test computer, you can probably move the hard disks and start both computers without receiving the Stop 0x0000007B error. However, other hardware differences can cause other problems.
Copy the following information into Notepad, and then save the file on a 3.5-inch disk. Name the file Mergeide.reg, without the .txt file name extension.
  1. ********** Start copy here **********
    Windows Registry Editor Version 5.00

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

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

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

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

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

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

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_0e11&dev_ae33]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="pciide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1039&dev_0601]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="pciide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1039&dev_5513]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="pciide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1042&dev_1000]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="pciide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_105a&dev_4d33]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="pciide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0640]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="pciide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0646]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="pciide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0646&REV_05]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="pciide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0646&REV_07]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="pciide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0648]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="pciide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0649]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="pciide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1097&dev_0038]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="pciide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10ad&dev_0001]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="pciide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10ad&dev_0150]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="pciide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5215]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="pciide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5219]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="pciide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5229]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="pciide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1106&dev_0571]
    "Service"="pciide"
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

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

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

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

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

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

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

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

    ;Add driver for Atapi (requires Atapi.sys in Drivers directory)

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\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"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\ 
      52,00,49,00,56,00,45,00,52,00,53,00,5c,00,61,00,74,00,61,00,70,00,69,00,2e,\ 
      00,73,00,79,00,73,00,00,00

    ;Add driver for intelide (requires intelide.sys in drivers directory)

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IntelIde]
    "ErrorControl"=dword:00000001
    "Group"="System Bus Extender"
    "Start"=dword:00000000
    "Tag"=dword:00000004
    "Type"=dword:00000001
    "ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\ 
      52,00,49,00,56,00,45,00,52,00,53,00,5c,00,69,00,6e,00,74,00,65,00,6c,00,69,\ 
      00,64,00,65,00,2e,00,73,00,79,00,73,00,00,00


    ********** End copy here **********

  2. Extract the Atapi.sys, Intelide.sys, Pciide.sys, and Pciidex.sys files from the %SystemRoot%\Driver Cache\I386\Driver.cab file, or copy the files to the %SystemRoot%\System32\Drivers folder.
  3. In Microsoft Windows Explorer, right-click the Mergeide.reg file in the floppy drive, and then click Merge.

    Windows XP displays the following message:
    Are you sure you want to add the information in A:\Mergeide.reg to the registry?
    Click Yes.

    After the import process is completed, Windows XP displays another message:
    Information from A:\Mergeide.reg was successfully entered into the registry.
  4. Quit Windows XP, turn off the computer, and then move the system disk to the other test computer, the one that previously produced a Stop 0x0000007B error, and then test to see if you can successfully start the second computer.

View More

View All

No Events found!

Top