tschak909 Posted January 23, 2021 Author Share Posted January 23, 2021 use the n-handler that's a part of the DOSes in the atari-apps/DOS/ folder and try again. Now that CP/M is in a workable state, I am resuming work on the N: device. -Thom 1 Quote Link to comment Share on other sites More sharing options...
+DrVenkman Posted January 23, 2021 Share Posted January 23, 2021 1 hour ago, tschak909 said: use the n-handler that's a part of the DOSes in the atari-apps/DOS/ folder and try again. Now that CP/M is in a workable state, I am resuming work on the N: device. -Thom No dice, same Error -136. Hmm. I know the N: handler worked for me in the past on the time or two I experimented but nothing doing today. Quote Link to comment Share on other sites More sharing options...
tschak909 Posted January 23, 2021 Author Share Posted January 23, 2021 I just saw some interesting garbage come across the TNFS server. (your address has been sanitized) XX.XXX.XX.XXX s=fcfc c=00 q=00 | Mounted / OK, SID=fcfc XX.XXX.XX.XXX s=fcfc c=17 q=01 | REQUEST cmd=0x17 TNFS_OPENDIRX XX.XXX.XX.XXX s=fcfc c=17 q=01 | opendirx: diropt=0x00, sortopt=0x00, max=0x0000, pat="", path="/��y0�/NETWORKING/�� y0�" XX.XXX.XX.XXX s=fcfc c=17 q=02 | REQUEST cmd=0x17 TNFS_OPENDIRX XX.XXX.XX.XXX s=fcfc c=17 q=02 | opendirx: diropt=0x00, sortopt=0x00, max=0x0000, pat="", path="/��y0�/NETWORKING/�� y0�" XX.XXX.XX.XXX s=fcfc c=17 q=03 | REQUEST cmd=0x17 TNFS_OPENDIRX XX.XXX.XX.XXX s=fcfc c=17 q=03 | opendirx: diropt=0x00, sortopt=0x00, max=0x0000, pat="", path="/��y0�/NETWORKING��y 0�" XX.XXX.XX.XXX s=fcfc c=17 q=04 | REQUEST cmd=0x17 TNFS_OPENDIRX XX.XXX.XX.XXX s=fcfc c=17 q=04 | opendirx: diropt=0x00, sortopt=0x00, max=0x0000, pat="", path="/��y0�/NETWORKING��y 0�" XX.XXX.XX.XXX s=fcfc c=17 q=05 | REQUEST cmd=0x17 TNFS_OPENDIRX XX.XXX.XX.XXX s=fcfc c=17 q=05 | opendirx: diropt=0x00, sortopt=0x00, max=0x0000, pat="", path="/��y0�" XX.XXX.XX.XXX s=fcfc c=17 q=06 | REQUEST cmd=0x17 TNFS_OPENDIRX XX.XXX.XX.XXX s=fcfc c=17 q=06 | opendirx: diropt=0x00, sortopt=0x00, max=0x0000, pat="", path="/��y0�" XX.XXX.XX.XXX s=fcfc c=17 q=07 | REQUEST cmd=0x17 TNFS_OPENDIRX XX.XXX.XX.XXX s=fcfc c=17 q=07 | opendirx: diropt=0x00, sortopt=0x00, max=0x0000, pat="", path="/��y0�//��y0�" XX.XXX.XX.XXX s=fcfc c=17 q=08 | REQUEST cmd=0x17 TNFS_OPENDIRX XX.XXX.XX.XXX s=fcfc c=17 q=08 | opendirx: diropt=0x00, sortopt=0x00, max=0x0000, pat="", path="/��y0�//��y0�" What DOS are you using? Quote Link to comment Share on other sites More sharing options...
tschak909 Posted January 23, 2021 Author Share Posted January 23, 2021 Also worth noting, I am noticing that TNFSD is terminating all sessions when ONE session expires. I will investigate and try to fix for a new tnfsd build. -Thom 1 Quote Link to comment Share on other sites More sharing options...
+DrVenkman Posted January 23, 2021 Share Posted January 23, 2021 6 minutes ago, tschak909 said: I just saw some interesting garbage come across the TNFS server. (your address has been sanitized) MY address? My local TNFS servers are not open to the public (the ports are not forwarded since 1) I have no need; and 2) my ISP periodically resets my gateway's IP and I don't want to mess with DNS nonsense). That said, 99% of my testing/use has been on my LAN using my own server. For that matter I just rebooted the Pi that hosts my main server for the first time in 58 days. It's been solid for my single-user needs. Quote Link to comment Share on other sites More sharing options...
mozzwald Posted January 23, 2021 Share Posted January 23, 2021 5 hours ago, Gunstar said: Or maybe everyone is using the same 3D printer .stl so all are the same? Everyone should be using the same STL but the tolerances from printer to printer will be different. The gap between the plug and receptacle was added after the first few units went out and there were issues with the SIO cable not staying in. This reduction in size helped those who had problems. The issues that I've heard since that change have been minimal. I think the spring/pressure pinned SIO cables are more likely to pop out due to the shorter pins in the Fujinet receptacle. I did a lot of searching for pins during the initial design and this was the best I could find. If anyone knows of longer ones, I'd be happy to update the design. I have found some that are ~1.25mm longer but cost twice as much. Not sure if that extra length would be worth the added cost or not. Quote Link to comment Share on other sites More sharing options...
MrFSL Posted January 23, 2021 Share Posted January 23, 2021 Just a note back on the PSU issues. I made a quick study of USB based power supplies with the Atari and I can tell you that MOST cell phone power supplies were not capable of outputing what was written on the case. I have wall-warts that claim 1.9A that can barely do 1.1 etc. Something like this can be very helpful https://www.amazon.com/gp/product/B07PWC7YMT/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&th=1 1 Quote Link to comment Share on other sites More sharing options...
Gunstar Posted January 24, 2021 Share Posted January 24, 2021 37 minutes ago, mozzwald said: Everyone should be using the same STL but the tolerances from printer to printer will be different. The gap between the plug and receptacle was added after the first few units went out and there were issues with the SIO cable not staying in. This reduction in size helped those who had problems. The issues that I've heard since that change have been minimal. I think the spring/pressure pinned SIO cables are more likely to pop out due to the shorter pins in the Fujinet receptacle. I did a lot of searching for pins during the initial design and this was the best I could find. If anyone knows of longer ones, I'd be happy to update the design. I have found some that are ~1.25mm longer but cost twice as much. Not sure if that extra length would be worth the added cost or not. My SIO cable seems to say in just fine, I was just noticing that on my Fujinet SIO there is a bit of a gap still between the port and plug as shown by others. I was only using the original side SIO of my 800 for the rare occasion when I wanted to use my SIO2PC which is built into my 1050 which is connected to my 1200XL and using a 6ft SIO cable I have to reach it across to my 800 instead of having to move the drive. But now that I have Fujinet, I've no need for SIO2PC & APE on my 800, so it can stay with my 1200XL and only Fujinet will ever be plugged into my 800's side port as all other devices are plugged in through my new SIO on the underside of my 800. So, it's just not an issue for me anyway. Eventually I may get another Fujinet for my 1200XL, if I feel I need more than one, but the way I have my 1200XL system set-up plugging the Fujinet into my 1200XL's SIO isn't really a choice, there's no headroom for it and the PBI I installed in my 1200XL with my Syscheck II plugged in (always for extended memory) there's no elbow room for it either. So, I'm wondering if the Fujinet needs to be the first in the SIO chain? or can I plug it into another peripheral on the daisy chain or into an APElink SIO extender I have in my 1200XL's daisy chain? (it has a couple open SIO ports on it) Does anyone else use their Fujinet with it connected anywhere but directly to the computer? Quote Link to comment Share on other sites More sharing options...
mozzwald Posted January 24, 2021 Share Posted January 24, 2021 19 minutes ago, Gunstar said: Fujinet with it connected anywhere but directly to the computer? You can put the Fujinet anywhere in the chain. You can even plug a SIO cable into the receptacle and use it that way if needed. 1 Quote Link to comment Share on other sites More sharing options...
Gunstar Posted January 24, 2021 Share Posted January 24, 2021 (edited) 4 hours ago, Peri Noid said: Plenty enough - if everything is OK with the computer. Maybe it could use a recap? I use a 3A PSU as well produced by Lotharek, my machine has 320KB of RAM, stereo, a built-in 3.5" floppy drive (yes, really) and Karin Mini floppy drive controller and AVG cart connected. It has completly no problem with additional powering of FujiNet. So, I bet, that 130XE is simply faulty. Or the PSU is only 3A on the paper, while actually it cannot deliver that much. I'll be adding an internal 3.5" floppy drive to my 1200XL soon myself, so no surprise to me that you or other's have one. I already use my 1200XL with these upgrades and external devices with my 3.4A PSU with no issues at all: Stereo Pokey, 32-in-1 OS, Dropcheck GTIA PAL board w/crystal, Internal RGB LED lighting, PBI upgrade w/Syscheck 2 XL, MyIDE II and Dropcheck Super SpartaDOS X w/RTC all working fine together. I'll be adding the internal drive, internal MIDI, Dual-PIA board with extra controller out ports and who knows what else in the future, and I'll be attempting to still use the PSU with it all. Edited January 24, 2021 by Gunstar Quote Link to comment Share on other sites More sharing options...
FreddieBear Posted January 24, 2021 Share Posted January 24, 2021 Today I updated my FujiNet device as I thought it would finally clear up the problem that's been bothering me since the last update (December). The problems started after the previous update by "killing" my FujiNet. It didn't boot up anymore and I assumed it was because I was disabling BASIC by holding down OPTION. It finally did boot up when I didn't press OPTION and I thought that issue was cleared up but today I couldn't get my device to boot no matter how manly times I reset it. So, today I noticed that there was a new update and I updated my device. Still doesn't work! It's dead. Even though all three LEDs light up and the RESET button seems to work I always get dumped to the READY prompt and the FujiNet never "catches and boots". Anyone else experience what I'm experiencing? My FujiNet IS BROKEN and I don't know why. I think this qualifies as a bug. Quote Link to comment Share on other sites More sharing options...
tschak909 Posted January 24, 2021 Author Share Posted January 24, 2021 20 minutes ago, FreddieBear said: Today I updated my FujiNet device as I thought it would finally clear up the problem that's been bothering me since the last update (December). The problems started after the previous update by "killing" my FujiNet. It didn't boot up anymore and I assumed it was because I was disabling BASIC by holding down OPTION. It finally did boot up when I didn't press OPTION and I thought that issue was cleared up but today I couldn't get my device to boot no matter how manly times I reset it. So, today I noticed that there was a new update and I updated my device. Still doesn't work! It's dead. Even though all three LEDs light up and the RESET button seems to work I always get dumped to the READY prompt and the FujiNet never "catches and boots". Anyone else experience what I'm experiencing? My FujiNet IS BROKEN and I don't know why. I think this qualifies as a bug. What system are you using? Are you seeing the blue (and possibly white LED) turn on when the FujiNet is reset? -Thom Quote Link to comment Share on other sites More sharing options...
FreddieBear Posted January 24, 2021 Share Posted January 24, 2021 When I RESET the FujiNet all LEDs within the case dim. Then I turn on the Atari 800XL and the orange (right most) LED lights briefly and the white LED (left side) lights up but I ALWAYS get dumped into the READY prompt / blue screen. FJ just doesn't "Catch". The blue LED stay on always. Quote Link to comment Share on other sites More sharing options...
tschak909 Posted January 24, 2021 Author Share Posted January 24, 2021 Can you load the fujinet flasher, and start the debug monitor? Then boot the machine, cutting and pasting here what output happens in the monitor? This will help debug the problem. -Thom Quote Link to comment Share on other sites More sharing options...
FreddieBear Posted January 24, 2021 Share Posted January 24, 2021 I'm sorry but I don't know what a debug monitor actually is nor how to access it. Please advise. Is it within my Atari? Quote Link to comment Share on other sites More sharing options...
tschak909 Posted January 24, 2021 Author Share Posted January 24, 2021 There is a button in the FujiNet flasher software, which can show debug output from the FujiNet. Can you please, press this button, attempt to boot the Atari, and paste the contents of the console window here in a reply window, so we can debug? -Thom Quote Link to comment Share on other sites More sharing options...
mozzwald Posted January 24, 2021 Share Posted January 24, 2021 9 minutes ago, FreddieBear said: The blue LED stay on always. This tells me that the FujiNet is in SIO2BT (Bluetooth) mode. Press and hold button A (far left button) until the blue light turns off. Then turn off/on the Atari and see if it boots Quote Link to comment Share on other sites More sharing options...
FreddieBear Posted January 24, 2021 Share Posted January 24, 2021 12 minutes ago, tschak909 said: There is a button in the FujiNet flasher software, which can show debug output from the FujiNet. Can you please, press this button, attempt to boot the Atari, and paste the contents of the console window here in a reply window, so we can debug? -Thom Using 'COM37' as serial port. Showing logs: [18:43:24][18:43:24] [18:43:24]--~--~--~-- [18:43:24]FujiNet 0.5.e6b3e94e 2021-01-22 01:42:35 Started @ 3 [18:43:24]Starting heap: 4051968 [18:43:24]PsramSize 3932108 [18:43:24]himem phys 4456448 [18:43:24]himem free 4456448 [18:43:24]himem reserved 262144 [18:43:24]FujiNet Hardware v1.0 [18:43:24]SPIFFS mounted. [18:43:24]SD mounted. [18:43:24]fnConfig::load [18:43:24]Found copy of config file on SD - copying that to SPIFFS [18:43:24]copy_file "/fnconfig.ini" -> "/fnconfig.ini" [18:43:25]copy_file copied 717 bytes [18:43:25]fnConfig::load read 717 bytes from config file [18:43:25]Starting SIO2BT [18:43:25]E (2415) BT_OSI: config_save, err_code: 0x4 [18:43:25] [18:43:25]ESP_SPP_INIT_EVT [18:43:25]ESP_SPP_INIT_EVT: client: start [18:43:25]ESP_SPP_START_EVT [18:43:25]Baudrate already at 19200 - nothing to do [18:43:25]disk MOUNT [18:43:25]ATR MOUNT [18:43:25]mounted ATR: paragraphs=5760, sect_size=128, sect_count=720, disk_size=0 [18:43:25]Creating a default printer using FS_SDFAT storage and type 12 [18:43:25]SSH client initialized. [18:43:25]ModemSniffer::ModemSniffer(FS_SDFAT) [18:43:25]SIO SETUP [18:43:25]Set HSIO baud from 0 to 67431 (index 6), alt=68209 [18:43:25]Available heap: 3885308 [18:43:25]Setup complete @ 958 (955ms) [18:45:25]BUTTON_A: LONG PRESS [18:45:25]ACTION: Bluetooth toggle [18:45:25]Stopping SIO2BT [18:45:25]Baudrate already at 19200 - nothing to do [18:45:25]E (122295) BT_OSI: config_save, err_code: 0x4 [18:45:25] [18:45:25]W (122295) BT_APPL: bta_dm_disable BTA_DISABLE_DELAY set to 200 ms [18:45:25]E (122495) BT_OSI: config_save, err_code: 0x4 [18:45:25] [18:45:25]WiFi connect attempt to SSID "Frontier7904" [18:45:25]WIFI_EVENT_STA_START [18:45:25]esp_wifi_connect returned 0 [18:45:25]fnConfig::save [18:45:25]fnConfig::save wrote 717 bytes [18:45:25]Attemptiong config copy to SD [18:45:25]copy_file "/fnconfig.ini" -> "/fnconfig.ini" [18:45:25]copy_file copied 717 bytes [18:45:25]WIFI_EVENT_STA_CONNECTED [18:45:26]IP_EVENT_STA_GOT_IP [18:45:26]Obtained IP address: 192.168.254.17 [18:45:26]SNTP client start [18:45:26]Starting web server on port 80 [18:45:28]SNTP time sync event: Sat Jan 23, 18:45:27 2021 -0800 [18:45:44] Serial port closed! Thanks for helping out. BT blue LED out and white LED full on. Still can't boot. Same issue. Quote Link to comment Share on other sites More sharing options...
tschak909 Posted January 24, 2021 Author Share Posted January 24, 2021 Somehow, You have bluetooth enabled. Hold down button A until the lights change. -Thom Quote Link to comment Share on other sites More sharing options...
FreddieBear Posted January 24, 2021 Share Posted January 24, 2021 Yes I did this by holding down the WiFi button which turned off BT. Quote Link to comment Share on other sites More sharing options...
Atari8guy Posted January 24, 2021 Share Posted January 24, 2021 I've noticed since the last (or potentially previous) update that when I boot Fujinet now, it never connects to my network any longer. I go into config and "reconnect" and its fine for the duration of the session but it used to just connect automagically. Anyone else notice this? Quote Link to comment Share on other sites More sharing options...
NISMOPC Posted January 24, 2021 Share Posted January 24, 2021 3 hours ago, MrFSL said: Just a note back on the PSU issues. I made a quick study of USB based power supplies with the Atari and I can tell you that MOST cell phone power supplies were not capable of outputing what was written on the case. I have wall-warts that claim 1.9A that can barely do 1.1 etc. Something like this can be very helpful https://www.amazon.com/gp/product/B07PWC7YMT/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&th=1 Awesome. Just ordered that specific unit from Amazon Prime (delivers tomorrow) for just over $9 shipped (had a $3 coupon). Quote Link to comment Share on other sites More sharing options...
tschak909 Posted January 24, 2021 Author Share Posted January 24, 2021 For those who have updated firmware over the last few days, please flash again, @mozzwald has rolled back a change in CONFIG that is affecting some of you and your ability to connect to your network. -Thom Quote Link to comment Share on other sites More sharing options...
mozzwald Posted January 24, 2021 Share Posted January 24, 2021 1 hour ago, 8bitguy1 said: I've noticed since the last (or potentially previous) update that when I boot Fujinet now, it never connects to my network any longer. I go into config and "reconnect" and its fine for the duration of the session but it used to just connect automagically. Anyone else notice this? I had made a change to config that skips connecting to wifi at the start. This made for a slightly quicker boot by skipping the wifi poll and taking you right to the hosts screen. This does not prevent wifi from connecting automatically if you have already saved your ssid & password. Note, the white light indicates wifi is connected. I removed this change yesterday due to a different issue so you can update the firmware again to remove this change. 2 Quote Link to comment Share on other sites More sharing options...
FreddieBear Posted January 24, 2021 Share Posted January 24, 2021 I still have a broken FujiNet and refuses to boot up. This is a major problem (software problem I'm guessing) that renders the device useless. I wish someone could offer a solution other than purchasing another one. These are my thoughts for today. Quote Link to comment Share on other sites More sharing options...
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord
Recommended Posts
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.