home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.next.misc
- Path: sparky!uunet!europa.asd.contel.com!emory!swrinde!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!destroyer!cs.ubc.ca!unixg.ubc.ca!kakwa.ucs.ualberta.ca!news
- From: adrian@niagara.ucs.ualberta.ca (Adrian Smith)
- Subject: Re: X11R5: how to switch to NeXTStep
- Message-ID: <1992Dec18.002724.26899@kakwa.ucs.ualberta.ca>
- Sender: news@kakwa.ucs.ualberta.ca
- Nntp-Posting-Host: niagara.ucs.ualberta.ca
- Reply-To: adrian@niagara.ucs.ualberta.ca
- Organization: University Of Alberta, Edmonton Canada
- References: <1goeckINN25s@pith.uoregon.edu>
- Date: Fri, 18 Dec 1992 00:27:24 GMT
- Lines: 27
-
- In article <1goeckINN25s@pith.uoregon.edu> jfosback@darmok.uoregon.edu (Jason
- Fosback) writes:
-
- > No! Cmd-cmd-* will bootstrap your CPU, and cause your system to reboot!
- > DO NOT DO THIS. The original Mouse X used cmd-cmd-backspace (the rubout
- > key above the return key).
- >
-
- Hmmm. That's interesting. Cmd-Cmd-* (remember, it's the * on the keypad) makes my
- system beep at me (the "error" beep). Cmd-Cmd-* on the old Mouse-X, on the other
- hand, makes X switch back to NeXTSTEP 2.1.
-
- Perhaps your Mouse-X binaries were compiled with different hot keys than mine?
-
- The hardware reset on a NeXT is Cmd-Alt *.
-
- Or perhaps you type with different fingers than the rest of us?
-
- I don't intend to flame, but it's been a *very* long day, and it's nowhere over
- yet...
-
- Adrian Smith
-
- ---
- University of Alberta NeXT Campus Consultant
- adrian@niagara.ucs.ualberta.ca
- Audix: 5482
-