Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!sharkey!atanasoff!deimos!ksuvax1.cis.ksu.edu!tar
From: tar@ksuvax1.cis.ksu.edu (Tim Ramsey)
Newsgroups: comp.unix.wizards
Subject: Re: Problem reconfiguring SysV Rel 2.1.2 kernel on an ATT 3B15
Summary: Eureka!
Message-ID: <757@deimos.cis.ksu.edu>
Date: 11 Feb 89 22:13:45 GMT
References: <722@deimos.cis.ksu.edu> <207@rdahp.UUCP>
Sender: news@deimos.cis.ksu.edu
Reply-To: tar@ksuvax1.cis.ksu.edu (Tim Ramsey)
Organization: Kansas State University, Dept of Computing & Information Sciences
Lines: 31

In article <722@deimos.cis.ksu.edu> I wrote:

>I'm a little confused.  All I wanted to do was increase the number of process
>table entries on my system.  This is what I did:

[ ... ]

In article <207@rdahp.UUCP> scott@rdahp.UUCP (Scott Hammond) writes:

>I cannot speak for the warnings you received after this point, but about
>the networking driver, I believe your mistake is right here.  The
>problem with the WIN3b1.1 driver is not related to the parameters you
>changed.  Rather, certain driver initialization does not take place (or
>not correctly) if you rebuild UNIX from multi-user mode.  You must do
>the mkboot in single user mode in order to get the WIN3b driver to work
>correctly.

Bingo.  Thanks to Scott and the others who pointed this out by mail.
Remaking the kernel (mkunix -o /unix, *not* mkboot -o /unix -- silly
fingers) in single user mode seems to have solved everything.  No error
messages about timestamps, and the WIN/3B drivers are working fine.

I dunno what the cause is, but remaking the kernel in multi-user mode
doesn't seem to work.

Tim
--
Timothy Ramsey
BITNET: tar@KSUVAX1
Internet: tar@ksuvax1.cis.ksu.edu
UUCP: ...!rutgers!ksuvax1!tar