Uhm.How does it work?

[thErZAgH]

Hi Bo.

Sorry to nag you again. But: I set the baudrate of Zimodem to 1200. Then I loaded pml64.bin. After that I started one of the PRG files. IRC for e. g. But nothing happens. It stays at initializing message.....

You wrote to reset cpu and do all again. It changes nothing.

Must I disconnect 9600 cables to make it work? BTW: in CCGMS I have to change baudrate only and it works....

[bozimmerman]

I don't know what the 9600 cables are, but if you mean disable UP9600 compatibility, no -- you don't have to do that. However, UP9600 connections are not compatible with the C128, either in C128 mode OR in C64 mode. As you can tell by this response, I would need a lot more details before even guessing why it's not working. Do ANY of the Zimodem/C64Net tools work? Configure? telnet? ftp?

[thErZAgH]

Hi Bo.

Thanks for comming back, Yes. Any of the tools aren't working with my setup. Here's what I'm doing:

• start CCGMS
• set 1200 bd with ATB1200
• write 1200 bd with AT&W
• result: ok
  (can connect to BBSs without problems)
• warm reset C64
• LOAD"PML64.BIN",8,1
• LOAD"TELNET64-128",8,1
• screen with info "TELNET v1.0 Requieres .... Initializing modem....." comes up
• ... nothing - neither after two seconds nore after several minutes.

This happes with ALL of the basic programs. And yes: I did't cut the up9600 patch cords. I'm using C64C with 1541 II. Not a C128 or similar...

EDIT: I set ATR0 for C64 only mode?!
EDIT²: after AT&F nothing changed.
EDIT³: I'm using this ESP: https://www.amazon.de/AZDelivery-NodeMCU-ESP8266-ESP-12E-Development/dp/B06Y1LZLLY/ref=pd_lpo_vtph_107_bs_t_2/260-0062859-5488261?_encoding=UTF8&psc=1&refRID=42PB82VS0G7VJ1D2G43R

[bozimmerman]

OK, first off, you should do LOAD"TELNET64-128",8 and enter RUN. Do not load it ,8,1. And do not load"PML64.BIN" -- the telnet program will do that for you automatically.

The telnet program is one of the simplest programs, since it does not switch the modem to 9600 baud, or use packet-mode, so I'd like you to keep trying the telnet program.

You are using 2.61 (or maybe now 2.62) right?

If it still doesn't work after the changes I mention above, I would like to start running some BASIC experiments to figure out why. But first, please change how you load and run the program.

[bozimmerman]

OH! I wonder if V-1541 is conflicting with PML64 -- they both reside at $c000. I will make sure I change the telnet program to better detect when V-1541 is installed and disable it before loading PML....

[thErZAgH]

I think there are v-1541 lo drivers, too. They have other entry points, I guess.

[thErZAgH]

Hi Bo.
If I first load Telnet64-128 without doing anything else before and type RUN it will load something from tape!? "Press Play on Tage"... On ,8,1 or ,8

Using 2.62 now.

[bozimmerman]

LOAD"TELNET64-128",8

[bozimmerman]

RUN

[thErZAgH]

Small chars. Then "press play on tape".

But if I load PML64.BIN first, it shows "screen with info "TELNET v1.0 Requires .... Initializing modem....." But then nothing happens...

EDIT: If I change
ifsy=226andpeek(ml)<>76thenclose5:load"pml64.bin",peek(186),1:run
to
ifsy=226andpeek(ml)<>76thenclose5:load"pml64.bin",8,1:run
then TELNET loads PML64. But after that same result: stays at "TELNET v1.0 Requieres .... Initializing modem.....".....

EDIT2: After 5 dots it jumps to line 900 and stucks at SYSML (SYS49152?). Even if PML64 has loaded... And here it seems to loop.... I edited a line 902 PRINT"pre sys" and 912 PRINT"after sys" and I see
pre sys
after sys
pre sys
after sys
pre sys
after sys

Modem has 1200 baud and ATR0.

EDIT3: after doing changes mentioned in EDIT2 I had to change open5,2,0,CHR$(10) instead of CHR$(8)!!!! Then it seems to work.... But not sure....

