Ich habe verschiedene FMS mit dem #FujiNet N: Handler getestet.

Bis jetzt habe ich getestet:

Es funktionieren korrekt:
* Atari DOS 2.0S, DOS 2.0D[1]
* Atari DOS 3
* Atari DOS 4
* BeweDOS 1.30
* MyDOS 4.50 und 4.55 beta 4.
* OSS DOS XL 2.1
* OSS DOS XL 4.1
* ICD SpartaDOS 1.1HS
* ICD SpartaDOS 3.2d, 3.2f, 3.2g, 3.2.gx, 3.3 Pro
* Eclipse TOP DOS 1.5
* Turbo DOS XE
* LiteDOS 3.x (Hallo Mr. Atari!)
* XDOS 2.43 (Hallo StefanD!)
* DOS II+/D (Hallo StefanD!)

1] Das DUP von DOS 2.0D wird über den N: Handler geladen und kann daher nicht verwendet werden. Aus diesem Grund habe ich die N*-Utilities geschrieben.


Disketten mit jedem dieser FMS sind auf atari.apps.irata.online im Ordner DOS verfügbar.

Das, was aus irgendeinem Grund nicht funktioniert hat:
* Bibo-DOS (getestet 5.4, und 6.3)

Gibt es etwas, das Sie alle verwenden, das nicht getestet wurde?

-Thom

---

I have been testing different FMS with the #FujiNet N: handler.

So far, I have tested:

Working correctly:
* Atari DOS 2.0S, DOS 2.0D[1]
* Atari DOS 3
* Atari DOS 4
* BeweDOS 1.30
* MyDOS 4.50 and 4.55 beta 4.
* OSS DOS XL 2.1
* OSS DOS XL 4.1
* ICD SpartaDOS 1.1HS
* ICD SpartaDOS 3.2d, 3.2f, 3.2g, 3.2.gx, 3.3 Pro
* Eclipse TOP DOS 1.5
* Turbo DOS XE
* LiteDOS 3.x (Hello Mr. Atari!)
* XDOS 2.43 (Hello StefanD!)
* DOS II+/D (Hello StefanD!)

[1] The DUP of DOS 2.0D loads over the N: handler, and thus can't be used. This is why I wrote the N* utilities.

Disks containing each of these FMSes are available on atari.apps.irata.online in the DOS folder.

The one that didn't work for some reason:
* Bibo-DOS (tested 5.4, and 6.3)

Is there anything that you all are using that hasn't been tested?

-Thom

Hallo -Thom,

prima Arbeit!!
great job!!

tschak909 hat geschrieben:* Bibo-DOS (getestet 5.4, und 6.3)

Hast Du bei BiBoDos 5.4 Normal und Fast Version probiert?
Did you try normal and fast Version with/ at BiBoDos 5.4?

Normal ist die Variante welche besser kompatibel zu DOS 2.5 ist.
Normal is the variant which is better compatible to DOS 2.5.



Achtung! Nach den ersten Sektoren ist 10 sec Pause beim Laden
Attention! After the first sectors there is a 10 sec pause while loading.



dl7ukk

Ich habe versucht, eine Diskette mit BiboDOS 5.4 (Normal) und dem N: Handler aus fnc-tools.atr zu erstellen. Der Handler lädt, aber es sieht so aus, als ob der Relocating-Handler irgendwie einen Teil des FMS verwischt. Der Quellcode für den Handler, ist hier:
https://github.com/FujiNetWIFI/fujinet- ... andler/src

Ich vermisse DOS 2.5.
Ansonsten sind alle wichtigen DOS Versionen dabei.

I am missing DOS 2.5.
Other than that, all important DOS versions are included.

The DOS list above is not correct, the correct list is in this thread:
viewtopic.php?f=3&t=10679

Hi Thom,

yesterday I played a bit with the FNC tools. Very nice, the tools support the XDOS command line - and there are really many tools

Here are some issues I found:
1) I can't boot the XDOS 243.atr image from the TNFS-Server (on an unmodified 800XL), it gives me "Boot Error" when loading the first or second sector. But the Atari DOS 2.5.atr image works.
2) The FMOUNT help says, there should be spaces between the parameters. This doesn't work - I need to use commas instead of spaces. I would prefer spaces if possible (XDOS supports spaces and commas).
3) FINFO says 140K for SS/ED disks, 130K is correct
4) NDIR should display, if the entries are files or dirs (e.g. display "DIR" instead of dir entry size 4K)
5) NCD: Often I forget the trailing slash and thus NCD doesn't work - perhaps NCD could append it, if it's not there? (Same with other dir tools like NDIR)
6) NDEL help says, it's used to delete dirs. But in the example, a file is deleted, so it's for use with files, not dirs. (And there is NRMDIR.)
7) After playing around a while with NCD, NPWD and NDIR, all paths for N1:, N2: and so on are the same, and NDIR doesn't work any more: FUJINET IS NOT RESPONDING or SIO ERROR is displayed - in the first case, the disk rotate button also didn't work any more.
8.) When using tnfsd.exe with a write enabled ATR, the ATR can't be used in Altirra after mounting it on a drive. I need to stop tnfsd.exe (press Ctrl-C in the cmd window). Does tnfsd flushes the ATR file (immediately) - i.e. all contents from the Atari is written to the ATR even if I abort tnfsd? (It seems so.)

