[Coco] OS9Exec (OT?)

[Bob Devries]

hmm, curious.....

I copied what you did (also using my USB drive), and lo and behold, it works 
that way.

However, although I now have the $ prompt, if I type 'dir', I get an error 
"can't install trap handler cio", and the dreaded error 216 again. I was 
able to solve that by finding a copy of cio, and putting that in the CMDS 
dir.

Not all my problems have gone away yet, however.

If I type 'dir', I get the complaint :

dir: can't open ".". Error #000:216 (E_PNNF) Path name not found. Evidently 
more is required.

Typing 'mdir' works, though.

If you find more clues, please let me know, and I'll keep pounding away at 
it too.

Regards, Bob Devries

--
Besides a mathematical inclination, an exceptionally good mastery of one's 
native tongue is the most vital asset of a competent programmer.

Edsger W.Dijkstra, 18 June 1975

----- Original Message ----- 
From: "Aaron Wolfe" <aawolfe at gmail.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Wednesday, February 10, 2010 1:53 PM
Subject: Re: [Coco] OS9Exec (OT?)


This seems like the same thing I did..  I have a directory on drive E:
called "os9".  In it I put the os9app.exe.  I also created a directory
in "E:\os9" called "cmds".   In this directory I put the 'sh' shell
from rtsi's os9-68k archive.  so there is a file "E:\os9\cmds\sh"
which is an os9-68k executable.

I type:

cd e:\os9
set OS9CMDS=cmds
os9app.exe sh

and it runs the sh shell.
not sure if things are case sensitive, might be something to check.
also note that there is no path specified for sh on the os9app.exe
command line, just "sh".
-Aaron


On Tue, Feb 9, 2010 at 9:37 PM, Bob Devries <devries.bob at gmail.com> wrote:
> Hi Aaron,
>
> I don't seem to be able to get past the error 216.
>
> I typed SET OS9CMDS=CMDS
>
> My current directory is the one where the CMDS directory is. All the OS9 
> 68k
> binaries are in that CMDS directory (from an MM/1 distribution disk).
>
> I don't have a disk image to try either (at least not here with me; I'm in
> the wrong hemisphere now).
>
> Regards, Bob Devries
>
>
> --
> Besides a mathematical inclination, an exceptionally good mastery of one's
> native tongue is the most vital asset of a competent programmer.
>
> Edsger W.Dijkstra, 18 June 1975
>
> ----- Original Message ----- From: "Aaron Wolfe" <aawolfe at gmail.com>
> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
> Sent: Wednesday, February 10, 2010 1:02 PM
> Subject: Re: [Coco] OS9Exec (OT?)
>
>
>> I just tried it out, pretty interesting. Is there an easy way to get
>> an image of a working os9-68k system? (without having such a system
>> :)
>>
>> I was able to run a couple of the shells from rtsi. without any
>> commands and missing most directories, its not much fun but certainly
>> works. with a proper system it could be very nice.
>>
>> It seems you must set the environment variable "OS9CMDS" to the place
>> you have your shell or other application. This allowed me to get past
>> the216 and actually run some shells.
>> Still a long way from a working system, but I'm going to play some more.
>>
>> On Windows at least, and in my very limited testing, the path set in
>> the environment variable also needs to be relative to the location of
>> "os9app.exe", doesn't seem to want to parse drive letters at all,
>> probably because its more of a unix/mac thing. for instance I have
>> os9app.exe in E:\os9. setting OS9CMDS to E:\cmds did not work,
>> setting it to E:\os9\cmds did not work, but setting it to just "cmds"
>> does work fine. (combined with putting the binaries in a directory
>> called cmds under the place os9app.exe lives).
>>
>> hope that helps
>>
>> -Aaron
>>
>>
>> On Tue, Feb 9, 2010 at 8:22 PM, Bob Devries <devries.bob at gmail.com> 
>> wrote:
>>>
>>> Hi all,
>>>
>>> Does anyone here have experience using the OS9Exec programme for
>>> Windows/Mac/Linux?
>>>
>>> For those who have not heard of it, it's an OS9/68000 emulator based on
>>> the
>>> core from UAE (Unix Amiga Emulator).
>>>
>>> I have it installed, but it only returns ERROR 216. Even if I tell it 
>>> the
>>> path to the shell, it gives that error. Sadly, the documentation is
>>> rather
>>> sparse. There are some html files in the CVS, but nothing very
>>> definitive.
>>>
>>> Regards, Bob Devries
>>>
>>> --
>>> Besides a mathematical inclination, an exceptionally good mastery of
>>> one's
>>> native tongue is the most vital asset of a competent programmer.
>>>
>>> Edsger W.Dijkstra, 18 June 1975
>>>
>>>
>>> --
>>> Coco mailing list
>>> Coco at maltedmedia.com
>>> http://five.pairlist.net/mailman/listinfo/coco
>>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>

--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco