[Coco] OS9Exec (OT?)

[Aaron Wolfe]

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
>