176

Re: New NMI handler / .commands

Hello to everybody, new release of NMI navigator, v.0.0.12:
https://www.dropbox.com/s/e8g3g805jyi70 … 2.zip?dl=0
https://www.dropbox.com/s/f9j461srsh80x … 2.zip?dl=0
Changes:

  • Configure navigator keys option (K) saves configuration. It uses nmi.cnf file in /sys/nmi

  • Configure navigator keys option (K) checks not available and used keys

  • Max overlay size changed to 774 bytes, custom module (M) can use it.

  • ENTER and view (V) opens file with hexview if filetype is unknown

New dot command hexview, v0.1:
https://www.dropbox.com/s/x8o8zd5pdbbvf … 1.zip?dl=0
It shows a hexadecimal dump of a file.  Cursor up and cursor down moves to previous and next screen, and BREAK exit.

hexview v0.1 By Dr. Slump 2017

Usage: hexview [filename]

New dot command drives, v0.1:
https://www.dropbox.com/s/5r6nfshq52r2x … 1.zip?dl=0
It show all detected drives/devices by esxDOS, using various methods.

drives v0.1 By Dr. Slump 2017

Usage: drives [args]

-1 use M_DRIVEINFO syscall (*)
-2 use M_GETSETDRV syscall
-3 use DISK_INFO syscall
* default option

-? this help info

177 (edited by Spezzi63 2017-12-02 19:40:41)

Re: New NMI handler / .commands

Hello,
I've tried something wink
Everything is running smoothly.
I did not test the saving of the user-definied keys.
Up soon,
Günter

178 (edited by Spezzi63 2017-12-11 18:18:15)

Re: New NMI handler / .commands

Hello,
A request has been made as to whether it is possible to install a key function in the NMI browser to empty the TAP-Slot.
Afterwards REALTape could be accessed again.
http://forum.tlienhard.com/phpBB3/viewt … 761#p33761
I think that it would be very useful.
Bye for now,
Günter

179 (edited by david_ps 2017-12-12 12:31:38)

Re: New NMI handler / .commands

Spezzi63 wrote:

Hello,
A request has been made as to whether it is possible to install a key function in the NMI browser to empty the TAP-Slot.
Afterwards REALTape could be accessed again.
http://forum.tlienhard.com/phpBB3/viewt … 761#p33761
I think that it would be very useful.
Bye for now,
Günter

I think that's possible, I need to do some tests before.
UPDATE: Tests ok, available on next release!

180

Re: New NMI handler / .commands

New release, v0.0.13:
https://www.dropbox.com/s/fod0l87v5n71w … 3.zip?dl=0
https://www.dropbox.com/s/6zfgyhl597uhe … 3.zip?dl=0
Changes:

  • SS+I detach .TAP from input

  • SS+O detach .TAP from output

New dot command, rm, v0.1:
https://www.dropbox.com/s/b9cna3nwn8286 … 1.zip?dl=0
rm v0.1 By Dr. Slump 2017

Usage: rm [OPTIONS]... [FILE]...

Remove the FILE(s)

-f ignore nonexistent files and
   arguments, never prompt
-i prompt before every removal
-r remove directories and their
   contents recursively
-d remove empty directories
-v explain what is being done
-? display this help and exit

181 (edited by Luzie 2017-12-12 15:09:59)

Re: New NMI handler / .commands

david_ps wrote:

New release, v0.0.13:
New dot command, rm, v0.1:
rm v0.1 By Dr. Slump 2017

Thank you! Tried both (NMI.SYS and .RM DOT-Command), but it´s not working for me to remove an empty directory hd0:\NMI000 (which is an empty directory)
It displays OK, but directory still exists. (esxDOS 0.8.6 Beta 4)

Update: I found my problem with .RM-Command with using -v parameter for verbose:
It shows only 0 OK:, 0:1 when I entered: .rm -f nmi000
but with -rm -v nmi000 I got : Is a DIRECTORY, 0:1
With -rm -f -v nmi000 I got : cannot remove ´nmi000´: Is a directory
I have to add -d: This works for me to remove this empty directory: .rm -d nmi

182 (edited by david_ps 2017-12-12 15:18:24)

Re: New NMI handler / .commands

Luzie wrote:

Thank you! Tried both (NMI.SYS and .RM DOT-Command), but it´s not working for me to remove an empty directory hd0:\NMI000
It displays OK, but directory still exists. (esxDOS 0.8.6 Beta 4)

Luzie, NMI don't remove directories, it remove only files
rm -r directory removes empty/non empty directories
rm -d directory removes only empty directories
I have tested rm command exhaustively and works hmm
Try -v option to show what it's doing

183

Re: New NMI handler / .commands

Ok, wink -f skips errors also

184 (edited by Luzie 2017-12-14 18:43:47)

Re: New NMI handler / .commands

I tried many .TRD-Files with NMI.SYS v0.0.13 simply loading by ENTER.
All I´ve tested crashed with Black Screen showing number 12151.
When I load them with old NMI.SYS, they work. How I can load from new NMI.SYS without TRDN (TRDOS-Navigator)? SS+ENTER?

