Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!samsung!munnari.oz.au!bruce!goanna!minyos!s892024
From: s892024@minyos.xx.rmit.oz (Richard Muirden)
Newsgroups: comp.unix.xenix
Subject: Re: Problems with SCO Unix 3.2.0
Summary: "w" also gave [me] an error under Xenix 2.3.2!
Message-ID: <4664@minyos.xx.rmit.oz>
Date: 8 Jun 90 08:25:59 GMT
References: <11414@yunexus.UUCP> <300007@hpspcoi.HP.COM>
Organization: RMIT Computer Centre, Melbourne Australia.
Lines: 10

In article <300007@hpspcoi.HP.COM>, darko@hpspcoi.HP.COM (David Arko) writes:
> 
> Yes, It does seem that SCO Unix 3.2.0 has a bug with 'w' and 'uptime'.
> Maybe it will be fixed in 3.2.2

And under Xenix 286 2.3.2 "w" used to give me a seek error but uptime
worked just fine. I have yet to test this under the new version of
Xenix I have for the 386 (2.3.2).

-Richard