kaz@cadovax.UUCP (Kerry Zimmerman) (11/03/87)
[] 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.
andy@cbmvax.UUCP (Andy Finkel) (11/04/87)
In article <1838@cadovax.UUCP> kaz@cadovax.UUCP (Kerry Zimmerman) writes: >[] > >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 >Kerry Zimmerman Fortunately, I'm a little ahead of you on this one :-) (Not far enough ahead to prevent it from happening at all, though :-( ) Anyway, this effect is caused by the hddisk.device initialization code. (which gets called via binddrivers). There are 2 ways around it. Once is to always let the initial CLI go away. :-( The other is for me to email you the latest&greatest harddisk.device. Open offer...if you've got the Commodore hard disk, and want the latest hddisk.device, send me email with a *working* uucp path between you and me (ARPA and BITNET people may have trouble with this; its been awhile since I've been able to send mail sucessfully to anyone on those networks) and I'll send you a uuencoded hddisk.device. Enclose the label from your box...err the cover of the instruction manual... um, how about promise you've got one ? (its also a sneaky way to find out how many NET people have Commodore hard disks.) BTW, if you don't have your hard disk yet (ie, its on back order) the harddisk.device you'll get is the latest one. (33.38) (Kerry, I'm mailing yours now...) andy -- andy finkel {ihnp4|seismo|allegra}!cbmvax!andy Commodore-Amiga, Inc. "Interfere? Of course we'll interfere. Always do what you're best at, I always say." Any expressed opinions are mine; but feel free to share. I disclaim all responsibilities, all shapes, all sizes, all colors.
kim@amdahl.amdahl.com (Kim DeVaughn) (11/05/87)
In article <2682@cbmvax.UUCP>, andy@cbmvax.UUCP (Andy Finkel) writes: > In article <1838@cadovax.UUCP> kaz@cadovax.UUCP (Kerry Zimmerman) writes: > > > >> I have encountered a problem with the hard disk device ... > > Open offer...if you've got the Commodore hard disk, and want the latest > hddisk.device, send me email with a *working* uucp path between you > and me ... This is really being supportive, Andy! Thank you (and your management for allowing it)!!! Alas, I still don't have one myself ... /kim -- UUCP: kim@amdahl.amdahl.com or: {sun,decwrl,hplabs,pyramid,ihnp4,uunet,oliveb,cbosgd,ames}!amdahl!kim DDD: 408-746-8462 USPS: Amdahl Corp. M/S 249, 1250 E. Arques Av, Sunnyvale, CA 94086 CIS: 76535,25