New NMI handler / .commands (Page 14 of 15)

Hi everybody

I'm sorry to say that I was exited a lot by trying this nmi.sys. I've read almost all of the 14 pages and was frustrated because I cannot have esxdos 0.8.6 working on my spectrum and first versions of nmi.sys wanted that version....Then I was happy to see that the latest version is working on my (real 48K). But I am ... disapointed.

1 - EDIT does not work, one have to press SHIFT 1, 1 alone should do the job (as the old nmi.sys)
2 - 64 chars is useless as one said before, half of screen is empty and LFN is not supported. Even if it was, I think this'll be useless
3 - Speed, this nmi is a lot slower that the old one. Just for this reason I will not use it.
And speed is a concern, I have many and many files in many and many folders (so I like the 1 feature of the old nmi)

4 - Keys, why not having cursor keys working. I guess the default is to use the joystick, but both cursor + joystick could work. No need to redefine keys
5 - When leaving a folder (EDIT) the selected folder is not the one we just left... It is so easy to implement such a feature !!!

I guess that  key redefinition (except for EDIT ...) + conf load/save + use of keydef costs a lot.
Having joystick + cursor hardcoded should be sufficient and easier (I had not my joystick at first try...)

I guess also that 64 chars is the reason of slowness. Too bad because 32 chars are enough.

Wasted bytes for 64chars + config maybe could have been used to support LFN ?

Fixing EDIT, adding cursor keys + joystick, returning back to 32 chars and speed could really make your nmi really great !!!

Anyway, I don't like to be negative but I had to. Maybe you'll listen to my arguments...

Is the code of the NMI open source ?

Is your enhanced version of NMI code source available ?

Thanks and best regards

Hi Luzie

> I think you should have a look at these alternative NMI-Handlers which offer LFN-Support: http://board.esxdos.org/viewtopic.php?pid=1553#p1553

I do not search (at all) for lfn support. But just because I'm curious, I'll have a look to your link. So thanks for that.

> The author of this NMI handler has already written that he see support for LFN should come from esxDOS itself ...

Yes, before writing my post, I had read that in the whole thread. But since esxDos does not (yet) offer LFN, I think (but may be wrong) that the speed problem of this NMI handler is due to the 64 chars feature that is useless without LFN

> I like this "Dr Slumps NMI navigator" here. "Dr Slumps NMI navigator" has so many additional features against the original "Old/Original NMI navigator" like file- and directory-delete, create directory, integration of "TR-DOS Navigator"-Bootdisk etc. For me "Dr Slumps NMI navigator" is still one of the Masterpieces of Utility-Software from the last years.

Yes, of course I'm sure there are some great features in that handler. And I could like a lot this handler if only it was as fast as the old one (it is more than 2x slower !).
Btw I couldn't create a folder...

Thanks for your answer, I'm still waiting for a possible answer from David to my 5 questions
(Speed, Config, Dual key / joystick, Edit, folder focus on back). I hope he'll had time for that.

And maybe the most important question about ability to view / modify / patch his code.
(github ?)

Btw I'm a software engineer and am currently coding since one month an attempt of a modern emulator / C++ IDE for ZX Spectrum (https://github.com/hsaturn/klive).

This why I'm concerned by the avalability of the source code (in order to fix myself what I see as problems).
This is also why I'm concerned about ergonomy of the handler which I think can be enhanced.

Best regards

Here´s my HACKED version of INIT for "Dr. Slumps New NMI handler v.0.0.17" so it starts on esxDOS 0.8.9:
Download: https://forum.tlienhard.com/phpBB3/down … p?id=12122

Just copy this INIT over \sys\nmi\init.

WARNING: This only a HACK, which changes Byte of esxDOS-Version-Check on adress #3A (=Char "8") from value #38 to value #39 (=Char "9"). It´s not tested any further from me, and I don´t give any warranry that "Dr. Slumps New NMI handler/NMI navigator" in last Beta-Version v.0.0.17 works OK together with esxDOS v0.8.9 in all concerns!

Now we can get:

Dear david_ps,

great to hear from you!
I'm looking forward to any news regarding your navigator.

Regards
Luzie

btw. Maybe you can have a look here at my question: http://board.esxdos.org/viewtopic.php?id=1033 "TRDBOOT.BIN - How does it work?"

Hello,

Update release of NMI navigator, v.0.0.18:
https://www.dropbox.com/s/1x7bg5i0pheb9 … 8.zip?dl=0
Changes:

• Updated \SYS\NMI\init to detect 0.8.9 esxDOS version

• Added \SYS\NMI\old089.sys to able to load old NMI navigator for 0.8.9 esxDOS version

• Added \SYS\NMI\enter option to open .SCL disk images

Packed release of custom module, v.0.0.18 (it is identical to the version v.0.0.17):
https://www.dropbox.com/s/gh3npvmrqm5mg … 8.zip?dl=0

Updated README_NMI.txt:
https://www.dropbox.com/s/lm5laqpeop549 … E.txt?dl=0
Please read it! It contains an instruction manual and explains the operation of all the keys.

ESXDOS v0.8.9 system configured with my NMI navigator and utilities:
https://www.dropbox.com/s/a3geuwl3a6wdu … 9.zip?dl=0

Thank you for your answer. And for the new version of your Navigator. Will try it soon!

I think I found the cause:

Files sys\nmi\help1.scr, help2.scr and help3.scr are missing in your Download package "ESXDOS v0.8.9 system configured with my NMI navigator and utilities: https://www.dropbox.com/s/a3geuwl3a6wdu … 9.zip?dl=0

but they are present in your package "Update release of NMI navigator, v.0.0.18:
https://www.dropbox.com/s/1x7bg5i0pheb9 … 8.zip?dl=0

TRDBOOT.BIN is TR-DOS Navigator executable, binary code, it isn't a TRD Image.

When the appropriate system call is called, BETADISK.SYS loads TRDOS54T.KO (esxDOS TR-DOS Emulator) using configuration stored in CONFIG/TRDOS.CFG. Emulator automatically loads TRDBOOT.BIN if Boot is present (there is an option to change it to load always). In esxDOS v0.8.9, TRDBOOT.BIN is loaded at address $6000 with SP pointing to $FF32, then controll is passed to address $6000. TR-DOS Navigator start running.

Hello All, I have a question - I am using Mac to create SD card with esxdos, nmi and all other files; however, it seems Mac creates some files, which are not visible under Mac, but in my zx spectrum, e.g. I have esx089.nfo file (ok) and then _esx08~1.nfo (not ok). It happens for all the files.

Is there any way to get rid of those?
Thanks, M.

No solution "hide files", but maybe a solution to delete them before removing SDCard from Mac: https://discussions.apple.com/thread/1574764 "Q: How to stop Mac OS from adding hidden files to SD cards?":

Do you mean copy and overwrite both NMI folder and NMI.sys from your dropbox to the SYS folder on the sd card? I assume I should check if the hidden files and folder are visible, correct?

Is it enough too just copy one file nmi.sys (I see that content of NMI folder is basically the same as 0.0.18 version)? I have already NMI 0.0.18 and esxdos 0.8.9 installed.