Dmitry

So speaking of a machine with only Rapidus, to make this simple. It cannot see the onboard OS rom. So, where does the OS come from? A 6502 OS is onboard the rapidus? or do I not understand something? And will an atari with no onboard ram, os rom, or even onboard mmu, still work because the rapidus doesn't use it - I mean for my particular case that would be good, if that is the case.

Page 52, of u1mb: If you have the PBI BIOS enabled, you must set the ‘Hard Disk’ to disabled, otherwise external cartridges may be suppressed. OK, one workaround I intended to try, which is PBI BIOS enabled - suppress Basic, but keep external cartridges - gonna try it now

After I got your message, I took a look at it again. It turns out my observation that I had also disabled basic, was superfluous. Merely turning on the PBI bios disables my cartridge port, and turning it back on re-enables the cartridge port. If there is a way to turn on PBI bios - which I don't currently need except it enables the option to disable basic, but leave my physical cartridge port enabled, I haven't figured it out yet.... I am googling around and I see a discussion where a person recommended not trying to even do that, because " PBI HDD functionality still reads from the CCTL region, and this can upset certain flash cartridges with address-based banking." In fact, that person might be Jon, I just found an old post discussing PBI functionality. OK but anyway, it was a workaround. I still think it's theoretically possible for me to flash this thing such that all CAR images are blank. I know in my past configuration two of the slots weren't flashed. If I could make it all four, then I wouldn't need PBI bios. That's not a simple route either, because I don't have a windows machine. Not sure if the software for making your own flash works on an m1 mac.

Thanks! No, I have zero hardware skills. I have destroyed several atari's trying to put in the simplest of upgrades. Let's see I destroyed an Atari 800, an XE GS system, and an 800XL so far - I'm probably making some folks mad a this point. I'm terrible. But I learned my lesson, I will never pick up a soldering iron again. And as near as I can tell, the documentation for the Rapidus indicates only that it has a 65C816 dedicated OS on board. It says nothing about a 6502 OS on board. So it will go to a professional. But this leaves me with the question. If I have a VBXE and Rapidus, I am told the VBXE, with one of its core images can supply 256K of extended Ram. What I'm getting at is - I want Rapidus mode and classic mode. But even classic mode I want to have 128k or 256K of ram - not just the stock 64k. Has anyone done this? Or is the more reliable thing to do put an actual memroy upgrade in the machine? Obviously the u1mb had been meant to be a memory upgrade - why it was in the machine in the first pla

I completely agree with you, in terms of if reliability in classic mode was my only concern, I would do that. But I also want the accelerator functions of rapidus. I think I understand the situation - the u1mb is a great piece of kit, it is a pity, that this all doesn't interface, but....anyway, I feel like I can get SDX from another source besides the U1MB.

I took apart the case with the intention of removing the U1MB. If I remove the U1MB, I don't think my system will have an OS rom left. The two sockets that would represent the OS rom sockets - one is empty, the other has a ribbon cable going directly to the U1MB. And not only that there is another ribbon cable going to where the MMU used to be. I suspect the system would actually be non-functional if it had no MMU or OS rom of any kind - but I don't know so I'm now going to ask some comical questions. Although Rapidus has 256k for OS rom, it is in no way clear to me, if that means it can supply an OS ROM when it is running in classic mode. So for me, I'm guessing, the very least it is now a hardware project to remove U1MB - purchase an MMU and an OS Rom. Correct me if wrong...but while the rapidus manual states it has 256K for OS rom - does that mean it supplies both classic and rapidus mode roms? Or just in rapidus mode? Obviously the rapidus has its own memory. Can it supply extended ram - 256k even in classic mode? Or do you need another ram expansion if you want more than 64k (this is a 1200xl, again) in classic mode?

Agreed. Also, I believe tf_hh is saying he hasn't noticed many issues in Rapidus mode, and that is my experience too. In fact, this install was done in 2016, and in part I didn't have issues because I wasn't in the Atari scene as much, but also, because I didn't have a need to be in classic 6502 mode. What changed for me is I didn't want to test FujiNet with Rapidus - I wanted to just use 6502 to eliminate one thing from the equation, and then I ran into some annoyances, and was no longer happy. Now, I want to be more meticulous with my observations, but in reality, I just don't know what is normal - I am still just jumping into more regular use of the Atari. I turned on PBI Bios and disabled basic in U1MB. But then to my surprise plugging in a cartridge now does nothing. I assume that is normal and part of what disabling "basic" means- but I didn't want my physical real cartridge port to be unusable, so this solution is unacceptable. Today, I am now testing with Rapidus in classic 6502 mode, and U1MB in non-PBI bios mode. When I hit reset, the machine locks up. Unless the purpose of the Reset button is to lock up the machine, it just doesn't work, and doesn't take any time to find the problem. If I hold down option to disable basic, (absurd, I have no basic), it will reset OK for a while. But not forever, it will eventually still lock up. I appreciate all this extended discussion, I know the thread is about discussing a long standing issue. From my perspective, I still need to solve my issue, and I'm also not got the time to really delve into it. To me, the solution of pulling the U1MB is just something that is fast to do, and should work fine... I'm going to give that a try next. And then get SDX on cartridge.

