The #OpenMSX #MSX emulator is getting #FujiNet support. I am using it here to develop a Mastodon client using #Z88DK.

Code in GitHub: github.com/FujiNetWIFI/...

Noah Burney has uploaded schematics and other hardware ephemera for the #MSX #FujiNet WiFi Adapter prototypes. We are currently using #2, and it connects to a fujinet-lwm instance running on PC over USB.

#retrocomputing

github.com/FujiNetWIFI/...

A reminder that there is a Game Lobby built into #FujiNet, offering access to cross-platform multi-player networked games! Press 'L' in CONFIG!

5 Card Stud, Battleship, Fujitzee, in an open API.

#atari8bit #apple2 #coco #retrocomputing #retrogaming

Successfully opened SSH connection to my Linux box from my Panasonic FS-A1 #MSX via #FujiNet. This means network functions are working as expected.

Now our apps can start to be ported.

#retrocomputing

Writing March 2026 @Computesgazette for the FujiNet report. This one covers the Battleship game server.

moved from #Atari8bit AtariWriter to SpeedScript (was published in Compute! in 1985) as it's smaller and faster.

#FujiNet made moving across network easy!

#retrocomputing

Google voice typing mangled #FujiNet to Booty Net somehow and I can't stop laughing in the middle of the airport.

VCF SoCal 2026 - The Oasis BBS VCF SoCal 2026 lands in Orange, CA Feb 14-15 with exhibits, talks, vendors, and consignment deals at Hotel Fera.

VCF SoCal 2026 is this weekend, Feb 14th - 15th.

#VCFSoCal #VCFSoCal2026 #VintageComputerFestival #RetroComputing #ClassicComputers #ComputerHistory #VintageComputing #RetroTech #RetroGaming #Commodore64 #AppleII #FujiNet

theoasisbbs.com/events/vcf-s...

Connected Retro Computing - The Oasis BBS Connected retro computing gets real in COMPUTE!’s Gazette Issue #8 with FujiNet, TeensyROM, C64 Ultimate networking, and more

Connected Retro Computing: COMPUTE!’s Gazette Issue #8 Arrives
#RetroComputing #Commodore64 #ComputeGazette #FujiNet #TeensyROM #C64Ultimate #8Bit #VintageComputing #TypeInPrograms #HomebrewComputing

theoasisbbs.com/connected-re...

Just pushed a new feature on Southern Amis and AMIS XE, a take on the #FujiNet #ISS tracker live on a #BBS. 5 Hour Tracking showing the station’s positions — plus “Over/Near” location, lat/lon, UTC, other info. #bbsing #atari

VCF SoCal | Vintage Computer Festival in Southern California VCF SoCal is the premier Vintage Computer Festival in Southern California. Come see amazing vintage computers and retro tech, share your passion, and connect with other enthusiasts. Stroll the exhibit...

I will be at #VCFSoCal at the Hotel Fera in Orange CA on Feb 14-15, showing off #FujiNet & giving talk on 14th at 1pm on the State of the Union of the project. See you there!

www.vcfsocal.com

#retrocomputing

CubeDot, Fuji Do, and Fuji Poo, programs for #Atari8bit computers equipped with FujiNet, which allow interaction with cubeSQL, a database management system based on SQLite unfinishedbitness.info/2026/02/01/a... #atari #fujinet

GitHub - FujiNetWIFI/fujinet-hardware: Schematics and design files for FujiNet hardware Schematics and design files for FujiNet hardware. Contribute to FujiNetWIFI/fujinet-hardware development by creating an account on GitHub.

Anyone want to attempt a parallel port #FujiNet design?

The existing hardware designs can be found here as a reference:
github.com/FujiNetWIFI/...

Come by Discord if interested.

#retrocomputing

VCF East: #FujiNet - How to Use YouTube video by Vintage Computer Federation

The original #FujiNet Introduction video, when it was still just an #Atari8bit network adapter.

youtu.be/QQZ2bKe-8I0?...

I find it exceedingly ironic that this video didn't even break 1.5K views after five years.

#FujiNet #Atari8bit users:

ATARI Mailing List is now on TNFS://apps.irata.online/Atari_8-bit/Databases/Mailing List/

#retrocomputing

For #Atari8bit #FujiNet users, fnc-tools has been updated

* NCOPY NOW RETURNS PROPER ERROR CODE

* ATARI DOS 3 SCREEN IMPROVEMENT.

* ONLY SHOW PRESS ANY KEY IF NEEDED.

TNFS://irata.online/Atari_8-bit/fnc-tools.atr

Updated DOS disks in /Atari_8-bit/DOS/

#retrocomputing

Apple II and Atari 800 Internet Chess Clients YouTube video by Greg Gallardo

#appleii vs #atari8bit internet chess with #fujinet and freechess.org youtu.be/PGUzpJ8tF2k

@fozztexx has been working on a regression testing system for #FujiNet, because we really need it.

Here it is running on #Atari8bit

#retrocomputing

