FWIW, it's a SATA disk. I've downloaded the repair CD image from Lenovo and can boot from it. However, it complains about an error using RAM disk. It crashes whenever I try FDISK32. I wonder if the CD image is bad, so I'm going to try a fresh one. TIA for any additional suggestions. <div>On 2/27/07, Simon Ruiz <<a href="mailto:sruiz@mccsc.edu">sruiz@mccsc.edu</a>> wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> You can find photos of the different connector types below: <a href="http://en.wikipedia.org/wiki/AT_Attachment">http://en.wikipedia.org/wiki/AT_Attachment</a> - IDE <a href="http://en.wikipedia.org/wiki/SATA">http://en.wikipedia.org/wiki/SATA </a> If the Windows CD's fdisk can see the hard disk, though, it shouldn't be a driver problem. I haven't the slightest clue why the Installer wouldn't be able to see something Microsoft's fdisk can see... Is there perhaps some form of "factory formatting" option in fdisk? I dunno, I'm grasping at straws here... Simón ________________________________ From: Michael Steigerwald [mailto: <a href="mailto:mikesteigerwald@gmail.com">mikesteigerwald@gmail.com</a>] Sent: Tue 2/27/2007 3:01 PM To: Simon Ruiz Subject: Re: edubuntu-users Digest, Vol 9, Issue 20 Thanks for the complement. I assume it's IDE, but I don't really know how to tell. The fdisk I'm referring to is what I run from the installer command shell I get into from the Rescue a Broken System startup option. </blockquote> </div> -- Michael Steigerwald 4041 12th Ave S. Minneapolis, MN 55407-3239 <a href="mailto:Steiger@UMich.edu">Steiger@UMich.edu</a> 651.261.2098