On Tue, Apr 30, 2002 at 12:33:47PM +0200, Miroslav Mazurek wrote:
> I'm trying to install Potato (2.2r3) on PC with 386/387, 16MB, 2GB SCSI IBM, 
> Advansys SCSI, ATAPI CDROM and NE2000 compatibile.
> Does this make any sense? Would that configuration be usable for anything? 
> Any suggestions? I run SCO on such configuration years ago.

It should be usable, just watch what you install. I'm writing this on a
system that is a little newer (a P100 laptop) but also with 16M RAM, a
2GB harddrive, and a SCSI CDROM. This system is used (but a little slow)
for everything that I do. I merely have an average load average of about
1.5 - 3.0, with occasional spikes to ~7 (don't let this scare you... I'm
on a network that _requires_ java to use the internet, and I'm online
while compiling kernels, and in X, and doing homework with programs that
recommend a system with 2-3 times the processing power of mine, and
running a terminal off my serial port, and half a dozen other things at
the same time).

> Problem is:
> 
> I have Debian on CDROM but I can't boot from CDROM.
> I made rescue and root disc and 4 or 5 driver discs. (I also tried with 
> compact which have one driver disc - it should also support advansys 
> controller)
> After beginning of instalation I am ofered to load modules from disc, I 
> supply driver disc but inst. program says - cannot mount floppy.

I remember having some floppy problems when I installed debian a few
months ago. I also remember that each time there was a problem with a
floppy, it was a bad block or two that caused it. I know from experience
that it is somewhat difficult to mount a floppy when its first couple of
sectors are bad.

> After that I cannot do disk partitioning because advansys is not recognized.
> Any idea?

You can always try a more recent set of disks. Checking the
kernel-config for the 2.2r4 installation floppies, advansys is compiled
in. The current potato is 2.2r6

-- 
Seneca
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to