Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!hplabs!sdcrdcf!trwrb!cadovax!kaz
From: kaz@cadovax.UUCP (Kerry Zimmerman)
Newsgroups: comp.sys.amiga
Subject: shell problem with A2000
Message-ID: <1835@cadovax.UUCP>
Date: Mon, 2-Nov-87 18:30:13 EST
Article-I.D.: cadovax.1835
Posted: Mon Nov  2 18:30:13 1987
Date-Received: Fri, 6-Nov-87 23:56:06 EST
Reply-To: kaz@cadovax.UUCP (Kerry Zimmerman)
Organization: Contel Business Systems, Torrance, CA
Lines: 46
Keywords: shell cli A2000 raw hard disk

[]

This weekend I upgraded to an A2000.  I went whole hog and got
an extra two megs of memory, a 20 Meg hard disk and the bridge card.
I don't know if the problem I am about to describe is because of the
A2000 or not.

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.

If I call the shell from a NEWCLI window, then everything works fine.
It only fails if started in the original AmigaDos window.

After much experimentation, I determined that the shell won't work in
the initial CLI window anytime after the call to binddrivers.  A shell
started before binddrivers will work, but after I call binddrivers,
even a working shell stops working.

Further, it appears that the device causing the trouble is the hard disk
device.  If I only bind the Janus device, the shell operates correctly.
But, if the hard disk device is in the expansion drawer, binddrivers will
render the shell inoperable.

The last experiment I performed was to recompile the shell with
RAW_CONSOLE 0.  This means the shell will not allow command line editing
or the help button or the function keys to work.  In this configuration,
the shell does work.  So, there is something about setting raw mode in the
initial CLI window that doesn't work with the hard disk device.

If anyone knows how I can solve this problem please tell me.  I should
be able to start the shell from the startup-sequence, but because of this
problem, I am forced to open a newcli window and start the shell from
there.  It is very frustrating that my new A2000 computer is acting somewhat
incompatable with the A1000.

Any help would be appreciated.  Thank You.

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.