Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Imaged Drive no Longer boots - Blinking cursor only


  • Please log in to reply

#1
ClickRight

ClickRight

    Member

  • Member
  • PipPipPip
  • 109 posts
I've got a system here that had a bad hard drive (WD 40GB.) I imaged the drive to a brand new 80GB IDE hard drive. When I put the new drive in the machine, a Compaq Presario S4000NX, the BIOS POST completes, then all I get is a blinking cursor.

I put the new drive in one of my test machines, and it started booting up XP just fine, so I know there is nothing wrong with the MBR, etc. I slaved the drive and ran chkdsk, which was also just fine. I've been googling around and there are thousands of accounts of this blinking cursor syndrome, but no definite answer (and no situation that seems to be exactly like mine.)

I've reset the BIOS to defaults, removed all extra Drives (CD and Floppy) and I still get the blinking cursor. ANY ideas would be greatly appreciated. I need this fixed for tomorrow, the client wants their computer back.
  • 0

Advertisements


#2
anzenketh

anzenketh

    BSOD Warrior/Computer Surgeon

  • Technician
  • 2,854 posts
Hello Clickright,

Have you tried putting in a Hard Drive that you know works and boots into the system that is not working?
Have you Replaced the Cables?

A blinking Cursor usually means that the system attempts to boot but is unable too.

Try clearing Clearing your CMOS Settings by using the Jumpers on the Mainboard.
  • 0

#3
ClickRight

ClickRight

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 109 posts
Thanks tuxmaster, but I *JUST* figured it out. I hope this information is helpful to anybody else in a similar predicament!

It's really simple: The machine the drive was originally in had LBA disabled in the BIOS, and the computer I did the imaging on had LBA enabled in the BIOS. Simply enabling LBA on the original machine solved the problem! :)
  • 0

#4
anzenketh

anzenketh

    BSOD Warrior/Computer Surgeon

  • Technician
  • 2,854 posts
That is good that you could figure out the solution.

Yes that would create a no boot scenario.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP