🚀 go-pugleaf

I did a clean install of 3.0 (Hyper3B) after reformatting my NeXTdimension's  
400M NeXT drive for 1024 byte blocks.

I have tried printing on three occasions, and the system panicked each time.   
Here are the relevant excerpts from /usr/adm/messages (note the large gap  
between the previous message and each panic, showing that nothing else was  
interacting):

- 1 -
Sep 28 08:49:26 sounds syslog: Workspace logged in
Sep 28 15:58:11 sounds mach: panic: (Cpu 0) No more room in kernel map
- 2 -
Sep 28 23:21:28 sounds mach: 	Disk Label: disk.1
Sep 28 23:21:28 sounds mach: 	Disk Capacity 1440 KB, Device Block 512 bytes
Sep 28 23:58:09 sounds mach: panic: (Cpu 0) No more room in kernel map
- 3 -
Sep 29 09:33:41 sounds WindowServer[192]: IPCFlushOutput: failed to flush  
output for stream 0x211524.
Sep 29 09:39:05 sounds mach: panic: (Cpu 0) No more room in kernel map

The first time I printing from NewsGrazer, the second from 3.0's Edit, and the  
third from 2.1's WriteNow.

I have 28MB System and 20M dimension memory and I am running UUCP with  
Mamakos's SLIP.

I just got the Printer Test page to print today after using PrintManager.app  
for the first time since I loaded 3.0 - I'll give printing another trial run,  
but I wanted to get this post out before I take a chance on panicking my  
machine again.
-- 
Brian Willoughby	Software Design Engineer, BSEE NCSU
BrianW@SoundS.WA.com	Sound Signal Processing Software and Consulting
NeXTmail welcome	- NO EMAIL SOLICITATION without prior permission