Question about loading basic programs via FujiNet

[chad5200]

49 minutes ago, mozzwald said:

Looking at your logs there I see that lseek is not called when there were 2 timeouts in a row. The other had a single timeout and received an out of order packet and continued to lseek. Perhaps it's getting stuck after 1 timeout error

Right but here is one where the BASIC load failed with a single timeout:

 

[15:07:47] 
[15:07:47] CF: 31 52 67 00 ea
[15:07:47] disk sio_process()
[15:07:47] ACK!
[15:07:47] ATR READ
[15:07:48] Timeout after 1000 milliseconds. Retrying
[15:07:49] TNFS OUT OF ORDER SEQUENCE! RETRYING
[15:07:49] ->SIO write 256 bytes
[15:07:49] COMPLETE!
[15:07:49] 

 

I am really thinking there are occasions where the "TNFS OUT OF ORDER SEQUENCE" error occurs but the FujiNet does not actually attempt to correct the packet sequence request because the log isn't even showing the follow up "tnfs_lseek" message.  Every time mine fails, it corresponds to that situation.  However, every time that a "TNFS OUT OF ORDER SEQUENCE" event occurs and it is followed up by a "tnfs_lseek success" it succeeds.

 

I really wish I understood the code enough to troubleshoot this.

 

Hoping one of the FujiNet developers would take a look at that part of the code which appears to be around here:

https://github.com/FujiNetWIFI/fujinet-platformio/blob/master/lib/TNFSlib/tnfslib.cpp#L1250

 

and here:

https://github.com/FujiNetWIFI/fujinet-platformio/blob/master/lib/TNFSlib/tnfslib.cpp#L598

 

 

[TZJB]

13 hours ago, mozzwald said:

 

You are using an old version, please use the latest updated yesterday which should have debug output enabled: https://github.com/FujiNetWIFI/spectranet/blob/master/tnfs/tnfsd/bin/tnfsd.exe

 

Thanks @mozzwald the new TNFSD version 23.0207.1 has a working output now, but isn't logging the time. (I can picture you rolling your eyes).

 

@chad5200 if you want to, would you be able to run the new version of TNFSD and capture the output using the Windows Powershell commands that I used previously please, while simultaneously capturing the Fujinet logs?

 

Here is an output sample running GATETEST:-

 

 

Gatetest TFNS output.txt

[chad5200]

11 hours ago, TZJB said:

if you want to, would you be able to run the new version of TNFSD and capture the output using the Windows Powershell commands that I used previously please, while simultaneously capturing the Fujinet logs?

Just did this.  The same FujiNet log where we see a TNFS OUT OF ORDER SEQUENCE! RETRYING with no corresponding "tnfs_lseek success".

 

[16:00:19] 
[16:00:19] CF: 31 52 83 00 07
[16:00:19] disk sio_process()
[16:00:19] ACK!
[16:00:19] ATR READ
[16:00:20] Timeout after 1000 milliseconds. Retrying
[16:00:22] TNFS OUT OF ORDER SEQUENCE! RETRYING
[16:00:22] ->SIO write 256 bytes
[16:00:22] COMPLETE!
[16:00:22] 

 

and now here is the corresponding timeframe from the TNFS log which just shows a bunch of READs:

 

