[Coco] 6309 port of NitrOS-9 Level 1

[Kip Koon]

Hi Tormod,
I tried booting nos96309l1v030300coco2_6309_dw.dsk from Drivewire 4.  After I typed DOS in hdbdos 1.4 DW3 coco 1 on my coco 1, the screen never changed.  I still saw the DOS command on the DECB screen.  The clear screen and "nitros9 booting" never took place.  If this runs in an emulator configured as a Coco 1, then something is wrong.  I think I have a Coco 2 that is upgraded to 6309.  I'll try a coco2_6309 dsk file on that machine and let you know.  
Now that I have a desoldering vacuum gun and have been practicing with it a bit, I think it might be time to upgrade one of my Coco 3's to a 6309.  I'll have to practice a little on a nonfunctional Coco2 I have first to gain more confidence.  Once I feel better about my skills, I'll try my hand on a real Coco 3.  If I can successfully get a 40-pin chip off that Coco 2 motherboard, I think I will then upgrade one of my Coco 3's to an HD63C09EP microprocessor CPU!  Whoo-Hoo!  

Kip Koon
computerdoc at sc.rr.com
http://www.cocopedia.com/wiki/index.php/Kip_Koon


> -----Original Message-----
> From: Coco [mailto:coco-bounces at maltedmedia.com] On Behalf Of Tormod Volden
> Sent: Thursday, July 23, 2015 5:27 AM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] 6309 port of NitrOS-9 Level 1
> 
> On Thu, Jul 23, 2015 at 11:14 AM, Kip Koon wrote:
> > Hi Tormod,
> > I 'hg updated lwtools-4.11' to my local lwtools repo.  I didn't even know I was using a development version all this time.  Up to this
> point I have always used hg pull, hg update.
> > This time when I ran make PORTS=coco2_6309 dsk SOFTLINK=cp, all the lwasm commands looked like they executed correctly so all
> I included was the part that seemed to go wrong.  Here is what the output looks like.  The resulting dsk file was almost empty.  Some
> data at the beginning and some data at the very end of the file.
> 
> > make[2]: execvp: echo: Permission denied
> > make[2]: *** [showobjs_dw] Error 127
> 
> I would guess this is because your Cygwin environment has the current
> directory "." in the PATH, so when the makefile try to launch "echo"
> the Cygwin shell will try to execute the nitros9 echo executable that
> happen to be in the current directory at that time. Either try to
> clean up your PATH to not include the current directory (I know this
> is pretty much impossible in MSYS) or append this to your make
> command:
>  ECHO=/bin/echo
> (assuming the echo executable is in /bin on your Cygwin setup!)
> You can also set this in rules.mak.
> 
> Tormod
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco