[Coco] SysCall source listing (and OS-9 source code find)

[Wayne Campbell]

I downloaded the Full Kit version, and ran the Setup.exe that it contained.
It installed the emulator, but the emulator won't run any emulation for
OS-9. It reports an error trying to read the rom image. Looking in it's rom
images folder, there is no rom image for OS-9, but there is one rom image
for unibug, named UNIBUG.BIN, and another one named UOS_35_UNIFLEX.BIN.
There are many other files in this folder, but none with a .rom extension.
I tried putting a copy of the coco.rom image from MESS, but apparently this
emulator does not know how to identify the rom.

Wimgtool (from MESS) and EmuDisk both report unknown format errors, so I
have no way to look at the DSK images that came with this emulator.

Wayne



On Thu, Nov 28, 2013 at 4:39 PM, Wayne Campbell <asa.rand at gmail.com> wrote:

> I am downloading the archive as I type this. I will be looking more
> closely at it soon, but it's already getting too dark in here, so it's
> almost time for me to go.
>
> Happy Thanksgiving, everybody. :)
>
> Wayne
>
>
>
> On Thu, Nov 28, 2013 at 6:27 AM, Joel Ewy <jcewy at swbell.net> wrote:
>
>> On 11/27/2013 11:49 PM, Joel Ewy wrote:
>>
>>> On 11/27/2013 10:07 PM, Wayne Campbell wrote:
>>>
>>>> Please do that, Joel. It will help to answer the question.
>>>>
>>> Here's what I've found.  I took another look at all the OS-9 disks that
>>> come with the SWTPC emulator using Toolshed and found no instance of
>>> SysCall, nor did I see a mention of it in a PDF of a Microware BASIC09
>>> manual from 1984 that was supposed to have come with a GIMIX computer.
>>>
>>> I did find among the SWTPC emulator disk images some interesting files
>>> that appear to be commented original Microware source code for os9p1,
>>> os9p2, sysgo, Clock, and several utilities.  If you want to take a look at
>>> this, it is in SJT002.DSK, which can be found here:http://www.evenson-
>>> consulting.com/swtpc/Downloads.htm in the "Full Kit".  It is a Windows
>>> executable that will extract and install under Wine.  I think I've had it
>>> running under Wine before, but I have since upgraded to Xubuntu 13.10
>>> (can't stand Unity Desktop) and need to do something (possibly install .net
>>> or Mono or something) to get the emulator to run.
>>>
>>> JCE
>>>
>>>
>>>  ...
>> Here's a note included with the OS-9 source files:
>>                         OS-9 SOURCE FILE INFORMATION
>>
>>
>>       Description of the source
>>
>>        1 - The "Kernal" is composed of two parts.  OS9P1 is the source
>>       for the "P1" ROM which goes at $F800.  OS9P2 contains the rest of
>>       the  OS-9 Kernal and the INIT module.  The OS9P2 and INIT modules
>>       go in the  "P2" ROM along  with the BOOT module.   You will find
>>       source  to a BOOT module for either the specified disk controller
>>       or a representative sample.
>>
>>
>>        2 - There are three device  drivers  included.   "Acia"  is the
>>       MC6850  acia  device  driver.  "Pia" is the MC6821(20) pia device
>>       driver.  The Acia and Pia drivers are "SCF" (sequential character
>>       file)  type device drivers.   Then there is a DRVR  (disk driver)
>>       for either the specified  controller or a representative sample.
>>       The disk  driver  is an "RBF" (random  block  file ) type device
>>       driver.
>>
>>
>>        3 - There are several device descriptors included.  "Term", "T1"
>>       and "P1"  are acia type device descriptors. The first two are for
>>       terminals and  the other is for a serial  printer.   "P" is a pia
>>       type device  descriptor for a parallel printer.
>>
>>
>>        4 - The "Shell" is source for the  "command  interpreter". Our
>>       experience  has  shown  that  changes  to  shell  can often cause
>>       seemingly  unrelated  problems  which  are really shell problems.
>>       Therefore be careful if you modify this source.
>>
>>
>>        5  -  The "Sysdefs.sys" file is  used to define  the particular
>>       system for which this source was created.   It should be moved to
>>       your DEFS  directory.   It is used by many of the source files to
>>       define changeable configurations for different systems. It is the
>>       user's  responsibility to check  that the  sysdefs match  what is
>>       currently  needed for his  system and make any  required changes.
>>       The  defsfile is a convenient file for "using" all the different
>>       OS-9 definitions files.
>>
>>
>>        6  -  In  addition  there  is an assortment of example utilities
>>       which will give you a good look at how to use  OS-9  in assembly
>>       language  programs.  Comments on several of these: You may notice
>>       a similarity  between Copy, List, and Merge.  This is a result of
>>       OS-9's  unified I/O  handling.   Note  that  SYSGO is the system
>>       starter  module which sets  up the default  directories and keeps
>>       the system  going even if shell "dies".   Details on SYSGO can be
>>       found in the System Programmers Manual.
>>
>>
>>        7  -  NOTE:  Not all of the utilities are included in the source
>>       package.  The intent in sending out any of them is to guide users
>>       into good programming techniques.   Those sent are representative
>>       of the utilities done by Microware.
>>
>>
>>           (C) 1980 Microware Systems Corporation and Motorola Inc.
>>
>> Anybody here ever seen this before?
>>
>> JCE
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>
>
>
> --
> The Structure of I-Code
> http://www.cocopedia.com/wiki/index.php/The_Structure_of_I-Code
>
> decode
> http://cococoding.com/wayne/
>



-- 
The Structure of I-Code
http://www.cocopedia.com/wiki/index.php/The_Structure_of_I-Code

decode
http://cococoding.com/wayne/