FujiNet RetroMate Internet Chess for Apple II (AppleWin) YouTube video by Greg Gallardo

More progress on my #fujinet RetroMate conversion. Retromate is a Free Internet Client for freechess.org. It uses ip65 and runs on Apple II, Commodore 64 and AtariXL/XE computers. I've been working on converting it from ip65 to FujiNet lately. youtu.be/WYmr10fS7MA

Handling Daisy-chaining storage on Apple II Following the release of BurgerDisk, I have been asked what it would take to handle daisy-chaining in Fujinet. I am going to explain what I’ve done and what I’ve found in this post. ## The basics – being a Smartport device Implementing a Smartport device and having it work alone on the bus is rather easy. There a few lines from the Smartport connector that we’re going to use. **Line**| **Use** ---|--- +5V| Power for your device GND| Ground for your device PH0 aka REQ| The four stepper motor phases, and REQ PH1| PH2| PH3| RDDATA| Data read WRDATA| Data write WRPROT aka ACK| Write protect signal, and ACK Apple has repurposed signals in a smart manner, so that non-smartport drives would not react to Smartport packets. ## Smartport bus basics The Smartport bus has three states: * RESET: PH0 and PH2 are high. PH1 and PH3 are down. * ENABLED: PH1 and PH3 are high. PH0 and PH2 are ignored. * DISABLED: any other state. When the Apple II boots, it resets the Smartport for a short time. Devices notice that only PH0+PH2 are high and act accordingly. Afterwards, each Smartport packet is exchanged with the bus ENABLED, PH1+PH3 high. When the packet has been exchanged, the bus goes back to DISABLED. When the bus enables, the computer wants to send a packet to a device. A device informs the computer that it is ready to receive the packet by raising ACK high. The computer replies by raising REQ (aka PH0). Data is exchanged, then the device lowers ACK to indicate reception, the computer lowers REQ, and the bus disables. This is simple. The necessary connections look like this (**Note:** the pinout is **not** the one used in BurgerDisk. The pinout shown here was cleaner to draw the schematic): ## Chaining with other devices Of course if multiple Smartport devices are on the bus, things get a bit more complicated. First, a device must know whether a given packet if for itself or another device. Devices have IDs, which are assigned at boot, right after the Smartport RESET: the computer sends INIT packets, with incrementing device IDs, until everything got an ID. In order to avoid every device getting IDs at once, when the Smartport bus RESETS, every device in the chain must pull PH3 low on its daisy chain port. This has the effect that every device after the first one sees the Smartport bus as DISABLED, and will not be able to answer INIT packets. Our device handles its INIT packet(s) and registers its ID (or IDs, if multiple volumes are present). When it is done, it stops pulling PH3 low on the daisy port, and goes back to mirroring it. The next device sees the bus ENABLED, and is able to answer the next INIT packet(s) and register its own ID(s). **This means that our device has to control PH3 on the daisy port.** How does the computer know that everything has an ID and the INIT is over ? In each INIT packet response, the device sets a flag to inform the computer “there are more volumes after this one” or “we’re done”. To determinate whether there is another Smartport device on the Daisy port, a device has to check whether the HDSEL signal is grounded. **This means our device has to ground its input HDSEL (in order to be recognized as a Smartport device), and check the daisy out HDSEL (in order to recognize the presence of a next Smartport device).** In addition to that, if the device behind is a “dumb” floppy disk drive, we have to disable it while the Smartport bus is enabled. Otherwise, even if the phases lines don’t make sense to the stepper motor, the drive will start running. **This means that our device has to control DRV1 and DRV2 on the daisy port.** Basically, we have to: * Disable daisy PH3 before we have our ID. Mirror PH3 as soon as we do. * Mirror DRV1 and DRV2 when the bus is disabled. Disable them when it is enabled. The rest of the lines can be shared. Our schematic now looks like this: Notably, we added diodes to the WRPROT (ACK) and RDDATA lines to avoid undesired interactions with other devices driving them. Some input lines that we don’t have to filter are connected directly from IN to both the microcontroller and OUT (PH0, PH1, PH2, WRDATA). Some input lines we don’t use at all are just connected from IN to OUT (EN3.5, WREQ, +12V, -12V, and of course +5V and GND). Inputs we have to filter are connected from IN to the microcontroller, and from the microcontroller to OUT (PH3, DRV1, DRV2). ## The case of /DRV2 DRV1 and DRV2 lines control enabling dumb 5.25″ drives behind the Smartport devices. LOW means enabled, HIGH means disabled. DRV2 is only used on computers that can have two 5.25″ drives on the external bus: the IIgs and the IIc+. But this line is, once again, repurposed by Apple, and on old 5.25″ disk controller cards, this pin (17) is a +12V line, which would fry the microcontroller if the user was to connect it directly to the Arduino. To be safe, it has to be decoupled. We will use an optocoupler: (**Note:** I didn’t yet receive the PCB batch with the optocoupler setup and it might be wrong). ## The firmware First we have to setup pin modes: * WRDATA (D9 here) is input pullup * DRV1 IN and DRV2 IN are input (D7 and D8) * PH3 OUT (A5) is output. We pull it low at boot as we expect a RESET. * DRV1 OUT and DRV2 OUT (A3 and A2) are outputs * HDSEL OUT (A4) is input pullup * By default, WRPROT (ACK) is input, RDDATA is input pullup. This allows the device to be silent on the bus when required. The precise algorithm of the firmware is best explained in code, but here is a bit more detail about the important question of “how to not interfere with another device when a packet is not for us?” When the Smartport bus enables, we pull ACK high and so do every device in the chain. We receive a command packet, which contains the destination device ID. If the packet is not for us, we have to let the other device answer, without interfering. This is done by: * not acknowledging the packet (not pulling ACK back low) * muting ACK and RD lines * waiting until REQ is back to low (the computer has acked the answer from the other device). On the other hand, if the packet was for us, we: * acknowledge it by pulling ACK low * wait for the computer to pull REQ low * answer the computer with our response packet Afterwards, we always re-mute ACK and RD. **Watching out for infinite loops** As soon as we need to ignore packets, it starts being dangerous to receive packets when the bus is enabled: when REQ is back to low, we’re going to notice that the bus is still enabled, and start trying to receive another packet, pulling ACK high and waiting for REQ to be high – which may never come. So, our ReceivePacket function must switch from a simple /* tell computer we're ready */ set_ack_high(); set_ack_output(); while (req_is_low()) { /* wait for computer ack */} while (wrdata_is_low()) { /* wait for start of transmission */} // receive packet to verifying that the bus is still enabled: /* tell computer we're ready */ set_ack_high(); set_ack_output(); /* wait for computer ack as long as bus is enabled */ while (req_is_low()) { if (smartport_get_state() != SP_BUS_ENABLED) { return ERROR; } } /* wait for start of transmission as long as req is high */ while (wrdata_is_low()) { if (req_is_low()) { return ERROR; } // receive packet ## More? I think going into more details in this page would make it harder to digest, and most questions/doubts should be answered by studying the schematics and firmware code. However, if I’ve left out important details here, feel free to ask questions in the comments. Note that I don’t claim to be an expert of the Smartbus, and am also far from an expert in the hardware side of things. What I made here makes sense to me, seems logical and safe, and does work on different computers with different daisy-chaining setups, so I think it must be a fairly good implementation.

