Jump to content
IGNORED

#FujiNet Testing and Bug Reporting Thread


Recommended Posts

Anyone who prefers to use AtariAge as their bug reporting thread, can do so here.

 

Please try to provide a concise description, doesn't have to be verbose, but enough information to reproduce the problem, e.g. if the problem is with a disk image, please provide the disk image (or a TNFS location).

 

We'll try to fold this into github issues, so we can keep track.

 

-Thom

  • Like 4
Link to comment
Share on other sites

Running the Copy Disk from Internet test I've run into a couple issues.

 

  1. First, SCOPY810.ATR does not seem to run on an XL/XE operating system (at least not on my Incognito 800). I switched to Colleen mode and OS B and it loads and boots. 
     
  2. Second, the test procedure says to begin the sector copy at sector 0. The program actually begins numbering sectors at 001 and will make an error buzz if you try to specify sector 0.
     
  3. Third, starting the copy fails every time with "ERROR 8A ON 3".  I have confirmed that the single density 90K ATR created in the prior test is mounted as R/W in the D3: slot.

 

 

Link to comment
Share on other sites

1 minute ago, DrVenkman said:

Running the Copy Disk from Internet test I've run into a couple issues.

 

  1. First, SCOPY810.ATR does not seem to run on an XL/XE operating system (at least not on my Incognito 800). I switched to Colleen mode and OS B and it loads and boots. 
     
  2. Second, the test procedure says to begin the sector copy at sector 0. The program actually begins numbering sectors at 001 and will make an error buzz if you try to specify sector 0.
     
  3. Third, starting the copy fails every time with "ERROR 8A ON 3".  I have confirmed that the single density 90K ATR created in the prior test is mounted as R/W in the D3: slot.

 

 

Very strange. I run that SCOPY810 on XL OS 1.3 on my U1MB.... Thanks, am verifying. I'll try on both my 1200XL and on the XEGS.

 

-Thom

  • Like 1
Link to comment
Share on other sites

45 minutes ago, DrVenkman said:

Running the Copy Disk from Internet test I've run into a couple issues.

 

  1. First, SCOPY810.ATR does not seem to run on an XL/XE operating system (at least not on my Incognito 800). I switched to Colleen mode and OS B and it loads and boots. 
     
  2. Second, the test procedure says to begin the sector copy at sector 0. The program actually begins numbering sectors at 001 and will make an error buzz if you try to specify sector 0.
     
  3. Third, starting the copy fails every time with "ERROR 8A ON 3".  I have confirmed that the single density 90K ATR created in the prior test is mounted as R/W in the D3: slot.

 

 

OK, so:

 

1. Amended test instructions so that SCOPY810 will boot properly. BASIC must be disabled, so OPTION must be held.

 

2. Yup, that was dumb. My bad. I amended starting sector to 1.

 

3. Ok, I've now reproduced this after I re-mounted a freshly made disk in D3:

 

We do need to do a new firmware build. @jamm ?

 

-Thom

Edited by tschak909
just now reproduced it.
Link to comment
Share on other sites

Regarding Galaxian: I tried it a few times and had issues sometimes, not others.  Its not related to TNFS caching, as it happens both with SD and TNFS loads.  Looks more like a timing sensitivity.

  • Loaded consistently the times I tried it when I had HSIO turned off (Colleen mode loaded every time)
  • It seemed more finicky with XL/XE OS and would frequently end up in a constant reboot loop.
  • It seems to work pretty reliably, even with HSIO turned on, right after a reboot of the FN

This one is going to take some deep digging, I think, so it's going on the GitHub issues list.

 

 

Edited by jamm
Link to comment
Share on other sites

@DrVenkman OK, I've figured it out.

 

and talked it over with @jamm

 

Turns out, pressing the lone RESET button to go back into config is a BAD idea now. :) 

 

--------------------------
[]  []                    [X]

--------------------------
 

The button marked X is a hard reset button, it's wired into the RESET line of the ESP32 and kills everything immediately.

 

This wasn't affected with the Arduino code, because the Arduino code closed the SD card after something like 30 seconds of inactivity.

 

We can try to implement this into the IDF code, but, for now, holding down button B until the white LED goes off will gracefully restart the device.

 

-----------------------

[] [X]                 []

-----------------------

 

(the FRESET.COM fnc-tools command should also do this.)

 

 I will go back through all the test procedures tonight, and amend this.

 

-Thom

  • Like 1
Link to comment
Share on other sites

Earlier, I reflashed my FujiNet using @mozzwald's newest version of the flasher and the latest (overnight?) build of the device firmware. Loading The Print Shop from a remote host now works correctly. 

 

This version of The Goonies, when loaded from a local TNFS server, fails with HSIO enabled on the Atari - it gets to just about the very end of the loading cycle, the computer appears to reset, then the game begins loading again, with the same result, over and over. However, with HSIO disabled, this ATR loads and runs as normal.

 

