Jump to content

Photo

Troubleshooting XB256 Compiler:A sense of accomplishment

XB256 Compiler Assembler Extended Basic

5 replies to this topic

#1 Sinphaltimus OFFLINE  

Sinphaltimus

    River Patroller

  • 2,517 posts
  • Distracted at the Keyboard
  • Location:Poconos, PA

Posted Sat Nov 5, 2016 2:58 PM

Shout out to Tursi and Senior Falcon.

I ran in to another issue compiling today. I was determined not to ask for help.

So I read all the things you guys posted and shared all the other times I had issues and it was a success.

 

So happy.

 

Thank you.

For others drawn here because of the title, here's what happened and how it played out.

I'm using classic99 with Harry Wilhelm's XB256 and his 256D Compiler to compile an Extended BASIC program.

The program compiled without issue.

It was the Assembler that threw this at me...

.

Attached File  Z43TSISSUE.png   30.69KB   3 downloads

So without changing any DSK settings (I do not save all dv to windows text and I do not save in TIFiles format)

I typed this into the compiler "DSK2.?w.Z43,TXT"

The ?W being a flag for classic99 to tell it to save dv as windows text as long as I use the txt extension I think.
I assumed that everything after the DSK2. was a filename character count. so ? to the second T equals 10 total characters.

I could be mistaken but better safe than sorry.

.

Attached File  Z43TS.png   35.95KB   5 downloads

 

 

Then I loaded the saved txt file into notepad++ with line numbers turned on and scrolled down to line number 1252.

I found 1252 to contain a line reference to line 3500 and it was right above line 3500 with line 3490 preceding it. 

.

Attached File  Z43TStrack.png   52.72KB   3 downloads

 

 

I went to lines 3490 and 3500 in my Extended Basic program and found a typo!

Attached File  Z43TSfound.png   147.71KB   3 downloads

I'm so grateful for the knowledge everyone shares with the community. Bravo and thank you for making me that much more self reliant.


So happy. :)

 

 

 

Attached File  Z43TSFIXED.png   28.41KB   4 downloads

 


Edited by Sinphaltimus, Sat Nov 5, 2016 3:14 PM.


#2 Ksarul ONLINE  

Ksarul

    Quadrunner

  • 5,136 posts

Posted Sat Nov 5, 2016 3:26 PM

The dreaded Typo strikes again. . .and such frustrations may have had a part in the creation of two old-school TI games too: Typo and Typo II ;)



#3 senior_falcon OFFLINE  

senior_falcon

    Stargunner

  • 1,369 posts
  • Location:Lansing, NY, USA

Posted Sat Nov 5, 2016 8:32 PM

Feel good to figure it out on your own, doesn't it? I had something like that happen once in an assembly program where I typed RO instead of R0.  I had a heck of a time finding it!  

Try running the XB program in Classic99 using turbo mode which just might speed things up enough for you to do some useful debugging in XB.  Especially if your computer is newer than the clunkers that I use!



#4 Tursi OFFLINE  

Tursi

    Quadrunner

  • 5,487 posts
  • HarmlessLion
  • Location:BUR

Posted Sun Nov 6, 2016 12:02 AM

Congratulations! To answer your one question:

So without changing any DSK settings (I do not save all dv to windows text and I do not save in TIFiles format)
I typed this into the compiler "DSK2.?w.Z43,TXT"
The ?W being a flag for classic99 to tell it to save dv as windows text as long as I use the txt extension I think.
I assumed that everything after the DSK2. was a filename character count. so ? to the second T equals 10 total characters.
I could be mistaken but better safe than sorry.


Correct, everything after the "?W." is the filename, including the ".TXT". You can omit that, but then you will have to figure out how to open the file on the Windows side. It's easier if you include it, but Classic99 doesn't care.

So to break it down:

DSK2. - the file system device name
?W. - a flag to Classic99's FIAD disk system
Z43.TXT - the filename itself

