Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uunet!brunix!rca
From: rca@cs.brown.edu (Ronald C.F. Antony)
Newsgroups: comp.sys.next
Subject: Re: Problems with 2.0
Keywords: 2.0 NextStep problems
Message-ID: <60002@brunix.UUCP>
Date: 19 Dec 90 21:20:44 GMT
References: <2919@ux.acs.umn.edu>
Sender: news@brunix.UUCP
Reply-To: rca@cs.brown.edu (Ronald C.F. Antony)
Organization: Brown University Department of Computer Science
Lines: 45

In article <2919@ux.acs.umn.edu> m9tardiv@cs.stthomas.edu (Max Tardiveau) writes:
>
>I just installed 2.0 and I am having tons of problems.
>What I don't understand is that everyone else in this newsgroup
>seems to be OK, so I guess there is something wrong with me.

You are not the only one, but at the moment I'm busy to collect all
the bugs in a list to send it to NeXT. This is more helpful than to
bitch about the new release. It is easy to see that many things,
especially most of the apps in /NextDeveloper/Demos/ are so fragile
that they can't be used at all for anything reasonable. Obviously NeXT
was busy enough debugging the OS so that there was no time left to
debug the goodies. I hope that we soon get a release 2.1 (2.0a won't
do it this time...) However as I need to use 2.0 (got my '040) I
rather shut up and isolate the bugs as good as possible.

>Problems :
>[...]
>When I log out, I have to kill the window server to log back in.
>In other words, if I log out, and then try to log in, the login window
>goes away when I type Return after the password, but comes back after
>a couple seconds. So I have to log in as 'exit' (i.e. kill the window
>server), and only then can I log in.

If you have Motd.app installed as a login hook, deinstall it. It does
provoke the efffects you mention. Is there a new version in the works,BTY?

>I can't print anymore ! I have a Sun set up as a print server. It is
>used by the whole network, and is working fine for everyone, and was
>working fine for the Next until I installed 2.0, but now the print
>jobs get partially transmitted and then get lost.

There is a known problem with remote non-next printers. There was a
posting about it a while ago. I have no solution.

>LockScreen is now useless, since the title bar of the big window used to
>cover the screen is visible.
Well, I thought that binary compatible meant that but there must be
some changes in how screen coordinates are interpreted.

Ronald
------------------------------------------------------------------------------
"The reasonable man adapts himself to the world; the unreasonable one persists
in trying to adapt the world to himself. Therefore all progress depends on the
unreasonable man."   G.B. Shaw   |  rca@cs.brown.edu or antony@browncog.bitnet