Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!ucla-cs!sdcrdcf!trwrb!scgvaxd!wlbr!wlbreng1!pete From: pete@wlbreng1.UUCP Newsgroups: comp.sys.m6809 Subject: Re: OS9 Level II Message-ID: <186@wlbreng1.UUCP> Date: Mon, 30-Mar-87 19:00:15 EST Article-I.D.: wlbreng1.186 Posted: Mon Mar 30 19:00:15 1987 Date-Received: Thu, 2-Apr-87 08:08:08 EST References: <1987Mar27.123438.23604@gpu.utcs.toronto.edu> Reply-To: pete@wlbreng1.UUCP (0000-Pete Lyall) Organization: Eaton Inc. IMSD, Westlake Village, CA Lines: 34 In article <1987Mar27.123438.23604@gpu.utcs.toronto.edu> ac@gpu.utcs.toronto.edu (Mark Acfield) writes: > > > I have run into another problem with OS9 Level II for the COCO. The >system crashes whenever I try to use CHD. At first I though any use of >CHD would cause it to die but now it seems that CHD works as long as the >disk is not write protected i.e. no write protect tab. It seems odd to me >that CHD would even know if the disk was write protected. Does this imply >that CHD writes on the disk or is it possible for the software to know if >a disk is write protected without writing on it. In any case, why should >the system crash if it is? .... [text deleted] CHD will attempt to update the last modified date of the directory that you CHD to. If it fails (i.e. for reasons of write protect, or possibly attributes), it *should* give up gracefully. > One other oddity. Issuing EX from the lowest level shell hangs the >system. On level I, I thought SYSGO would restart things. On coco3 there is no 'sysgo'. The CC3Go is the startup job, and it does not respawn shells if I recall. I believe this was partially the reason for adding the 'i' option ('i'mmortal) in the new Shell. -- Pete Lyall Usenet: {trwrb, scgvaxd, ihnp4, voder, vortex}!wlbr!pete !wlbreng1!pete !wlpx!pwl Compuserve: 76703,4230 (OS9 SIG Sysop) OS9 (home): (805)-985-0632 (24hr./1200 baud) Phone: (818)-706-5693 (work 9-5 PST) ----------------------------------------------------------------------