When you are using FIAD files under Classic99, as long as they are not V9T9 (that is, TIFILES or Windows files), you are NOT restricted to 10 characters. That is a limitation of the TI Disk Controller that many systems chose to copy, but Classic99's disk system does not impose that limit. This is not an emulation concept - the TI itself supports very long strings in the filename. ;)

I do plan to change the scheme slightly before bringing it to hardware, as documented in my file system proposal (mostly to remove the ambiguity of the periods ;) ). But for now that's the case!

#5 Sinphaltimus OFFLINE  

Sinphaltimus

    River Patroller

  • Topic Starter
  • 2,517 posts
  • Distracted at the Keyboard
  • Location:Poconos, PA

Posted Sun Nov 6, 2016 4:44 AM

I enjoy learning things. I enjoy teaching things. I'm uncomfortable not knowing things I want to know. There are so many resources here, it's often confusing as to where I should look for the information I need. Often times I forget there is a manual for just about everything. I ask for help or I'm drilling through tasks as dictated by the information I find and it has me touching on so many different aspects of what makes it all work. I rarely get to slow down and expand on each and every facet of info. 

This small and relatively easy task of finding basic issues like typos is huge for me. It's actually the first time I've ever looked at assembly with any sense of what might be going on in it. Namely due to the labels being line nume numbers from the actual BASIC program I wrote. So there was some familiarity at a rudimentary level. 

I'm enjoying this journey. I am reminded why I fell in love with computers to begin with. I never imagined returning to the TI in such a way. I also never imagined the TI held strong all these years with the support of so many intelligent people constantly developing new things for it. Keeping it going all these years. 

I've had an interesting life so far. And it's still getting interesting. The TI represents one constant that been with me for most of it even if I left it for a large chunk. It will always be the computer that started it all. The seed in which I sprang into creative computing. So here I am, returning to it in an attempt to reboot some core competencies and strengthen my programming skills and understanding. There's a lot of work to do and I greatly appreciate all of you for assisting. It's my pleasure to contribute in any ways that I can.

:thumbsup:


Edited by Sinphaltimus, Sun Nov 6, 2016 4:46 AM.


#6 Airshack OFFLINE  

Airshack

    Dragonstomper

  • 895 posts
  • Location:Phoenix, AZ

Posted Fri Nov 25, 2016 5:02 PM

Shout out to Tursi and Senior Falcon.

I ran in to another issue compiling today. I was determined not to ask for help.

So I read all the things you guys posted and shared all the other times I had issues and it was a success.

 

So happy.

 

Thank you.

For others drawn here because of the title, here's what happened and how it played out.

I'm using classic99 with Harry Wilhelm's XB256 and his 256D Compiler to compile an Extended BASIC program.

The program compiled without issue.

It was the Assembler that threw this at me...

.

attachicon.gifZ43TSISSUE.png

So without changing any DSK settings (I do not save all dv to windows text and I do not save in TIFiles format)

I typed this into the compiler "DSK2.?w.Z43,TXT"

The ?W being a flag for classic99 to tell it to save dv as windows text as long as I use the txt extension I think.
I assumed that everything after the DSK2. was a filename character count. so ? to the second T equals 10 total characters.

I could be mistaken but better safe than sorry.

.

attachicon.gifZ43TS.png

 

 

Then I loaded the saved txt file into notepad++ with line numbers turned on and scrolled down to line number 1252.

I found 1252 to contain a line reference to line 3500 and it was right above line 3500 with line 3490 preceding it. 

.

attachicon.gifZ43TStrack.png

 

 

I went to lines 3490 and 3500 in my Extended Basic program and found a typo!

attachicon.gifZ43TSfound.png

I'm so grateful for the knowledge everyone shares with the community. Bravo and thank you for making me that much more self reliant.


So happy. :)

 

 

 

attachicon.gifZ43TSFIXED.png

 

 

Thanks! Just learned something new.







Also tagged with one or more of these keywords: XB256, Compiler, Assembler, Extended Basic

0 user(s) are browsing this forum

0 members, 0 guests, 0 anonymous users