Goonies, The (1985)(Datasoft)(US)(NTSC)[!][cr CSS].atr

Link to comment
Share on other sites

10 minutes ago, DrVenkman said:

Earlier, I reflashed my FujiNet using @mozzwald's newest version of the flasher and the latest (overnight?) build of the device firmware. Loading The Print Shop from a remote host now works correctly. 

 

This version of The Goonies, when loaded from a local TNFS server, fails with HSIO enabled on the Atari - it gets to just about the very end of the loading cycle, the computer appears to reset, then the game begins loading again, with the same result, over and over. However, with HSIO disabled, this ATR loads and runs as normal.

 

Goonies, The (1985)(Datasoft)(US)(NTSC)[!][cr CSS].atr 90.02 kB · 1 download

That sounds like the same behavior I saw in Galaxian.  Interestingly, @tschak909 couldn't reproduce it on his machine, but both you and I have an Incognito 800, so I'm wondering if there isn't something special happening there.

 

Have you tried loading off of SD to see if the behavior is the same?

 

Edited by jamm
Link to comment
Share on other sites

1 minute ago, jamm said:

That sounds like the same behavior I saw in Galaxian.  Interestingly, @tschak909 couldn't reproduce it on his machine, but both you and I have an Incognito 800, so I'm wondering if there isn't something special happening there.

 

Have you tried loading off of SD to see if the behavior is the same?

 

From the SD card, with HSIO enabled, the file will load once, reset as if about to start, then load again, and the second time it will start up and begin playing. I tested it twice and the behavior was the same each time. 

 

Then I tried over my LAN again. With HSIO enabled, the first time the file loaded and then the Atari locked up rather than restarting. After resetting the FujiNet (B button, extended hold) and trying again, the program loaded properly from the network.

 

Link to comment
Share on other sites

N: device testing and general file I/O ...

 

BUG REPORT:

I loaded Atari DOS 2.0s with NDEV.COM (renamed to AUTORUN.SYS to load at boot) from the SD card on the device and then tried the "smoke test" from the Github page. At the BASIC READY prompt, I tried LOAD "N:HTTP://ATARI-APPS.IRATA.ONLINE/BLACKJACK.BAS"

 

With HSIO enabled, the program will seemingly load but at the end of the loading process, there is a long-ish pause (on the order of 10 seconds or more), then an odd SIO "fart" kind of noise, then return to the READY prompt. However, at that point, BASIC acts very odd - any command will freeze the computer. Tested twice in a row from a cold boot of the Atari (Incognito 800, XL/XE OS, PBI BIOS enabled, hard disk disabled, HSIO enabled, BASIC at "Default" - that is, not disabled). 

 

However, if I turn HSIO off, everything works normally. The program loads through the N: device and runs as expected.

 

EDIT: Even with HSIO disabled, the load often fails with the same symptoms as above. I do note that when this happens, the yellow SIO activity light stays lit for several seconds, then goes dark. The white light also goes dark at the same time. Then the BASIC READY prompt reappears but the file has failed to load and BASIC is misbehaving as described above. 

 

BUG REPORT:

When booting Atari DOS from the SD card, the presence of Atari BASIC as set by the Incognito BIOS is not immediately recognized; the computer will load and go straight to DUP.SYS. Selecting B to boot cartridge will result in an error message stating that no cartridge is present. However, after the initial boot, either returning to the Incognito BIOS and booting again, or simply pressing SELECT-SYSTEM RESET to trigger a cold boot per the Incognito BIOS setting will result in DOS.SYS loading only and a BASIC READY prompt.

 

BUG REPORT:

After booting to SpartaDOS X with disk images mounted in the FujiNet drive slots, SDX file operations (copying file) from the mounted drive images may inconsistently and unpredictably hang or freeze. After a warm reset of the Atari, a second attempt will sometimes complete, sometimes not.

For example: I had the FujiNet sample Atari DOS 2.0s .ATR image mounted in drive slot 1 and then enabled and booted SDX from the Incognito BIOS. From the SDX command line, I created a new \FujiNet directory on my E: drive, then attempted to copy all the *.COM files from the mounted A: drive image to the new directory. After several files copied normally, the Atari became unresponsive - I waited for some kind of an error message but did not get one. I did a System Reset on the Atari and tried again. Once more the file operation started but then halted/froze after several files, getting "stuck" on a different file. Note that I had HSIO turned OFF for drives D1: and D2: in the Incognito BIOS, so file operations should have been attempted at normal SIO speed.

Link to comment
Share on other sites

Ok.

 

in order:

 

1. There seems to be more debugging I need to do with NDEV.COM and the latest DOSes, now that PROCEED interrupt behavior has changed.

 

