[Coco] FW: Coco Digest, Vol 154, Issue 66
Taylor, Phillip L CIV
Phillip.L.Taylor at uscg.mil
Wed Sep 23 13:47:03 EDT 2015
Hello
I have already read this link
You are not authorized for this page. https://globalpayroll.direct-access.us/psc/HCPRD_2/EMPLOYEE/HRMS/c/CG_HRMS_EXT_(GBL).CG_PHS_MBR_INFO.GBL
-----Original Message-----
From: Coco [mailto:coco-bounces at maltedmedia.com] On Behalf Of coco-request at maltedmedia.com
Sent: Wednesday, September 23, 2015 1:33 PM
To: coco at maltedmedia.com
Subject: Coco Digest, Vol 154, Issue 66
Send Coco mailing list submissions to
coco at maltedmedia.com
To subscribe or unsubscribe via the World Wide Web, visit
https://pairlist5.pair.net/mailman/listinfo/coco
or, via email, send a message with subject or body 'help' to
coco-request at maltedmedia.com
You can reach the person managing the list at
coco-owner at maltedmedia.com
When replying, please edit your Subject line so it is more specific than "Re: Contents of Coco digest..."
Today's Topics:
1. Re: [SPAM] Re: [SPAM] Re: Re Links Broken or Down
(Plt at freemail2.com)
2. Re: [SPAM] Re: [SPAM] Re: Re Links Broken or Down (Barry Nelson)
3. Re: MC-10 Composite board progress (Steve Batson)
4. Re: [SPAM] Re: [SPAM] Re: Re Links Broken or Down (Robert Gault)
5. Re: DS1216 (Bill Pierce)
6. E-mail Netiquette: How to Start a New Thread (John W. Linville)
7. Re: E-mail Netiquette: How to Start a New Thread
(John W. Linville)
8. Re: E-mail Netiquette: How to Start a New Thread (Zippster)
9. Re: E-mail Netiquette: How to Start a New Thread
(Christopher R. Hawks)
10. Re: E-mail Netiquette: How to Start a New Thread (Zippster)
11. Re: E-mail Netiquette: How to Start a New Thread (Brian Blake)
12. Re: [] Re: [] Re: Re Links Broken or Down (Dennis Bathory-Kitsz)
13. Re: DS1216 (K. Pruitt)
14. Re: DS1216 (K. Pruitt)
----------------------------------------------------------------------
Message: 1
Date: Wed, 23 Sep 2015 01:24:23 -0400
From: "Plt at freemail2.com" <plt at freemail2.com>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Subject: Re: [Coco] [SPAM] Re: [SPAM] Re: Re Links Broken or Down
Message-ID: <2C98C7FF-B331-4A0D-8135-5F97E3678EF9 at freemail2.com>
Content-Type: text/plain; charset=us-ascii
The old boot disk loads fine but when I use the new boot from the link and type dos 254 or doss 255 I get a syntax error.
Phil Taylor
> On Sep 22, 2015, at 8:03 PM, Robert Gault <robert.gault at att.net> wrote:
>
> Plt at freemail2.com wrote:
>> I am using nitros9.vhd and the boot disk that was provided on the Maillist and when it boots it display krel to. Nitros9 then locks up.
>>
>> Phil Taylor
>
> Phil,
>
> The nitros9.vhd came with a boot disk on either drive 254 or 255. You
> should be able to boot into OS-9 with the command DOS 254 or DOS 255
> depending on witch drive has the boot disk.
>
> Does the above work correctly? If not, the .vhd disk is not a good one.
>
> You still need to try an appropriate disk from the site referred to in previous messages. If you have tried one, give the exact name of the disk and the version of VCC you are using.
>
> Robert
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
------------------------------
Message: 2
Date: Wed, 23 Sep 2015 04:15:46 -0400
From: Barry Nelson <barry.nelson at amobiledevice.com>
To: coco at maltedmedia.com
Subject: Re: [Coco] [SPAM] Re: [SPAM] Re: Re Links Broken or Down
Message-ID: <4B8C06AC-2E00-4F92-A3BB-3521FF70B943 at amobiledevice.com>
Content-Type: text/plain; charset=us-ascii
Please read and follow the directions at:
http://www.cocopedia.com/wiki/index.php/VCC_1.4.3b_and_DW4_Installation_Guide
Most likely you did not follow the directions for setting up the hdbdos rom.
> Plt at freemail2.com plt at freemail2.com
> Wed Sep 23 01:24:23 EDT 2015
> The old boot disk loads fine but when I use the new boot from the link and type dos 254 or doss 255 I get a syntax error.
>
>
> Phil Taylor
>
> > On Sep 22, 2015, at 8:03 PM, Robert Gault <robert.gault at att.net> wrote:
> >
> > Plt at freemail2.com wrote:
> >> I am using nitros9.vhd and the boot disk that was provided on the Maillist and when it boots it display krel to. Nitros9 then locks up.
> >>
> >> Phil Taylor
> >
> > Phil,
> >
> > The nitros9.vhd came with a boot disk on either drive 254 or 255. You should be able to boot into OS-9 with the command
> > DOS 254
> > or
> > DOS 255
> > depending on witch drive has the boot disk.
> >
> > Does the above work correctly? If not, the .vhd disk is not a good one.
> >
> > You still need to try an appropriate disk from the site referred to in previous messages. If you have tried one, give the exact name of the disk and the version of VCC you are using.
> >
> > Robert
> >
> >
> >
> > --
> > Coco mailing list
> > Coco at maltedmedia.com
> > https://pairlist5.pair.net/mailman/listinfo/coco
------------------------------
Message: 3
Date: Wed, 23 Sep 2015 04:43:16 -0700
From: Steve Batson <steve_batson at yahoo.com>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Subject: Re: [Coco] MC-10 Composite board progress
Message-ID: <4EDA11E0-D09D-40BB-A264-ADD885D4356F at yahoo.com>
Content-Type: text/plain; charset=windows-1252
Very Cool...Add me to your list :)
On Sep 22, 2015, at 5:37 PM, Zippster <zippster278 at gmail.com> wrote:
> Well, I finally got around to working out the sound portion of the MC-10
> Composite board. A voltage divider/low-pass circuit seems to be giving good
> results (you can make out the patch for the divider on the board).
>
> I think these are probably ready for me to order some final-version PCBs.
>
> <https://drive.google.com/open?id=0B1sgl615FlGnanZSaDlpVDRJZnM <https://drive.google.com/open?id=0B1sgl615FlGnanZSaDlpVDRJZnM>>
>
> I’ll be sending one of these prototypes to Simon for him to use in his
> MC-10 coding efforts. :)
>
> - Ed
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
------------------------------
Message: 4
Date: Wed, 23 Sep 2015 08:52:08 -0400
From: Robert Gault <robert.gault at att.net>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Subject: Re: [Coco] [SPAM] Re: [SPAM] Re: Re Links Broken or Down
Message-ID: <5602A078.3040309 at att.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Plt at freemail2.com wrote:
> The old boot disk loads fine but when I use the new boot from the link and type dos 254 or doss 255 I get a syntax error.
>
>
> Phil Taylor
That is because none of the disks at http://nitros9.sourceforge.net/latest/ are
designed to boot from a .vhd image. Also the command will only work if you are
running RGBDOS and currently on a .vhd image with the Disk Basic partition
formatted and containing a boot disk.
If you want to update the version of NitrOS-9 on your .vhd image, you will need
to generate a new 35-track single sided floppy image with an appropriate Boot
module (for .vhd usage) and new OS9Boot file. That disk will need to be backed
up to a convenient "Basic drive" on the .vhd and all files on the downloaded
floppy will need to be transferred into appropriate directories in the NitrOS-9
portion of the .vhd image.
Robert
------------------------------
Message: 5
Date: Wed, 23 Sep 2015 09:24:28 -0400
From: Bill Pierce <ooogalapasooo at aol.com>
To: coco at maltedmedia.com
Subject: Re: [Coco] DS1216
Message-ID: <14ffa606d64-1fde-1d1b1 at webprd-m29.mail.aol.com>
Content-Type: text/plain; charset=utf-8
Kelly, if you're using the disassembler from the repo disks, it's a 6309 compatible disasm... hence the odd instructions.
Now why is it throwing 6309 code up when it's a 6809 program? It's hitting the FCBs & FDBs at the beginning and seeing them as code... some are reading as 6309 stuff. That's why you have no data at the beginning.
Try using Sleuth... it will give you the "Entry" address when it reads the file in, you can then set the FCB/FDB/FCC/FCS areas, and do fake disasms until you get all set... then save it to disk. I think you'll get a better disassembly with Sleuth... unless it IS actually 6309 code..... But what you described sounded like 6809 being disassembled by 6309 disasm from the wrong entry point.
Also, I think the sources are on RTSI...
Try this and see if it's the same program:
http://ftp://os9archive.rtsi.com/OS9/OS9_6X09/SYSMODS/RTC_Disto_RGB_Utils.lzh
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: K. Pruitt <pruittk at roadrunner.com>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Sent: Tue, Sep 22, 2015 11:32 pm
Subject: Re: [Coco] DS1216
----- Original Message -----
From: "Gene Heskett" <gheskett at wdtv.com>
To:
<coco at maltedmedia.com>
Sent: Tuesday, September 22, 2015 8:06 PM
Subject: Re:
[Coco] DS1216
> On Tuesday 22 September 2015 21:48:41 K. Pruitt wrote:
>
>> >
----- Original Message -----
>> > From: "Gene Heskett" <gheskett at wdtv.com>
>> >
To: <coco at maltedmedia.com>
>> > Sent: Tuesday, September 22, 2015 4:58 PM
>> >
Subject: Re: [Coco] DS1216
>> >
>> >> On Tuesday 22 September 2015 19:52:05 K.
Pruitt wrote:
>> >
>> > <snip>
>> >
>> >>> > --
>> >>>
>> >>> Not to hijack this
thread, but rather than start an entire new
>> >>> thread with no context...
>>
>>>
>> >>> Anybody have any idea why setclk doesn't disassemble correctly?
>>
>>>
>> >>> eim? oim? aim? Where are these op codes coming from? Are these
>> >>>
even real?
>> >>>
>> >>> L02A5 eim #$63,$0F,s
>> >>>
>> >>> Seriously? Is
this actually legit code?
>> >>
>> >> Legit code, but for a 6309?
>> >>
>> >>
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)
>> >> Genes Web page
<http://geneslinuxbox.net:6309/gene>
>> >>
>> >> --
>> >
>> > Thanks for taking
the time to answer Gene.
>> >
>> > --
>>
>> I found Chris Burke's "The 6309
Book" online. I'm surprised to se a
>> disassember from 1988 spit out 6309 code.
I thought the 6309 being put
>> in to CoCo's was much later. Also surprised to
see the setclk program
>> written in 1989 contain 6309 code. Some of you guys
were way ahead of
>> the curve.
>
> I bought my first HD63C09EP as a kit from
Chris Burke. In about that
> late 80's time frame.
>
> As for the setclk, there
should have been in those days, a separate
> version for each cpu as that code
would certainly not have worked on a
> 68x09. I doubt if it exists today
because of the extremely limited
> amount of difference it would make since its
normally only used by the
> user to set the clock. With the right clock, that
might be once a day
> if you were being picky.
>
> 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)
> Genes Web page
<http://geneslinuxbox.net:6309/gene>
>
> --
I don't think setclk is
disassembling correctly for whatever reason. I see
no data in this disassembly
and there should be, based on just looking at
the binary with a hex editor.
I've placed data at the bottom of my code and
seen disassembler results like
this before. I don't think I ever saw 6309
code pop up before. But it does run
on a 6809 and has been on my CoCo since
at least 1990 doing it's thing so I'm
going to assume the 6309 code in the
disassembly is just randomness. The
disaasembler had to spit out something
so it did.
--
Coco mailing
list
Coco at maltedmedia.com
https://pairlist5.pair.net/mailman/listinfo/coco
------------------------------
Message: 6
Date: Wed, 23 Sep 2015 09:26:46 -0400
From: "John W. Linville" <linville at tuxdriver.com>
To: coco at maltedmedia.com
Subject: [Coco] E-mail Netiquette: How to Start a New Thread
Message-ID: <1443014806.5466.2.camel at tuxdriver.com>
Content-Type: text/plain; charset="UTF-8"
Of the dozens (perhaps hundreds) of email lists in which I participate,
none of them has as much trouble with people hijacking threads instead
of starting new threads than this one does.
http://www.shlomifish.org/philosophy/computers/netiquette/email/start-n
ew-thread.html
Please -- when you want to start a new thread (i.e. a new subject for
discussion), send a new message rather than just replying to an
existing one with a changed subject!
Thanks,
John
--
John W. Linville Someday the world will need a hero, and you
linville at tuxdriver.com might be all we have. Be ready.
------------------------------
Message: 7
Date: Wed, 23 Sep 2015 10:31:51 -0400
From: "John W. Linville" <linville at tuxdriver.com>
To: coco at maltedmedia.com
Subject: Re: [Coco] E-mail Netiquette: How to Start a New Thread
Message-ID: <20150923143151.GD373 at tuxdriver.com>
Content-Type: text/plain; charset=us-ascii
On Wed, Sep 23, 2015 at 09:26:46AM -0400, John W. Linville wrote:
> Of the dozens (perhaps hundreds) of email lists in which I participate,
> none of them has as much trouble with people hijacking threads instead
> of starting new threads than this one does.
>
> http://www.shlomifish.org/philosophy/computers/netiquette/email/start-n
> ew-thread.html
Obviously, this link should be on one line...
http://www.shlomifish.org/philosophy/computers/netiquette/email/start-new-thread.html
> Please -- when you want to start a new thread (i.e. a new subject for
> discussion), send a new message rather than just replying to an
> existing one with a changed subject!
>
> Thanks,
>
> John
--
John W. Linville Someday the world will need a hero, and you
linville at tuxdriver.com might be all we have. Be ready.
------------------------------
Message: 8
Date: Wed, 23 Sep 2015 09:57:26 -0500
From: Zippster <zippster278 at gmail.com>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Subject: Re: [Coco] E-mail Netiquette: How to Start a New Thread
Message-ID: <8B4B7FEC-5C78-4284-8801-B71FC21C3C60 at gmail.com>
Content-Type: text/plain; charset=utf-8
Ah, well the link explains what the issue would be with some email software.
This “internet etiquette” issue has never been a problem for me with Gmail and Apple Mail,
but then, I’ve never understood the need for more than one type of fork at the dinner table either.
<http://www.etiquettescholar.com/dining_etiquette/table_setting/place_setting/flatware/forks.html <http://www.etiquettescholar.com/dining_etiquette/table_setting/place_setting/flatware/forks.html>>
I’m guilty of doing this almost every time, but since it’s a problem for some, and
I now understand the issue, I’ll do my best not to do it again.
But I refuse to comply with the fork thing. :)
- Ed
> On Sep 23, 2015, at 8:26 AM, John W. Linville <linville at tuxdriver.com> wrote:
>
> Of the dozens (perhaps hundreds) of email lists in which I participate,
> none of them has as much trouble with people hijacking threads instead
> of starting new threads than this one does.
>
> http://www.shlomifish.org/philosophy/computers/netiquette/email/start-n
> ew-thread.html
>
> Please -- when you want to start a new thread (i.e. a new subject for
> discussion), send a new message rather than just replying to an
> existing one with a changed subject!
>
> Thanks,
>
> John
> --
> John W. Linville Someday the world will need a hero, and you
> linville at tuxdriver.com might be all we have. Be ready.
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
------------------------------
Message: 9
Date: Wed, 23 Sep 2015 10:04:27 -0500
From: "Christopher R. Hawks" <chawks at dls.net>
To: coco at maltedmedia.com
Subject: Re: [Coco] E-mail Netiquette: How to Start a New Thread
Message-ID: <20150923100427.59f701eb at HAWKSoft>
Content-Type: text/plain; charset=utf-8
On Wed, 23 Sep 2015 09:57:26 -0500
Zippster <zippster278 at gmail.com> wrote:
> Ah, well the link explains what the issue would be with some email
> software.
>
> This “internet etiquette” issue has never been a problem for me with
> Gmail and Apple Mail, but then, I’ve never understood the need for
> more than one type of fork at the dinner table either.
>
> <http://www.etiquettescholar.com/dining_etiquette/table_setting/place_setting/flatware/forks.html
> <http://www.etiquettescholar.com/dining_etiquette/table_setting/place_setting/flatware/forks.html>>
>
> I’m guilty of doing this almost every time, but since it’s a problem
> for some, and I now understand the issue, I’ll do my best not to do
> it again.
>
> But I refuse to comply with the fork thing. :)
>
> - Ed
More forks means you can eat more and still be polite (you
change forks halfway thru the meal).
> > On Sep 23, 2015, at 8:26 AM, John W. Linville
> > <linville at tuxdriver.com> wrote:
> >
> > Of the dozens (perhaps hundreds) of email lists in which I
> > participate, none of them has as much trouble with people hijacking
> > threads instead of starting new threads than this one does.
> >
> > http://www.shlomifish.org/philosophy/computers/netiquette/email/start-n
> > ew-thread.html
> >
> > Please -- when you want to start a new thread (i.e. a new subject
> > for discussion), send a new message rather than just replying to an
> > existing one with a changed subject!
> >
> > Thanks,
> >
> > John
> > --
> > John W. Linville Someday the world will need a hero,
> > and you linville at tuxdriver.com might be all
> > we have. Be ready.
Christopher R. Hawks
HAWKSoft
--
The sun never sets on the British Empire. But it rises every morning.
The sky must get awfully crowded. -- Rod Schmidt
----------------------------------------
\ ^__^
\ (oo)\_______
(__)\ )\/\
||----w |
|| ||
------------------------------
Message: 10
Date: Wed, 23 Sep 2015 10:16:16 -0500
From: Zippster <zippster278 at gmail.com>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Subject: Re: [Coco] E-mail Netiquette: How to Start a New Thread
Message-ID: <97D4D0E8-4961-4FAA-AB1E-DA3885A622BF at gmail.com>
Content-Type: text/plain; charset=utf-8
Being an uncultured run-of-the-mill American, how changing forks would
have any bearing on politeness eludes me.
I remember while traveling in Europe years ago, I would even use the edge
of my fork to cut softer items on the plate while eating, which I thought nothing of.
People would comment that I was eating like an American, I guess we’re known for that.
They seemed amused. I told them it was more efficient. :)
- Ed
> On Sep 23, 2015, at 10:04 AM, Christopher R. Hawks <chawks at dls.net> wrote:
>
> On Wed, 23 Sep 2015 09:57:26 -0500
> Zippster <zippster278 at gmail.com> wrote:
>
>> Ah, well the link explains what the issue would be with some email
>> software.
>>
>> This “internet etiquette” issue has never been a problem for me with
>> Gmail and Apple Mail, but then, I’ve never understood the need for
>> more than one type of fork at the dinner table either.
>>
>> <http://www.etiquettescholar.com/dining_etiquette/table_setting/place_setting/flatware/forks.html
>> <http://www.etiquettescholar.com/dining_etiquette/table_setting/place_setting/flatware/forks.html>>
>>
>> I’m guilty of doing this almost every time, but since it’s a problem
>> for some, and I now understand the issue, I’ll do my best not to do
>> it again.
>>
>> But I refuse to comply with the fork thing. :)
>>
>> - Ed
>
> More forks means you can eat more and still be polite (you
> change forks halfway thru the meal).
>
> Christopher R. Hawks
> HAWKSoft
> --
> The sun never sets on the British Empire. But it rises every morning.
> The sky must get awfully crowded. -- Rod Schmidt
> ----------------------------------------
> \ ^__^
> \ (oo)\_______
> (__)\ )\/\
> ||----w |
> || ||
>
------------------------------
Message: 11
Date: Wed, 23 Sep 2015 11:17:53 -0400
From: Brian Blake <random.rodder at gmail.com>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Subject: Re: [Coco] E-mail Netiquette: How to Start a New Thread
Message-ID: <5602C2A1.8050901 at gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
On 9/23/2015 11:16 AM, Zippster wrote:
> Being an uncultured run-of-the-mill American, how changing forks would
> have any bearing on politeness eludes me.
>
> I remember while traveling in Europe years ago, I would even use the edge
> of my fork to cut softer items on the plate while eating, which I thought nothing of.
> People would comment that I was eating like an American, I guess we’re known for that.
> They seemed amused. I told them it was more efficient. :)
>
> - Ed
It's also a sign of someone who knows how to properly cook meat!
--
------------------------------------------------------------------------
Tandy Color Computer <http://www.tandycoco.com>
Tandy CoCo Forum <http://www.tandycoco.com/forum>
------------------------------
Message: 12
Date: Wed, 23 Sep 2015 12:40:47 -0400
From: "Dennis Bathory-Kitsz" <bathory at maltedmedia.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Subject: Re: [Coco] [] Re: [] Re: Re Links Broken or Down
Message-ID:
<47857e1213aa18c6af6e0c29da5d4ccb.squirrel at sm.webmail.pair.com>
Content-Type: text/plain;charset=iso-8859-1
Since Phil Taylor is new to the list, he probably doesn't realize that he
should always delete the [SPAM] added to the subject.
Phil, please also check your email system, as it is adding this; if you can't
fix it, please change your email provider.
Meanwhile, the rest of you should know better. Please delete [SPAM] before
replying.
Dennis
------------------------------
Message: 13
Date: Wed, 23 Sep 2015 09:54:04 -0700
From: "K. Pruitt" <pruittk at roadrunner.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Subject: Re: [Coco] DS1216
Message-ID: <01fc01d0f620$969d6c30$0200a8c0 at Desktop1>
Content-Type: text/plain; format=flowed; charset="UTF-8";
reply-type=original
Thanks Bill. I'll give that a shot.
I'd really like to get this modified for George to solve his issue with
setclk.
"But what you described sounded like 6809 being disassembled by 6309 disasm
from the wrong entry point."
Yep. that pretty much describes what I am seeing. Because not only am I
seeing what I now understand to be 6309 code, but the internal addressing is
off as well.
Thanks again.
----- Original Message -----
From: "Bill Pierce via Coco" <coco at maltedmedia.com>
To: <coco at maltedmedia.com>
Cc: "Bill Pierce" <ooogalapasooo at aol.com>
Sent: Wednesday, September 23, 2015 6:24 AM
Subject: Re: [Coco] DS1216
> Kelly, if you're using the disassembler from the repo disks, it's a 6309
> compatible disasm... hence the odd instructions.
> Now why is it throwing 6309 code up when it's a 6809 program? It's hitting
> the FCBs & FDBs at the beginning and seeing them as code... some are
> reading as 6309 stuff. That's why you have no data at the beginning.
>
> Try using Sleuth... it will give you the "Entry" address when it reads the
> file in, you can then set the FCB/FDB/FCC/FCS areas, and do fake disasms
> until you get all set... then save it to disk. I think you'll get a better
> disassembly with Sleuth... unless it IS actually 6309 code..... But what
> you described sounded like 6809 being disassembled by 6309 disasm from the
> wrong entry point.
>
> Also, I think the sources are on RTSI...
> Try this and see if it's the same program:
> http://ftp://os9archive.rtsi.com/OS9/OS9_6X09/SYSMODS/RTC_Disto_RGB_Utils.lzh
>
>
>
>
>
>
> 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
>
------------------------------
Message: 14
Date: Wed, 23 Sep 2015 10:30:16 -0700
From: "K. Pruitt" <pruittk at roadrunner.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Subject: Re: [Coco] DS1216
Message-ID: <020901d0f625$c3b07a50$0200a8c0 at Desktop1>
Content-Type: text/plain; format=flowed; charset="UTF-8";
reply-type=response
P.S. The link you provided is the source code for setclk. Shouldn't be a
problem modifying setclk to do what George wants it to do now.
This is awesome. Thanks.
----- Original Message -----
From: "K. Pruitt" <pruittk at roadrunner.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Wednesday, September 23, 2015 9:54 AM
Subject: Re: [Coco] DS1216
> Thanks Bill. I'll give that a shot.
>
> I'd really like to get this modified for George to solve his issue with
> setclk.
>
> "But what you described sounded like 6809 being disassembled by 6309
> disasm from the wrong entry point."
>
> Yep. that pretty much describes what I am seeing. Because not only am I
> seeing what I now understand to be 6309 code, but the internal addressing
> is off as well.
>
> Thanks again.
>
>
> ----- Original Message -----
> From: "Bill Pierce via Coco" <coco at maltedmedia.com>
> To: <coco at maltedmedia.com>
> Cc: "Bill Pierce" <ooogalapasooo at aol.com>
> Sent: Wednesday, September 23, 2015 6:24 AM
> Subject: Re: [Coco] DS1216
>
>
>> Kelly, if you're using the disassembler from the repo disks, it's a 6309
>> compatible disasm... hence the odd instructions.
>> Now why is it throwing 6309 code up when it's a 6809 program? It's
>> hitting the FCBs & FDBs at the beginning and seeing them as code... some
>> are reading as 6309 stuff. That's why you have no data at the beginning.
>>
>> Try using Sleuth... it will give you the "Entry" address when it reads
>> the file in, you can then set the FCB/FDB/FCC/FCS areas, and do fake
>> disasms until you get all set... then save it to disk. I think you'll get
>> a better disassembly with Sleuth... unless it IS actually 6309 code.....
>> But what you described sounded like 6809 being disassembled by 6309
>> disasm from the wrong entry point.
>>
>> Also, I think the sources are on RTSI...
>> Try this and see if it's the same program:
>> http://ftp://os9archive.rtsi.com/OS9/OS9_6X09/SYSMODS/RTC_Disto_RGB_Utils.lzh
>>
>>
>>
>>
>>
>>
>> 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
>>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>
------------------------------
Subject: Digest Footer
_______________________________________________
Coco mailing list
Coco at maltedmedia.com
https://pairlist5.pair.net/mailman/listinfo/coco
------------------------------
End of Coco Digest, Vol 154, Issue 66
*************************************
More information about the Coco
mailing list