Thanks for the info. I haven't read through all of it yet, but I got some important info. The main thing I didn't realize is the Rapidus card supplies its own OS. Somehow in my previous configuration DracOS was one of the ROM slots in U1MB. I noticed it, it definitely had been flashed previously, but if that wasn't needed, then it was just harmlessly not being used from that card, and loading from the Rapidus. And I'm probably going to update the Rapidus firmware as well later today. Not because I believe it will solve the problem. I'm flashing the latest because I feel it is pointless to troubleshoot older versions. Just generally speaking I like in situations like these to know i have the latest, and that would be what to troubleshoot. I said it once before, but to be clear, I own an Atari 1200XL, and I'm not willing to give up the "feature" that it doesn't have an internal basic. And therefore I should never have to disable something which it does not have. I will not be holding down option to start the machine. Despite the fact that I initially didn't use U1MB for anything, even its namesake of supplying 1mb of memory isn't something i needed since my understanding is both the VBXE (with correct core) or the Rapidus, could supply 256K of extended memory. I do have the desire at times to simulate 130XE banked memory at up to 128K, so I'm covered. I never use any game loaders, that isn't of interest to me. The other excellent features of the U1MB - are very interesting, but at this time, not requirements. However, I've come to use SDX, and at this time, U1MB supplies my copy of SDX. I mostly dink around with coding, not playing games. Despite the fact that I'm coding a game this go around, I may not on the next project. Anyway...gotta get back to that. I am just going to use the PBI bios, with basic disabled. If that works, great.... If not, I will have to figure out what compatible device wil supply SDX - it could be just the SDX cartridge, or maybe I do get a SIDE or something like that.

Hey all, I know I've just made my situation slightly worse - but no problem, I am sure I can flash it again. But I flashed the entire card, 512k, based on that being recommended to owners of stock cards, to remove an unneeded patched high speed OS. That sounded good to me, I have no idea what I ahve. But anyway, now I have four OS installed, but DracOS doesn't appear to be one of them. Whoops, I think I needed that. Also before I only had two carts, and now i have four installed, and no blank cart slots...that's not what I wanted. I don't want an internal cartridge. Now I do get a choice to disable basic, but only if I select PBI Bios. I don't use Side. Do I still enable PBI bios anyway? Just so, I can disable the cartridges? I guess what I was hoping for, is if I do have a glitched Atari, that if there at least isn't any cartridge at all - then it can never select one, even when it glitches. I would like to flash this with zero cartridges, if possible. And also I need to add DracOS back to one of the OS choices, I believe for the rapidus mode. Correct where I'm wrong....thanks again

Thanks for your help all. Honestly I started to get frustrated for a second, because it dawns on me, my initial view of how this works, is probably wrong. I've been wrong a lot. But it's ok, I'll figure it out, I'm just dealing with some out of date knowledge here. In the old days, if I jammed a cartridge in the slot, I expected that cartridge to load. And if I didn't jam the cartridge into the slot, I didn't expect it to appear from thin air and load anyway...haha omg.... But honestly no point in getting frustrated, I think you all are right, my initial reaction to pull the hardware is not the first thing to try However, it may be what i need to do, depending upon how this works. I do have an old version of the BIOS I suspect, I think it says 1.22, so maybe I should try a later version. And later version can suppress basic, but I'm reading in the doc it doesn't always work. Then again, I should see, maybe it'll work for my purposes.

A 1200XL does not normally drop into BASIC because it has no internal basic. I know I'm not telling you anything... not sure how this thread got confusing. I never selected a basic, never installed a basic, I don't want basic, it should not appear - ever. Someone flashed it onto the U1MB before installing the U1MB, but it is not selected to load in the U1MB config.

