Re: Apple // Game Server 1.1 Released!

["BLuRry" <brendan.robert@gmail.com>]

Kallikak wrote:
> Well I've gotten a bit further.  The problem with the HOME:CALL -151
> line was the case!

Holy cow... I forgot that the old firmware doesn't support lowercase --
how lame of me.  I'll update the binary-to-hex routines!  In short, you
can fix this cheaply by editing the writeParanoid method of GenericHost
like so:
Replace:

byte bytes[] = s.getBytes();

with

byte bytes[] = s.toUpperCase().getBytes();

If you email me I can send you an updated binary.

It appeared in uppercase on the Apple II screen,
> but was in lowercase in init.txt.  When I changed it to uppercase, then
> the syntax error disappeared.  I also changed the case of the hex bytes
> for the line:
> *300:A9 10 8D AB C0 A9 0B 8D AA C0 AD A8 C0 60
> in the file.  However,
> !typeHex /data/sos#060800 800
> didn't work.  Again the text on the Apple II monitor looked just fine,
> but the memory was not getting set.  To get around this, I changed the
> init file to read:
>
> ;!typeHex /data/sos#060800 800
> *800: 01 8D E8 C0 A9 1E 85 3C A9 FF 85 3E 85 42 A9 08
> *810: 85 3D 85 3F A9 BE 85 43 20 2C FE 4C FF BE 78 A9
> *820: 10 8D AB C0 A9 0B 8D AA C0 AD A8 C0 A2 68 20 C5
> *830: BF A2 69 20 C5 BF 4C 3D BF 20 D0 BF 8D 6C BF 20
> *840: D0 BF 8D 6D BF 85 ED 4C 3D BF 20 D0 BF 85 08 20
> *850: D0 BF 85 09 4C 3D BF A6 EB 20 C5 BF 20 D0 BF 38
> *860: E9 40 F0 C8 A8 88 F0 D1 88 F0 DF 88 F0 13 88 F0
> *870: E6 88 F0 37 88 F0 47 A9 00 85 ED 88 F0 4D 4C BF
> *880: BF A0 00 84 ED 84 EB 20 D0 BF 8D 6C BF 45 EB 85
> *890: EB EE 6C BF D0 03 EE 6D BF A5 08 38 E9 01 85 08
> *8A0: B0 E5 A5 09 F0 B6 C6 09 4C 68 BF A5 ED F0 2F 20
> *8B0: 89 FE 20 93 FE A9 00 8D AA C0 58 6C 6C BF A5 ED
> *8C0: F0 1C 20 A9 BF 4C 0D BF 6C 6C BF A0 00 88 F0 08
> *8D0: AE 00 C0 10 F8 8E 10 C0 20 C5 BF 4C 3D BF 20 3A
> *8E0: FF 4C 3D BF AD A9 C0 29 10 F0 F9 8E A8 C0 60 AD
> *8F0: A9 C0 29 08 F0 F9 AD A8 C0 60
> ;Now execute the driver.  Note: The first byte at $800 is unused.
> 801G
>
> hoping that would do the job, and it seems to have been successful.
> Not the most elegant of solutions I guess, but I'm not set up properly
> on this computer to attack the java source directly, so it was the
> easiest way to get it going.
> 
> Ken