2. That's weird.

 

3. @jamm I will re-set the default high-speed for now to 0x06 so that it will work reliably with SpartaDOS x 4.4X ( @drac030 has not incorporated the IDE+ high speed code yet, I don't think?). SDX will work with high speed 0x00 with PBI enabled and HSIO enabled, but this will allow it to work more reliably across the board.

 

-Thom

Link to comment
Share on other sites

So an addendum to my N: device bug report from earlier ...


I moved my FujiNet device over to one of my 1200XLs. This machine has been upgraded with a revision 11 OS, has a UAV installed, and the +5V SIO mod, but is otherwise stock. Loading the BLACKJACK.BAS program from Irata.Online worked perfectly (standard SIO speeds of course) twice in a row. That is, I booted the computer, loaded the game and ran it. Then did a warm reset, typed NEW and loaded it again. Worked perfectly the second time too. Not sure what to make of it, since theoretically an Incognito 800 with HSIO turned off and set to an XL/XE operating system should be functionally identical.

 

EDIT: And then I powered down the FujiNet, moved it over to my Incognito 800 with HSIO turned off and it worked there too again, even though it was terribly inconsistent earlier today. I wonder if the ESP32 device's uptime is an issue? 

Link to comment
Share on other sites

*nod* We'll get it. I suspect I will need to beat on the N: device some more.

 

I basically test it with the OSes in the local SD card pack, that is:

 

* DOS 2.0S

* DOS 2.0D

* DOS 2.5

* MyDOS 4.53

* SpartaDOS 3.2d

* XDOS 2.43

* DOS XL / OS/A+

 

Missing any? Anybody use Turbo DOS XE? ;) ... anybody use DOS XE? ;) DOS 3? :)

 

It's kind of silly to test N: with SpartaDOS X, as the CP can't really utilize it, and it will need a kernel driver... hopefully will get some help there soon. :)

 

-Thom

Link to comment
Share on other sites

Yep, I understand. Just reporting things in case (A), I'm simply missing or overlooking something on my end; or (B) finding something truly borken such as the Print Shop issue the other day; or (C) finding an intermittent issue or edge case (like this stuff about the N: driver today).

 

I have no expectation that any real issues will be fixed automagically the very day I point them out. I know a huge amount of time is going towards refactoring CONFIG and extending it for traversing directories with more than 20-odd files; improved long filename support, etc.  

 

No worries. :) 

  • Like 1
Link to comment
Share on other sites

I ran the initial R: device test from the Github test plan and it worked fine on my Incognito 800 using BobTerm.

 

Bug Report:

 

After initial success with BobTerm, I tried to load ICETXE from the same disk but it won't run on this machine. The program will load but at the end of the load process, the machine resets and boot menu loads again. The same thing happens with HSIO enabled or disabled. ICET800 works however. I then made a sector copy of the modem-programs.atr from Irata.Online and tried the same test from the local SD card. However, there was no change in results.

 

Enhancement Request:

 

Since creating a new ATR in #CONFIG requires specifying the size of the file at the outset, please add the option to retrieve some minimal file information for ATRs from the #CONFIG utility. Specifically, the ability to know the size of the ATR would be useful for making local SD card copies of ATRs hosted on TNFS servers. 

  • Like 1
Link to comment
Share on other sites

19 minutes ago, DrVenkman said:

Bug Report:

 

After initial success with BobTerm, I tried to load ICETXE from the same disk but it won't run on this machine. The program will load but at the end of the load process, the machine resets and boot menu loads again. The same thing happens with HSIO enabled or disabled. ICET800 works however. I then made a sector copy of the modem-programs.atr from Irata.Online and tried the same test from the local SD card. However, there was no change in results.

Same issue here. I captured debug output using FujiNet-Flasher where it resets and goes back to menu:

 

Spoiler

