Jump to content

a8isa1

Members
  • Content Count

    1,805
  • Joined

  • Last visited

Everything posted by a8isa1

  1. That drive is configured for use on a PC. IBM originally set both floppy drives to DS1 and used a *flip* in the cable for the second drive. You could desolder the holes and install dip switches. The ATR8000 designates the drive with DS0 selected as Atari D1: -SteveS p.s. The drive after the flip in the cable was probably the first drive on a PC. (It's been a long time. Memory sketchy)
  2. Yep, 1.2 MB drives on the ATR8000 format to 4004 sectors. I tried to write a procedure to make it easy to setup a 1.2 MB drive but the ATR8000 is so quirky in a single drive configuration that I didn't come up with instructions for all the things that can and often do go wrong. Below is basically what happens if the process goes smoothly. I'm using FujiNet in this example because nothing else I still own wanted cooperate, not SDrive-MAX (homebrew), SIO2PC cable, swapping drive mechs It's easier if one is able to change the drive the drive select but hopefully this will work for your situation Leave the drive and the ATR8000 powered off. Boot Atari w/ MyDOS 4.53/4 using FujiNet. My was plugged directly into the ATR8000 because cables won't stay plugged into the fujinet 1.0 passthru SIO port. While the Fujinet is still attached use MyDOS option O - Change Config. Use it twice (because it works more reliably). Once to remove drive 1 then again with the 1.2MB drive parameters which are: Drive Number: 1 Remove Drive: N Is drive configurable? Y High capacity drive: N I drive double sided? Y Tracks/side? 77 Step rate: 3 When I hit enter I should se under the MyDOS title the following: Disks 1S= '=' signifies a double sided disk. 'S' signifies Single density. Disk is not formatted yet so 'S' is assumed UNPLUG FUJINET. Power up disk. Insert diskette. Power up ATR8000. I try to change density with command 'P' 'P' and then '1,D' which is drive 1, double density If it works then great but ften the density won't change. This seems to be one of those ATR8000/MyDOS quirks. I go ahead and format the disk. If it formatted in single density I use the 'P' command again. Density should change this time. Format the disk again. If while formatting I hear the stepper motor has a regular cadence then all is well. If there's one sound and very long pause before the next sound then something is not right. Probably have to start over If formatting, in double density, is successful then write DOS to the disk, MyDOS option 'H' Test by booting the computer. No need to reset the ATR8000. Hang onto that disk. Note: I had to unplug my FujiNet 1.0 during the process. With FujiNet version 1.4 and up perhaps one can just switch it off. Configuring a drive is much easier if the drive select of the ATR8000's drive can be set to DS1 (aka D2:). Usually I can just set the drive parameter and format. No issues at all or far fewer issues at least. Well, that's it for my re-visit to setting up a 1.2 MB drive on the ATR8000. Eric, I hope it works for you as well. Regard, SteveS
  3. I'm going mad! Someone please try this: Make sure FujiNet is powered externally. Make sure webui has Config Boot set. Boot Atari to CONFIG Mount from ATARI-APPS.IRATA.ONLINE/DOS/Atari DOS 2.0s.atr Press OPTION to boot Atari DOS Press FujiNet Button C *RESET* Try to get a directory listing. You should get Error 138 <------- Do NOT skip this step Try to reboot your Atari. Do an atari RESET. Turn off the machine then on. Try FN Reset more times. Just don't unplug Fujinet's power cable *YET*. For me CONFIG will never boot again. I'm stuck until I unplug FujiNet's power cable. Regards, SteveS
  4. I see. Here's my 2 cents: Configured as I described. I press FN Reset. Now my ATR is no longer mounted. Config disk is not mounted either. I shut off my Atari and turn it back on. I don't get into CONFIG and I don't boot a mounted disk. I have nothing available. I can only get back to operational if I remember to pull the plug on FujiNet. I have to do this to physcially reach the power switch on Fujinet 1.0 as the cable end partially blocks access to the switch. No, I don't offer a solution. I'm just venting. SteveS p.s. Done venting. Perhaps yet another button mode that forces CONFIG disk to be mounted. [EDIT] Once FNC-TOOLS are available I can help myself of out my mess.
  5. I don't know if I've encountered a bug, two bugs, or I'm misunderstanding how this is supposed to work. I'm running Fujinet 1.0 hardware. It's externally powered plugged into my 800XL. FN firmware is 0.5.879c407c 2021-04-02 01:14:21. WebUI has CONFIG Boot set. I've mounted Atari DOS 2.0S ATR from ATARI-APPS.IRATA.ONLINE. It boots OK. When I press FujNet Reset I expect to see the Config disk appear as D1:. However, when I try to get a directory listing the activity light flashes brightly then goes to dimly lit for a couple of seconds. I get Error 138. If I then do a coldstart (FN is still powered) the activity light flashes once dimly then the 800XL reboots itself, over and over again. I'm providing a debug trace. It begins when I try to get that directory listing. Regards, SteveS FN_reset_capture.zip
  6. This turns out to be a user problem but it was one of years of bad habits in the making. I some distant past I had appended RVerter/Bobverter drivers to most of the terminal programs I had been using on the disk that I use for everything. A few years ago I started using SpartaDOS X and the newest updates/betas of ICET XE. By this time I had dropped the habit of attaching the driver to the executables. I don't need such a shortcut. SDX has batch files. Now FujNet comes along and I need the 850 driver loaded. No problem with this. Later on I decide to test FujiNet on my 800. Unfortunately, I can't use SDX or my CF card or ICET XE on my stock 800. This forces me to dig my old and small collection of terminal programs. I load the 850 driver and whichever terminal program I wish to use not realizing a driver conflict was waiting for me, Well, at least that's what I assume was happening. I don't see the Bobverter splash notice on my 800. (It does appear now when I repeat the exercise on my 800XL). I don't have debug tools on 800 and I don't have the know-how to recreate the problem in emulators. So, yeah. Just an assumption of what happened. Sorry, for the false alarm! Regards, SteveS
  7. It runs on my stock 48K 800 but it will not accept any keystrokes which means I can't select Forecast. Console keys do work. I'm running firmware 0.5.879c407c 2021-04-02 01:14:21 on a FujiNet 1.0. I love your program BTW (when using my 800XL)! Regards, SteveS
  8. Someone asked in IRC about 80 column terminal programs for 800. I could not recall if Omnicom works on the 800 or not. Apparently it doesn't, however when the program crashed I tried Flickerterm 80 which I know should work. After I load the 850 handler and start Flickerterm 80 it comes up in ASCII mode and at 1200 baud. However, the keyboard does not respond. After about 5 seconds the emulation switches to VT100 and baud rate is now at 19,200. The keyboard still will not respond and now the FujiNet activity LED is flashing brightly with about 3 pulses per second. It never stops flashing. Pressing button C resets Fujinet but the LED continues to flash. I next tried Bobterm but it halts while loading some module. I then tried AMODEM 4.2. I'm able to enter an ATDT sequence and connect but the keyboard stops responding here as well. Fujinet is not flashing. I recently updated the firmware. Fujinet works fine on my 800XL I'm providing fujinet debugging data. It begins at the point I started the 850 handler. Below are some excerpts that I thought odd. They occured with no intervention from me. The keyboard remained non responsive the whole time. set_baudrate change from 19200 to 1200 Modem streaming at 1200 baud Modem was active - resetting SIO baud set_baudrate change from 1200 to 19200 set_baudrate change from 19200 to 1200 Modem streaming at 1200 baud Modem was active - resetting SIO baud set_baudrate change from 1200 to 19200 set_baudrate change from 19200 to 19200 Modem streaming at 19200 baud Modem was active - resetting SIO baud set_baudrate change from 19200 to 19200 set_baudrate change from 19200 to 19200 Modem streaming at 19200 baud Modem was active - resetting SIO baud set_baudrate change from 19200 to 19200 Regards, SteveS atari800_fujinet_debugging.zip
  9. There were two separate issues as far as I can tell. 1) A binary load file I hadn't used previously used on FujiNet didn't work then 3 more files also did not work 2) Something happened to my TNFS server and nothing was loading. I did not realize this at the time and thought this was a continuation of the issue above. Mozzwald suggested I restart the server. The file that was queued was a binary file that did have an .XEX extension. I thought issue #1 had been solved. However, the next file I tried was Galactic Chase. This did not load. I queued up each of the files that hadn't loaded the first time and once again none of them would load. I thought nothing had been resolved. I kept trying. A new file, perhaps Bosconian, then worked. At this point I had learned how I can obtain the debug data which I did and passed it on to Thom. I subsequently learned that binary load files need an extension that FujiNet firmware can parse. 'XEX' was mentioned. I was not previously aware of this requirement but now I am. Problem solved. I've never needed to do this for any other disk emulation, disk emulation hardware, or Atari emulators but now I know it's needed for FujiNet. The collection from sourced my files from was originally derived from someone else's disk set. None of the file names have extensions. Not knowing I needed file extensions I simply copied the files to the TNFSD folder. -SteveS
  10. Still having problems. Many XEXes will no load from my local TNFS server. No activity light on FujiNet. I'm providing a debug trace of the game Galactic Chase. Captured with mincom terminal emulator -SteveS CF: 31 53 00 00 84 FujiNet CONFIG boot disk sio_process() ignoring status command CF: 31 53 00 00 84 FujiNet CONFIG boot disk sio_process() ignoring status command CF: 31 53 00 00 84 FujiNet CONFIG boot disk sio_process() ignoring status command CF: 31 53 00 00 84 FujiNet CONFIG boot disk sio_process() ignoring status command CF: 31 53 00 00 84 FujiNet CONFIG boot disk sio_process() ignoring status command CF: 31 53 00 00 84 FujiNet CONFIG boot disk sio_process() ACK! disk STATUS response: 0x00, 0xff, 0xe0 ->SIO write 4 bytes COMPLETE! CF: 31 52 01 00 84 FujiNet CONFIG boot disk sio_process() ACK! ATR READ ->SIO write 128 bytes COMPLETE! CF: 31 52 02 00 85 FujiNet CONFIG boot disk sio_process() ACK! ATR READ ->SIO write 128 bytes COMPLETE! CF: 31 52 03 00 86 FujiNet CONFIG boot disk sio_process() ACK! ATR READ ->SIO write 128 bytes COMPLETE! CF: 31 52 04 00 87 FujiNet CONFIG boot disk sio_process() ACK! ATR READ ->SIO write 128 bytes COMPLETE! CF: 70 fa 00 00 6b sioFuji::sio_process() called ACK! Fuji cmd: GET WIFI STATUS ->SIO write 1 bytes COMPLETE! CF: 70 d7 00 00 48 sioFuji::sio_process() called ACK! ::mount {5} "192.168.1.188" ::mount_local Attempting mount of "192.168.1.188" ::mount_tnfs {5:0} "192.168.1.188" Calling TNFS::begin Resolving hostname "192.168.1.188" Resolved to address 192.168.1.188 TNFS mount 192.168.1.188[192.168.1.188]:16384 TNFS mount successful. session: 0x23c6, version: 0x0102, min_retry: 1000ms vfs_tnfs_register "/tnfs0x3fff9c98" @ 0x3fff9c98 = 0 "ESP_OK" Selecting '/Galactic Chase (1981)(Spectrum)' from host #5 as r on D1: fujiHost #5 opening file path "/Galactic Chase (1981)(Spectrum)" TNFS open file: "/Galactic Chase (1981)(Spectrum)" (0x0001, 0x01b6) File opened, handle ID: 0, size: 15898, pos: 0 ::get_filesize tnfs_lseek currpos=0, pos=0, typ=1 tnfs_lseek success, new pos=0, response pos=0 tnfs_lseek currpos=0, pos=0, typ=2 tnfs_lseek success, new pos=15898, response pos=15898 tnfs_lseek currpos=15898, pos=0, typ=0 tnfs_lseek success, new pos=0, response pos=0 disk MOUNT ATR MOUNT tnfs_lseek currpos=0, pos=0, typ=0 tnfs_lseek success, new pos=0, response pos=0 ATR header missing 'NICKATARI' ::mount {1} "fujinet.online" ::mount_local Attempting mount of "fujinet.online" ::mount_tnfs {1:0} "fujinet.online" Calling TNFS::begin Resolving hostname "fujinet.online" Resolved to address 157.245.127.133 TNFS mount fujinet.online[157.245.127.133]:16384 TNFS mount successful. session: 0x9f99, version: 0x0102, min_retry: 1000ms vfs_tnfs_register "/tnfs0x3fffa9e4" @ 0x3fffa9e4 = 0 "ESP_OK" Selecting '/cassette/O_Rileys_Mine.cas' from host #1 as r on D8: fujiHost #1 opening file path "/cassette/O_Rileys_Mine.cas" TNFS open file: "/cassette/O_Rileys_Mine.cas" (0x0001, 0x01b6) File opened, handle ID: 0, size: 11891, pos: 0 ::get_filesize tnfs_lseek currpos=0, pos=0, typ=1 tnfs_lseek success, new pos=0, response pos=0 tnfs_lseek currpos=0, pos=0, typ=2 tnfs_lseek success, new pos=11891, response pos=11891 tnfs_lseek currpos=11891, pos=0, typ=0 tnfs_lseek success, new pos=0, response pos=0 disk MOUNT Cassette image filesize = 11891 tnfs_lseek currpos=0, pos=0, typ=0 tnfs_lseek success, new pos=0, response pos=0 FUJI File Found COMPLETE! CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84
  11. sorry, unable to build the fujinet_flasher on this old system. I update the firmware with esptool.py. -SteveS
  12. I can no longer boot XEX files after this update. -SteveS
  13. [EDIT] I was typing this before I retested. Sorry, for the initial contradictory statements. [Correction] Also sounds similar to when my cell phone is within 1 foot of my A8 speakers. Record-2.wav For my sound it does not matter whether my Atari or the #FujiNet are powered. Only the speakers need be powered. The speakers don't need to be connected to anything. This is a sound I have had for years, across ownership of 3 cell phones. -SteveS
  14. Are you pressing START at the Bosconian screen and again at the "GAMER" screen? -SteveS
  15. The 128K version loads OK here with NTSC 800XL, Rambo XL, Fujinet (Feb 6, 2021 firmware) 64K version at that post is PAL-only so I can't use it. Did you remember to disable BASIC? -SteveS
  16. 17 year, 6 month, 15-day necrobump? Nice! -SteveS P.S. I guess that would be 14 days.
  17. Coincidentally, Yesterday I tried Telelink with Fujnet. I hadn't used that cartridge in 40 years and I was feeling nostalgic. I saw "RS232 ERROR: 130" and no typed characters. I tried this with zero device slots mapped on fujinet to mimic how I used Telelink which was with an just 850 and a Novation D-CAT modem. I next tried a disk image with an 850 boostrap file. This got me into the Telelink program but acting only as a terminal with local echo enabled. I think the driver is downloading. However, within the Telelink program there wasn't a response from Fujinet's modem emulation. -SteveS
  18. Back in business! Thanks! Never would have tracked down that offset for SPIFFS on my own. Regards, -SteveS
  19. I don't have the ability to run the Fujinet-Flasher. Laptop is crippled so I'm running live with RAM file system and I don't have the necessary resources. This is also why I am using ESPTOOL.PY. Where does SPIFFS.BIN belong? What offset? -SteveS
  20. Unable to build Fujinet-Flasher I had been using manual flashing with esptool.py using the following command line which had been provided to me: python esptool.py --chip esp32 --port /dev/ttyUSB0 --baud 460800 --before default_reset --after hard_reset write_flash -z --flash_mode dio --flash_freq 40m --flash_size detect 0x1000 bootloader.bin 0x8000 partitions.bin 0xe000 boot_app0.bin 0x10000 firmware.bin With firmware for 2/4/2021 I thought I had a success but discovered the new "COPY" feature was not available. I confirmed from the web interface that an update to the firmware had been completed. Looking at the command I realized the spiffs.bin wasn't being updated. I tried to add it. not knowing where it belonged I tried adding to the end. Had insufficient twice. One time this didn't happen but neither was the COPY function available. After a few more attempts something seriously went wrong. After flashing the 3 LEDs blinked for 1 second then my #FujiNet went dark. I tried the update as done above. Still dark.I I tried to restore the original firmware with which my #FujiNet had been supplied. Restore was from a backup which I had made first thing. Still dark I feel as though I have wiped SPIFFS and just don't know where it belong but perhaps I have done worse. Is my error recoverable from here. I mean my location? Did I brick my #FujiNet? -SteveS
  21. Didn't know where to post this. This thread seems to be the catch-all. To my surprise my new TBA #FujiNet 1.0 is perfectly happy with my SWP ATR8000. I mean seemless cooperation of the two devices. Either can act as D1:. Although the ATR8000 is strictly a 1X SIO device neither it nor the #FujiNet get confused while the #FujiNet is running divisor 0, via Hias Reichl's patched (in RAM) OS or his MyPicoDOS. P: device acts as expected. I get an error 140 if using LPRINT while #FujiNet is set as default. If I set it to use P2:, thus both P: devices have unique IDs, then I don't get an error. LPRINT output would be going to ATR8000's printer spooler and no error generated. Opening a channel to P2: works great and #FujiNet's logical printer gets any ouput. No problems accessing #FujiNet's R: device. I did not attempt to use the ATR8000's R:. I don't have a modem or cable for its RS232 port. I did have one issue with my #FujiNet. Most of my SIO cables will not stay attached to my TBA #FujiNET but I found two that have no problem at all. The usable cables have the connector shown below. (Sorry but I always have been a terrible photographer). I'm very happy with #FujiNet. Congratulations to Thom, Mozzwald and everyone else involved in the project, and to the community for supporting the project so enthusiastically. -SteveS
×
×
  • Create New...