[Coco] I dunno what happened

[Bill Pierce]

Wayne,
I gave it a shot
First I had to find "elapsed" in my archives as you didn't provide it on the disk or a link to it.
You also gave no specifics on doing it, so here are the steps I took and the results after copying elapsed to the disk

In Vcc (highly overclocked)

CHD /d1
CHX /d1/cmds
decode elapsed


All I got was "Initializing..." at the bottom of the screen with a flashing cursor near the top... it just hung there till I killed it

Then I tried it on my Coco 3 with same cmds.
It printed "Initializing..." at the bottom again, then cleared the screen and printed the number 67 in it's place and ended.

Don't know if this right or if it helps...

Bill Pierce
My Music from the Tandy/Radio Shack Color Computer 2 & 3
https://sites.google.com/site/dabarnstudio/
Co-Webmaster of The TRS-80 Color Computer Archive
http://www.colorcomputerarchive.com/
Co-Contributor, Co-Editor for CocoPedia
http://www.cocopedia.com/wiki/index.php/Main_Page
E-Mail: ooogalapasooo at aol.com




-----Original Message-----
From: Wayne Campbell <asa.rand at gmail.com>
To: CoCoList <coco at maltedmedia.com>
Sent: Mon, Sep 23, 2013 12:45 pm
Subject: [Coco] I dunno what happened


As I was working on removing the display-related code from decode I ran
into a problem where the program ran until it got to the part where it
begins to build the source instructions, and then it started ending before
it printed a single statement. I could find no reason for this, and started
going back through previous versions. I decided to replace all the modified
modules with the 1.1.5 version and start from there. Lo and behold, now
1.1.5 doesn't work either. Decoding elapsed it now does not identify the
one line reference that elapsed contains, and when it begins to build the
source statements, the line number function is erroring out because it
can't find the reference.

The only thing that has changed is the computer I am using. The OS (XP Pro
SP3) is the same OS I had installed on my laptop. Not being a hardware
tech, I don't know if it's common for a program to break between hardware
differences, but this seems to be the case. decode 1.1.5 was working fine
on my laptop, and for the short bit I worked on it on the church's Dell
tower it worked fine, but now it is broken, and I don't know why.

I'm almost afraid to change any of the code because it was good code
before, so why should it be bad code now?

Will someone who has downloaded the 1.1.5 .os9 image from
http://cococoding.com/wayne/ please run it on the elapsed module from RiBBS
and tell me what the result is? If it was a fluke that it was working on my
laptop, then I'd like to know.

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

decode
http://cococoding.com/wayne/

--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco