Member Avatar for tholkien

I have XP Home SP2 installed as my master harddrive and it now refuses to even start up (it refers to a dump line x). I've tried to change it to slave, and just install another XP based drive as master, but my PC cannot figure it out. - Or is it me? I Really need some of the info on the "frozen" HDD. Can anyone tell me what to do?

Any suggestions are highly appreciated!

Tom H.

  • 3 Contributors
  • 3 Replies
  • 137 Views
  • 2 Days Discussion Span
  • Latest Post Latest Post by DMR

Dani AI

Generated

As noted, the single most useful thing is the exact stop/error text and where it appears in the boot sequence. As suggested, a clear list of what was changed during installation or drive swapping (BIOS settings, jumper positions, any edits to boot files) makes diagnosis far easier.

Priority actions (non-destructive first)

  • Preserve important files before running low-level repairs. If the drive contains irreplaceable data, create an image or copy files first; repeated repair attempts can make a failing disk worse.
  • Verify the BIOS detects the drive and note any unusual noises or SMART warnings.

Common Recovery Console sequence (XP)
Boot the XP CD, enter Recovery Console (press R), then run these commands against the Windows volume:

chkdsk C: /p /r
fixmbr
fixboot
bootcfg /rebuild

Brief notes: chkdsk repairs filesystem problems; fixmbr and fixboot replace MBR/boot sector; bootcfg rebuilds boot.ini entries. These can fix software-level boot failures but should be used only after imaging if hardware failure is suspected.

If Recovery Console fails or the disk is flaky

  • Image the drive first using a Linux live USB and GNU ddrescue:
    ddrescue -f -n /dev/sdX /mnt/backup/image.img /mnt/backup/image.log
  • Check SMART (smartctl) and use TestDisk to recover/repair partitions. PhotoRec or Windows tools like Recuva can recover files from the image.
  • If the drive clicks or fails to spin, stop and consult a professional data-recovery service.

Dual-XP boot tip
When two XP installs exist, boot.ini must point to the correct rdisk/partition for each installation. Moving a Windows disk between different hardware often requires a repair install or sysprep to resolve driver/HAL mismatches. Image first, then attempt non-destructive fixes.

Recommended Answers

All 3 Replies

Member Avatar for prof.thakur

tell me what u did during the next installation
then only u can get any information

specify what u did during the selection process at installation

Member Avatar for tholkien

It's actually been awhile since I tried it last, but I went into the boot.ini and selected the new harddrive, as well as changing master/slave switches. Is that what you were asking me?

Hey, I'm sory if I'm not too fast at answering back. Job's kinda holding me up these days. I appreciate any patience given, though.

TH

Member Avatar for DMR

...it now refuses to even start up (it refers to a dump line x)

Please give us the full and exact specifics of the error message, as well as telling us exactly where in the boot process the error appears. Also, give us some details on the history of the problem if possible.

and just install another XP based drive as master, but my PC cannot figure it out.

Not unusual- unless the computer from which you obtained the second XP drive was identical (hardware-wise) to the problematic computer, there's a very good chance that trying to use the new XP drive will just cause more headaches.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.