185 (edited by Spezzi63 2017-12-14 22:33:51)

Re: New NMI handler / .commands

You're right, there is something wrong.

The TRD disk normally starts over the bootfile.
If it does not exist it stops in line 20. With bootfile it works.
The integration of the TRDOS-Navigator was not the best idea.
(With Spectrum 2A you can not control with keys and is frozen.)
And very few opportunities in the TRDOS-Navigator.

Unfortunately, I have not observed handling TRD-Disk for a while sad

186

Re: New NMI handler / .commands

Spezzi63 wrote:

You're right, there is something wrong.

The TRD disk normally starts over the bootfile.
If it does not exist it stops in line 20. With bootfile it works.
The integration of the TRDOS-Navigator was not the best idea.
(With Spectrum 2A you can not control with keys and is frozen.)
And very few opportunities in the TRDOS-Navigator.

Unfortunately, I have not observed handling TRD-Disk for a while sad

I think using TRD Navigator is a good idea. The new nmi menu behaves like that. In nmi menu I press SS+ENT.  Then after a while happens TRD image catalogue (same like in Basic after RANDOMIZE USR 15616) and after the whole catalogue for which I have to wait TRD Navigator is loaded.  Personally, I would skip the catalogue part and would load TRD Navigator straight away.

In the nmi menu, some machine code monitor+memory paging option would be very useful, I think. Otherwise, superb work

187

Re: New NMI handler / .commands

Hood wrote:

I think using TRD Navigator is a good idea. The new nmi menu behaves like that. In nmi menu I press SS+ENT.

Is there a way/key combination to load TRD as behaving with old NMI.SYS? So we can have both options (with or without TRDN).

Hood wrote:

In the nmi menu, some machine code monitor+memory paging option would be very useful, I think. Otherwise, superb work

There´s a monitor from Velesoft: http://board.esxdos.org/viewtopic.php?pid=6#p6
not yet in NMI-menu, and I don´t know if both can work together.

188 (edited by david_ps 2017-12-16 11:10:55)

Re: New NMI handler / .commands

Hello,
Old NMI handler do the following:
· Unmount previous TRD on A via API
· Mount new TRD on A via API
· Autoboot TRD, if fails, open TR-DOS Navigator (/sys/TRDBOOT.BIN), all via only one API call
My handler do the following:
· Unmount previous TRD on A via API
· Mount new TRD on A via API
· Attach .TAP with TR-DOS Navigator to IN (/sys/nmi/TRDN.tap) via API
· If SS pressed, load and run /sys/nmi/boot.bas via API

10 RANDOMIZE USR 15619 : REM : LIST
20 RANDOMIZE USR 15619 : REM : RUN "boot"
30 CLEAR 32171
40 LOAD "" CODE 32172
50 RANDOMIZE USR 32172
60 RANDOMIZE USR 32172

This try to autoboot, if fail, loads TR-DOS Navigator.
· If SS not pressed, load and run /sys/nmi/load.bas via API

10 RANDOMIZE USR 15619 : REM : LIST
30 CLEAR 32171
40 LOAD "" CODE 32172
50 RANDOMIZE USR 32172
60 RANDOMIZE USR 32172

This loads TR-DOS Navigator directly.
My approach fails with some TRD images and with version v0.8.6 beta 5.1. The approach of the old NMI handler does not allow to avoid the autoboot mechanism.
I can try a mixed approach.

189 (edited by david_ps 2017-12-15 15:24:28)

Re: New NMI handler / .commands

Hood wrote:

I think using TRD Navigator is a good idea. The new nmi menu behaves like that. In nmi menu I press SS+ENT.  Then after a while happens TRD image catalogue (same like in Basic after RANDOMIZE USR 15616) and after the whole catalogue for which I have to wait TRD Navigator is loaded.  Personally, I would skip the catalogue part and would load TRD Navigator straight away.

Enter over a .TRD file try to autoboot it.
SS+Enter over a .TRD file skip autoboot and open TR-DOS Navigator.
In both cases, first, .TRD image is mounted on drive A (via API call), then, TR-DOS system is initialized (via BASIC RANDOMIZE USR 15619 : REM : LIST). This second step cannot be omited.

Hood wrote:

In the nmi menu, some machine code monitor+memory paging option would be very useful, I think. Otherwise, superb work

As Velesoft indicates, during the loading of a snapshot (via snapload dot command/NMI pressing ENTER over a .Z80 or .SNA file), is possible to load monitor:
...
1) copy MON file to directory BIN on your disc with esxdos
2) during loading snapshot hold key SHIFT. You will see color lines in border area. Now press key "m" for load MONITOR/DEBUGGER
...
Open it directly from the NMI handler is possible, what is really complicated is to start debugging the program (game) interrupted, omitting the code part of the NMI handler and the esxDOS itself that transfers the control to the interrupted program and, in this case, to the monitor.
If we want to debug running programs (already loaded programs), esxDOS is who should run the monitor, loading it instead of the NMI browser.