[16:51:50]CF: 31 52 01 00 84
[16:51:50]disk sio_process()
[16:51:50]ACK!
[16:51:50]disk READ
[16:51:50]tnfs_lseek currpos=121872, pos=0, typ=0
[16:51:50]_tnfs_cache_seek current=121872, destination=0, cache_start=121856, cache_end=122368
[16:51:50]_tnfs_cache_seek outside cached region
[16:51:50]tnfs_lseek success, new pos=0, response pos=0
[16:51:50]tnfs_read fh=1, len=128
[16:51:50]_tnfs_read_from_cache: buffpos=0, cache_start=121856, cache_avail=0, dest_size=128, dest_used=0
[16:51:50]_tnfs_read_from_cache - nothing in cache
[16:51:50]_TNFS_FILL_CACHE fh=1, file_position=0
[16:51:50]_tnfs_fill_cache requesting 512 bytes
[16:51:50]_tnfs_fill_cache got 512 bytes, 0 more bytes needed
[16:51:50]_tnfs_read_from_cache: buffpos=0, cache_start=0, cache_avail=512, dest_size=128, dest_used=0
[16:51:50]TNFS cache providing 128 bytes
[16:51:50]tnfs_read fh=1, len=128
[16:51:50]_tnfs_read_from_cache: buffpos=128, cache_start=0, cache_avail=512, dest_size=128, dest_used=0
[16:51:50]TNFS cache providing 128 bytes
[16:51:50]->SIO write 128 bytes
[16:51:50]COMPLETE!
[16:51:50]
[16:51:50]CF: 31 53 01 00 85
[16:51:50]disk sio_process()
[16:51:50]ACK!
[16:51:50]disk STATUS
[16:51:50]->SIO write 4 bytes
[16:51:50]COMPLETE!
[16:51:50]
[16:51:50]CF: 31 52 69 01 ed
[16:51:50]disk sio_process()
[16:51:50]ACK!
[16:51:50]disk READ
[16:51:50]tnfs_lseek currpos=256, pos=46080, typ=0
[16:51:50]_tnfs_cache_seek current=256, destination=46080, cache_start=0, cache_end=512
[16:51:50]_tnfs_cache_seek outside cached region
[16:51:50]tnfs_lseek success, new pos=46080, response pos=46080
[16:51:50]tnfs_read fh=1, len=128
[16:51:50]_tnfs_read_from_cache: buffpos=46080, cache_start=0, cache_avail=0, dest_size=128, dest_used=0
[16:51:50]_tnfs_read_from_cache - nothing in cache
[16:51:50]_TNFS_FILL_CACHE fh=1, file_position=46080
[16:51:50]_tnfs_fill_cache requesting 512 bytes
[16:51:50]_tnfs_fill_cache got 512 bytes, 0 more bytes needed
[16:51:50]_tnfs_read_from_cache: buffpos=46080, cache_start=46080, cache_avail=512, dest_size=128, dest_used=0
[16:51:50]TNFS cache providing 128 bytes
[16:51:50]tnfs_read fh=1, len=128
[16:51:50]_tnfs_read_from_cache: buffpos=46208, cache_start=46080, cache_avail=512, dest_size=128, dest_used=0
[16:51:50]TNFS cache providing 128 bytes
[16:51:50]->SIO write 128 bytes
[16:51:50]COMPLETE!
[16:51:50]
[16:51:50]CF: 31 52 6a 01 ee
[16:51:50]disk sio_process()
[16:51:50]ACK!
[16:51:50]disk READ
[16:51:50]tnfs_read fh=1, len=128
[16:51:50]_tnfs_read_from_cache: buffpos=46336, cache_start=46080, cache_avail=512, dest_size=128, dest_used=0
[16:51:50]TNFS cache providing 128 bytes
[16:51:50]->SIO write 128 bytes
[16:51:50]COMPLETE!
[16:51:50]
[16:51:50]CF: 31 52 6b 01 ef
[16:51:50]disk sio_process()
[16:51:50]ACK!
[16:51:50]disk READ
[16:51:50]tnfs_read fh=1, len=128
[16:51:50]_tnfs_read_from_cache: buffpos=46464, cache_start=46080, cache_avail=512, dest_size=128, dest_used=0
[16:51:50]TNFS cache providing 128 bytes
[16:51:50]->SIO write 128 bytes
[16:51:50]COMPLETE!
[16:51:50]
[16:51:50]CF: 4f 40 4f 4f 2e
[16:51:50]SIO TYPE3 POLL
[16:51:50]Sending TYPE3 poll to dev 50
[16:51:50]sioModem::sio_process() called
[16:51:50]$40 TYPE 3 POLL #57
[16:51:50]
[16:51:50]CF: 4f 40 4f 4f 2e
[16:51:50]SIO TYPE3 POLL
[16:51:50]Sending TYPE3 poll to dev 50
[16:51:50]sioModem::sio_process() called
[16:51:50]$40 TYPE 3 POLL #58
[16:51:50]
[16:51:50]CF: 4f 40 4f 4f 2e
[16:51:50]SIO TYPE3 POLL
[16:51:50]Sending TYPE3 poll to dev 50
[16:51:50]sioModem::sio_process() called
[16:51:50]$40 TYPE 3 POLL #59
[16:51:50]
[16:51:50]CF: 4f 40 4f 4f 2e
[16:51:50]SIO TYPE3 POLL
[16:51:50]Sending TYPE3 poll to dev 50
[16:51:50]sioModem::sio_process() called
[16:51:50]$40 TYPE 3 POLL #60
[16:51:50]
[16:51:50]CF: 4f 40 4f 4f 2e
[16:51:50]SIO TYPE3 POLL
[16:51:50]Sending TYPE3 poll to dev 50
[16:51:50]sioModem::sio_process() called
[16:51:50]$40 TYPE 3 POLL #61
[16:51:50]
[16:51:50]CF: 4f 40 4f 4f 2e
[16:51:50]SIO TYPE3 POLL
[16:51:50]Sending TYPE3 poll to dev 50
[16:51:50]sioModem::sio_process() called
[16:51:50]$40 TYPE 3 POLL #62
[16:51:50]
[16:51:50]CF: 4f 40 4f 4f 2e
[16:51:50]SIO TYPE3 POLL
[16:51:50]Sending TYPE3 poll to dev 50
[16:51:50]sioModem::sio_process() called
[16:51:50]$40 TYPE 3 POLL #63
[16:51:50]
[16:51:50]CF: 4f 40 4f 4f 2e
[16:51:50]SIO TYPE3 POLL
[16:51:50]Sending TYPE3 poll to dev 50
[16:51:50]sioModem::sio_process() called
[16:51:50]$40 TYPE 3 POLL #64
[16:51:51]
[16:51:51]CF: 4f 40 4f 4f 2e
[16:51:51]SIO TYPE3 POLL
[16:51:51]Sending TYPE3 poll to dev 50
[16:51:51]sioModem::sio_process() called
[16:51:51]$40 TYPE 3 POLL #65
[16:51:51]
[16:51:51]CF: 4f 40 4f 4f 2e
[16:51:51]SIO TYPE3 POLL
[16:51:51]Sending TYPE3 poll to dev 50
[16:51:51]sioModem::sio_process() called
[16:51:51]$40 TYPE 3 POLL #66
[16:51:51]
[16:51:51]CF: 4f 40 4f 4f 2e
[16:51:51]SIO TYPE3 POLL
[16:51:51]Sending TYPE3 poll to dev 50
[16:51:51]sioModem::sio_process() called
[16:51:51]$40 TYPE 3 POLL #67
[16:51:51]
[16:51:51]CF: 4f 40 4f 4f 2e
[16:51:51]SIO TYPE3 POLL
[16:51:51]Sending TYPE3 poll to dev 50
[16:51:51]sioModem::sio_process() called
[16:51:51]$40 TYPE 3 POLL #68
[16:51:51]
[16:51:51]CF: 4f 40 4f 4f 2e
[16:51:51]SIO TYPE3 POLL
[16:51:51]Sending TYPE3 poll to dev 50
[16:51:51]sioModem::sio_process() called
[16:51:51]$40 TYPE 3 POLL #69
[16:51:51]
[16:51:51]CF: 4f 40 4f 4f 2e
[16:51:51]SIO TYPE3 POLL
[16:51:51]Sending TYPE3 poll to dev 50
[16:51:51]sioModem::sio_process() called
[16:51:51]$40 TYPE 3 POLL #70
[16:51:51]
[16:51:51]CF: 4f 40 4f 4f 2e
[16:51:51]SIO TYPE3 POLL
[16:51:51]Sending TYPE3 poll to dev 50
[16:51:51]sioModem::sio_process() called
[16:51:51]$40 TYPE 3 POLL #71
[16:51:51]
[16:51:51]CF: 4f 40 4f 4f 2e
[16:51:51]SIO TYPE3 POLL
[16:51:51]Sending TYPE3 poll to dev 50
[16:51:51]sioModem::sio_process() called
[16:51:51]$40 TYPE 3 POLL #72
[16:51:51]
[16:51:51]CF: 4f 40 4f 4f 2e
[16:51:51]SIO TYPE3 POLL
[16:51:51]Sending TYPE3 poll to dev 50
[16:51:51]sioModem::sio_process() called
[16:51:51]$40 TYPE 3 POLL #73
[16:51:51]
[16:51:51]CF: 4f 40 4f 4f 2e
[16:51:51]SIO TYPE3 POLL
[16:51:51]Sending TYPE3 poll to dev 50
[16:51:51]sioModem::sio_process() called
[16:51:51]$40 TYPE 3 POLL #74
[16:51:51]
[16:51:51]CF: 4f 40 4f 4f 2e
[16:51:51]SIO TYPE3 POLL
[16:51:51]Sending TYPE3 poll to dev 50
[16:51:51]sioModem::sio_process() called
[16:51:51]$40 TYPE 3 POLL #75
[16:51:51]
[16:51:51]CF: 4f 40 4f 4f 2e
[16:51:51]SIO TYPE3 POLL
[16:51:51]Sending TYPE3 poll to dev 50
[16:51:51]sioModem::sio_process() called
[16:51:51]$40 TYPE 3 POLL #76
[16:51:51]
[16:51:51]CF: 4f 40 4f 4f 2e
[16:51:51]SIO TYPE3 POLL
[16:51:51]Sending TYPE3 poll to dev 50
[16:51:51]sioModem::sio_process() called
[16:51:51]$40 TYPE 3 POLL #77
[16:51:51]
[16:51:51]CF: 4f 40 4f 4f 2e
[16:51:51]SIO TYPE3 POLL
[16:51:51]Sending TYPE3 poll to dev 50
[16:51:51]sioModem::sio_process() called
[16:51:51]$40 TYPE 3 POLL #78
[16:51:51]
[16:51:51]CF: 4f 40 4f 4f 2e
[16:51:51]SIO TYPE3 POLL
[16:51:51]Sending TYPE3 poll to dev 50
[16:51:51]sioModem::sio_process() called
[16:51:51]$40 TYPE 3 POLL #79
[16:51:51]
[16:51:51]CF: 4f 40 4f 4f 2e
[16:51:51]SIO TYPE3 POLL
[16:51:51]Sending TYPE3 poll to dev 50
[16:51:51]sioModem::sio_process() called
[16:51:51]$40 TYPE 3 POLL #80
[16:51:51]
[16:51:51]CF: 4f 40 4f 4f 2e
[16:51:51]SIO TYPE3 POLL
[16:51:51]Sending TYPE3 poll to dev 50
[16:51:51]sioModem::sio_process() called
[16:51:51]$40 TYPE 3 POLL #81
[16:51:51]
[16:51:51]CF: 4f 40 4f 4f 2e
[16:51:51]SIO TYPE3 POLL
[16:51:51]Sending TYPE3 poll to dev 50
[16:51:51]sioModem::sio_process() called
[16:51:51]$40 TYPE 3 POLL #82
[16:51:51]
[16:51:51]CF: 4f 40 4f 4f 2e
[16:51:51]SIO TYPE3 POLL
[16:51:51]Sending TYPE3 poll to dev 50
[16:51:51]sioModem::sio_process() called
[16:51:51]$40 TYPE 3 POLL #83
[16:51:51]
[16:51:51]CF: 4f 40 4f 4f 2e
[16:51:51]SIO TYPE3 POLL
[16:51:51]Sending TYPE3 poll to dev 50
[16:51:51]sioModem::sio_process() called
[16:51:51]$40 TYPE 3 POLL #84
[16:51:51]
[16:51:51]CF: 4f 40 00 00 8f
[16:51:51]SIO TYPE3 POLL
[16:51:51]Sending TYPE3 poll to dev 50
[16:51:51]sioModem::sio_process() called
[16:51:51]$40 TYPE 3 POLL #85
[16:51:51]
[16:51:51]CF: 4f 40 00 00 8f
[16:51:51]SIO TYPE3 POLL
[16:51:51]Sending TYPE3 poll to dev 50
[16:51:51]sioModem::sio_process() called
[16:51:51]$40 TYPE 3 POLL #86
[16:51:51]
[16:51:51]CF: 4f 40 00 00 8f
[16:51:51]SIO TYPE3 POLL
[16:51:51]Sending TYPE3 poll to dev 50
[16:51:51]sioModem::sio_process() called
[16:51:51]$40 TYPE 3 POLL #87
[16:51:51]
[16:51:51]CF: 4f 40 00 00 8f
[16:51:51]SIO TYPE3 POLL
[16:51:51]Sending TYPE3 poll to dev 50
[16:51:51]sioModem::sio_process() called
[16:51:51]$40 TYPE 3 POLL #88
[16:51:51]
[16:51:51]CF: 4f 40 00 00 8f
[16:51:51]SIO TYPE3 POLL
[16:51:51]Sending TYPE3 poll to dev 50
[16:51:51]sioModem::sio_process() called
[16:51:51]$40 TYPE 3 POLL #89
[16:51:51]
[16:51:51]CF: 4f 40 00 00 8f
[16:51:51]SIO TYPE3 POLL
[16:51:51]Sending TYPE3 poll to dev 50
[16:51:51]sioModem::sio_process() called
[16:51:51]$40 TYPE 3 POLL #90
[16:51:51]
[16:51:51]CF: 4f 40 00 00 8f
[16:51:51]SIO TYPE3 POLL
[16:51:51]Sending TYPE3 poll to dev 50
[16:51:51]sioModem::sio_process() called
[16:51:51]$40 TYPE 3 POLL #91
[16:51:51]
[16:51:51]CF: 4f 40 00 00 8f
[16:51:51]SIO TYPE3 POLL
[16:51:51]Sending TYPE3 poll to dev 50
[16:51:51]sioModem::sio_process() called
[16:51:51]$40 TYPE 3 POLL #92
[16:51:51]
[16:51:51]CF: 4f 40 00 00 8f
[16:51:51]SIO TYPE3 POLL
[16:51:51]Sending TYPE3 poll to dev 50
[16:51:51]sioModem::sio_process() called
[16:51:51]$40 TYPE 3 POLL #93
[16:51:51]
[16:51:51]CF: 4f 40 00 00 8f
[16:51:51]SIO TYPE3 POLL
[16:51:51]Sending TYPE3 poll to dev 50
[16:51:51]sioModem::sio_process() called
[16:51:51]$40 TYPE 3 POLL #94
[16:51:52]
[16:51:52]CF: 4f 40 00 00 8f
[16:51:52]SIO TYPE3 POLL
[16:51:52]Sending TYPE3 poll to dev 50
[16:51:52]sioModem::sio_process() called
[16:51:52]$40 TYPE 3 POLL #95
[16:51:52]
[16:51:52]CF: 4f 40 00 00 8f
[16:51:52]SIO TYPE3 POLL
[16:51:52]Sending TYPE3 poll to dev 50
[16:51:52]sioModem::sio_process() called
[16:51:52]$40 TYPE 3 POLL #96
[16:51:52]
[16:51:52]CF: 4f 40 00 00 8f
[16:51:52]SIO TYPE3 POLL
[16:51:52]Sending TYPE3 poll to dev 50
[16:51:52]sioModem::sio_process() called
[16:51:52]$40 TYPE 3 POLL #97
[16:51:52]
[16:51:52]CF: 4f 40 00 00 8f
[16:51:52]SIO TYPE3 POLL
[16:51:52]Sending TYPE3 poll to dev 50
[16:51:52]sioModem::sio_process() called
[16:51:52]$40 TYPE 3 POLL #98
[16:51:52]
[16:51:52]CF: 4f 40 00 00 8f
[16:51:52]SIO TYPE3 POLL
[16:51:52]Sending TYPE3 poll to dev 50
[16:51:52]sioModem::sio_process() called
[16:51:52]$40 TYPE 3 POLL #99
[16:51:52]
[16:51:52]CF: 4f 40 00 00 8f
[16:51:52]SIO TYPE3 POLL
[16:51:52]Sending TYPE3 poll to dev 50
[16:51:52]sioModem::sio_process() called
[16:51:52]$40 TYPE 3 POLL #100
[16:51:52]
[16:51:52]CF: 4f 40 00 00 8f
[16:51:52]SIO TYPE3 POLL
[16:51:52]Sending TYPE3 poll to dev 50
[16:51:52]sioModem::sio_process() called
[16:51:52]$40 TYPE 3 POLL #101
[16:51:52]
[16:51:52]CF: 4f 40 00 00 8f
[16:51:52]SIO TYPE3 POLL
[16:51:52]Sending TYPE3 poll to dev 50
[16:51:52]sioModem::sio_process() called
[16:51:52]$40 TYPE 3 POLL #102
[16:51:52]
[16:51:52]CF: 4f 40 00 00 8f
[16:51:52]SIO TYPE3 POLL
[16:51:52]Sending TYPE3 poll to dev 50
[16:51:52]sioModem::sio_process() called
[16:51:52]$40 TYPE 3 POLL #103
[16:51:52]
[16:51:52]CF: 4f 40 00 00 8f
[16:51:52]SIO TYPE3 POLL
[16:51:52]Sending TYPE3 poll to dev 50
[16:51:52]sioModem::sio_process() called
[16:51:52]$40 TYPE 3 POLL #104
[16:51:52]
[16:51:52]CF: 4f 40 00 00 8f
[16:51:52]SIO TYPE3 POLL
[16:51:52]Sending TYPE3 poll to dev 50
[16:51:52]sioModem::sio_process() called
[16:51:52]$40 TYPE 3 POLL #105
[16:51:52]
[16:51:52]CF: 4f 40 00 00 8f
[16:51:52]SIO TYPE3 POLL
[16:51:52]Sending TYPE3 poll to dev 50
[16:51:52]sioModem::sio_process() called
[16:51:52]$40 TYPE 3 POLL #106
[16:51:52]
[16:51:52]CF: 4f 40 00 00 8f
[16:51:52]SIO TYPE3 POLL
[16:51:52]Sending TYPE3 poll to dev 50
[16:51:52]sioModem::sio_process() called
[16:51:52]$40 TYPE 3 POLL #107
[16:51:52]
[16:51:52]CF: 4f 40 00 00 8f
[16:51:52]SIO TYPE3 POLL
[16:51:52]Sending TYPE3 poll to dev 50
[16:51:52]sioModem::sio_process() called
[16:51:52]$40 TYPE 3 POLL #108
[16:51:52]
[16:51:52]CF: 4f 40 00 00 8f
[16:51:52]SIO TYPE3 POLL
[16:51:52]Sending TYPE3 poll to dev 50
[16:51:52]sioModem::sio_process() called
[16:51:52]$40 TYPE 3 POLL #109
[16:51:52]
[16:51:52]CF: 4f 40 00 00 8f
[16:51:52]SIO TYPE3 POLL
[16:51:52]Sending TYPE3 poll to dev 50
[16:51:52]sioModem::sio_process() called
[16:51:52]$40 TYPE 3 POLL #110
[16:51:52]
[16:51:52]CF: 4f 40 00 00 8f
[16:51:52]SIO TYPE3 POLL
[16:51:52]Sending TYPE3 poll to dev 50
[16:51:52]sioModem::sio_process() called
[16:51:52]$40 TYPE 3 POLL #111
[16:51:52]
[16:51:52]CF: 4f 40 00 00 8f
[16:51:52]SIO TYPE3 POLL
[16:51:52]Sending TYPE3 poll to dev 50
[16:51:52]sioModem::sio_process() called
[16:51:52]$40 TYPE 3 POLL #112
[16:51:54]
[16:51:54]CF: 31 53 00 00 84
[16:51:54]disk sio_process()
[16:51:54]ACK!
[16:51:54]disk STATUS
[16:51:54]->SIO write 4 bytes
[16:51:54]COMPLETE!
[16:51:54]
[16:51:54]CF: 31 52 01 00 84
[16:51:54]disk sio_process()
[16:51:54]ACK!
[16:51:54]disk READ
[16:51:54]tnfs_lseek currpos=46592, pos=0, typ=0
[16:51:54]_tnfs_cache_seek current=46592, destination=0, cache_start=46080, cache_end=46592
[16:51:54]_tnfs_cache_seek outside cached region
[16:51:54]tnfs_lseek success, new pos=0, response pos=0
[16:51:54]tnfs_read fh=1, len=128
[16:51:54]_tnfs_read_from_cache: buffpos=0, cache_start=46080, cache_avail=0, dest_size=128, dest_used=0
[16:51:54]_tnfs_read_from_cache - nothing in cache
[16:51:54]_TNFS_FILL_CACHE fh=1, file_position=0
[16:51:54]_tnfs_fill_cache requesting 512 bytes
[16:51:54]_tnfs_fill_cache got 512 bytes, 0 more bytes needed
[16:51:54]_tnfs_read_from_cache: buffpos=0, cache_start=0, cache_avail=512, dest_size=128, dest_used=0
[16:51:54]TNFS cache providing 128 bytes
[16:51:54]tnfs_read fh=1, len=128
[16:51:54]_tnfs_read_from_cache: buffpos=128, cache_start=0, cache_avail=512, dest_size=128, dest_used=0
[16:51:54]TNFS cache providing 128 bytes
[16:51:54]->SIO write 128 bytes
[16:51:54]COMPLETE!

 

