phigan

The universe wanted to punish me for that post, I guess. Tonight I was using the Atari with the XEP plugged in but no HDMI in it for a bit, but then I wanted the 80 col so I plugged in the HDMI .. When I loaded BobTerm with the XEP module and connected to some places, I got garbage characters on the big screen! Same thing regardless of baud rate. Power cycled everything and tried just running 'xep80.sys' in SDX.. same thing! Garbage characters just doing a 'dir'. Has anyone else had this happen?

Wonder if the firmware author has done any further development on it. Does anyone read the polish forums?

Where's the best (cheapest? ) place to get Nextion displays right now? Ali?

This is fun. Stuck on lv 4. Got on the right side somehow once, but not sure how

Well, it sort of runs. When you first run it, the menu comes up on the XEP screen, but it's not formatted correctly. This is what I got: Then I hit C and started to type.. when I got to the end of the line, the screen went blank as if the XEP80 emulator in the Pico crashed. After power cycling everything, I tried it all again and got a different result.. Once I got to the end of the line, it started duplicating my text, and pushing the duplication off as I typed more and more.... So then I tried booting the 130XE version, and it crashed at the end of the first 80 column line I tried to type just like the first attempt. And btw, that was without the chinese screen attached to the Sophia 2. I was just using RF out. There were no further attempts

Thought I could edit my original message, but have to reply. Looks like the module should be named module1.btm instead of what I was trying. There's also a bootup.btm and I'm not sure which module that is yet.

Anyone get this working with BobTerm yet? I've tried with 1.21 and 1.23, both having the module named xep80.btm and xep.btm. Nada out the HDMI (in terminal mode).

Hey, I wonder how Chatari will look on this.

This is pretty awesome stuff. Not to distract from the graphics, sound, and games optimizations, but any plans to add R: device/modem emulation, by chance?

Wow, I haven't looked at the spreadsheet but it seems like this list is very long. I'd like to get a Sophia 2 for a US 130XE please!

This is from the latest episode of Young Sheldon. Yeah, he's on a Tandy PC but it looks like it says ProTERM 2.2 by Greg Schafer to me, but that's not what my ProTERM splash screen looks like. What does it look like to you?

I just hooked up the SDrive Max to the back of the FujiNet.. I loaded something in D2: on the SDrive and was able to bring up the FujiNet CONFIG. Then I selected a MyDos bootable disk image in D1: on the SDrive and randomly the 850 Express! disk in D2: on the FujiNet. Booted off the MyDos disk and could see both it from SDrive and the 850 Express disk from the FN. My SDrive does have that diode in it to help it work with other SIO devices, which may or may not make a difference.

? Inter-connectable servers sounds pretty fancy. I'm guessing the initial iteration wouldn't have something like that :).

Can we run our own server?

Very strange. Nothing was perhaps cutting out any extra characters before? Oh well, some kind of fluke I guess

On another note, but still on topic of new FN firmware... Previous versions would let you dial 555-1234 (with a dash) in BobTerm to do the macro immediately after.. now if I have the dash in there, it waits for a long time for NO CARRIER and then does the macro. Taking the dash out goes back to the old behavior. Was something re-written that it no longer does the same with the dash?

Testing on 1.6 here as well. It seems to work for the most part, but I kind of feel like it's a tad bit slower/flakier than another FN on 0.5.ba2f6751. Right now the OS ROM in this 800XL is the one I got from Montezuma with the SIO2BT. At first I was getting a lot of errors/retries.. Like the 80s music 'demo' from the 2022 New Year Disk at first took almost a minute to load, but then I saw PicoDOS's HSIO setting was on 'Auto'. Another time I loaded the same file, it took only 20 seconds. If I set HSIO to OFF in PicoDOS it consistently loads in that amount of time. With Auto, it's hit or miss. On the other FN firmware, even set on Auto it seemed to always load properly, and might've even taken 19 seconds vs 20. It's possible that I didn't try enough times for it to go the other way though. Loading the Lovebyte 2022 invite was also ever so slightly faster on the other FN. This was ~10 seconds where the other/old firmware took ~9 seconds.

So nobody got the 22" one yet to see if it supports the same frequencies?

Would the version of Fujinet matter at all? Like 1.3 vs 1.6 or something? Did you test on 1.6?

@Stephen You can buy the issue that it's in here, I think! https://www.amazon.com/dp/B08BCRG3MW A friend found this

I'm using one in my 130XE from the early 90s. Combined with the replacement keycaps from Best, it's amazing.

It was the document I was looking for. Not sure why it wasn't working for me earlier, sorry

I came here to offer the tnfsd I compiled under MacOS 10.15 .. The link to the ones in the OP didn't work for me, and the Mac binary isn't on the fujinet site with the Windows and Linux ones. tnfsd

Are there more? The document seems to be gone now.

Applied this update and all three of those PoP carts now work for me. Stock 130XE. Thanks, FJC.