190 (edited by Spezzi63 2017-12-15 22:46:22)

Re: New NMI handler / .commands

------------------------------------------------------------------------------------
TR-DOS Navigator V0.75b
User Guide

                        system requirements
                       ================
      TRDN can be used on ZX-Spectrum compatible computers
with a minimum of 48 KB of RAM and is equipped with one
Beta 128-compatible hard disk interface and TR-DOS version
5.01 or 5.03 (TRDN does not work with other TR-DOS versions)
------------------------------------------------------------------------------------

Maybe a stupid question:
With which TR-DOS version do we work under Esxdos?
Bye for now,
Günter

191 (edited by david_ps 2017-12-18 07:29:53)

Re: New NMI handler / .commands

Spezzi63 wrote:

Maybe a stupid question:
With which TR-DOS version do we work under Esxdos?
Bye for now,
Günter

TR-DOS Ver 5.04T in v0.8.5 and v0.8.6
TR-DOS version

192

Re: New NMI handler / .commands

david_ps wrote:

TR-DOS Ver 5.04T in v0.8.5 and v0.8.6

It´s file \sys\trdos54t.ko but which is diffent size in 0.8.5=13285 Bytes and in 0.8.4b4=13638 Bytes

david_ps: The link to you Photo doesn´t work?:
*img=TR-DOS version]https://photos-2.dropbox.com/t/2/AAC_4v … de=5*/img]

193 (edited by Spezzi63 2017-12-18 17:50:30)

Re: New NMI handler / .commands

In 0.8.6B2 the file trdos54t.ko has 13414 Bytes; Apparently not exceptional.
Maybe this file is generated by the API ?

194

Re: New NMI handler / .commands

I don't know anything about it, everything is part of the esxDOS kernel. Please ask Lordcoxis.

195 (edited by Luzie 2017-12-21 21:34:09)

Re: New NMI handler / .commands

I´ve tested v0.0.13 under a real "Spectrum Next Board": Cursor-Keys don´t work here. But with J I could load "load NMI.SYS" and with this Cursor-Keys work.

196 (edited by david_ps 2017-12-26 08:08:56)

Re: New NMI handler / .commands

Luzie wrote:

I´ve tested v0.0.13 under a real "Spectrum Next Board": Cursor-Keys don´t work here. But with J I could load "load NMI.SYS" and with this Cursor-Keys work.

Hi Luzie, I tested all versions on real machines and emulators and works ok. I have a 48k, a 48k+, a superfo ZX Nuvo 128 and a zaxon Just Speccy 128k and cursors works on all.
Try to replace /sys/nmi/nmi.cnf by original one.
Regards,
UPDATE: Luzie, see https://www.specnext.com/spectrum-next- … -bugfixes/ you may have to update the firmware.

197

Re: New NMI handler / .commands

david_ps wrote:

UPDATE: Luzie, see https://www.specnext.com/spectrum-next- … -bugfixes/ you may have to update the firmware.

I discovered that it was my fault: I had to press Caps Shift to get those Cursor-Keys working in the PS/2-Keyboard on my Spectrum Next Board. Maybe later FW-Versions of Spectrum Next will fix this.

198 (edited by david_ps 2017-12-28 21:01:00)

Re: New NMI handler / .commands

New release of dot command hexview, v0.2:
https://www.dropbox.com/s/rzoqhs56m0lxz … 2.zip?dl=0

hexview v0.2 By Dr. Slump 2017

Usage: hexview [filename]

Shows a hex dump of [filename]

Navigation keys:

  ENTER,  BREAK - Exit
  UP,        LEFT    - Prex page
  DOWN,  RIGHT  - Next page
               EDIT    - First page

199

Re: New NMI handler / .commands

Christmas release of NMI navigator, v.0.0.14:
https://www.dropbox.com/s/2iiaubdrz1m94 … 4.zip?dl=0
https://www.dropbox.com/s/5bfxfbz4lqvzc … 4.zip?dl=0
Changes:

  • Max overlay size changed to 765 bytes, need recompile custom module (M).

  • Open a .TRD file now uses same method than old NMI handler. There are three options available:
    ENTER: Try to autoboot disk, if it fails then open TR-DOS Navigator with disk attached to drive A (like old NMI handler).
    CS+ENTER: Enter TR-DOS mode with disk attached to drive A (supported by the API).
    SS+ENTER: Open TR-DOS Navigator with disk attached to drive A (my method revisited).

Known problems:
My NMI navigator works on versions from v0.8.5 to v0.8.6 beta 4. On version v0.8.6 beta 5.1 load .BAS files don't work.

Now, all the TRDs that work with the old NMI navigator should work with the new one. Guys, please check it!

Another question people, do you think it is necessary to create a small manual with the instructions to install it, changes with respect to the old NMI browser, and operation with the keyboard / joystick?

200

Re: New NMI handler / .commands

david_ps wrote:

Christmas release of NMI navigator, v.0.0.14

Thank you very much! Maybe you could think over adding the remove Directory / your .rm command to the NMI-navigator?