Jump to content
9640News

MyBasic 4.05 Docs-Program-Src

Recommended Posts

The executables are in the ABASIC-405.zip file.  Unzip, and transfer.

 

  • Like 1

Share this post


Link to post
Share on other sites

Just a note.  There will be an ABASIC update.  Tim identified a bug dropping into ABASIC chasing another issue, and identified an error reporting routine.  After a bit of chasing some code around, I had to shorten some strings reporting errors as the strings dropped into a separate 8K page and was being overwritten during the linking process.  Now, ABASIC will report Insufficient Memory if one's configuration with AUTOEXEC  doesn't have enough free memory.  There were also a couple of other error messages that had the same issue as well.

 

Beery

  • Like 2
  • Thanks 2

Share this post


Link to post
Share on other sites

BEEP and CALL Speed(x) don't work but are listed in the manual?

 

  • Like 1

Share this post


Link to post
Share on other sites
1 hour ago, hloberg said:

BEEP and CALL Speed(x) don't work but are listed in the manual?

 

I just tested BEEP, granted it is with 4.06, but BEEP works for me. I tested in both the a program and at the command prompt for ABASIC.

 

Also, CALL SPEED has bene removed and is not part of the  manual documentation anymore.


Beery

 

  • Like 1

Share this post


Link to post
Share on other sites
1 minute ago, BeeryMiller said:

I just tested BEEP, granted it is with 4.06, but BEEP works for me. I tested in both the a program and at the command prompt for ABASIC.

 

Also, CALL SPEED has bene removed and is not part of the  manual documentation anymore.


Beery

 

OK. thanks.

Share this post


Link to post
Share on other sites
1 minute ago, BeeryMiller said:

I just tested BEEP, granted it is with 4.06, but BEEP works for me. I tested in both the a program and at the command prompt for ABASIC.

 

Also, CALL SPEED has bene removed and is not part of the  manual documentation anymore.


Beery

 

CALL SPEED I believe was an artifact from a much older version

 

@hloberg and @BeeryMiller  is there an opportunity now for anyone willing to do some testing to look through the commands and report back any corrections?    I have an old document from the 90s that Jim Uzzell had sent me with some ABASIC bugs that I will try to locate and share today so that they can be evaluated.  I know that I fixed some errors in the OS but never got to work with Jim on the remaining issues.

Share this post


Link to post
Share on other sites
40 minutes ago, InsaneMultitasker said:

CALL SPEED I believe was an artifact from a much older version

 

@hloberg and @BeeryMiller  is there an opportunity now for anyone willing to do some testing to look through the commands and report back any corrections?    I have an old document from the 90s that Jim Uzzell had sent me with some ABASIC bugs that I will try to locate and share today so that they can be evaluated.  I know that I fixed some errors in the OS but never got to work with Jim on the remaining issues.

Now that I started reading the current manual 405 (doh), sure, get me a bug list and I'll test away.

Share this post


Link to post
Share on other sites
7 minutes ago, hloberg said:

Now that I started reading the current manual 405 (doh), sure, get me a bug list and I'll test away.

Cool, if you find any commands or errors as you read, it will be good to fix those.

 

Here is a short list I found in one of my release notes.  I can't find the electronic copy of Jim's notes so I am going out to the garage soon to look for the paper copy that I hope I still have tucked away in my folders. 

(More bugs reported by Jim Uzzell)

       CALL DISTANCE and CALL COINC _XOP_ routines return incorrent values. 

       CALL FILES() in Advanced BASIC reports an erroneous BYTE size when
       programs larger than 32K are catalogged.  (VERIFIED 7/10/96, the catalog
       routine in Adv.BASIC is displaying a signed 16-bit number, so the largest
       displayable byte size is 32767.  This fix would have to be made to
       Advanced BASIC, not MDOS).

       CALL KEY() in Advanced BASIC.  If Mode 4 is used then a switch is made t
       to 0,1, or 2 some values values below 33 and above 126 are corrupted.
       If you use mode 4 you must switch to 3 or 5 before using 0,1, or 2.

 

 

 

Share this post


Link to post
Share on other sites

Seems that most of the bugs Jim reported were fixed though I don't know that he ever confirmed them independently.  I found the original document right where I thought it would be... it is from 1996.  Egads, time sure flies. Seems I consolidated the remaining bugs into the MDOS 2.21 release notes above.  I thought Jim created a ABASIC/MYBASIC buglist that he was working through, maybe Beery has seen it as I don't seem to have it.

 

FEBB85CF-7ABA-483E-914B-082828BD6189.thumb.jpeg.cb4f7e75f04a65cdde7c3f50c426e1fb.jpeg

Share this post


Link to post
Share on other sites

I don't think I have a buglist.  Around 97/98, I was going through a divorce and I was backing away from the Geneve stuff during that time period.

 

Beery

  • Sad 1

Share this post


Link to post
Share on other sites
7 hours ago, BeeryMiller said:

