Are you sure it is a problem with Disk Druid and not the BIOS or drive jumpering? Does the BIOS recognize the drive as (approximately) 10 gB? During kernel boot, does the kernel report the drive as 10 gB capacity? If you try to partition with fdisk or cfdisk, what does the "print the partition table" display tell you about partitions and capacity? These programs are not as convenient as DD, but they are somewhat more informative. What prompts me to ask these questions is that you say the CPU is a "233 mmx". THat suggests to me possibly an old mobo with an old BIOS, perhaps one that has trouble with drives over 8 gB. Some >8gB drives have jumper settings that cause them to look like 8 gB drives, just to accommodate these old BIOSes. At 09:52 PM 7/12/00 +0100, Jill wrote: >Hi all. > >I have a problem with disk druid, that I cannot find a solution for. > >What i am trying to do is run a Linux print server on a network of 10 >machines. Using a 233 mmx with 2.5 gigs of fixed drive ( linux) and windoze >7 gig dual booting using RH 6.2 and KDE. The drive is fully functional with >no bad sectors, and had a write test performed on it. > >Problems that I have are even though I delete all partitions and create new >swap space and native . I get the error, cannot create as not enough room on >the drive. I have even tried just asking for 1 gig native and 100 swap and >still get the same message. I am ensuring that I do this on the correct >drive. > >I think I am missing something here as on my machine at home I could install >the two with a 100 meg swap and the 2.9 gig as native -- ------------------------------------"Never tell me the odds!"--- Ray Olszewski -- Han Solo Palo Alto, CA [EMAIL PROTECTED] ---------------------------------------------------------------- - To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.linux-learn.org/faqs
