Sinclair ZX80 / ZX81 / Z88 Forums

Perhaps a problem with the large card. Does it work with other cards? What format are you using FAT16 or FAT32?

I've had commander crash on me mostly when invalid characters are used for files / directory names

Regards andy

A large number of files make the Commander crash.
Or the machine itself, and the Commander freezing is only a manifestation of the hardware phenomenon.
We have to remember it's not a modern PC after all.
So I just split catalogues into smaller ones. It helps.

I once tried opening a folder with 2000 music files inside it using commander.
After a lovely green led light show and a large puff of smoke it give up the ghost and told me to go F@@@K myself.


I now have many music folders including one labelled "YERZ".


But to be serious I find the commander is a superb piece of software especially when shuffling/copying music files around and in my case the ONLY weak spot is renaming files when using an external keyboard, if a normal keypress style of typing is used as opposed to a fast tippy-tap method then renaming say TEST.STC to DONE.STC, ends up as DDOOONNNEE.STC.
The too-many-chrs effect is a joy to behold and backspace then becomes key of the month.

Oddly enough Toddy Forth exhibits this same phenomenon.
All part of its charm I suppose and I wouldn't change it for anything, along with the tracker and STC compiler this is my favourite piece of software.

I emptied and reformat SDHC 16GB and COMMANDER works properly now. I take it that working near the beginning sectors of flash memory is more better.

Still having question with TAPESCRP ...

Anyone tested this on the ZXpand+ yet?

manic23 wrote: ↑Mon Jul 10, 2017 12:41 pm Anyone tested this on the ZXpand+ yet?

Works for me.

Great program.

One thing I miss: Unfortunately Execute does only work on .P files.

I have files with different extensions that are ordinary program files.

.AS2 ZX Assembler 2 source
.TAS Tasword files
.WS2 WordSinc II.3 files
.BER Berch Assembler source
Etc.

These cannot be loaded with ZXpand Commander.

A better way to find out if the file is a program is to test E-LINE against file length and see if they “match”.

If it’s too complicated to test with E-FILE, then maybe a Force Load command

The file length solution is very clever. It would be a lot of work though. A force load would be much easier. I'd have to check the PIC firmware to ensure that there are no special cases for P files.