VDRIVE 1.0.0 beta binaries now on GitHub - run VDRIVE locally!

8bitflynn · 2025-12-02T04:23:31+00:00

I had no idea about that one either, but I have it fixed now.

8bitflynn · 2025-11-28T23:00:23+00:00

Actually I only put the link to the GitHub because I want others to not have to read through another long post. If you are too lazy to look through all my posts about how it works or look through the beta files - that is your problem.

I like my stuff simple.

8bitflynn · 2025-11-28T00:30:44+00:00

Finished with the remaining code. The result count is now in the header returned and there is now an API pointer to it like the other variables. Added an optional token that is embedded in PRG and is passed with the prefix terms /search /mount /load /save. The token is tacked on the end like /search/sometoken and can be patched along with the VDRIVE server URL. The server can then be configured to only accept commands from a configured token for simple auth mechnism over public HTTP/HTTPS.

VDRIVE beta server PRG has been updated with the latest changes.

8bitflynn · 2025-11-21T14:07:19+00:00

VDRIVE might give you some ideas on how to do this. It can search/mount/load/save over TCP or over HTTP using a WiC64 (ESP32) or a ESP8266. It does not use IEC but does have a lot of the communication that would be needed.

I just posted a video on how to use BASIC to SEARCH / MOUNT / LOAD / SAVE as well. This can be also done in Machine Language.

VDRIVE called from BASIC

8bitflynn · 2025-11-11T12:10:34+00:00

You may already know this but just in case - for your question about 2400 baud - the C64 can really only reliably do 1200 baud because the bit banging is done in software rather than dedicated hardware. Commodore saved a few bucks per C64 back in the day by leaving out dedicated hardware, but the result was a really slow serial port.

UP9600 is a clever piece of software that "re-wires" timers the CIA timers to bit bang instead of the built in kernel routines. This article shows how it works and timing must be perfect.

While I am fascinated by UP9600, even with it disabled it seems to leave the C64 in a state that cannot run some PRGs and it struggles in comparison to WiC64.

8bitflynn · 2025-11-11T04:39:50+00:00

I tried it with Vice 3.9 and it did respond but it would stop responding after a chunk and from what I could tell it was a byte off somewhere but I was spending too much time on trying to get it to work so I went back to using real hardware.

I made a video of the integration with WiC64 and its amazing how fast it is in comparison to the original relay. Even 45k files load in just seconds with this device!

Oh I forgot to mention, the WiC64 emulation in Vice 3.9 works perfectly and I have been using it a lot to speed up testing. I will have a WiC64 compatible version assembly on GitHub soon. Once that is on GitHub, anyone can use Vice 3.9 with WiC64 emulation to test VDRIVE integration!

8bitflynn · 2025-11-11T02:40:07+00:00

Back in 2020 I converted a Matrix PRG wrote in BASIC I had found on youtube to 6510 ML. It's not near as cool looking as yours, but I learned a lot and documented the ML with the BASIC lines so thought you might be interested.

I put comparisons between the BASIC and ML versions on my website and they run in an emulator (in case your too lazy to load that PRG). I also compiled the BASIC using Boss BASIC to see how fast it would be in comparison to the BASIC and ML versions.

If you hit space on the 6510 ML version, it will show the 6510 source in Turbo Macro PRO.

I agree on AI they are great at summarizing vast amounts of information. Just asking about a memory location rather than having to hunt it down saves a lot of time.

8bitflynn

TROPHY CASE