[bozimmerman]

I see.. it DOES sound like v-1541 was interfering, and that the modem was still in 2400 baud mode. In other words, there were several problems all happening at once, and any one of the problems would be enough to break it. I definitely need to detect v-1541, and remember that all of those programs require that the modem be set to 1200 baud.

[bozimmerman]

Also, if you type in LOAD"TELNET64-128",8 and your computer responds with "PRESS PLAY ON TAPE", then your computer has some sort of problem. :(

[thErZAgH]

Hi Bo.

I haven't loaded the V-1541 driver. I'm using the D64 disk provided in the repo.

If I patch TELNET with OPEN5,2,0,CHR$(10) and LOAD"PML64.BIN",8,1 it steps over the initializing message. If I want to call BBS then (coffemud) I get this exception:

http://imgur.com/a/U9wtL

BTW; can we have a chat in IRC or somewhere?

[bozimmerman]

I fixed that exception .. please try 2.63

BTW, CHR$(10) is the code for 2400 baud, and if it works, it is proof your modem is set to 2400 baud.

[thErZAgH]

Hi Bo.

I know that $(10) is for 2400 baud. But I set modem speed to 1200 baud!!!

Call me wrong, but after loading PML64.BIN software ist getting data with 2400 baud speed? so $(10) is the right value?

BTW: 2.63 seems to run better with all of the prg tools...

[bozimmerman]

Yea, sorry about 2.62 -- I put a pretty nasty bug in it that I didn't find until later.

[bozimmerman]

Are you in Europe, BTW? Using a PAL C64? If so, that may explain a lot.

[thErZAgH]

Hi Bo.

Yes. I'm in Europe and using a PAL C64.

[bozimmerman]

Do you think you can help me make the software work better for PAL users?
For example, in the TELNET64-128 program, on line 30, you see this: poke 665,73:poke666,3
Those pokes are "corrections" to the Commodore 64 KERNAL to allow it to get 1200 baud without errors. Do they work OK for you? Do you see bad characters when using that program?

[thErZAgH]

Hey Bo.

Sure. I'll test it t'night...

[thErZAgH]

Hi Bo.

Nope. Doesn't work for me. I have to change

15 OPEN5,2,0,CHR$(8):DIMPP$(25):P$="ok":POKE186,PEEK(254)
to
15 OPEN5,2,0,CHR$(10):DIMPP$(25):P$="ok":POKE186,PEEK(254)
(otherwise initializing stucks)

and

40 IFSY=226ANDPEEK(ML+1)<>209THENCLOSE5:LOAD"pml64.bin",PEEK(186),1:RUN
to
40 IFSY=226ANDPEEK(ML+1)<>209THENCLOSE5:LOAD"pml64.bin",8,1:RUN
(otherwise C64 will load from TAPE)

[bozimmerman]

Well, I set up my PAL C64C and tried out one of the programs. You are right, you have to change it to chr$(10). That is the craziest thing I've ever seen. Even more so because almost immediately the program, written for 1200 baud, tweeks some of the timing registers to better match 1200 baud. I clearly have much research to do.

[bozimmerman]

I have the official fixes for you! I will try to upload a fixed disk with all of these changes today:

1. Keep the chr$(8)... it really is necessary.
2. On line 30 of almost every program you see POKE665,72. Change that to POKE665,43. That is the proper PAL value. The version I release will check PAL/NTSC first, of course.
   Everything else should work fine. Let me know if you still have problems. That change fixed the programs for my PAL C64C running on 110V at 60hz.

[bozimmerman]

Oh, change all the loads that use peek(186) to use peek(254) instead .. doing that also.

[thErZAgH]

Hey Bo,

I changed POKE665,73 to POKE665,43 and peek(186) to peek(254). This seems to work WAY BETTER then the code before 👍 . IRC CHAT v1.0 and TELNET v1.0 are working now. Just tested the two yet.

So I'm ready to test the whole new D64 if you have uploaded it to gh.

[bozimmerman]

OK, I've updated the .D64 image and the apps in github -- they should all be PAL compatible now. Let me know if you have any troubles.