192.168.1.176 s=18be c=21 q=e3 | REQUEST cmd=0x21 TNFS_READ
192.168.1.176 s=18be c=21 q=e4 | REQUEST cmd=0x21 TNFS_READ
192.168.1.176 s=18be c=21 q=e5 | REQUEST cmd=0x21 TNFS_READ
192.168.1.176 s=18be c=21 q=e6 | REQUEST cmd=0x21 TNFS_READ
192.168.1.176 s=18be c=21 q=e7 | REQUEST cmd=0x21 TNFS_READ
192.168.1.176 s=18be c=21 q=e8 | REQUEST cmd=0x21 TNFS_READ
192.168.1.176 s=18be c=21 q=e9 | REQUEST cmd=0x21 TNFS_READ
192.168.1.176 s=18be c=21 q=ea | REQUEST cmd=0x21 TNFS_READ
192.168.1.176 s=18be c=21 q=eb | REQUEST cmd=0x21 TNFS_READ
192.168.1.176 s=18be c=21 q=ec | REQUEST cmd=0x21 TNFS_READ
192.168.1.176 s=18be c=21 q=ed | REQUEST cmd=0x21 TNFS_READ
192.168.1.176 s=18be c=21 q=ee | REQUEST cmd=0x21 TNFS_READ
192.168.1.176 s=18be c=21 q=ef | REQUEST cmd=0x21 TNFS_READ
192.168.1.176 s=18be c=21 q=f0 | REQUEST cmd=0x21 TNFS_READ
192.168.1.176 s=18be c=21 q=f1 | REQUEST cmd=0x21 TNFS_READ
192.168.1.176 s=18be c=21 q=f2 | REQUEST cmd=0x21 TNFS_READ
192.168.1.176 s=18be c=21 q=f3 | REQUEST cmd=0x21 TNFS_READ
192.168.1.176 s=18be c=21 q=f4 | REQUEST cmd=0x21 TNFS_READ
192.168.1.176 s=18be c=21 q=f5 | REQUEST cmd=0x21 TNFS_READ
192.168.1.176 s=18be c=21 q=f6 | REQUEST cmd=0x21 TNFS_READ
192.168.1.176 s=18be c=21 q=f7 | REQUEST cmd=0x21 TNFS_READ
192.168.1.176 s=18be c=21 q=f8 | REQUEST cmd=0x21 TNFS_READ
192.168.1.176 s=18be c=21 q=f9 | REQUEST cmd=0x21 TNFS_READ
192.168.1.176 s=18be c=21 q=fa | REQUEST cmd=0x21 TNFS_READ
192.168.1.176 s=18be c=21 q=fb | REQUEST cmd=0x21 TNFS_READ
192.168.1.176 s=18be c=21 q=fc | REQUEST cmd=0x21 TNFS_READ
192.168.1.176 s=18be c=21 q=fd | REQUEST cmd=0x21 TNFS_READ
192.168.1.176 s=18be c=21 q=fe | REQUEST cmd=0x21 TNFS_READ
192.168.1.176 s=18be c=21 q=ff | REQUEST cmd=0x21 TNFS_READ
192.168.1.176 s=18be c=21 q=00 | REQUEST cmd=0x21 TNFS_READ
192.168.1.176 s=18be c=21 q=01 | REQUEST cmd=0x21 TNFS_READ
192.168.1.176 s=18be c=21 q=02 | REQUEST cmd=0x21 TNFS_READ

 

By the way, here is the settings I use on the IntelBurnTest to best force the failure.  Notice how I set it to Custom, 200 MB, and Times to run is 100.  This causes the test to quickly run, pause, run, pause, etc, essentially causing a stutter.

 

[TZJB]

Nothing actually to see there! You should not really have a stutter with your machine specifications. This is looking more and more like a Windows issue. As a suggestion look at the Resource Monitor and see what the CPU time is being used by and whether it's needed?

 

Other than that, and it would take some time, but maybe image the Windows boot drive on to a second drive with Macrium Reflect Free (with the verify image option), and try a Windows reset to erase anything that shouldn't be there? Then you can compare the performance of the two installations.

 

Reflect offers restore options so you can do that at any time by either making the machine bootable for Reflect or creating bootable Reflect media.

 

Out of interest have you looked to see if there are any common issues with your PC motherboard?

[DjayBee]

34 minutes ago, TZJB said:

image the Windows boot drive on to a second drive with Macrium Reflect Free (with the verify image option), and try a Windows reset to erase anything that shouldn't be there?

Before doing this I would temporarily create a new Windows account and retry it running tnfsd with this account.

[chad5200]

I've already moved on to using a Raspberry Pi with the TNFS image on it.  So I am all good now.

 

But it's just interesting to see how this is behaving with at least my PC.  Maybe someone else will encounter the same issue in the future and this thread will be a place to discuss further.

 

[chad5200]

Happy to report that this update posted by @mozzwald has fixed my issue!