Search results

Honestly, I'm not spending countless hours on it, I'm mostly just posting comments musing about it as that's easier. I've got my Init code written and I'm testing it in Xcode at the moment, so I'll be able to find out if it ought to stay within memory bounds fairly soon. If you can cope with me...

A very thorough job and impressive results! I too have an Apple //c I picked up for free around 1998, it's not as white as that, but maybe not as yellow as many! I did notice the ZX Spectrum with Interface 1 and a Microdrive! For those not in the know, the Sinclair Microdrive was a...

I guess that's a question for @Mu0n . I'm using their repo. In the meantime (to go off-topic) I was musing about how well a PC at the time could handle MOD playback, assuming an equivalent sample playback to a Mac Plus (which is reasonable, since it's pretty simple hardware). My inner loop code...

I read about this on ArsTechnica. There's something like 127K people in the US still using America On-Line (soon to be America Off-Line for them). I imagine that keeping such an old service going is still not going to be loss-making, because you hardly need to update the hardware and the...

Yes, that's what the code does. I can see it substitutes the next va_arg for the literal field width you'd otherwise expect. That's a good point. You can't push a char on the 68K. I can see it doesn't support all of the combinations, but I was only checking for 'l' and 'd'. There's no 'q'...

@Mu0n , @joevt . I did a bit more looking for how sprintf is handled. In <stdio.c> we have: int sprintf(char *s, const char *fmt, ...) { return(vsprintf(s, fmt, __va(fmt))); } int vsprintf(char *s, const char *fmt, void *p) { FILE f; int n...

[ @Mu0n ] THINK C 5 has <stdarg.h> for handling variable arguments. The example on page 268 of the User Manual (which I have a paper copy of): #include <stdarg.h> int minimum(int count, ...) { va_list xp; // Declare arg pointer. int x,min; va_start(xp, count); // init the pointer...

I tried adding the custom command making my CMakeLists.txt file: cmake_minimum_required(VERSION 3.28) project(NanoMacTracker) enable_language(C ASM) add_application(NanoMacTracker nanomactracker.c wc_mod.s nanomactracker.r ) # make the result as small as possible #...

Thank you very much for sparing the time, all the Cmake stuff looks very helpful! OK, thanks again! That'll do the job. I'm likely to define it as __Retro68__ as __MWERKS__ and the other compiler environment defines have a double '__' on either side. It's a good point about being able to...

@bribri . I still don't know how to incorporate hfsutils commands into CMAKE, but instead I wrote a simple shell script which calls hfsutils commands to add a .mod file to the .dsk image. That will do for now. I've been playing around with revamping the MOD tracker prep code as per my comments...

(and @cluster_fsck ), @cheesestraws . The beauty of SAX parsers is that as well as being extremely CPU & memory resource-light, they're well-suited to giving up control, because they function as event-driven systems. The application-side handler gets called for each token, so it'll get called...

SAX JSON Parsers can be well-suited to low-memory/embedded systems. https://rapidjson.org/md_doc_sax.html https://github.com/X-Ryl669/JSON Because they're event-driven they should map quite well to Classic Mac OS.

I was going to use @cheesestraws 's approach to rebuilding my battery by using batteries that have a nub; which you don't need to weld (as I won't be able to do any welding). I was thinking of getting some suitable ones from RS or Farnell along with some other stuff in a combo order, but can't...

@MIST, @Mu0n . I've been modifying the code a bit to free it from the built-in .mod file. I found that the assembly code in prepare probably isn't correct for the Mac. Here's what happens. After Init, all the waveform pointers are stored in sample starts: DS.L 31 and the waveforms themselves...