Re: Game server and SSC

["Alex Freed" <alexf@mirrow.com>]

"BLuRry" <brendan.robert@gmail.com> wrote in message
1152716033.864766.8370@i42g2000cwa.googlegroups.com">news:1152716033.864766.8370@i42g2000cwa.googlegroups.com...
>
> Very odd.  If you have disabled the echo feedback mode, then it is most
> likely that bytes were dropped along the way.  The core problem is that
> the SSC (and //c) firmware is very very slow and unbuffered.  So if the
> host is sending data faster than the apple can keep up (and this is
> very easy to recreate at 19200 baud), the apple drops characters right
> and left.

Let's try to debug this together :)

The bad news is I don't speak java and don't even know how to recompile the
java source.
Or is it interpreted? But still you need to byte-compile, right?

The good news is I have all kinds of toys line scopes and logic analizers.

So here is what I see:
1. Power cycle a2e and type "IN#2".
2. Start a2gameserver in 19200 mode.

Native lib Version = RXTX-2.1-7
Java lib Version   = RXTX-2.1-7
Opened port: //./COM1
Executing init script.
Expect echo: true
Skipping to label try19200
Trying 19200 baud
error in script, line 60:expected ] but timed out

Apple beeps with a "syntax error", but I see "PR#2" on the screen.
I don't think it's a case of missing bits: same exact thing happens at 300
baud.

So I type "PR#2" myself. Apple waits without a "]" prompt as the SSC doesn't
see DTR.
Start the script again. Still "syntax error" on the apple, but the script
doesn't mind and continues.
Sends the driver over at 19200 baud with no trouble.
"Sending driver" at the top of the Apple screen.
So far, so good.
*300G

and Apple starts beeping. While java sais:
Executing driver script.
Sending driver
Failure writing line, retrying...
Failure writing line, retrying...
Failure writing line, retrying...
Failure writing line, retrying...
Failure writing line, retrying...
Failure writing line, retrying...
Failure writing line, retrying...

If I control-C out of it and start a terminal at 19200 it looks like the SOS
driver
is executing fine: @ results in "hi" sent back. "Axx" works etc.

> Again, the FAQ and troubleshooting sections have some more information
> about this.  Let me know if you're still stuck.

I'm affraid I am. Is there any way to execute java with a debugger? Should
be easy
with an interpreted language...

>
> -B
>