Rapidus and U1MB are likely not working correctly together. I gathered this from watching FJC videos today, where in some of his videos is he describes the very symptoms my machine is displaying. However, there are likely other solutions that I'm simply not aware of, one quick thought was to remove the U1MB. But, also, I am now googling a bit, and it seems this altirra basic was flashed onto the U1MB. So, there may be a way to simply unflash all the cartridges - with Altirra basic "removed" there is no longer anyway to have it load in error. It's quite frustrating to hit reset and have that fail into Altirra basic, or have altirra basic interfere with another load - when I have never installed this basic, and it is not selected to run in the U1MB config. But, now I will investigate merely unflashing it, as a first step, I guess. I'm in Nashville, btw, I'll update my profile.

OK, for unknown reasons a long time ago I obtained two ST connector to SCART cables. So I got the device pictured above which is in a nice case and cost $30, it is a generic SCART to HDMI converter. Well, the first cable "OF COURSE" didn't work, but by now I know everything hardware related must first give me a scare, before then working. With my second cable, this converter does work. It doesn't blink, as the GBS-8220 can in 800x600 mode. The GBS-8220 didn't have the blink, after I configured it to 1366x768, but id did then have garbage, although perfectly stable garbage on about every screen. This one works entirely...in 80 column mode, it works in regular mode, it's solid and decent. Probably high end stuff would be more crisp, but I like it, one problem solved. One quirk, while it has a 1980x1080 output mode, which would match my monitor, I must output to 800x600. If I output to the monitors native 1920x1080, then it won't hold the picture and constantly goes dark. However, the mode that works - good enough. So I just wanted to report that, in case anyone else wants to pick up one of these cheap converters to take you to HDMI output on your VBXE. Now, as I'm ramping up my use of the Atari, things that I overlooked for years, are now annoying me. This machine really doesn't "reset" properly and will often glitch into Altirra Basic. I haven't installed BASIC AT ALL. And while I'm aware that is loading off the U1MB, which is installed, it isn't selected to do so. I kind of feared installing the U1MB. I wonder how much trouble it would be to remove it? Is anyone familiar with the matter know if it is installed in such a way that you can merely pull it, or will wires be soldered on? The machine seems to work mostly OK if I leave it in 65816 mode with DracOS, but I kind of wanted to be able to switch out of that.

