Re: Getting to NeXt Command prompt

2017-06-23 Thread Noel Chiappa via cctalk
> From: Eric Christopherson >> On Mon, Jun 19, 2017, william degnan via cctech wrote: >> [Command + ~] is a system reset. > Just out of curiosity: do you mean the shift key gets held down too? > If not, it would write it as Command + `. I found the syntax slightly confusing.

Re: Back To: Getting to NeXt Command prompt

2017-06-21 Thread Ian Finder via cctalk
Wow those threads make me cringe. Keyboard poachers are /really/ annoying. On Wed, Jun 21, 2017 at 6:19 PM, Chris Hanson via cctalk < cctalk@classiccmp.org> wrote: > It’s command-backquote, not quote. The backquote key is in the upper left > of the numeric keypad. > > Sorry for linking to a ke

Re: Getting to NeXt Command prompt

2017-06-21 Thread william degnan via cctalk
just replying here too just tried it and yes it's Command + ` (not ~ which would require the shift key). Bill On Tue, Jun 20, 2017 at 10:39 AM, Eric Christopherson via cctech < cct...@classiccmp.org> wrote: > On Tue, Jun 20, 2017 at 12:00 AM, william degnan > wrote: > > > > > On Jun 20, 2017

Re: Back To: Getting to NeXt Command prompt

2017-06-21 Thread Chris Hanson via cctalk
It’s command-backquote, not quote. The backquote key is in the upper left of the numeric keypad. Sorry for linking to a keyboard poaching site but it has a couple good images of the NeXT keyboards: https://deskthority.net/photos-f62/next-non-adb-keyboard-t12259.html

Re: Previous, was Re: Getting to NeXt Command prompt

2017-06-21 Thread Torfinn Ingolfsen via cctalk
On Wed, Jun 21, 2017 at 2:09 PM, william degnan via cctech wrote: > > What is a Previous? Never heard of one. An emulator, see http://previous.alternative-system.com/ HTH -- Regards, Torfinn Ingolfsen

Back To: Getting to NeXt Command prompt

2017-06-21 Thread william degnan via cctalk
Confirmed. It's Command + ' (not shift + Command + ~) "Command + The key with the tilde and the single quote in the number pad of a Next keyboard:" Bill

Re: Previous, was Re: Getting to NeXt Command prompt

2017-06-21 Thread william degnan via cctalk
> > > > I don't have a NeXT -- though I suppose I could set up Previous and try it > > there :) > > > > On that note...has anyone successfully networked multiple Previous > instances, or a Previous instance with a real NeXT? I briefly tried to get > Maze War running between my NeXTstation Turbo and

Previous, was Re: Getting to NeXt Command prompt

2017-06-20 Thread Kyle Owen via cctalk
On Tue, Jun 20, 2017 at 9:39 AM, Eric Christopherson via cctalk < cctalk@classiccmp.org> wrote: > > I don't have a NeXT -- though I suppose I could set up Previous and try it > there :) > On that note...has anyone successfully networked multiple Previous instances, or a Previous instance with a r

Re: Getting to NeXt Command prompt

2017-06-20 Thread Eric Christopherson via cctalk
On Tue, Jun 20, 2017 at 12:00 AM, william degnan wrote: > > On Jun 20, 2017 12:36 AM, "Eric Christopherson via cctech" < > cct...@classiccmp.org> wrote: > > > > On Mon, Jun 19, 2017, william degnan via cctech wrote: > > > [Command + ~] is a system reset. I noticed it takes a little longer to > >

Re: Getting to NeXt Command prompt

2017-06-20 Thread william degnan via cctalk
On Jun 20, 2017 12:36 AM, "Eric Christopherson via cctech" < cct...@classiccmp.org> wrote: > > On Mon, Jun 19, 2017, william degnan via cctech wrote: > > [Command + ~] is a system reset. I noticed it takes a little longer to > > Just out of curiosity: do you mean the shift key gets held down too?

Re: Getting to NeXt Command prompt

2017-06-19 Thread Eric Christopherson via cctalk
On Mon, Jun 19, 2017, william degnan via cctech wrote: > [Command + ~] is a system reset. I noticed it takes a little longer to Just out of curiosity: do you mean the shift key gets held down too? If not, it would write it as Command + `. > boot up from the command prompt that the regular GUI wa

Getting to NeXt Command prompt

2017-06-19 Thread william degnan via cctalk
I think it was here on this list there was a request for instructions on how to access the command prompt directly rather than jumping to the GUI upon boot. Was this ever answered? This past weekend I tested/documented how I was taught to do it: Just after you power up the system "testing system