LFN support doesn't need the extra divMMC memory to work. Up until v0.12, I wasn't using the additional memory banks as I didn't know about them. My NMI browser saved the RAM contents to the SD card, letting me use 16k of memory from address 49152 to store the 8.3 filenames and their long file name descriptions. This is why there is a limit of files the browser can show - I can only fit so many files in 16k. When you exited the NMI, the RAM contents were reloaded back from disk.bytedelight wrote: ↑Wed Jan 27, 2021 6:18 pm I've not read the complete thread yet (45 pages!) - as said, it's extremely busy at this moment - but is there no way of getting LFN working on an interface with 128K RAM?
velesoft gave me the information to access the additional memory banks, so I used these to back up the RAM to these additional banks instead of writing the RAM to the SD card. This made things quicker and also fixed the issue where writing the RAM to the SD card took up to 18 seconds on some brands of card.
I develop the browser primarily using the Fuse emulator and on my ZX-UNO. Both of these implement esxdos/divMMC with 128k of extra memory which is what I'm targetting.
So to recap, you don't need 512k of memory. This browser only needs the standard 128k that divMMC devices typically support.