This is the same as the cracked version from Vendetta, with boot file fix, y2k fix, enhancements for wifi modems like the Strikelink WiFi (make sure to add/connect the DCD pin on the C64 to D4 on the nodemcu for Strikelink WiFi use). Still only 2400 baud, but tested and working. I may take a shot at adding Swiftlink drivers for faster speed in the future. I’ve already hacked the ml and know how the modem drivers work, just a matter of seeing if it plays nice with other modem types. The 2400 baud routines that originally come with this version of DS2 are the proper George Hug 2400 baud routines, so it’s solid at 2400.
For original sysops who don’t want to use files from the Vendetta release, heres the y2k fix information.
In ml-2577, change the following bytes:
a479 – change #$b1 to #$b2
a47a – change #$ba to #$b0
a080 – change #$90 to #$20
UPDATE: An original DS-2 11.6 disk has been confirmed to boot with this dongle. Thanks for sending that info in.
Thanks to Hoy Brothers from 13th Floor BBS for sending me the results of tests on an original C-Net dongle. Between that, some cryptic info I found on old comp.sys.cbm posts, and lots and lots of testing, I figured it out.
This should allow all those oldschool sysops who lost their original dongles (like me) to load their original C-Net disks again. Should work with various versions. Not sure about C-Net 128, but I’d love feedback from anyone who tries this to confirm different versions it runs on. My original C-Net 12.0 runs fantastic now.
Parts needed: 4.7k ohm resistor (1/4 watt should be fine), 10uf non-polarized capacitor (5v minimum rating i assume), 1n4148 diode (the cheap ones you used to get in batches from radio shack), and a female 9-pin serial connector (for the joystick port).
Using the diagram on https://www.c64-wiki.com/wiki/Control_Port
Connect pin 7 to pin 9
Pin 5 -> 4.7k ohm resistor -> Pin 9
Pin 5 -> 10uf Non-polarized Capacitor -> Pin 9 (the resistor and capacitor run in parallel)
Pin 1 -> Anode of Diode – Cathode of diode -> Pin 5
That’s it. Let me know how this works out for you. Remember it plugs into port 2.
Versions confirmed so far:
Well, I finally figured it out, and it wasn’t that complex after all.
In Windows Vice 3.1, make these settings in RS-232 Settings
ACIA Settings -> Off (Do not enable ACIA)
Userport Settings -> Device 1 -> 2400 Baud
RS232 Settings -> Device 1 -> 192.168.0.xx:25232
The xx is your local machine IP. (In windows, check Ethernet Settings -> Hardware Properties -> IPv4 Address)
Then get tcpser going with these settings in command prompt:
tcpser -v 25232 -p 6400 -s 2400 -l 4
Load CCGMS, use User Port 300-2400 and 2400 baud settings.
As with all versions of vice, file transfers do not work. If you want to upload and download programs, get a real c64. 🙂 Or use CGTerm.
Cases for the Strikelink WiFi are now available from
They look pretty cool and come in a variety of colors.
At this time, modems are still out of production, but I hope to resume in the near future.
I’ve sold out of my current run of Strikelink Wifis. I hope to resume production in the near future.
Download link http://csdb.dk/release/?id=158456
I modded CMBBS to 2400 baud (works with the Strikelink WiFi!) and added multiple drive/partition/sd2iec folder support. Multiple U/D Drives, fixes to the user account system to make it more stable. There’s a few bugs. Check out the docs file for what to fix and some other features. The source is included. Sorry, I’m not offering support but if you have a major problem, let me know.
In the interest of allowing more people to enjoy Quantum Link Reloaded, I’ve made a program that patches the Q-link Disk to have the following abilities:
– 2400 baud on the user port
– 2400 baud via Swiftlink
– Use of any drive # besides drive 8 and disabled 1541 fastload.
There’s some bugs in this. The patcher causes Q-Link to not work on my particular sd2iec setup in anything other than the People Connection area (I get a disk error message when switching to another area), but on my other system it works 100% perfectly. So I need people to help test this out and tell me what they experience with their setup so I can pinpoint what external factors are causing this issue.
You must load and run the patcher from the same device # you’re going to be patching, so if you have an sd2iec as drive #10, for example, you need to also load the patcher program from drive #10, then switch to the d64 image of your Q-link disk before running. Planning on changing this for future versions.
This will only work with a .d64 image or 1541 formatted floppy. It will not work with a 1581 disk or .d81 image, or a raw directory on an sd2iec type system, as Q-link stores user data in the directory track #18 and expects it to be there next time it loads. I’d like to get this modified for a future version, where Q-Link would store all data in an actual program file on the disk.
You need to get a QuantumLink.d64 disk image from Q-link.net to run Q-link.
Initial Q-Link Reloaded First Time Setup (The simple version):
- Use Patcher to disable 1541 Fastload and SD2IEC Fix (if needed)
- Set your modem to 1200 baud. (Or 2400 if using Swiftlink)
- Load Q-Link
- Select “Connect to Qlink” from the initial Welcome screen
- Change modem type to the bottom option (Other Command Driven Modems)
- Change Access Number to +5551212 (This isn’t important, just needs to have something there with a + and 7 digits mimicing a phone number).
- Load Q-Link
- At the green screen, type atdtq-link.net:5190 and hit F1 when you connect. (If using Swiftlink, apply patch now before dialing).
- If using 2400 baud user port patch, sign up for Q-Link at 1200 baud, then apply the patch after your first call. The 2400 baud user port patch crashes Q-link on the initial sign up but works fine once you already have an account.
Download the patcher here.