Back in the day, my progress was Atari 400->800XL->130XE And as the 16-bit era began, I nevertheless bought one more 8-bit machine, a Tandy Color Computer 3, because it had upgraded graphics and could go to 512k on a budget price. However, by taht time I was already used to certain requirements, such as a disk drive, monitor and modem. I never got the all the pieces for the Tandy Coco in place, and I simply owned the base unit, never used it. Right now I have a 1200XL and 130XE and a Coco 3 (the Coco 3, once again, don't really have the full system in place, darn it!) Anyway, I was collecting for a bit, but now, I'm not, I will just keep the the 1200XL and 130XE as a backup. And - I personally would be glad to purchase new software. I would especially like an 80-column terminal emulator to support VBXE. I would pay for an AtariAge client that uses FujiNet. And games are always fun, of course

anyway, while I'm here I'll share a bit - I've primarily been working on the display list interrupts and vbi routine the last few days. It's been interesting, I initially tried to cram far more into a display list interrupt than was in any way reasonable. I mean like 2 to 3 times more than you can actually do, lol.... But the good news is, is that nevertheless, the code is coming together. I'm getting too anxious, I want to be done already, ha!

Well that's odd, I must have signed up for a different account at some point. Anyway, that other post was me...thanks for the help @fenrock!

Ah, I'm going to over update, cause I'm a chatterbox. So, I got to using FujiNet this weekend, it is an awesome device. Took me forever to set it up, unfortunately. Then I got the Player/Missile graphics setup for Fire Balloon, and got the joystick working. But, that wasn't as easy as it should've been, because my Atari800 emulator (Atari800MacX) wasn't registering the joystick or even the keyboard joystick on my M1 Mac, and for a while I just thought it was my code - for like 2 hours a while. LOL...anyway, turns out you can launch a "Rosetta Terminal" and even though brew doesn't support ARM yet, run brew anyway. So I installed the regular Atari800 emulator, and it works just fine..... I am going with a 5 player setup, with sprite multiplexing. I will have up to four fires per window row, each two color, one coming from the not yet shown background color and as part of tile animation and the other from a player. And the dude will be able to launch four balloons at once. Which is a single sprite being sliced and diced by the DLI - we'll see how it goes.....

Follow up, I tried to be a good internet citizen by contributing to the QuickStart guide on GitHub, based on my experience. But, it just said Error 500. I just signed up, maybe I don't have permission? Anyway,I was just going to add a couple things to help and not waste anyone's time on it.....basically these two things might be a slight improvement: #Getting to know your FujiNet -The guide speaks of power switch, but I would mention new devices don't have power switch #Connecting your #FujiNet It is mentioned to remove cartridges and SIO devices. I would also mention, U1MB can also get ahead of the FujiNet boot (reminder to turn off internal SDX on U1MB) I am not sure about this one, but I"ll mention: #When the #FujiNet is powered on and ready, the leftmost (white) status light will be solid and brightly lit. - if this is true, then it needs no change. However, I don't recall my light turning on until after I configured the device. The Quickstart does already mention "SD" keyword for access of local files on the Micro-SD. Doh, I missed that one big time. ok moving on....

I'm gonna watch those videos.....and many more I'm sure.

ah forget, I'm a quirky communicator, unfortunately I cannot really change that - hardwired into my brain. But, I want to add I love this device, thanks for all you do! The truth is, I was super keen to get it working, cause it really inspires the imagination with all the possibilities it opens up.

I don't follow the community particularly closely. I bought this device a few days ago, hadn't heard about it till last week. Even though I don't know you at all, I did get the sense that you were trying to help me at a technical level. I thought it would be respectful not to waste your time. That's why I posted very specific commands and even stated they don't make much sense to run. I thought I was pretty clear about that even describing that the commands made no sense to run since they were invalid. As it happens I did find out about the SD keyword by eventually googling long enough to find videos and one showed the SD keyword.. I find it somewhat interesting you are saying my communication technique didn't work - and yet you also figured out from my text the SD keyword was missing - and also mentioned the videos. I only coincidentally had found them from google a few minutes earlier, but even had I not, the conversation would've come to the successful answer. Communicating openly isn't a bad thing - except in this community it causes people to get upset. Please don't be upset, I'm not - from my perspective you came into the thread to help me. And you did. Thanks. But as far as this community with people getting upset all the time - I don't really get it. So - here is what we can do - I just post to the public, not to any particular person. Feel free to ignore any post you see. Either way, we're cool.

SD Thats the magic word I was missing. After googling around, I finally came across Patreon's website, and some videos and I noticed they had an entry SD. I had no such entry. So, I put that in, and wa-la, I had a "TNFS Host" of "SD" and it could read from my local SD. It works. And it creates disks as well. I may still have some very harsh crashing in SDX, but in truth I may have never used it with SDX, except for the earlier issues which brought me to trying that.

Thanks, that helps me understand what you meant me to do. However, we aren't at the point where there is something to troubleshoot in that fashion. I mentioned specifically the command I had used. fnew.com 3,3,1,test.atr It literally makes no sense to run that command. A parameter to that command is host slot. I chose 3. Why would that be a correct choice? I have nothing defined for host 3, so it probably shouldn't work, right? Are we saying that I should run a non-sensical command and then check it in monitor? I think you are hoping I can consistently create a problem creating a TNFS disk, and I cannot. That isn't the issue. My machine, with this device plugged in, does regularly crash in SDX, within minutes. However, are we hoping when the crash occurs, which might be even when I run a DIR command that it will show in a monitor attached to FujiNet? Things have changed a bit since my first post - based on your advice that the BBS stuff doesn't always work - I took that to mean, the state of the software is that my experience that nothing worked at first, might be normal. So I changed the baud rate from the setting that was on by default from that TNFS server (the one I happened to use, had set it at 9600) and made it 2400BPS. Then I was able to establish a working session with Dark Force BBS. So, even if that is the only known working BBS for me right now, it felt much different to have one that worked. Now going back to disk access....the TNFS disks download, that has worked from the start. But FujiNet online also states "Load floppy disk images from onboard MicroSD or networked server" - So the first. part, from onboard, and not from a networked server - what is the mechanism to do that? Can anyone point to how that is done? It may seem simple, but I tried simply copying ATR images to the MicroSD, but if they are meant to show up somewhere, I don't know where they would. I am curious as how someone would do that part of loading disk images from onboard MicroSD without the networked server. Once I can isolate this down to something that is known to work for other people, and doesn't for me, and if I can get it to be repeatable, then I will hook up that monitor and get the output, but right now, I think the system while not stable for me - I am still doing things most people wouldn't do - right, because I don't know how it operates, so I need to clear that up some.

p.s. given the syntax for that command seems to pair a host slot to a peripheral slot, there could easily be a 'concept' that isn't immediately obvious to me. One thing I want to do is create an ATR locally on my SD Card. Why would I need to pair that to a host? It's massively confusing when using a new device that also has problems - because I don't know if this is how it works, or if it is a problem. I'm almost certain some things I'm trying don't make sense - at the same time, just having random lockups when even typing "DIR" seems kind of obvious I may have an issue with my cart....unless, I caused that lockup with DIR. I notice when it fails to create a disk, it nevertheless shows that disk on subsequent reboots.