... them. Given that these are simple mathematical functions, I'm hoping to find working code to reuse.

Me: The good news is that the comparison, io, memory, and stack unit tests are all passing. I think I will learn more by getting the interpreter and compiler working.

Claude: Good plan — the math can ...

Thanks, MIT is a fine choice - visual6502 uses it, for example.

For memory allocation, I was thinking of TOP, LOMEM and HIMEM kinds of pseudo-variables. In some cases users are expected to PEEK the respective zero page locations to figure out where things are. In some cases one might use a string ...

... The other approach is to use a predefined linearly allocated file, or more likely a second partition with _no_ file system as a flat 24-bit memory pool. Still a lot of thinking to do about that one, and to be of usable speed it would probably require a DMA system, but it would require only 32k ...

... you automatically check the older records which may have been cleared.

For sanity's sake I keep copies of fsi_next_cluster and fsi_free_count in memory, and rewrite them after each allocation. At the last test - because it's very easy to break the entire filing system if I get something wrong ...

... call)
The CREATE system call (new processes)
The VFS interface to the I/O (currently, only the WRITE call has been tested)
The GETMEM system call (memory allocator). FREEMEM hasn't been tested yet.

The code file is a little disorganized - I was adding syscalls to the bottom, and there are two or ...

... compiler is 2 files of 2500 and 4100 lines respectively. I can not compile the compiler on the '816 system as it takes many hours and runs out of memory. The editor compiles in a few minutes.

And that's sort of where I'm at today, but the platform has moved to RISC-V (and ARM32) with memory sizes ...

... then that we can move to other FAT sectors, and then with deleted files from a full disk...

Note: LYA is a macro that loads Y:A as a pointer to memory, usually a 32-bit int. It gets used _everywhere_...


;-----------------------------------------------------------------------
; f_alloc ...

... The FSI is usually the sector following the VIB (it is on my disks).
(To avoid too many reads and writes to the disk, keep these two variables in memory).
FSI_Next_Cluster appears to hold the last cluster allocated, not the next free space. It's where MS say we should start looking for new space ...

... are alive than can fit into available core (RAM). Swapping is characteristic of older systems with small amounts of RAM. Demand paging brings into core parts of a program as it runs. Demand paging works in conjunction with virtual memory and is characteristic of most systems since the latter 1980s.

... other.

We maintain copies of FSI_Next_Cluster (where the system should start looking next time) and FSI_Free_Count (how many clusters remain) in memory, but we _must_ write the FSI_Free_Count cluster back each time we deallocate files.

So there are a total of a minimum of four sectors written to ...

... issue that's making me want to consider FAT. So, I'm still making a decision. I'm not sure FAT will be comfortable to work with with such modest memory resources, and I still need to get to grips with it. )))). I've mastered the process of writing memory blocks to HDDs and compact flash drives in ...

... issue that's making me want to consider FAT. So, I'm still making a decision. I'm not sure FAT will be comfortable to work with with such modest memory resources, and I still need to get to grips with it. )))). I've mastered the process of writing memory blocks to HDDs and compact flash drives in ...

... 16Kb) with the last six bytes set to the reset/nmi/irq vectors from his image. I concatenated that to the 32Kb Taliform image (leaving 16Kb of low memory for the emulator etc). I configured the emulator to use the 16Kb address space (14 constant MBITS) at a fixed location ($4000 constant MBASE ...

... things.

You will also have to enact strict rules about how one black box communicates with the other...effectively imitating in hard-coded memory regions what the 65C816 can do with stack operations. When I messed with this on the 65C02, I strictly used parameter blocks, even when it was ...

... FAT.

A third approach sacrifices the ability to use undelete utilities. Instead of simply marking deleted files as deleted, we reallocate the memory at delete time (marking the directory entry with zero for file size and cluster pointers). We don't change FSI_Nxt_Cluster so we keep writing new ...