Jump to content

MrFSL

New Members
  • Content Count

    42
  • Joined

  • Last visited

Community Reputation

24 Excellent

About MrFSL

  • Rank
    Space Invader
  • Birthday August 20

Profile Information

  • Gender
    Male
  • Location
    Rochester, NY

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Here ya go Larry. This was posted recently in a different thread.
  2. Well, this is unfortunate for you. You make it work, but cannot enjoy the fruits of your labor. At least your changes haven't made things worse. Perhaps, new capacitors or no capacitors as suggested earlier. For me, if I remove the IDE÷ and use just a HIAS patched OS ROM I could achieve index 0. This was my indication that it might be possible with the IDE+. Also, i had no idea how the device switches between SIO methods. I expected no change for SDX SIO, but couldn't be sure there wasn't a connection in software so i was testing both ON and OFF. Now I know. Lastly, my pleasure to test. Why are any of us fooling around with these old ataris if not too tinker and marvel at them as they do those things we could have not imagined 30+ years ago. Thank you, and all the other guys who do what you do here at atariage.
  3. Well.... I started looking into this further by opening this thread here: What I learned there, which is relevant here, is that the default index of 6 should be acceptable for any SDX. However, I also learned (and I don't see it documented other places) that SDX SIO driver isn't really capable on its own of exceeding an index of 4ish. Much of this depends on the version of SDX as well as the condition of the hardware in your atari and even on the types of add-on hardware you might have installed or on the SIO bus. Regardless - straight up SIO on SDX is known to be slow and having this index higher could make things not work well. Devices like the SDrive-Max seem to negotiate around the speeds if errors occur causing IO operations to usually continue. With the Fuginet today - not so much. While it might be a bit early in testing - regarding the IDE+ v2 SDX - @drac030 seems to have gotten it working with its own internal IO at much faster indexes! Cool.
  4. WIFI CONFIGURATION At startup - it is very convenient that the configure WIFI comes up, but there really needs to be a way to exit that configuration and continue to use the unit. After all it does have an SD card in it that does not require WIFI.
  5. So with IDE+ SIO off --- we are about the same. Index 6 works fine. 5 seems ok too. 4 isn't reliable. BUT!!!!!! with IDE+ SIO on --- ummmm..... wow. All the way to Index 0 seems stable. So stable in fact that I threw extra testing at it. To include loading yoomp from SDX (log included) and other binaries. Nice work. I simple thought that IDE+ SIO should perform better than SDX SIO... but you sir... you have managed to max things out. What did you change this time? IDE_HSIO_OFF.zip IDE_HSIO_ON.zip
  6. Just now with a cryptic amount of RESET pushes and key holds and weirdness... I did manage to get SDX up and reading a D1 that was not the fnc tools. I can't reproduce what I did. But it is possible! LOL.
  7. I will try it tonight I am sure!!!!
  8. So - I am doing something wrong - or it is a bug?
  9. MyPicoDos I find it useful to use dir2atr from Hias (https://www.horus.com/~hias/atari/#atarisio) to quickly create ATR files. When creating these disk images with MyPicoDos I find an interesting bug. Fujinet will boot the DOS but then drops the configured drives and instead offers up the D1 fnc tools as if I were using a SDX cart. It would be nice to be able to use MyPicoDos. I will include an ATR I made earlier as an example. This ATR has a single file BIOS17C.COM. If this is somehow expected behavior, I guess I do not understand how the Fujinet determines when to offer up the tools disk image on D1. Ultimately it would be nice to be able to access D2, D3, etc on the Fujinet from SDX. If that is possible I have not been able to find out how to make that work. bios17c.atr
  10. These changes make SDX on IDE+ much nicer than running SDX on a cart. So much fun.
  11. Attached are the debug logs from the Fujinet. I started at the last known working Index for either IDE+ HSIO ON/OFF (Index 7 for IDE+ SIO ON, Index 5 for IDE+ SIO OFF.) Amazing results! HSIO Off does not seem to have changed (I don't think.) HSIO ON now works as I would expect. Things seem stable up to Index 3 (before Index 7 was the best.) Directory listings and binary execution still work at Index 2 and 1 but there are significant delays or hangs. Index 0 fails unsurprisingly. I swapped over to the SDrive-Max which admittedly I do not know how to get good debugging logs. I can watch the screen and count the time it takes binaries to load. As best as I can determine, whatever changes you have made seem to have positively effected HSIO there as well. Congratulations! IDE_HSIO_OFF.zip IDE_HSIO_ON.zip
  12. Well I can test. I have a Sys-check card and can change the ROM to use the Hias patches. The difficulty is doing this while still using SDX. Enabling the ROM feature on the Sys-check knocks out the IDE+. I can use the Maxflash1 ROM image on a cart - but I am not sure if that would be helpful If I don't use any flavor of SDX and I just use the Hias ROM patches to load files from the Fujinet or SDrive-Max it seems that Hi Speed IO works immensely better than anything under SDX. I can adjust the index on Fujinet (including index 0) and roughly time the loading screen of yoomp for instance to see that their is a capability of high speed IO. This fact alone leads me to believe that there are many more places to look before I chop out capacitors. More important then whether I achieve reliable 0 index verses 1 or 2 or 3 really doesn't matter. What this thread is really about is the IDE+ and its High Speed IO functionality. Currently when enabled we are seeing less reliable / slower IO then when disabled. That appears to be an interesting bug indeed. If drac030 wants to get to the bottom of it that would be cool and I am enjoying assisting and testing and learning. One thing that would be useful (if it existed) is a DOS independent SIO meter application or method - perhaps something akin to dd in Unix. This would help standardize testing. So far I am either listing a directory or loading a larger binary; in Fujinet I get better debug logs; in SDrive-Max not so much (seems the SDrive-Max is making adjustments on its own when it sees errors.) What do you guys think? Is there a good program or method to achieve SIO testing more robust? Oh and thanks for the additional input on this thread. @fenrock I too would not have known the proper way to remove the caps and then what to do after. Like you, my strengths are not in hardware. @flashjazzcat and @drac030 and @BillC just taking the time to educate us is appreciated. I'm sure you all know that or why else would you keep doing it? Riches and fame, eh? LOL.
  13. FLS.COM not working in SDX As above this is tested on the Maxflash1 cart as well as the IDE+ v2. The odd "special" characters that seem to follow a "return" key press is a ^A character and its the same odd character we see following the network password on the previous post. Perhaps there is some sort of line-ending issue? Attached are logs from the tnfs server. The logs follow the screenshots below. Log A is working (without directory) while Log B demonstrates problems with sub-directories and filters. tnfs_log_A.txt tnfs_log_B.txt
  14. FNET.COM not working in SDX Using SDX on 800XL both IDE+ v2 and Maxflash1 rom cartridge image the FNET command fails to connect to network. Attached are the serial logs for each SDX environment. This is the output from hostapd (wireless router) I can verify if I boot directly to the Fujinet I can select and properly connect to this TestNet network. I can also verify running config.com I can connect as well. FNET_SDX.zip
×
×
  • Create New...