I have been asked "what would it take to make the #Fujinet daisy-chainable" on #AppleII , so I tried to answer the question and share what I learnt during #BurgerDisk development:

www.colino.net/wordpress/en/archives/20...

#retroComputing

Working on the #c64 meatloaf version of #fujinet retromate. Worked out a memory issue but still need to get it to talk to freechess.org

Before apps.Before the web. Modems built communities.

This month’s Dialed Back in Compute!’s Gazette tells the story—and Southern AMIS BBS lets you live it again!

southernamis.com
Web Telnet Modem #FujiNet WiFimodem

#RetroComputing #BBSing #ComputeGazette #atari #telnet

Look at my timeline history. It's full of stuff like this. I am one of the firmware engineers for the #FujiNet project, and getting word out is a pain in the arse.

The ATARI 8-bit OS is primarily in ROM, and for disk functions you load a DOS on top of it which adds a disk handler.

This case, There's no disk, only the #FujiNet network adapter, and I do not need disk support, so we wrote NOS, which allows AtariWriter (written in 1982) to talk to modern systems.

Writing next month's COMPUTE! article on my #Atari8bit using AtariWriter, directly saving the file over the LAN to my main system via #FujiNet and NOS. No disk images. #retrocomputing

#FujiNet App Idea if someone wants to make a calendar viewer.

* ICS is easily parsed
* Google Calendar shares calendars in ICS.
* Make a nice little calendar viewer with today, week, month views.

example ICS: calendar.google.com/calendar/ica...

#retrocomputing

Using #Atari8Bit #FujiNet NOS with an SD Card. YouTube video by tschak909

The #FujiNet Network provides an SD protocol to access the SD card slot.

This can be used e.g. with #Atari8bit NOS.

How? Watch this video.

youtu.be/G0gXB3Z4Nmc

#retrocomputing

I need to finish the #Atari8Bit #FujiNet Users Manual. It has been slow going.

But part of it is that absolutely nobody has provided feedback, which I need to focus its content.

Does the content make sense?

fujinet.online/wp-content/u...

#retrocomputing

#FujiNet #WiFi Adapter for #retrocomputing systems has become a mature project. We are doing a major refactor, while trying to implement regression testing. If you can help, please come by discord. fujinet.online

#Atari8bit #FujiNet, Pole Position, Sharing tracks across the Internet! YouTube video by tschak909

For #Atari8bit #FujiNet users: I modified Pole Position - Race Designer to save its tracks on apps dot irata dot online so we all can share and play across the Internet.
youtu.be/XI0sgh9DGaw

TNFS URL in vid description.

#retrocomputing #retrogaming