Jump to content
IGNORED

PLATOTerm for Atari - Working out tgi and ser issues.


Recommended Posts

Ok, so.. I've now cut a brand new test release.

 

DOS 2.5 is now used as the base DOS.

 

The fancy loader is temporarily gone, until I can come up with a solution that works well, that will automatically load the right handler and PLATOTerm. any pointers on this would be welcome.

 

The "touch" driver is now by default set to NONE. This is so R-Verter users can work out of the box, as R-Verter and Touch conflict with each other (it freezes while trying to do the mouse_load which also does mouse_install, which is where it actually fails...), so to end-around this for now, I have set the touch driver to none. If you are an R-Verter user, and change the Touch driver in the OPTION setup menu, you will freeze. If this happens, simply delete the CONFIG file. You have been warned. Atari 850 users do not have this issue. If you enable touch, and you're not an R-Verter user, and things freeze, please go to the Issues tracker in github and let me know.

 

The details and preliminary documentation is here:

https://github.com/tschak909/platoterm64/releases/tag/TEST_20180911

 

Please let me know how this fares, compared to previous builds. I want to tidy all this up as soon as possible, and get a solid release out to you guys.

-Thom

  • Like 2
Link to comment
Share on other sites

OK, got something working now.

Strange error (not reported, plato just continues), not closing IOCB #1 and opening it for atrrdev.ser....

 

anyhow

 

Using Rverter, 2400 baud, 256byte buffer, it overflows.

Switched down to 1200 baud, 256 byte buffer, OK, hardly 16 bytes used.

Same graphic issues as before, checkers is unplayable.

(see picture)

Also I noticed some weird rounding and strange angles in text/graphics.

 

Graphics are drawn faster, nicely done !

But crooked, alas less nice then the previous build.

Maximum baud-rate 1200 else it overflows (so, same as before).

 

Cheers.

Sijmen.

post-6668-0-80795700-1536672259.png

Edited by mr-atari
Link to comment
Share on other sites

I really want to cry.

 

DOS 2.0 allowed me to move the RUNAD down to $2200, which, gives enough space for everything to work, even the R-Verter.

 

Everything, except the fucking P:R: connection. With the P:R: connection, it shoves MEMLO up to $2411 (sloopy's testing)

 

But if I shove MEMLO up to $2500, then my Atari 800 with 48K of RAM is no longer able to install the CC65 serial driver.

 

I do not know what the fuck to do.

 

-Thom

Link to comment
Share on other sites

what did you define APPMHI as and what did you define RAMSIZ as?

I didn't get very far this time.

might I also ask why PlatoTerm doesn't like to relocate? Is it not using branches?

last really stupid question... If you don't like the R:handler how hard to make something to sit where you wish it to, people make their own handlers. another thought was if you don't like things moving because of different handlers and you use fixed code for term, why not pad the handlers out with null handlers to keep things slotted where you wish.

 

I sure I'm misreading the whole thing as usual, but just be abstract for a bit.

Edited by _The Doctor__
Link to comment
Share on other sites

130XE, MIO, Lantronix, hard and floppy

 

I think I'm going to just make a stack of R: for you and try it on every one each time.

MIO, BB, PR: 850 and sx212 rverter. putting it all away and digging it out and setting it up again is a hassle, might as well make it semi permanent.

 

I'll set up like this with real hardware.

MIO1meg-130XE

BB-320XE

850 800XL floppy only

PR 800XL MyIDE

 

will that cover the bases or do you want a specific combination to test with, lastly are you still wishing it to be tested with all DOS versions or just 2.5?

Edited by _The Doctor__
Link to comment
Share on other sites

yeah, that should cover a good solid # of bases.

 

And I'm testing with the following OS combos:

 

DOS 2.5

SpartaDOS 3.2 (and RealDOS)

SpartaDOS X

MyDOS 4.53

 

That should cover most of them. Any that others are using that I should explicitly cover?

 

(I did try with DOS 3, on a lark, and it almost works, but it crashes when loading the serial port driver) ;)

 

-Thom

Link to comment
Share on other sites

JIh8vds.pngmeanwhile, i've rolled out almost all the 8-bit ports, for a picture:

 

Atari 800

Apple ][

Commodore 64

TI 99/4A

Sinclair ZX Spectrum

Amstrad CPC

 

Not pictured, but working:

Radio Shack Color Computer 3 (DECB)

Commodore 128 (uses the VDC for a full scale PLATO display, but x128 does not emulate the VDC completely enough to show.)

 

All from the same code-base :)

 

-Thom

  • Like 2
Link to comment
Share on other sites

sigh.

 

You want to write lots of different ports each in Assembly? Have you actually tried to tackle something like that? :) You'd still be stuck debugging the protocol handler. :) (I speak from experience.)

 

I have limited amount of time, and a huge project scope that must be tackled to achieve the goals that I want to achieve. So I am trying to attack the problem as intelligently, as I can.

 

step 1, is getting a terminal written and out there in the hands of everyone, for as many systems as I can, just get it working.

step 2, is to accept patches from others to make things better and faster, possibly to foster a path to ownership of each port to other people.

 

-Thom

Link to comment
Share on other sites

oh yes.

 

To start, functions in C can be replaced with assembler functions, to be called from the main C code.

 

This process can be done to systematically leverage speed in critical sections, while keeping e.g. the protocol decoder sections in C, due to their extreme complexity (if you look at the protocol decoder on the original Atari cartridge, you'll see that it is dense and full of gymnastics tricks.)

 

-Thom

  • Like 1
Link to comment
Share on other sites

oh yes.

 

To start, functions in C can be replaced with assembler functions, to be called from the main C code.

 

This process can be done to systematically leverage speed in critical sections, while keeping e.g. the protocol decoder sections in C, due to their extreme complexity (if you look at the protocol decoder on the original Atari cartridge, you'll see that it is dense and full of gymnastics tricks.)

 

-Thom

Nice :)

Link to comment
Share on other sites

When plato is loaded from D2, it assumes the rest of the files are on D1....

That should not be this way.

It should be using DUNIT and load files from the active drive.

The resulting errors, file not found, end of file, are not shown when loading.

Took me some hours to hunt down these ghosts.

 

Memlo should not be an issue, did you minimize DOS?

That can shave off some bytes.

For me it's certainly no issue, memlo without driver is $0f00

 

I'm still unlucky to get online with my ESP8266 connected directly to SIO.

Only had success with Bobterm connecting to a BBS.

 

Question 1:

Does plato let me send $0A / CONTROL-J ?

So I can add RETURN and CONTROL-J to send commands to my module?

 

Question 2:

Does plato send out a Xoff when the buffers fills up and Xon when its drained below treshhold?

I noticed that 2400 baud is to fast, my buffer of 256 bytes overflows.

 

Question 3:

Why does plato clears page 6?

 

Grtz,

Sijmen.

Edited by mr-atari
  • Like 2
Link to comment
Share on other sites

Hmmm, OK.

 

I tried this in my driver.

Xoff when 80% buffer and Xon (when Xoff was used) when empty again.

When I send Xoff, the plato server does not stop sending.

 

I looked into your keydef_table.

control-x is mapped to $0A.

So I tried this.

AT <return> <control-x>

-nothing-

 

Checked serout, it does not send out $0A, it does $26.

Then I changed your keydef, added $0A for the /|\ or inverse key.

That was undefined with $FF.

Nop, still no $0A sended out, again $26

 

Page 6, why does plato clears it?

I notice that it is not used, so why clear it.

 

This is what I can do so far.

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