tschak909

not sure if you were being funny. I don't think that would work very well -Thom

All the bits and pieces are there, e.g. the Lobby shows how arbitrary programs can be mounted and run: https://github.com/FujiNetWIFI/fujinet-apps/blob/master/lobby/atari/src/main.c#L529 This works by sending commands to the Fuji device to mount an image to device slot 1, and rebooting. The main thing to work out is the UI. Which, given the wild array of possible graphics modes, combinations of display list craziness, etc, maybe doing something like Total Replay might be sane? -Thom

Yes. -Thom

The fine folks at @ZeroPageHomeBre showed the first working breaths of the #FujiNet for the #Atari2600, which extends #PlusCart with powerful networking. Shown here playing #FujiNet 5-card-stud from the Game lobby! #retrogaming #retrocomputing (yup, that's right fellas, cooperative cross-platform networking and gaming, even on the Atari 2600!)

Well, it's funny you should mention that. This thread got us talking with Oliver Schmidt of the a2pico project, and we think we may have a path forward. -Thom

Hey! Oh man. So... I was able to test the printer by writing software that explicitly printed to the smartport printer device. And Jeff Mazur was able to make a replacement //c ROM that redirected slot 1 accesses ($C10x) to the smartport printer device, but it needs more work. Supporting this well needs the work of people much more versed than me in Apple // arcana. This, along with the smartport modem is a case of running out of bridge--mid bridge. Apple never anticipated this. -Thom

oh cool, i'll download em! Thanks! -Thom

No, it does not

This is precisely why I made the docker image. -Thom

For anyone who hacks in MAD Pascal, could you please help me, and take the PASCAL section in part 2, and convert the example programs to build in MAD Pascal? (Optionally cut and paste and adjust the content in the other parts to match?) it's intended to be a Rosetta Stone to show the same examples and pattern for every language. -Thom

I need a command I can run as part of an automated backup batch file. Did someone write a recursive copy function for SpartaDOS 3.x? or am I gonna have to slam one together? -Thom

Anyone want to come together on writing a better #atari8bit terminal program for #FujiNet? While we can use BobTerm and the like, those classic terminal programs have their limitations. The N: device has none of these. the N: device can talk a wide variety of protocols, and is packet based, so no dropped characters. It's also very fast, running at whatever the current SIO rate is (so high speed SIO can speed it up). The FujiNet also has a very large receive and transmit buffer (up to 65535 characters for both, currently.) So taking netcat, adding a dialing directory would be a good start. Attached is a short vid demo of netcat. 2024-03-23 11-51-47.mp4

it's a good idea. Will need to think on how to fold it in. -Thom

@apc @massiverobot @DjayBee and a few others got together on Discord, and we put together a custom CONFIG loader that will be used for the upcoming Atari classes at VCF East 2024. What do you guys think? 2024-03-21 18-22-32.mp4

I'm currently working on the FujiNet Atari User's Guide, and I got to NDEV.DOC, which documents loading the N: handler, and I had a particular thought: Right now, NDEV.COM can't load in DOS 2.0S' DUP.SYS, because the driver is a bit too big to fit in the area between MEMLO and where DUP is loaded. MEM.SAV only helps when you jump to a cartridge, in this case, bringing the N: handler back into memory. While we really can't do anything with the N: handler loaded via AUTORUN.SYS, could we potentially do a Load of NDEV while in DUP, detect if we're in DUP, and adjust the relocation to a higher memlo? Yes, I know this would raise MEMLO, a bunch. But it would make file operations on N: possible from within DOS 2.0 DUP. FWIW: MyDOS 4.53, nor any of the other FMS suffer from this problem (OS/A+ and DOS XL even handle NDEV just fine). The other aspect would be to try and shrink NDEV's memory footprint to below DUP's load point. For reference, the current N: device handler code is here: https://github.com/FujiNetWIFI/fujinet-nhandler Thoughts? -Thom

Part of the reason for writing the #Atari8bit #FujiNet Users Guide, is to formally document the correct behavior of commands. NCD is a complex command, with a lot of expected implicit behavior. It doesn't quite work like this, but it will someday. #retrocomputing

It is possible. The interpreter tends to wipe over the N: handler if loaded from a normal DOS, But you can load it from NOS! Once in NOS, you can: CD N:TNFS://APPS.IRATA.ONLINE/Atari_8-bit/NOS/LISP LOAD LISPXL.EXE ; for XL systems, or... LOAD LISP800.EXE ; for 400/800 systems. Once in, you have full access to N:. "D:" is also mapped to N:. (of course, the people who would need to see this, won't see this, because it's in a sub-forum they don't go into, sigh. I seriously am getting frustrated trying to get the message out...) Maybe a set of LISP functions can be made? -Thom

I thought I would ask around, before digging in to make one, I need a cartridge PCB that can accept an EEPROM (e.g. a 28C64, or 27C64 EPROM), for doing bootstrap development on FujiNet. Has anyone made one yet? If not, no big deal, I have the schematics and the pinouts. -Thom

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