This can also be caused by having the wrong settings for CHS, or if there is HD management software on the HD, seagate and connor drives had one that could make the HD bigger than what could be read by some of the fdisk programs.. ----- Original Message ----- From: "Kyle Carter" <kylecarter(a)xtra.co.nz> To: <wlug(a)list.waikato.ac.nz> Sent: Sunday, December 09, 2001 7:41 PM Subject: Re: [wlug] silly laptops

----- Original Message ----- From: "Greig McGill" <greig(a)win.co.nz> To: <wlug(a)list.waikato.ac.nz> Sent: Sunday, December 09, 2001 6:30 PM Subject: Re: [wlug] silly laptops

...

...

looks like its written.. however reboot it or continue on.. and the

...

...

partitions are still there... real strange..

no useful options in the bios for virus MBR protection etc..

any ideas?

Had this problem twice before. Once was a dead controller - hope that's not it! The second was just a screwy partition table - low-level format fixed it.

Ive tried 2 hard drives, 2 laptops (i got given 2 ;-) ) both are identical.. but i have changed the ram to give 1 8MB ram, and the other 16 MB ram

however i get the same error.. have enough ram in there to do it.. im wondering if its something to do with the hard drive controller. or the bios..

im just rawriting the parted disk.. im pretty sure once i get the

old partitions

set up the thing will work fine.

------------ WLUG - The Waikato Linux Users Group WWW: http://wlug.linuxcare.co.nz To unsubscribe, send an email to majordomo(a)list.waikato.ac.nz with "unsubscribe wlug" in the body of the message.

------------ WLUG - The Waikato Linux Users Group WWW: http://wlug.linuxcare.co.nz To unsubscribe, send an email to majordomo(a)list.waikato.ac.nz with "unsubscribe wlug" in the body of the message.