Re: Can't view recovery D: drive

Tech-Archive recommends: Fix windows errors by optimizing your registry


"Jamie Neve" <jamieneve@xxxxxxxxxx> wrote in message
news:E7A7901A-0F08-4395-9F24-DCFF4C6F78BB@xxxxxxxxxxxxxxxx
Is there a method to delete the backup partition? I know the risks, but to
save disk space.


You may not know ALL the risks. I'm not sure about the newer Compaqs, but a
few years someone gave me an old one and the first thing I did was format to
wipe the drive clean. After that I was unable to access or make changes to
the BIOS since that was on a hidden partition on the HD. I could view the
BIOS at Bootup, but couldn't make any changes. Thank goodness the machine
was a freebee


.

Relevant Pages

  • Re: XP SP2 and 137GB of my 300GB WD SATA Hard drive
    ... I thought that since SP1 supported 48-bit and XP doesn't use the BIOS once ... In Windows I can see the correct disk space of the hard drive. ...
    (microsoft.public.windowsxp.general)
  • Re: startup hangs
    ... F1 on Compaqs allows the system to continue past the POST. ... Pay very close attention to the BIOS messages. ... That message can indicate imminent hard disk failure. ... Otherwise, look at the boot settings in the BIOS, for any Pause On Error ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: 5.2 Floppy install
    ... Tanks for you info. ... it back to 48521/16/63 i was able to access the full disk space. ... I don't have a clue to the number in the BIOS, ...
    (freebsd-current)
  • Re: 30GB Hard Drive shows up as 12.1GB - Please Help!!
    ... GB of RAM. ... I was running out of disk space. ... BIOS shows it as a 30 GB HDD and all ... sector or MFT might be becoming un-reliable and you are possibly ...
    (microsoft.public.windowsxp.general)
  • Re: Rescuing an XP machine
    ... That, of course, is what I usually do, but Compaqs don't appear to like you ... There must be something in the BIOS which makes it difficult to ... use anything but their recovery discs. ... perfectly sound but this one was in a mess and so required recovery. ...
    (microsoft.public.windowsxp.customize)