Hi Anders, >I tried both the "pet3001" and "pet4001" server programs. I was able to >load both, but neither works reliably with cbmlink once started. I have >enough ROM/EPROM to downgrade my PET to Basic 2, effectively making it >a 3032. However in the release notes for cbmlink, it says that the 3000 >series "may not work", so perhaps it is a moot point? I only tested the BASIC programs with the two or three 8032 that I had at that time. I do not remember if I got a success report from anyone who used a 4032. It has been a long time ago. One thing to try would be to load the "pet3001" or "pet4001" program to VICE and see what happens, that is, if it is jumping to the machine code, or where the machine code is misbehaving. Do you think you can do this? I am busy with work currently. And I do not have any PET hardware any more, as you very well know. :-) >I do have an IEEE interface for the VIC-20 too, perhaps that one would >work better with C2N232 and cbmlink? I have never tried this. The C2N232 transfers on cbmlink are a bit unreliable especially on the C64 and C128, because the KERNAL routines can sometimes reset the state of the CASS READ signal by reading $dc0d or $dd0d. On the Vic-20 it should work better, as the 6522 needs an explicit write to clear a flag. Best regards, Marko Message was sent through the cbm-hackers mailing listReceived on 2012-10-15 11:00:06
Archive generated by hypermail 2.2.0.