Mine was pretty much a copy/paste text dump using print2pdf years ago. I seem to recall I dropped some of the link-dependent stuff; I just wanted an easy-lookup document for personal use.

And yesterday I went digging for the PDF, and have no idea where I stuck it -- it's been a decade or so since I used it, pre-dating my current eBook archive.

If you're getting a copy with usable links, that'd be great! Feel free to ping me if you get stuck anywhere, but it sounds like you've already done more than my quick hack job.

I just used a PDF printer driver. It doesn't have links, but it does look like what you would get with a dead tree version.

Comodo see this as suspicious. Can you talk to Comodo ? The below link which has the GUI file, works without suspicion.



Basilisk II (2015-02-26) for Windows bundled w/ Mac OS 7.5.3
https://www.macintoshrepository.org/7643-basilisk-ii-for-windows-68k-emulator-w-floppy-support

_________________
dosbox turbo

Unfortunately I don't know anyone at Comodo to flag this up with -- best is to flag it as a False Positive through their product or website.

However, Comodo is often bases their detections on other security vendor detections, so they're likely picking up on the Symantec detection.

Symantec has continued to be disinterested in removing their detection.

I would love if this was a more recent version of basilisk ii, but it seems the windows version is being neglected in favor of the macOS builds.

That's because for the most part, the Windows build still works, but the OS X one keeps breaking, so it needs update.

Thanks for making me smile, adespoton!
You did bring it to the point.
Even BII Build 142 does still write HFS floppies on a W10-64 host.
Nobody would have believed we would use Windows to write HFS floppies in the future, when we had our Mac II or similar.

I disagree with the statement "the Windows build still works". It crashes constantly in router and slirp mode, udp tunneling doesn't work at all, and to top it all off I can't even look into fixing any of this because the build doesn't seem to work with either MinGW/MSYS or MSVC.

Basilisk II for Windows feels like an abandoned project.

Are other people having these issues with the latest SDL and SDL2 builds too? This sounds like issues I had with older builds, but I don't use BII on Windows anymore.