[Coco] Trying to build new images

[Bill Pierce]

Bill, the Coco3F{GA is a working simulation of an enhanced Coco 3 on the Altera DE-1 Development System. There has been some progress in porting to the De-2, but I'm not sure how far it has gone. The Coco3FPGA is an awesome piece of work by Gary Becker and supports most Coco 3 software (still a couple of glitches being worked on).

The Coco3FPGA user's group is here:
https://beta.groups.yahoo.com/neo/groups/CoCo3FPGA/info

 

 


Bill Pierce
"Charlie stole the handle, and the train it won't stop going, no way to slow down!" - Ian Anderson - Jethro Tull

 

My Music from the Tandy/Radio Shack Color Computer 2 & 3
https://sites.google.com/site/dabarnstudio/
Co-Contributor, Co-Editor for CocoPedia
http://www.cocopedia.com/wiki/index.php/Main_Page
Global Moderator for TRS-80/Tandy Color Computer Forums
http://www.tandycoco.com/forum/

E-Mail: ooogalapasooo at aol.com


 

 

-----Original Message-----
From: Bill Gunshannon <bill.gunshannon at hotmail.com>
To: coco <coco at maltedmedia.com>
Sent: Sun, Jan 8, 2017 3:30 pm
Subject: Re: [Coco] Trying to build new images

On 1/8/17 12:49 PM, Bill Pierce via Coco wrote:> Bill, I was only going on what you were providing. Also, I sent that email BEFORE you sent the one saying you could get all the way through.> I'm not sure what's going on. If the boot script works, then it should be creating a bootable file.> Either something is missing, or it is failing on the loading of external modules loaded by "sysgo". Several files must be in the root or cmds dir. These are:>> Root:> sysgo (L2 only, sysgo should be in the boot in L1)sysgo is not in the root of the running image from the zipfile.Ident does show sysgo  in the OS9Boot file, however.Maybe I should provide this as well.  I am booting     nos6809l1v030300coco2_dw.dskas my work system.> startup>> /DD/CMDS:> shell> grfdrv (L2 only)> echo (used by startup)> setime (used by startup)> date (used by startup)> link (L2 only, used by startup)> load (L2 only, used by startup)The script only put shell in CMDS on the new disk but I have addan additional step that copies everything (except OS9Boot) fromthe /DD to /X1.>> If you are using DW & HDBDOS,Not sure what that means.  I am using an HDB-DOS ROM Cartridge to bootfrom Drivewire.  But HDB translation is off and if I turn it on DW turnsit off anyway.  The image I am using is "raw" "OS9".> then the boot disks in the repo that I linked in the email should work to> give you a base to create a new disk.I'll go take a look.  That's on another machine. :-)> Just put the disk in slot 0 of DW and type DOS. If you are trying>to boot from a VHD, then that's a whole new ballgame.>> As for how people build new boots, until recently, almost no one was building new boots. The OS9 users> were getting to be few and most were just using the pre generated repo disks. I use NitrOS9 daily on> real Cocos, emulators, and the Coco3FPGA.Now that you mention that, I remember long ago people talking about"emulating" the COCO in hardware.  I assume that is what you meanby COC3FPGA.  I have an Altera and Lattice Evaluation boards (weused them in the Physics Dept at the University where I used towork).  Is there a COCO3 description that is likely to work on eitherof these?  That would be a whole new experience.  :-)> I create ALL my boots in OS9, but I do not use the system> provided on the disks. I use the repo disks as a starter (disk based on what I need) then use cobbler &> ezgen and build from there.> Like you, I don't like using PC tools to work with the Coco. I'd rather do it on the Coco. I do like to> use the emulators as they give me speed when compiling C projects. Large C projects can take hours to> compile on a Coco and with VCC overclocked, I can compile my projects in seconds.>Have to look into "ezgen".  Don't remember that from my pastexperiences.  As for the time, I'm not in a hurry, I do this forfun.  I run stuff while I watch the Steelers play because just watchingTV is really boring.bill-- Coco mailing listCoco at maltedmedia.comhttps://pairlist5.pair.net/mailman/listinfo/coco