[Coco] OS-9 Level1 Version 02.00.00 FYI

Gene Heskett gheskett at shentel.net
Fri Apr 17 06:38:08 EDT 2020


On Friday 17 April 2020 04:07:45 Bill Pierce via Coco wrote:

> Walter, if that was true, then Level 2 would fail as well, but it
> doesn't. No, it's a problem in VCC's interrupt design. Something ONLY
> triggered by L1 code. I've yet to see any COCO 1 & 2 programs (RSDOS)
> that cause this and it seems to be exclusive to OS9. I remember when
> we discovered this a few years ago, we tried removing the "setime"
> from the startup and L1 would boot all the way to the cmd prompt. As
> soon as you hit a key, it would crash. Same thing happens if you set a
> program to autoexec on boot up. It will run the program up until you
> hit a key. I guess the key would be to examine how L1 (v2.0) & L2
> (since it will run), each handle the interrupts (yes they are
> different) and find what L1 is doing that L2 is not doing that could
> cause VCC to fail. Once we know what causes the fail, then VCC can be
> examined to find the problem. Other than that, it's worse than finding
> a needle in a haystack
>
>
> -----Original Message-----
> From: Walter Zambotti <zambotti at iinet.net.au>
> To: coco at maltedmedia.com
> Sent: Fri, Apr 17, 2020 1:37 am
> Subject: Re: [Coco] OS-9 Level1 Version 02.00.00 FYI
>
> I had a go with OVCC and the same result.
>
> Stuck at entering the date.
>
> An ident of the OS9Boot file from that floppy shows
>
> IOman
> RBF
> CCDisk
> DD
> D0
> D1
> SCF
> CCIO
> CO32
> TERM
> PRINTER
> P
> RS232
> T1
> PipeMan
> Piper
> Pipe
> Clock
> SysGo
> Shell
>
> The startup does a :
>
> SETIME </TERM
>
But its extremely vital, because settime starts the clock, which is also 
the heart of its multitasking. And w/o settime to start the clock, you 
have no interrupt handler. So of course, touching a key, which generates 
an IRQ, is going to crash.

What did you expect to happen?

> That's it!!!
>
> Could the SysGo be failing to start the shell with the correct device?
>
> Walter
>
> On 2020-04-17 09:21, Robert Gault wrote:
> > There is a .zip in the archive
> > https://colorcomputerarchive.com/repo/Disks/Operating%20Systems/OS-9
> >%20Level%201%20v02.01.00%20(Tandy).zip
> >
> > which freezes with VCC on a key stroke when asked for the date. The
> > same OS9-L1V201-SYS.dsk works with MAME/MESS in Coco3 mode.
> >
> > This particular OS-9 version on boot says
> > Phonenix release 11/04/2002
> > HTTP://COCOOS9.SOURCEFORGE.NET
> > when booting.
> >
> > So, there may still be a problem with VCC emulation.
> >
> > Robert
> >
> > L. Curtis Boyle wrote:
> >> Correct. That was fixed in OS9 Level 1 version 2.00, since they
> >> knew the Coco 3 was coming out. Versions 1.00 and 1.01 both do not
> >> work on a Coco 3, for the reason that William has stated.
> >>
> >> L. Curtis Boyle
> >> curtisboyle at sasktel.net
> >>
> >>> On Apr 16, 2020, at 2:01 PM, William Astle <lost at l-w.ca> wrote:
> >>>
> >>> That's probably because they overwrite the FExx page when they
> >>> load, and, thus, the interrupt vectors get hosed.
> >>>
> >>> On 2020-04-16 1:58 p.m., David Ladd wrote:
> >>>> Thank you sir.
> >>>> Yeah OS-9 L1 normally doesn't work with VCC, and not sure why. 
> >>>> NitrOS-9 L1
> >>>> also doesn't work on VCC either.
> >>>> That is why it is always best to have real hardware around for
> >>>> testing of
> >>>> stuff :D
> >>>
> >>> --
> >>> Coco mailing list
> >>> Coco at maltedmedia.com
> >>> https://pairlist5.pair.net/mailman/listinfo/coco
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>


More information about the Coco mailing list