Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!labrea!rutgers!ll-xn!oberon!sdcrdcf!trwrb!cadovax!kaz
From: kaz@cadovax.UUCP (Kerry Zimmerman)
Newsgroups: comp.sys.amiga
Subject: problem with shell, hd.device and initial CLI
Message-ID: <1838@cadovax.UUCP>
Date: Tue, 3-Nov-87 15:38:27 EST
Article-I.D.: cadovax.1838
Posted: Tue Nov  3 15:38:27 1987
Date-Received: Sat, 7-Nov-87 09:51:34 EST
Reply-To: kaz@cadovax.UUCP (Kerry Zimmerman)
Organization: Contel Business Systems, Torrance, CA
Lines: 31
Keywords: shell CLI hd.device A2000

[]

This is a followup to the problem I described yesterday:

> I have encountered a problem with the hard disk device, the initial
> AmigaDos CLI and Matt/Drew's shell (both versions 2.06M and 2.07M).  If
> I end my startup-sequence, as I have always done on my A1000, with a
> call to shell, the shell starts, I get the $ prompt, but I cannot get
> the shell to accept my keystrokes.  The system is not hung, because the
> characters I type are echoed and the mouse is alive, but the shell
> process is effectivly hung and won't do anything but echo.
> 

I did more investigation last night.  I found that the shell is not hung,
it is waiting for a cursor report from the console device.  It is supposed
to get a report in the form <CSI>row;colR, and waits until it receives
the 'R' before continuing.  Well, the report never comes.  Why?  Because
the initial CLI will NOT go into raw mode, as it should, from Manx's
set_raw() routine.

So, why is the initial CLI unable to to switch to RAW mode after
binding the hd.device?  A NEWCLI does not have this problem.

I thought the A1000 and A2000 had the same OS.  Do they?

Thanks for any responses.

Kerry Zimmerman
#  {ucbvax,decvax}!trwrb!cadovax!kaz  Contel Business Systems 213-323-8170
A difference between an amateur and a professional, 
is that a professional has the right tools.