Jump to content
IGNORED

Magellan + TIPI (file formats!?)


Recommended Posts

Having finally completed my TI-99/4a + Tipi+FinalGrom setup, I'm attempting to recreate a game I made on the TI back when I was 12 or 13, using Magellan to create the graphics. I'm having trouble, however, transferring the XB files, which appear to be in the wrong format. Can someone help me understand how to translate the Basic or XB files from the magellan into a format an actual TI can read after transferred? They are being seen as dis/var as opposed to program. 

 

 

Screen Shot 2022-05-06 at 1.39.43 PM.png

Screen Shot 2022-05-06 at 1.38.48 PM.png

  • Like 3
Link to comment
Share on other sites

I don't have Magellan, so I have questions... 

 

Is the screen.xb file that it saves text? or a binary XB PROGRAM image file? I used it once, I don't believe it produces FIAD PROGRAM image files as output. I've only used it to produce assembly source which was just PC text files. 

 

I think most people load the generated .xb file into their clipboard, and paste into XB via Classic99, and then save that as a PROGRAM image... but as the page Arcadeshopper linked to points out, you can let TIPI convert it to PROGRAM image by just trying to LOAD it with the OLD or RUN command in XB. (dots '.' are slashes '/' on the 4a in filenames, and case matters - https://github.com/jedimatt42/tipi/wiki/File-name-rules)

 

What is the 'screen' file? is that the Magellan project/proprietary data file? 

 

The TI filesystem is complex. So to allow editing source as source in text editors on a 4A, the file type for these special source code extensions is still DISPLAY VARIABLE 80 as that is what our text editors are constrained to. But accessing a PROGRAM image file uses a special operation called LOAD ( as opposed to open/read/write/close ) in the disk controller. Since BASICs cannot load the plain text forms of the code, TIPI tries to encode it into a PROGRAM image temporarily if that LOAD operation is requested. It's a kind of magic, magic, magic... 

 

If you haven't worked with disks on a 4A, you'll learn that it is more complex than any of its contemporaries. 

  • Like 1
Link to comment
Share on other sites

So the answer was Magellan does not produce a file to be used on the 4A. It produces a proprietary file that includes some xb source code, but the file itself is not xb source code.

 

Maybe this is a Magellan bug, as the difference is just the lack of a line number on the first line. 

  • Like 1
Link to comment
Share on other sites

1 hour ago, jedimatt42 said:

So the answer was Magellan does not produce a file to be used on the 4A. It produces a proprietary file that includes some xb source code, but the file itself is not xb source code.

 

Maybe this is a Magellan bug, as the difference is just the lack of a line number on the first line. 

aaand blank lines

aaand lines out of order

 

  • Like 1
Link to comment
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.
Note: Your post will require moderator approval before it will be visible.

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...