I can not get the RR-Net MK3 to work. It boots and the RR-Net MK3 Codenet server interface is displayed when pressing the C= key. Sofar so good. I change the IP adress to the correct one on my network (192.168.0.210) - outside DHCP "territory" and I see "CodeNet Server waiting for commands". If pressing the RUN/STOP key the Codenet server interface menu exits, BUT if I wait for a while, like a minute or so, it hangs and does not exit when pressing RUN/STOP. It also seems to hang once I use Warpcopy on the PC and the "Send server" command and I get a dialog box saying "Could not send server to C64". I tried this on Windows7 and Windows10.
Also, I tried to change the IP-adress to various adresses on both "sides" with the same result. Furthermore, I tried network setups with a media bridge setup on my spare router but also direct wired connection to the RR-Net MK3 from the main router and different network cables. I also tried this on an older "Breadbin C64" (that I haven't opened and checked the ASSY NO of) with the same result.
- C64C - ASSY NO: 250469 REV4, PCB NO: 252311, CPU: 8500 (week:8833), VICII: 8565R2(week:3088), CIA: 6526B(week:3088, 3288), SID: 8580R5 (week:3588), "PLA+TTL": 271715-01 (64pin IC, week:8832).
- RR-Net MK3(from GGSdata) without "carrier cards": Serial no (?): 1352, MAC: 28:CD:4C:FF:F7:69, Firmware: "RR-NET MK3 CodeNet Server (R38)", jumper in open position,
- WarpCopy0.6 on Windows 10 and also Windows7 PC. (I also tried with Warpcopy II V0.1 Alpha 3 released in 2010 but to no avail - same result).
I see other people have similar problems in the forum regarding RR-Net MK3(Paul Nelsen and Micky). My next idea is to try the "alternative firmware" as I have the correct ASSYNO 250469 to do so. Do you recommend this or know if it solves the problem?
Any other ideas on what to check on how to solve this issue? Any other info you'd like to have to solve this issue?