Quote from: cpcoldie on Yesterday at 22:52I've tinkered a "rom-box" and can confirm the rom version works.I forgot to mention: "...for the uIDE interface".
Quote from: Arnaud on Yesterday at 06:33Hi,I can confirm that works! Thank you!
i think @ervin is right, the decompression is overwriting the stack.
To solve your problem try to set the size of your image to 0, 0 (image size by default) and no args after image:
$(eval $(call IMG2SP, CONVERT , img/transition.png, 0, 0, transition, , ))
I have done this some weeks ago and the size file was OK.
Quote from: kolleykibber on Yesterday at 17:24Never seen an EME-101 before...Very seldom...
https://www.ebay.co.uk/itm/135047634465
Quote from: GUNHED on Today at 13:27Sure, I'll post the results.Quote from: abalore on Yesterday at 20:41Theoretically it is compatible with the X-MEM software with little adjust, just before and after writting, commands for unprotect and protect the flash must be issued via OUT (operation which is done by moving a switch in the X-MEM if I'm not wrong). Anyway, I can send you the source code. Right now I'm working in a |FLASH,"filename.rom",slot command which is installed by running a program from disk and has same parameters than the one used by the X-MEM, so from BASIC there is no difference. I'll send you a PM with the sources when they are finished and tested.
Ah great! X-MEM compatibility is a very nice and decent feature!
Can you please test if ROManager (2.4.6 from 2024) for FutureOS does work with it?
All you need to do is to start ROMananger with your Flash-Box connected. It should show 'Device: X-MEM' in the upper middle of the screen.
Also, can you please try if FutureOS installs correctly when using 'Install to X-MEM'?
In both cases the software protection of the Flash Chip will be used to have everything save...
If it doesn't work then I'm willing to receive your source code and add support to all my software for your Flash-ROM - if you like.
Page created in 0.052 seconds with 17 queries.