Johnglad to hear you got it up and running. However I'm not sure I
understand why you moved your entire linux installation area (free
space) instead of just creating a small /boot partition at the beginning
of your original free space?
I'm not so good at networking stuff yet, so maybe someone else can
answer that one.
Screen resolution problems just like yours have been covered in this
list many times before, have you scanned through the archives? I
suggest you go to console mode and run setup (as root) and do X
configuration. When it comes time to choose a resolution, pick only
one, then that resolution will fill the screen like you're used to in
windows.
I recommend Boot Magic, but by editing /etc/lilo.conf and changing the
order of the sections in it you can change the default boot system. But
since I've never done it (used Boot Magic instead) I am unable to go
into detail, someone else may chime in here.
Alan
"Karnos, John G" wrote:
Hi Alan!
Moved the whole install to the first partition and almost everything worked
great. It doesn't want to recognize my 3com 3905C E'net card, but worse,
Everything is so big I can't use it. There must be someway of adjusting
screen resolution while in the Xwindows (KDE) environment, but I haven't
figured it out yet. I have a 22 inch Mitsubishi monitor, but it's acting as
if I've got a 10FT screen in front of me.
Guess I'll keep at it later today.
BTW, can LILO be set to default boot to my Windows 98 OS? This is where, of
necessity, I've got to spend the majority of my time, and I really don't
want to get booted into Linux unless that's really what I want.
Thanks for your earlier response... it gave me the insight necessary to get
the program loaded, which was a huge step in the right direction.
-Original Message-
From: Alan Shoemaker [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 08, 1999 11:03 AM
To: Karnos, John G; newbie
Subject: Re: Linux Install problem
Alan Shoemaker wrote:
Johnyou probably have a removable media scsi device (like a cdrom)
and disk druid can't read it because theres no disk inserted. That's
ok, you don't want to partition it anyway, just tell disk druid (oops,
you said fdisk, why are you using that?) to skip it and you'll be able
to get on with your partitioning. Linux installs fine on scsi disks.
Alan
"Karnos, John G" wrote:
I have skipped it and still have the problem. I suspect, but won't
know until tonight, that I need to create the root partition (/) on my
first drive ( a 9Gb SCSI drive where I normally boot Windows98 from
(cough...gag...spit...) then put everything else into the 3rd
partition of my 2nd drive which I've already set aside for Linux. I do
use the DRUID app, but the Fdisk error comes up first. The master
device on my IDE bus is a CD-ROM, which would account for the error
message, just as you stated.
If you've got any words of wisdom on where I need to put the root
partition, please let me know. I'd love to forego the trial and error
part of this install.
Thanks for the help. I really do appreciate it. I'm very anxious to
get this up and running. By the way, I'm getting the impression that
LINUX doesn't support PS2 devices. Is that a correct statement?
Thanks again, Alan.
John G. (Jack) Karnos
(760) 939-8507
[EMAIL PROTECTED]
JohnI don't know how much wisdom I have, but I have sucessfully
installed several Linux distributions on my dual scsi drive system.
Basically I have scsi 0 dedicated to win98 and scsi 1 dedicated to
linux. I now use Boot Magic to control the multiple booting, but
originally I used lilo and you can too. Scsi 0 is identified by linux
as sda and scsi 1 as sdb. When referring to the partitions of the
drives sda1 is your windows drive c: (if you are using a multiple
partitions for windows there will be more).
The only location issue for the linux partitions is that your /boot
partition needs to be totally located within the first 1024 cylinders of
whatever drive that it is on, sda or sdb. I make my /boot partition
16-24 megs in size. Minimally you'll also need a swap partition 32-128
megs in size (depending on how much memory your system has and what
installation scenario you're following). Your / partition (the slash
identifies the root partition) can take up the rest of your available
drive space (or you can further divide up that space into / and other
partitions, again depending upon the installation scenario you are
following).
When it comes time in the installation to write lilo to disk (right
after you create your floppy boot disk, a very important item), you need
to tell it to install in the mbr of sda (lilo then becomes the boot
loader that controls your ability to boot the windows system or the
linux system). If you ever need to reinstall windows, the process will
overwrite lilo with the windows boot
