27 May
2025
27 May
'25
5 p.m.
I am going to assume there are other TRS-80 people hanging out
here and go ahead and ask this:
Has anyone here used the DEFUSRx command?
I tried to use it for something I am working on and it
didn't work.
So, I copied the example program from page 115 of the
Model III Disk System Owner's Manual and, guess what,
it didn't work either.
150 DEFUSR1 = &H7D00
returns a Syntax Error
150 DEFUSR1 = 32000
works fine.
Anybody else ever run into this?
I can't believe something as blatant as that could have
gone on for all those years.
bill
27 May
27 May
5:19 p.m.
I used that command once and I seem to remember having the same issue. That would have
been in about 1984.
Sent from my iPhone
Robert Harrison
bobh(a)tds.net
On May 27, 2025, at 8:08 PM, Bill Gunshannon via
cctalk <cctalk(a)classiccmp.org> wrote:
I am going to assume there are other TRS-80 people hanging out
here and go ahead and ask this:
Has anyone here used the DEFUSRx command?
I tried to use it for something I am working on and it
didn't work.
So, I copied the example program from page 115 of the
Model III Disk System Owner's Manual and, guess what,
it didn't work either.
150 DEFUSR1 = &H7D00
returns a Syntax Error
150 DEFUSR1 = 32000
works fine.
Anybody else ever run into this?
I can't believe something as blatant as that could have
gone on for all those years.
bill
5:32 p.m.
$9C
or
9Ch.
Try these?
Bill
On Tue, May 27, 2025 at 8:23 PM Bill Gunshannon via cctalk <
cctalk(a)classiccmp.org> wrote:
I am going to assume there are other TRS-80 people hanging out
here and go ahead and ask this:
Has anyone here used the DEFUSRx command?
I tried to use it for something I am working on and it
didn't work.
So, I copied the example program from page 115 of the
Model III Disk System Owner's Manual and, guess what,
it didn't work either.
150 DEFUSR1 = &H7D00
returns a Syntax Error
150 DEFUSR1 = 32000
works fine.
Anybody else ever run into this?
I can't believe something as blatant as that could have
gone on for all those years.
bill
6:36 p.m.
On 5/27/2025 8:32 PM, Bill Degnan via cctalk wrote:
> $9C
> or
> 9Ch.
>
> Try these?
On Wed, 28 May 2025, Bill Gunshannon via cctalk wrote:
What are the supposed to mean?
They are simply some of the alternatives to writing &H9C
not everybody used the same notations.
DISK BASIC added the &H notation; prior to that, "Level 2" BASIC did not
have a notation that the numerals were HEX, so you had to write all
numbers in base 10.
--
Grumpy Ol' Fred cisin(a)xenosoft.com
6:37 p.m.
They are different representations of 9C Hexadecimal (10011100).
Kindest regards,
Doug Jackson
em: doug(a)doughq.com
ph: 0414 986878
Follow my amateur radio adventures at vk1zdj.net
On Thu, 29 May 2025 at 11:28, Bill Gunshannon via cctalk <
cctalk(a)classiccmp.org> wrote:
On 5/27/2025 8:32 PM, Bill Degnan via cctalk wrote:
$9C
or
9Ch.
Try these?
What are the supposed to mean?
bill
29 May
29 May
5:50 a.m.
On 5/28/2025 9:37 PM, Doug Jackson wrote:
They are different representations of 9C Hexadecimal
(10011100).
But they are not the form used by TRS-80 BASIC. It uses
the format "&H7D00" (and &O1777 for OCTAL) as depicted not
only in the example I tried to use from Page 115 of the manual
but also clearly explained on pages 93-94 under the title "Hex
and Octal constants. Printing them works fine but trying to
use them as arguments to DEFUSR does not.
bill
27 May
27 May
8:17 p.m.
On 28/05/2025 10:00, Bill Gunshannon via cctalk wrote:
I am going to assume there are other TRS-80 people hanging out
here and go ahead and ask this:
Has anyone here used the DEFUSRx command?
I tried to use it for something I am working on and it
didn't work.
So, I copied the example program from page 115 of the
Model III Disk System Owner's Manual and, guess what,
it didn't work either.
150 DEFUSR1 = &H7D00
returns a Syntax Error
150 DEFUSR1 = 32000
works fine.
Anybody else ever run into this?
I can't believe something as blatant as that could have
gone on for all those years.
A misprint in a manual never corrected? Surly not!
I can't speak for the TRS-80 (you don't say which one) but Microsoft
BASIC of the time didn't allow for non-decimal numbers in its syntax.
I'm more familiar with the 6502 variants, but I'd expect the parser
would be expecting an integer expression at that point.
I've written few Microsoft compatible BASICs for embedded processors in
my time, and hex constants are one of the additional features I add.
If you think it does support hex manifest constants, try PRINT &H7D00
and see how far you get. I'd expect the normal Microsoft expression
parser to be called for DEF USRx - there's no reason to call anything
else. It's just not how it works.
Regards, Frank.
28 May
28 May
1:32 a.m.
It was thus said that the Great Bill Gunshannon via cctalk once stated:
I am going to assume there are other TRS-80 people hanging out
here and go ahead and ask this:
Has anyone here used the DEFUSRx command?
Yes, on the TRS-80 Color Computer. It's defined for Extended Color BASIC.
I tried to use it for something I am working on and
it
didn't work.
So, I copied the example program from page 115 of the
Model III Disk System Owner's Manual and, guess what,
it didn't work either.
150 DEFUSR1 = &H7D00
returns a Syntax Error
150 DEFUSR1 = 32000
works fine.
Anybody else ever run into this?
Nope. ECB supports hexadecimal constants. It sounds like the BASIC you
have doesn't. I know Microsoft's 8-bit BASICs were all compiled from a
common code base, so it may be that the Model III BASIC didn't opt for
hexadecimal support, but no one told the documentation department.
-spc
29 May
29 May
5:53 a.m.
On 5/28/2025 4:32 AM, Sean Conner via cctalk wrote:
Nope. ECB supports hexadecimal constants. It sounds like the BASIC you
have doesn't. I know Microsoft's 8-bit BASICs were all compiled from a
common code base, so it may be that the Model III BASIC didn't opt for
hexadecimal support, but no one told the documentation department.
Nope, not just the documentation. PRINT &H7D00 works fine
DEFUSR1 = &H7D00 returns syntax error. Go figure.
bill
6:20 a.m.
On Thu, May 29, 2025 at 2:04 PM Bill Gunshannon via cctalk
<cctalk(a)classiccmp.org> wrote:
On 5/28/2025 4:32 AM, Sean Conner via cctalk wrote:
Have you tried :
DEFUSR1=(&H7D00)
DEFUSR1=&H7D00+0
I assume you're running TRS-DOS. What happens if you use LBASIC under LDOS?
-tony
Nope. ECB supports hexadecimal constants. It sounds like the BASIC you
have doesn't. I know Microsoft's 8-bit BASICs were all compiled from a
common code base, so it may be that the Model III BASIC didn't opt for
hexadecimal support, but no one told the documentation department.
Nope, not just the documentation. PRINT &H7D00 works fine
DEFUSR1 = &H7D00 returns syntax error. Go figure.
5:15 p.m.
On 5/29/2025 9:20 AM, Tony Duell wrote:
On Thu, May 29, 2025 at 2:04 PM Bill Gunshannon via
cctalk
<cctalk(a)classiccmp.org> wrote:
Interesting. This works.
On 5/28/2025 4:32 AM, Sean Conner via cctalk wrote:
Have you tried :
DEFUSR1=(&H7D00)
Nope. ECB supports hexadecimal constants. It sounds like the BASIC you
have doesn't. I know Microsoft's 8-bit BASICs were all compiled from a
common code base, so it may be that the Model III BASIC didn't opt for
hexadecimal support, but no one told the documentation department.
Nope, not just the documentation. PRINT &H7D00 works fine
DEFUSR1 = &H7D00 returns syntax error. Go figure.
DEFUSR1=&H7D00+0
I assume you're running TRS-DOS. What happens if you use LBASIC under LDOS?
I was not looking for a work around. I could do that by not
using HEX notation. (or OCTAL for that matter) I was just
surprised that, apparently, no one ever ran into this or at
no one ever said anything about it. I got 80-Micro, Kilobaud
and even Creative Computing until each of them went under.
I have never seen any mention of something that must have been
a bug that was run into thousands of times. And, in all
likelihood, could have been easily fixed by many of the ace
system programmers that were using these systems in their
heyday.
bill
31 May
31 May
1:01 a.m.
Unfortunately, many bugs go unfixed. Especially back when you couldn’t just download the
update from the internet. You had to get a new diskette.
Their word processing program, ScripSit had a bug that as far as I know was never
acknowledged publicly. Scripsit was replaced with Super Scripsit, a totally different
program.
Sent from my iPhone
Robert Harrison
bobh(a)tds.net
On May 29, 2025, at 8:23 PM, Bill Gunshannon via
cctalk <cctalk(a)classiccmp.org> wrote:
On 5/29/2025 9:20 AM, Tony Duell wrote:
Interesting. This works.
On Thu, May 29, 2025 at 2:04 PM Bill Gunshannon
via cctalk
<cctalk(a)classiccmp.org> wrote:
On 5/28/2025 4:32 AM, Sean Conner via cctalk wrote:
Have you tried :
DEFUSR1=(&H7D00)
Nope. ECB supports hexadecimal constants. It sounds like the BASIC you
have doesn't. I know Microsoft's 8-bit BASICs were all compiled from a
common code base, so it may be that the Model III BASIC didn't opt for
hexadecimal support, but no one told the documentation department.
Nope, not just the documentation. PRINT &H7D00 works fine
DEFUSR1 = &H7D00 returns syntax error. Go figure. DEFUSR1=&H7D00+0
I assume you're running TRS-DOS. What happens if you use LBASIC under LDOS?
I was not looking for a work around. I could do that by not
using HEX notation. (or OCTAL for that matter) I was just
surprised that, apparently, no one ever ran into this or at
no one ever said anything about it. I got 80-Micro, Kilobaud
and even Creative Computing until each of them went under.
I have never seen any mention of something that must have been
a bug that was run into thousands of times. And, in all
likelihood, could have been easily fixed by many of the ace
system programmers that were using these systems in their
heyday.
bill
28 May
28 May
8:09 a.m.
On Tue, May 27, 2025 at 7:08 PM Bill Gunshannon via cctalk
<cctalk(a)classiccmp.org> wrote:
So, I copied the example program from page 115 of the
Model III Disk System Owner's Manual and, guess what,
it didn't work either.
150 DEFUSR1 = &H7D00
returns a Syntax Error
&H is a Disc BASIC extension. You have to be actually booted under
TRSDOS and run "BASIC" from the disk before that will work I believe.
29 May
29 May
5:56 a.m.
On 5/28/2025 11:09 AM, Gavin Scott via cctalk wrote:
On Tue, May 27, 2025 at 7:08 PM Bill Gunshannon via
cctalk
<cctalk(a)classiccmp.org> wrote:
It is. As formerly stated PRINT &H7D00 works DEFUSR1 = &H7D00 does not.
bill
So, I copied the example program from page 115 of
the
Model III Disk System Owner's Manual and, guess what,
it didn't work either.
150 DEFUSR1 = &H7D00
returns a Syntax Error
&H is a Disc BASIC extension. You have to be actually booted under
TRSDOS and run "BASIC" from the disk before that will work I believe.
8:03 a.m.
Now you're tempting me to get out a Model III to try this!
On Thu, May 29, 2025 at 9:43 AM Bill Gunshannon via cctalk <
cctalk(a)classiccmp.org> wrote:
On 5/28/2025 11:09 AM, Gavin Scott via cctalk wrote:
On Tue, May 27, 2025 at 7:08 PM Bill Gunshannon
via cctalk
<cctalk(a)classiccmp.org> wrote:
It is. As formerly stated PRINT &H7D00 works DEFUSR1 = &H7D00 does not.
bill
So, I copied the example program from page 115 of
the
Model III Disk System Owner's Manual and, guess what,
it didn't work either.
150 DEFUSR1 = &H7D00
returns a Syntax Error
&H is a Disc BASIC extension. You have to be actually booted under
TRSDOS and run "BASIC" from the disk before that will work I believe.
3
days inactive
6
days old
16 comments
9 participants
participants (9)
-
Bill Degnan -
Bill Gunshannon -
bobh＠tds.net -
Doug Jackson -
Frank Leonhardt -
Fred Cisin -
Gavin Scott -
Sean Conner -
Tony Duell