Computer - Medion (possibly model 8083). Windows XP SP1. 200 GB hard drive partitioned as follows - C: Boot, D: Backup and E: Recover.
Just before Xmas a program crashed on my PC, it froze completely and had to turn the power off. When I turned it on again I got a small beep
(not the normal one) and a black screen with the message - "Disk boot failure. Insert system disk and press enter". There is no chance that this was a virus as I had earlier that day run checks with both Avast and Malwarebytes.
After weeks of trying to solve it using info on the 'net (including this forum) including using the Recovery Console (including using CHKDSC /p, CHKDSC /r fixmbr and others!) and a non-destructive reinstall of Windows, I've got to the stage where the drive will boot if I use a 'Paragon Rescue Kit 10' CD - this enables me to search for OSes on the hard drive and then boot from that OS - this works fine and boots into Windows as I left it, with all my files intact and seemingly working fine.
I don't really understand all the info that the Recovery Kit gives me, but some of what I think might be helpful is as follows -
The 'Find OS' screen finds 'Win 2K/XX/2003 "BOOT".'
Details = Hard Disk:0
Partition : Primary 00
File System NTFS
Paragon Boot Corrector finds - 1 Disk0, Partition0 - Windows XP
[boot loader]
timeout = 30
default = multi(0) disk(0) rdisk(0) partition(1)\WINDOWS
[operating systems]
multi(0) disk(0) partition(1)\WINDOWS="Microsoft Windows XP Home Edition"/fast detect
Boot Partition Record
Basic Hard Disk 0
Type Active File System Label Size
Primary No NTFS BOOT 93.2GB
Extended 83.4GB
Logical No NTFS Backup 83.4GB
Primary No NTFS Recover 9.8GB
(All options are greyed out)
I did find it odd that the Boot Corrector found Windows on Partition0 whereas the boot.ini states partition(1), so I did try editing that using the Boot Corrector (changing both incidences of 'partition(1) to 'partition(0)'), but it didn't work so I editied it back to what it said originally.
I'm no expert with PC's (this is the most complicated stuff I've ever done with it!) and wanted to ask if anyone has any ideas on what else I can try so the PC can once again boot form its hard drive?
I'm only onsite to attempt repairs on the PC on Sunday, Monday and Tuesday nights, but welcome all suggestions at any stage to try when I get a chance. Thanks!
Jac
Just before Xmas a program crashed on my PC, it froze completely and had to turn the power off. When I turned it on again I got a small beep
(not the normal one) and a black screen with the message - "Disk boot failure. Insert system disk and press enter". There is no chance that this was a virus as I had earlier that day run checks with both Avast and Malwarebytes.
After weeks of trying to solve it using info on the 'net (including this forum) including using the Recovery Console (including using CHKDSC /p, CHKDSC /r fixmbr and others!) and a non-destructive reinstall of Windows, I've got to the stage where the drive will boot if I use a 'Paragon Rescue Kit 10' CD - this enables me to search for OSes on the hard drive and then boot from that OS - this works fine and boots into Windows as I left it, with all my files intact and seemingly working fine.
I don't really understand all the info that the Recovery Kit gives me, but some of what I think might be helpful is as follows -
The 'Find OS' screen finds 'Win 2K/XX/2003 "BOOT".'
Details = Hard Disk:0
Partition : Primary 00
File System NTFS
Paragon Boot Corrector finds - 1 Disk0, Partition0 - Windows XP
[boot loader]
timeout = 30
default = multi(0) disk(0) rdisk(0) partition(1)\WINDOWS
[operating systems]
multi(0) disk(0) partition(1)\WINDOWS="Microsoft Windows XP Home Edition"/fast detect
Boot Partition Record
Basic Hard Disk 0
Type Active File System Label Size
Primary No NTFS BOOT 93.2GB
Extended 83.4GB
Logical No NTFS Backup 83.4GB
Primary No NTFS Recover 9.8GB
(All options are greyed out)
I did find it odd that the Boot Corrector found Windows on Partition0 whereas the boot.ini states partition(1), so I did try editing that using the Boot Corrector (changing both incidences of 'partition(1) to 'partition(0)'), but it didn't work so I editied it back to what it said originally.
I'm no expert with PC's (this is the most complicated stuff I've ever done with it!) and wanted to ask if anyone has any ideas on what else I can try so the PC can once again boot form its hard drive?
I'm only onsite to attempt repairs on the PC on Sunday, Monday and Tuesday nights, but welcome all suggestions at any stage to try when I get a chance. Thanks!
Jac