I don't think I have a buglist.  Around 97/98, I was going through a divorce and I was backing away from the Geneve stuff during that time period.

 

Beery

In the letter he sent me, Jim said that "most of the bugs in MYBASIC are gone as of v4.00."   The bug list I am thinking of could have predated his message or I could be remembering the same message he sent me.  The CALL LINK fix was not referenced anywhere by Jim, that was something I uncovered trying to port S&T BBS to Advanced BASIC.  No list is good news.

  • Like 1

Share this post


Link to post
Share on other sites

I looked through the rest of my files tonight.  I did not find any more ABASIC bug reports in the stack.  @hloberg, the 2-3 bugs in posts 11/12 are probably the last to rule out if you are doing any testing, provided you don't uncover any new bugs!  :)

 

 

  • Like 1

Share this post


Link to post
Share on other sites

If he does find any bugs, he or anyone else is always welcome to stomp them before they bite someone!

Share this post


Link to post
Share on other sites
9 hours ago, InsaneMultitasker said:

I looked through the rest of my files tonight.  I did not find any more ABASIC bug reports in the stack.  @hloberg, the 2-3 bugs in posts 11/12 are probably the last to rule out if you are doing any testing, provided you don't uncover any new bugs!  :)

 

 

I check into them soon after I get the bugs out of my mille borne abasic game and add some color and sound.

Share this post


Link to post
Share on other sites

For those that have not caught it, ABASIC V4.06 was/is available for download through the GitHub repository or here.  You just need to download ABASIC1, ABASIC2, ABASIC3, and ABASIC4.  I just zipped them up now for here.

 

This fixes an error message if you have insufficient memory, and a couple of other display issues.

 

At this point, I am not aware of any other bugs.

 

And, I should point out, that should any significant bugs be found, I would hope someone might be able to step up and resolve the issue.  There is a lot going on within ABASIC, and really, Jim Uzzell was the only individual that had spent enough time in the code to fully understand it.  Simple things may be one thing, but the more complex issues, that would take a lot of time to understand.

 

ABASIC-V406.zip

Edited by BeeryMiller
  • Like 4

Share this post


Link to post
Share on other sites

In addition to the 2-3 possible ABASIC and/or MDOS bugs mentioned above, I know of a few quirks to watch out for:

 

1) Standard TI Extended BASIC programs typically load into ABASIC without issue; the reverse is not true if you use CALL subprograms and/or other items not supported by XB.

2) Extended BASIC prescan can mask syntax errors within existing programs. The interpreter sometimes gets lost during prescan and reports an error in a line that is perfectly acceptable.  Common causes are improper use of FOR/NEXT and IF/THEN statements.

3) On occasion, the statement separator "::" doesn't translate properly and PRINT statements with multiple ":" need adjusting.

4) Some PEEK/LOAD values used to speed up operations or trick the ROM and interrupt routine have no effect.  These are tricky to identify as they are not always apparent when trouble-shooting.  I think this may also apply to assembly code embedded with SYSTEX and other quick-load programs.  Fortunately, ABASIC's assembly object code loader is fast :)

 

 

  • Like 2

Share this post


Link to post
Share on other sites
On 2/25/2021 at 8:29 AM, BeeryMiller said:

For those that have not caught it, ABASIC V4.06 was/is available for download through the GitHub repository or here.  You just need to download ABASIC1, ABASIC2, ABASIC3, and ABASIC4.  I just zipped them up now for here.

 

t the more complex issues, that would take a lot of time to understand.

 

ABASIC-V406.zip 35.94 kB · 5 downloads

Beery, are you able to replace the 4.05 in post #1 with 4.06?

Share this post


Link to post
Share on other sites
On 2/27/2021 at 1:22 AM, 9640News said:

I can't edit previous posts if someone has posted after me.

 

Beery

 

You have to ask @OLD CS1 to make you admin of post #1, or @Albert

 

Share this post


Link to post
Share on other sites
On 2/26/2021 at 6:22 PM, 9640News said:

I can't edit previous posts if someone has posted after me.

 

Beery

You can now edit the first post indefinitely.  If you need the ability to edit other posts, you can send me a PM directly and I can help you (links to specific posts are helpful, you can click on the post number to get a direct link to that post).

 

 ..Al

  • Like 4

Share this post


Link to post
Share on other sites

Thanks.  I also added a 2 year subscription to AtariAge this week.

  • Like 4

Share this post


Link to post
Share on other sites

In the process of running a demo program attached from a demo from the StrangeCart, I added the use of the TIME$ function to store the start/finish time of the display.  Found a bug using the TIME$.  What the time should report is:

 

19:51:21

 

However, it is reporting:

19:51:2021

 

It is adding the "20" and increasing the length.

 

I've taken a quick look trying to find the source file where this may be defined, but thus far, it is eluding me.  I'm reporting here should anyone want to chase it down and find it before I have additional time to find it.  The ABASIC Github repository can be found at:

 

GitHub - BeeryMiller/ABasic: ABasic for MDOS

 

 

STRANGE

  • Like 4

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...