3 posts tagged with "compatibility"

One of the most useful ways to make Spectranext easier to adopt is to support the tools people already use. That is why esxDOS-compatible dot-command support is being implemented.

The goal is not to reimplement esxDOS, or to replace Spectranext's virtual filesystem. It is to let a familiar .dot utility run, make its usual calls, and see the files supplied by Spectranext: the RAM and flash overlay, ROM filesystem, network mounts, and the rest of the VFS.

HTTPS mounts are now possible on original Spectranet hardware.

Spectranext makes publishing resources much easier: host a folder on the internet, and the cartridge can mount it over HTTPS. That is good for new software, but it creates the same kind of problem the Spectrum 128K faced: developers want to use the newer capabilities, while still reaching the widest possible audience.

If a game, tool, catalogue, or update channel only works on Spectranext, it leaves original Spectranet users behind. That is not great for developers, and it is not great for users either.

Spectranext now supports Spectrum Next.

This was implemented with the help of an external tester, who provided access, testing, and feedback on real ZX Spectrum Next hardware while the compatibility work was being developed.