Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 GARFIELD 20/11/84; site garfield.UUCP
Path: utzoo!utcsri!utai!garfield!caveh
From: caveh@garfield.UUCP
Newsgroups: net.micro.6809
Subject: Re: Newdisk bugs?
Message-ID: <594@garfield.UUCP>
Date: Tue, 6-May-86 08:00:41 EDT
Article-I.D.: garfield.594
Posted: Tue May  6 08:00:41 1986
Date-Received: Wed, 7-May-86 03:36:15 EDT
References: <94@vaxb.calgary.UUCP> <1112@loral.UUCP>
Sender: paulc@garfield.UUCP
Reply-To: caveh@garfield.UUCP (Caveh Jalali)
Distribution: net.micro.6809
Organization: Memorial U. of Nfld. C.S. Dept., St. John's
Lines: 31
Keywords: shell, bug
Summary: 

In article <1112@loral.UUCP> dml@loral.UUCP (Dave Lewis) writes:

>  Did you net.micro.6809'ers know you can't boot from a write protected
>disk, under Version 2.00 anyway? Seems it won't chd to a directory it can't
>write to or something.

	What is this about write protected disks?!  If RS has managed to
	do this, it is a SEVERE blow to the phylosopy behind os9!
	Whatever happened to sweet ol' *ROMable* os9?!

	I don't have os9 2.0.0 yet due to a severe lack of interest on
	behalf of the local Radio Slack store, however, the problem
	you describe sounds like a problem that's been with us from the
	days of os9 1.0.0!
	The problem, if i recall correctly, was that the shell
	gave a silly mask to i$chdir.  It specified that it wanted write
	permission to the directory, thus not allowing a chdir to a
	directory for which you didn't have write permission.

	To fix this problem, either disassemble the shell, and change
	the permission the shell wants when it does the i$chdir, or
	use "debug" to find the i$chdir call in the shell and patch
	a 'lda  #$07' (or whatever the mask is) just preceding the
	i$chdir to not include the the write bit.

	If anyone is interested, I could find the location(s) and
	report back in a few days with a patch.


						Caveh Jalali
						caveh@garfield.UUCP