I found the FNC tools also here:
tnfs://atari-apps.irata.online/fnc-tools.atr
https://github.com/FujiNetWIFI/fujinet- ... -tools.atr
Are they all the same?

Hey Dietrich!

(1) I'll fix the copy of XDOS on atari-apps.
(2) The command line tools use commas instead of spaces because filenames can contain spaces. I need to update the documentation.
(3) Ok
(4) On the N: rewrite (make sure you are using latest firmware) directories are shown with a /
(5) I can't do this, because you can literally use NCD to point directly to a file resource, for operating systems and programs that think that only D: can support filenames. This is intentional.
(6) I will update documentation.
(7) That is very strange. Can you give me a reproducible test case?
(8) yes, all operations over D: are immediately flushed over TNFS.

and yes, the two copies of fnc-tools you've linked are the same.

Keep in mind, I am rapidly developing all of this, and so yeah, there are bugs, they will be ironed out over time. Thank you for attempting to use them!

It's worth noting that on DOSes that can support N:, the N: handler will translate filenames to 8.3 and back. This isn't perfect, but with your help it can be refined.

To see, in XDOS, literally do an NCD somewhere, and then do a DIR N:

-Thom

CharlieChaplin hat geschrieben:Ich vermisse DOS 2.5.
Ansonsten sind alle wichtigen DOS Versionen dabei.

I am missing DOS 2.5.
Other than that, all important DOS versions are included.

I will make a version of DOS 2.5.

Keep in mind, that because DUP overwrites the N: handler, it can't be used in the DUP menu for DOS 2.0S, 2.0D, or 2.5.

-Thom

Hello Thom

tschak909 hat geschrieben:Keep in mind, that because DUP overwrites the N: handler, it can't be used in the DUP menu for DOS 2.0S, 2.0D, or 2.5.

Doesn't DOS 2.xy use MEM.SAV to save whatever DUP would overwrite?

Sincerely

Mathy

MEM.SAV only comes into play when (B)RUN CARTRIDGE is used, not if you use anything in DUP.SYS.

So for DOS 2.0 or 2.5, you can gladly use N: outside of DUP just fine, and MEM.SAV can preserve the N: handler when you come back from DUP.

MyDOS, DOS XL, OS/A+, SpartaDOS, XDOS, and others don't have this problem.

If somebody has a solution to this problem, have at it, I would LOVE to be able to use N: from inside DUP.

Mind you, the N* utilities (like NCD, NPWD, NCOPY, NDIR etc.) do not have this problem because they talk to FujiNet directly over SIO, it's why I wrote them.

-Thom

(There is also the fact that I have taken a copy of the N: handler and started on a NOS, which does not contain D: at all, only N:... this would be nice to have help finishing, e.g. for the command processor)

also, just tested XDOS 2.43N on atari-apps, and it boots for me. It may be trying to shift into high speed (in which case, set the divisor lower such as 9 in the web admin)

-Thom

I found the reason, why the XDOS 2.43 image doesn't boot on my Atari: When I call the SIO Status command on the mounted drive with XDOS, Fujinet responds $20 $ff $fe $00.
But XDOS looks at the 3rd byte of the answer in DVSTAT (this is the timeout value for formatting a disk). If it is $fe, XDOS assumes an XF551 drive and try to use the XF high speed protocol, which of course doesn't work with Fujinet ($d9 is also used for my HyperXF mod of the XF551.) As I remember, Bibo-DOS also uses this byte to determine, if an XF551 is connected - thus Bibo-DOS may have problems with Fujinet also. Normal drives have $e0 as timeout value.

Now I issued a status command on all my mounted drives (see screenshot):
D1: to D5: respond with $fe, D6: and D7: with $e0 in the 3rd byte. D6: is fnc-tools from atari-apps, D7: is XDOS.atr (DD) from my local TNFS server and D3: is the XDOS 2.43.atr from atari-apps.

1. Can you tell, in what cases Fujinet sets $fe resp. $e0 in the 3rd byte of the answer of the SIO status command?
2. With XDOS, you can turn off this XF551 detection: Boot the XDOS disk, go to the XDOS command line, then enter ">711 11" (without quotation marks), then rewrite XDOS with the "INI" command.

(My Fujinet version is 0.5.e6b3e94e 2021-01-22 01:42:35)

We always send this status byte, as can be seen here:
https://github.com/FujiNetWIFI/fujinet- ... k.cpp#L123

-Thom

Oh, sorry - I forget, that D6: and D7: are mapped to the RAM disk by QMEG-OS by default. So it's always $fe.

[(7) That is very strange. Can you give me a reproducible test case?

I used NPWD 2: instead of NPWD N2:. This indeed displays the path from N1:. So it's my fault
The FUJINET NOT RESPONDING occurs from time to time, but I can't reproduce it reliable.

(4) On the N: rewrite (make sure you are using latest firmware) directories are shown with a /

[/quote]
Hm, in my NDIR lists, there are no /. After setting NCD N:TNFS://ATARI-APPS.IRATA.ONLINE/, I get this when using NDIR:

I have the latest firmware 0.5.e6b3e94e 2021-01-22 01:42:35 (with the green and red selection bar in CONFIG).

Yup, I noted this with the latest firmware, and have made a patch for it in the master branch.

I am trying to get more fixes out for N: before I ask for a build to be made.

-Thom