Jump to content
Bee

Writing for the XEP80

Recommended Posts

Wrote a basic program to add a TD line to the XEP80 in my programs.

 

60102099573__0C235ECA-2A98-4C0E-943A-BF27D3AC7573.thumb.jpg.47a0b18e1efc42425f94d783676bf1d4.jpg

 

60102233969__73EFCC32-A7A1-4D96-894A-2DDC6157AB6F.thumb.jpg.f92c997a4914f4f59dd2130661838fa0.jpg

getting a base set of tools built.

 

Thank you

 

  • Like 7

Share this post


Link to post
Share on other sites

Hello Bee

 

Have you looked at the XEP80 section om my special stuff page?  (After you click on the link, you'll find three files at the top of the screen you might want to have a look at)

 

Sincerely

 

Mathy 

  • Like 4

Share this post


Link to post
Share on other sites

Lemme get this straight... You used BASIC for this? I would have used Assembler and put this in the VBI to keep updated.

BASIC? Really?

 

Share this post


Link to post
Share on other sites

Yes - Basic because I have a bunch of things already written in basic.  I'm currently using the XEP80 driver in Sparta Dos.  I will have a stab at making a bob term Disk.

 

@Mathy Thanks I had a read through and learned a lot.

 

Thank you.

  • Like 1

Share this post


Link to post
Share on other sites

@Mathy I have down loaded Bob Term from you and the fast XEP80 handler.  When I un arc the fast driver it is a file called modual1.off?  I'm not sure how to use it.

 

Any advice?

 

Thank you

Share this post


Link to post
Share on other sites

bobterm module files are sometimes slightly modified drivers... you can rename them to what they are, I usually leave there real names and copy the ones I am using to modulex.btm or whatever the convention is x=0,1,2,3 etc... I may be slightly off but bobterm has documentation so If you read it, chances are the good information is there.

  • Like 1

Share this post


Link to post
Share on other sites

I haven't had my XEP80 out in years, but I remember that I never got past the horrible overscan issue -- I got something like 78 columns and 23+a half rows.  I remember researching it enough that I believed that the root cause was in the ROM.  Has anyone ever fixed that?  I believe that under Altirra, it is not an issue, but I'm referring to real hardware.

-Larry

Share this post


Link to post
Share on other sites

I can vaguely remember reading about a fix but don't remember if it was a modification of the unit itself or to a monitor.

Share this post


Link to post
Share on other sites

It's a combination of hardware and firmware. The hardware is limited in that it can only place vertical sync within one character row of the end of the display. Atari should have put blank rows at the beginning and end, but instead they just hugely overscanned it.

 

I ship a XEPVHOLD.COM program now with Altirra that reprograms the XEP80 for less overscan and better video timing so the display is less likely to roll on modern TVs. It shortens the character rows slightly and unfortunately cuts off descenders a bit, but that's unavoidable without reprogramming the character set ROM.

 

  • Like 3

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