Povl H. Pedersen (pope@netguide.dk)
Mon, 28 Sep 1998 08:28:26 +0200
>Regarding the floppy,
> I've been booting my installer.coff over the network using
>bootp. I've been getting the same CATCH errors, so I'd like to present that
>as evidence to rule out the floppy issue. I don't even have a floppy drive
>installed on my system.
SUMMARY: TRY RUNNING THE 2.1.24 INSTALLER.COFF TO THE POINT OF SELECTING
INSTALL/UPGRADE, THEN TRY A NEWER INSTALLER.
OK, here is my findings:
Doing everything on external disks, using the 2.1.24 installer.coff with no
ANS support works perfectly.
Trying to use the dusers kernel after a zapped PRAM can give me DEFAULT
CATH or CLAIM FAILED, depending on my settings of real-mode? and real-base.
Now, if I after a PRAM zap boots from the 2.1.24 installer, aborts when I
have to select install/upgrade, and then boots the dusers kernel, then I do
not get any of the above errors. So to me it seems like there is either
some hardware initializing, or part of the PRAM elsewhere that does not get
set up right.
When I tried the 2.1.121 kernel I had made myself, if would not handle my
internal SCSI controllers, as they were not initialized by PCI bios.
Neither was my NE2000 (RealTek) PCI network card.
So something in hardware initialization has changed since 2.1.24 !
What I want is a kernel that will allow me to install directly to the
internal SCSI drive, I have the Seagte drive ready for that.
I will take this task on myself, hopefully today.
PS: dusers needs to reconfigure their webserver to NOT send .coff files as
text/plain.
--- Povl H. Pedersen - Chief Technology Officer - NetGuide Scandinavia Phone: +45 8618 1845 Cellular: +45 4093 5511 Fax: +45 8618 1863 e-mail: mailto:pope@netguide.dk - PGP Key ID: 0x8F4BC755
This archive was generated by hypermail 2.0b3 on Thu Dec 10 1998 - 16:55:54 PST