David Given

Found it! I was doing this: ``` .byte value@mos16lo ``` `value` was an assembler equate containing a simple number. I guess that for some reason the assembler isn't exposing it...

Actually, if I can add a related feature request... it'd be really nice to be able to use `@mos16hi` and `@mos16lo` on numeric constants as well as symbols. Currently if...

I think I've just run into exactly this issue; the server is reporting a 503 with a non-JSON body, and the error handling in AadInstanceDiscoveryProvider.sendInstanceDiscoveryRequest() is throwing the wrong exception...

It's clearly trying to make a MINGW standalone Windows version rather than a Cygwin Unix-like version. Currently there's no way to tell it which you want; it assumes all Windows...

Right now I'm in the middle of redoing the build system which should, hopefully, fix this and other issues.

That looks like it's the same as the atari 800kB format. See https://github.com/davidgiven/fluxengine/blob/master/src/formats/atarist.textpb#L179. What platform uses it?

It's probably worth copying all of these to the IBM profile.

I've just tried this on my own system, and am seeing the same failures. At least the build pack (with runqemu) still works. This _used_ to work, at least for...

BTW, those unrecoverable errors means that it's failed to correctly load the ramdisk, so it's corrupt. That means that there's no point debugging after that point as it's just going...

It's reading 1024B blocks with a single FDD transfer. These are two sectors each. Except, they're aligned at an odd number of sectors, meaning that there's always a block split...