EDIT: I notice the Altirra handler is loaded from disk. Not sure if we need to do this or not

Edited by mozzwald
edit
Link to comment
Share on other sites

This was a mistake on my part, looks like the disk was incorrectly copied from its origin. I've since copied it again, and tested it, it should be fine.

 

I will also make a tool to show disk geometry of a disk slot. (FINFO), until I get such functionality folded into CONFIG.

 

-Thom

Edited by tschak909
  • Like 1
Link to comment
Share on other sites

1 hour ago, tschak909 said:

This was a mistake on my part, looks like the disk was incorrectly copied from its origin. I've since copied it again, and tested it, it should be fine.

 

I will also make a tool to show disk geometry of a disk slot. (FINFO), until I get such functionality folded into CONFIG.

 

-Thom

The new copy up on the remote server works now, thanks! However, when I make a sector copy of it on my SD card, the previous problem persists. That is, when trying to load and run ICETXE from the copy of the new ATR on my SD card, it will get the end of the load cycle, then reset and reload the menu. I made two sector copies of the new ATR and both exhibit the same problem. 

 

Just for the sake of completeness however, can you tell me what is the size of the ATR for modem-programs.atr? I assumed 90K and copies 720 sectors, but if the ATR is bigger than that, perhaps the local copies I created are truncated?

Link to comment
Share on other sites

Fantastic. :)

 

You know, sometimes it's just a matter of wrapping my head around something - once you confirmed that the modem-programs.atr was an ED disk, I started digging around looking for a sector copier that (a) spoke ED; and (b) allowed use of more than 2 drives. After faffing around for ... too many ... minutes, I decided to look at the disk directory and realized it was an ordinary DOS disk, not some obfuscated nonsense. Then I realized I could just boot DOS 2.5 on a local (SIDE Loader) mounted ATR, with the source and destination both mounted in FujiNet slots, the source being the remote hosted original, the destination being a new ATR I created on my SD card.

 

THAT led me to digging through my dusty memories on how to use DOS 2.5's SETUP.COM program to allow access to D3:, etc. 

 

Anyway, tl;dr: my local SD card-based copy of the disk has been made and works properly. Whew!

  • Like 2
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...