On Thu, 27 Mar 1997, Mike Long wrote:

> Date: Thu, 27 Mar 97 13:06:40 EST
> From: Mike Long <mike.long@analog.com>
> To: gevans@televar.com
> Cc: port-i386@netbsd.org, shrike@televar.com
> Subject: Re: Results of startx >& startx.log
> 
> 
> >Date: Thu, 27 Mar 1997 09:10:10 -0800 (PST)
> >From: "G. Evans" <gevans@televar.com>
> 
> >XFree86 Version 3.1.1 / X Window System
> >(protocol Version 11, revision 0, vendor release 6000)
> >Operating System: NetBSD 1.0 
> 
> You should update NetBSD to at least 1.2, and XFree86 to 3.2.  Many,
> many bugs have been fixed since those two were released.

Interestingly enough, upon system boot, it tells me that I am using:
 
NetBSD 1.2 (INSTOTHER), etc.

> 
> >Configured drivers:
> >  VGA16: server for 4-bit colour VGA (Patchlevel 0):
> >      et4000, et4000w32, et4000w32i, et4000w32p, ncr77c22, ncr77c22e,
> >      vgawonder, tvga8800cs, tvga8900b, tvga8900c, tvga8900cl, tvga9000,
> >      oti067, oti077, oti087, cl6410, cl6412, cl6420, cl6440, generic
> 
> >Mach64 detected but VGA Wonder capability cannot be enabled.
> 
> You should use the Mach64 server instead of the VGA16 server; a Mach64
> server exists in XFree86 3.2.


> 
> >MIT-SHM extension disabled due to lack of kernel support
> 
> You should add "options SYSVSHM" to your kernel config, then re-config
> and rebuild your kernel.  You will also need to either add "options
> INSECURE" or use the XFree86 aperture driver LKM.

If I am alreadyt using 1.2 as it showed above at boot time. will I need to
do this step??  (Cuase I have no idea how to reconfig and rebuild the
kernel..hey I'm a newbie)

> 
> >(**) Mouse: type: Microsoft, device: /dev/mouse, baudrate: 1200,
> >       3 button emulation
> 
> >Fatal server error:
> >Cannot open mouse (No such file or directory)
> 
> You gave XFree86 the wrong device name for your mouse.  If you have a
> serial mouse, the mouse device will be one of /dev/tty0[0-3]; if you
> have a PS/2 mouse it will be /dev/pms0, and if it's a Logitech or
> Microsoft bus mouse it will be /dev/lms0 or /dev/mms0 respectively.
> If the appropriate device node doesn't exist in /dev, use /dev/MAKEDEV
> to create it.

This I can fix....

Thanks again for the help.

-Greg