tschak909

If you pay attention to the video, it is pointing directly to it. https://fujinetwifi.github.io/ACTION-NIO/NIO.ACT as a N: URL: N:https://fujinetwifi.github.io/ACTION-NIO/NIO.ACT -Thom

With #FujiNet on your #Atari8bit. Using the N: device, you can include code and libraries directly from GitHub, directly in your programs. Shown here is a compile and run example MASTODON client that's part of the upcoming user's manual, but fetching NIO from N: #retrocomputing

Yes! https://github.com/FujiNetWIFI/fujinet-firmware/issues -Thom

Can you print the tnfsd version that comes up when you start it? -Thom

Can you paste output from the flasher's debug monitor, as the error happens?

Is there a significant delay before it states that it can't open the directory? It can possibly be a firewall on your Mac preventing connection to the tnfs server.

You're asking for an info-dump, so I'll start slow. All the info needed is in the wiki, if you dig. Firmware Bring-up instructions are here: https://github.com/FujiNetWIFI/fujinet-firmware/wiki/pio-6-x-howto In a very basic sense: Applications set up a DCB pointing to the device they want to deal with, call SIOV, repeat. The commands implemented by the Atari target: FujiNet device (control, setup): https://github.com/FujiNetWIFI/fujinet-firmware/wiki/SIO-Commands-for-Device-ID-%2470 Network Device: https://github.com/FujiNetWIFI/fujinet-firmware/wiki/SIO-Commands-for-Device-IDs-%2471-to-%2478 The Firmware is set up in three main sections: lib/ bus/ device/ media/ bus/ implements all the required bus arbitration bits. device/ implement all the various sub-devices media/ implements the media types used by the disk device. And yes, the fact that you're trying to implement a parallel implementation on an existing platform, without experiencing the existing solution is a bit silly. -Thom

Because the platform itself is built around a stable microcontroller, while there will be hardware changes (e.g. changing from micro-USB to USB-C), the firmware will always be in development, as new features are added. -Thom

We don't build them ourselves, but work with vendors to ensure they can build and make them available, a list of them are here: https://fujinet.online/purchase/ (if your favorite vendor is out, ask them to make more) As for the Astrocade, unless I am missing something, the whole processor bus is available at the expansion slot, no? -Thom

Yes. One is being developed for the Atari 2600, that is extending PlusCart. On the Astrocade, you have a full system bus via the expansion slot. -Thom

Thanks, any images at the moment, are placeholders, which will be re-drawn to match. (especially because as is, the images are far too dark to print well) -Thom

Would anyone be interested in starting a bring-up of FujiNet to the Astrocade? It could potentially work using the RP2040 as a front-end to the ESP32 running the network stack, and connecting via the expansion port. -Thom

Hello all. I've finally started on a User's Guide for the ATARI FujiNet. It's being written in DocBook, which is a standard for publishing technical books, articles, etc. Its big advantages are that it separates content from style, but it also has a good deal of tags to provide semantic context (such as marking up commands, screen shots, call-outs, etc.) The current style-sheet is being based on the type setting used by Atari for its more technical software products, such as "Telelink I" and "Music Composer" where the Optima font face is used as the primary font, and the highlight color is a light blue. The documentation, like everything else in FujiNet is being developed publicly, and is available in GitHub: https://github.com/FujiNetWIFI/fujinet-manuals in the fujinet_for_atari_users folder. The main DocBook file is: https://github.com/FujiNetWIFI/fujinet-manuals/blob/main/fujinet_for_atari_users/fujinet_for_atari_users.dbk I am using a combination of emacs, and XMLMind DocBook Editor to compose the material: http://www.xmlmind.com/xmleditor/docbook_editor.html While there is preliminary styling in place, this isn't being actively changed at the moment, as content floods in. Once content is stable, we can start thinking about refining the style sheets, not just for PDF, but for HTML and EPUB as well. I will periodically attach a render of content, as a PDF, as we go along. Any and all help would be appreciated, as this is a very important undertaking. Some snips of pages: I also recorded a video showing the process, here: -Thom fujinet_for_atari_users.pdf

Awesome! No, none of the Atari printers do ATASCII, this is why we made the ATASCII printers. -Thom

I am assembling talk notes on the whole process, and when it's recorded, I will also export this to markdown to put into the FuijNet Wiki. Please look over and comment if I am missing bits or context? https://github.com/FujiNetWIFI/fujinet-high-scores/blob/main/hse-talk-atari/talk.org Thanks, -Thom

Please contact the vendors and let them know that they need to build more FujiNets. The FujiNet project itself doesn't manufacture them, but rather works with each vendor to make sure that they are available. And the vendors need to know what to make based on customer feedback. -Thom

For those who find this later, FujiNet's CONFIG program needs at least 32K of RAM to work. If you have less, then you will need to use the Web UI to mount things. If you haven't configured the network yet, put an SD card into the slot, and power on the FujiNet once. This will write a fnconfig.ini file to the card, that you can modify the SSID and Password for your WIFI network. Placing the card back in the FujiNet and restarting, the FujiNet's white WIFI light should light within 30 seconds, and you should be able to connect to the device's wifi network, using its hostname, http://fujinet/ -Thom

I am aware of the M4 board, and they've used an 8266 basically as just a WiFi modem. I'd like for somebody to actually come over, now that we know a bit better on how to do a bus interface, and start a bring-up. -Thom

@apc (aka Jan Krupa) is hard at work making it possible for #FujiNet to boot disk images (e.g. ATR for #Atari8bit) over other protocols. This work is currently in master, and will be pushed to production when we can adequately test. #retrocomputing -Thom

Thanks, @mozzwald! -Thom

Interesting... I'm curious to see how best to implement this, as we can't just assume trackball either. -Thom

If anyone wants to add it. Go right ahead.

The file looks well formed in a hex editor. This is what I see from okular: So a bit odd. Can someone else reproduce with Print Shop? (there is a copy on apps.irata.online) -Thom

Perchance you can attach the PDF? Or is it a zero length file? It's also worth a look in the debug monitor window in the FujiNet flasher to see what is happening. -Thom

I'm trying to foster engagement. -Thom