phoenixdownita

Apologies for the confusing use of partitions but it means 3 things wrt Atari/MyIDE/SDX: 1) partition as in block device partitions (like in Windows/Dos) 2) partition for MyIDE, a special area that contains up to 16 16MB ATRs, each is called a partition 3) partition for SDX, a named chunk of the APT area So for a MyIDE+FAT32+APT card you have all 3: 3 block device type partitions: 1 FAT32, 1 MyBIOS image/partition space, 1 APT partition space. Inside MyBIOS image/partition space you can have 16 "partitions" each is roughly up to 1 16MB hard disk. Inside APT space you can have SDX partitions. So the FAT32 is obviously what FAT32Loader accesses and is shareable, compatible with other devices (Side2 for example). The MyIDE2 partition is the one containing both atari images as well as atari partitions accessible from MyBIOS and it's a MyIDE thing. The APT partition is for SDX consumption only, and in principle should be shareable among devices but it seems MyIDE2 does not play by the book here. Afaik the first partition on the CF is the FAT32 followed by the MyBIOS space followed by APT space. To get MyBIOS space to get big for "partitions" you should enter 3 when MyBIOS disk preparation asks you, this way you have space for quite a few 16MB MyBIOS "partitions". MyBIOS preparation tool always sets FAT32 at 50%, then the rest is MyBIOS image/partition, MyBIOS partition space tend to be quite small as default (3 or 4 16MB ATR max) but if you bump it to 3 when requested I believe you can reach space for 16), the rest is for MyBIOS images [up to 1024 I believe, each can contain up to an ATR of 720K so total it's around 1GB]. If you chose to do APT space you are actually splitting in half the MyBIOS image/partition space, in specific you are cutting in image space if that matters to you. I tried to prepare APT space with MyBIOS + MyIDE2 version of SDX and use the resulting CF over Side2/U1MB SDX to no avail, it appears that MyIDE2 considers the size to be 2 times what Side2/U1MB SDX does, but that is another story, that is to say you may not be able to share the APT space with other devices, FAT32 is fine while obviously MyBIOS image/partition is proprietary to start with. Hope this info help. Hope the explanation helps a little. In order to use the MyIDE2 SDX rom image successfully you need to edit the config file appropriately, there's a little tutorial at AtariMax.

No it's not. http://atariage.com/forums/topic/221048-options-for-flash-drive-hd/page-3?do=findComment&comment=2929792 But depending on what you want to achieve it may be a better solution or a worse one depending. Better: care about R16, fine to use its own tool to deal with the image and partition space (it is not bad, just need to use a PC as intermediary all the time and remember the logic of the tool, the day one can transfer ATRs from the FAT32 to image/partition directly on an A8 would be a great day). MyBIOS itself is pretty great but it is hardly stock. Worse: deal with APT, you may be able to make it to work but as the author fjc says myIDE2 support is perfunctory at best (http://www.merriam-webster.com/dictionary/perfunctory) Integration with U1MB (obviously as Side2 and U1MB are made by the same great HW designer) So up to you, it's nice to have choices, to each it's own.

It is not that simple, wall of text to follow . So if you leave SDX off on U1MB and don't care about PBI booting etc then you can use your MyIDE2 to drive the whole process and simply use U1MB as a mem expansion (320 or 576 or 1088 as the program demands). Among the MyBIOSes R2 is better than F2 as soft OS does not offer enough compat while R2 being in ROM offers much better compat as the apps can't overwrite it. Now to be able to flash R2 to U1MB you need to have SDX on and here is where the mess starts as U1MB with SDX on and MyIDE2 don't play nice, they clash in the registers so you may not be able to actually flash that R2 to starts with, I resorted to a PLCC adapter and a ROM/flash burner to get going. R1 also works with MyIDE2 and some people find it more compat. I know sijmen is still working on the new version of MyBios (R2 and F2) but there still work to do to iron out some bugs (you can check his progress on AtariMax). So if you are OK to use the MyIDE2 partition space (and images) as your source of data then U1MB can be used as mem only, whatever you boot from those partitions would decide which DOS (there's a MyIDE2 "ready" SDX rom build with soft driver to use MyIDE2 APT space [did you prepare that? ... yeah me neither] from SDX booted from MyIDE2). I ended up buying a Side2 and that plays much nicer with U1MB SDX and PBI than MyIDE2. I only use MyIDE2 for those R16 images and for the 4 PicoDOS games images that I can lock in in partition space, the rest it's likely easier/faster/better via Side2 [listing a FAT32 directory is much faster in Side2 than FAT32Loader]. Also because of the SDX on requirement in order to flash anything on U1MB if you want to benefit from those OS slots in U1MB and those 4 Basic slot you are better off with a Side2 ... or a real SIO device that you can use to boot the required flashing ATRs (those built by TheRomGen and U1MBRomBuilder). If you're fine with MyIDE2 partition space then flipping disk by CTRL+1....N is much better than Side2 "press the button", although I believe once the new PBI drivers and new goodies are in the U1MB SDX mounting ATRs in and out from Side2 would be a breeze. In truth no solution (MyIDE2 or Side2) that sits on the cart slot is fully compat with all programs as some do have custom SIO access routines and those simply cannot be automatically redirected, maybe there are patches maybe there aren't, it's not that common but you'll encounter some (Seven Cities of Gold is one of them, sijmen sent me a patch for MyIDE2 that got a little further than blocking at the "insert map disk", but still blocks further down on another unpatched SIO access). Also on MyIDE2 all those HighSpeed PicoDOS games compilation simply don't seem to work (F2 or R2) but in normal (non HS) it's all much better, I didn't try them on Side2 to be fair. I hope I haven't swamped you with info or lumped too many things together.

First and foremost thanks for the detailed answer. Second I recognize I'm chasing a slim and narrow corner case out of obsession, so feel free to cut it short at any time, the last thing I want is to piss you off to the detriment of the community at large, I guess this is down to answer "why is this one particular CF misbehaving?" which only makes sense to me because I stumbled on it, were I to buy the good CF first I would never have been interested in walking down this alley. And that is why I bought a second one that works just fine, just nitpicking before the crappy CF hits the shredder. I get no "Error mouting ATR" by SIDELoader so the next step is the reboot itself I guess when the CF screws up. Do you think there's any simple way to attempt to diagnose if the single 512byte read done by PBI can be the culprit? Not that PBI code is wrong, just the CF doesn't support it very well or doesn't support it according to the std. I presume that SIDEloader, FAT32Loader and even Windows likely use burst hence the issue may not have surfaced there. How about the soft drivers? Within the embedded SIDE2 SDX I can format and DIR the contents of the formatted partitions of the non FAT32 (all empty in my case, see below) but it may not use the same access pattern. On a different note, when you release the new wave of SDX for SIDE2/U1MB/MyIDE2 etc... will the CAR device also include the new goodies (FDISK4, MATR etc..]? If so would it be possible to use MATR against the FAT32 partition on the CF? The question may seem bizarre to you but as it stands once I boot to the embedded SDX [sIDE2 or U1MB] unless I have a way to mount other ATRs I cannot do much with the created APT partitions. I only possess SIDE2 and so unless I manage to mount the FAT32 or ATRs in it somehow I have no available source to copy files from, I have no SIO2SD/SIO2PC or any other SIO based device I can use as a source/target, and I am not aware of any Windows based app that can allow me to inject data into the non FAT32 portion of the CF (inside the FDISK1 created partitions, like to have FDISK4/MATR available to me).

Not sure how to "image" the whole card, any suggestion, like what tool to use? [ideally I would like to capture all the HW related info as well in case it has to do with some of those fields being misused by the manufacturer, if indeed they are accessed at all during the chain that leads to an ATR successful booting out of a SIDE2 via U1MB SIDEloader] But logically speaking the fact that if I take the same ATRs and put them in the good CF they work wouldn't rule out inherent ATR related issues and leave us with the crappy CF either being the cause per se or tripping a border case/unexpected/unplanned behavior somewhere on the SW chain? [i say that because on the crappy CF no ATR that I tried has ever been able to boot over SIDE2, the same ATRs on the good CF have no issues, also putting the crappy CF on MyIDE2 and use FAT32Loader to boot those same ATRs succeeds thus anecdotally showing that the FAT32 content of the crappy CF in principle should not be corrupted] For my own education do you mind explaining the steps that happens during the process from a point of view of information exchange among the pieces? Just trying to figure out how many SW pieces have to play in concert to make this to work. If it's considered Intellectual Property then obviously never mind. With regard to the good CF only, gut feelings tell me that this is what unblocked TRG flashing ATRs starting up correctly for me now over SIDE2, instead of having them lock at startup at a blue screen, but I speculate, I'm just very happy they work now.

Apologies, I believe that short of sending the crappy CF directly to you I won't be able to put in word what exactly happens and not giving you anything to work off of. Preemptive apologies for the wall of text following here. I have 2 distinct CFs (the crappy and a good one) with half their size devoted to FAT32 and with pretty much the dump of ataripl online archives plus a bunch of flashing ATRs in it, the same ones on both cards. Taking PBI out of the equation for a moment [literally disabling it from U1MB bios], and to recap I am successfully able to use the crappy CF with MyIDE2 [all features] and with SIDE2 [all features]. SDX for MyIDE2 or the embedded SDX on SIDE2, thru their relative FDISK 1.0 see the crappy CF device and allow me to partition it, I can then successfully create entries into the APT portion and format them etc... You already explained to me that "non PBI" support for SIDE2/MyIDE2 devices within SDX is done thru a soft driver that is different to PBI, although it may come from much of the same code it doesn't have to deal with a lot of the complexities the PBI counterpart has to. XEXs launched from any CF FAT32 portion on either MyIDE2 or SIDE2 can use the extra RAM onboard the U1MB, obviously SIDELoader embedded on SIDE2 and FAT32Loader for MyIDE2 can see the FAT32 partition and its content correctly, allow me to select and launch all that they support. Not an exhaustive test by any means just something that hints to me that my soldering job to install U1MB is fine as well as the hardware [in a generic sense] at least relative to the tolerance that the SW embedded in these devices allows it to be. I have to state this point because for long time I was told I probably did something wrong in the soldering department. Now as soon as I activate SDX on U1MB with support for SIDE2 (with button) the crappy CF is distinguishable from the good one. In this situation I am using SIDELoader in U1MB obviously ("L"). Still the FAT32 is perfectly accessible and support for XEXs works flawlessly, I can start them and I see the SIDE2 led flash as the XEX loads and everything is peachy. Now if I select an ATR, any ATR, that's when I can't boot it. Also If I let SDX from U1MB boot I can't see the media or any partition I may have created in the non FAT32 portion [created thru the onboard SDX via SIDE2, not the onboard U1MB SDX]. The good CF does not have these problems at all. My hypothesis as to why are: 1) crappy CF specimen, something wrong with this particular one that so far has only manifested itself via PBI but nonetheless hardware related 2) the CF type, all specimens are simply not good, brand to avoid 3) SIDELoader and/or PBI sw trip on bad information/non std information regarding the CF or the FAT32 on it 4) like 1 but only wrt my specific instance of SIDE2 1 is the current most likely cause in your opinion, and indeed very possible. 2 is a little scary because once there's one brand that has issues there may be more and it will be nice to start tracking them so new buyers would know what NOT to buy wrt "SIDE2+U1MB+ATR booting". 3 can only be diagnosed by hardware debugging meaning I send the CF to you. The only other way would be for SIDELoader to have a debug mode in which it prints to screen what info it puts in memory for PBI consumption so we can try to track something, I am not sure what PBI could do to help debugging as if it really trips on bad HW/info that make it "self test" or "boot to basic" it may not have a chance to print anything on screen. 4 I would need another SIDE2 to try it out but I believe to be unlikely the case I don't think ATR support per se inside PBI is broken, quite the contrary it gets better and better. Short of sending the CF to you, do you have any suggestion as to what to do next to attempt to track the cause down, even if it only impacts me? I do appreciate his works a lot. Don't take my words as criticism, they are not. I am a little obsessive in root cause analysis, for better or for worse, but last thing I want is spread beliefs that fjc work is not good, nothing further from the truth.

I used the XEX here http://atariage.com/forums/topic/210754-apt-hard-disk-preparation-and-utilities/page-13?do=findComment&comment=2922287 to flash and it reports 0.6.

Just upgraded to PBI 0.6 and now all flashing ATRs boot fine from my SIDE2, TRG or U1MBRomGen generated .... guess it had to do with TRG SDX 3.3, maybe "Page zero locations 0x3D-3E" fix has something to do with it. I also tried my DaneElec CF, the troubled one, some exact U1MB setting as the previous ATRs boot via same SIDE2, but no dice, attempting to boot to ATR goes to self test. [Just reporting it here, I know that fjc swears by a bad media quality diagnosis and I stubbornly stick to alternative explanations ]. In any case PBI 0.6 is definitely a step in the right direction for people that are attempting to use SIDE2 as the only way to use ATRs and to take care of their U1MB flashing needs.

Maybe so you can solder wires on the fly ... not sure it is any more convenient but it allows to have any cable soldered directly with much ease .... but soldering nonetheless. It's a snug fit, mind you. You'll bend some pins as the Dupont ends are for 2.54mm pitch, in my case rather than hard plastic the Dupont wires end had a soft rubber cover which due to the tight fit I almost ripped open, hence the idea of building an adapter with a 2.00mm 10pin header connector cable. I bought 2 for 1$ o something like that, shipped, just need to find the time to solder it to a perfboard and use a more commonly found 2.54mm header on the other side. I haven't decided what header type yet, a straight single line for the Dupont wires or a 14pin double line for the std xilinx cable .... will see what I have available when the time comes.

Also Candle already stated that it didn't follow any std when making the JTAG pinout so you can't just use any ready made cable. I managed to "force" the Dupont ends into the U1MB connector (it's a tight fit but it works) when I reprogrammed mine [multiple times to rule out I had a bad CPLD core] but then I bought a 10pin 2.00mm pitch header cable and once I have a little time I will build an adapter for my own usage .... I believe Candle is at work on an improvement for U1MB that requires JTAG programming, so it is not wasted effort. I'm pretty sure Lotharek could whip up a little cable + board to convert the std Xilinx 14pin header cable or Dupont fly wires to the U1MB pinout and sell it for quite cheap, with the new U1MB that doesn't even have the headers soldered it will be even more challenging but no more than a 10 pin 2.00mm pitch header soldering away.

In all honesty given uFlash supports full 512K I was looking forward to a XEX solution for the flashing of the whole content that doesn't depends on any FS support. The flasher XEX with embedded ROM that I hinted at would have also supported the whole bank. I could then have used any tool to generate the full ROM to be used with the flasher XEX [even just copy /b of the sections] and it could have been run from whatever source could jump start an XEX (assuming it is compatible with SDX on). I guess I like the fact that FAT32Loader on MyIDE2 can flash a selected MyIDE2 format ROM via CTRL-F, I am not sure that embedding such feature in SIDEloader is warranted although I think it could be a nice thing (for both U1MB/Incognito and SIDE2). So then the stand alone 512K XEX would be the next best thing. But if SIDELoader implements the MiniDOS fix in the foreseeable future there really is no need to put time and energy into a general purpose XEX based flasher with piggybacked ROM given that now we have uFlash for it. I wonder how hard would it be for uFlash to detect and support SIDE2?

Sorry, it's probably been said already but after 7 test versions I lost track. Is support for loading ROMs straight from FAT32 still pending on SIDELoader fixes or is it supposed to be working? Also, on a totally different note, would it ever be possible to have a tool to get a "ROM" for a given slot and U1MB or Incognito as targets and generate the relative XEXs to flash only that one ROM in the selected slot? More or less like the PBI 0.4 XEX flasher except with the possibility to specify ROM and slot and target platform so that we can create them on a self serving base, wouldn't mind if this would require uploading the ROM to fjc website and download the XEX after processing. I admit that if FAT32 support is coming then it is probably redundant, just asking.

WIll it be possible to only "buy" the cables? For people like me that have the old version. (although it seems like you dropped the unused pins from the BIOS cable so it may not be possible after all) I assume it would be easier to fit this kind of cables in an XEGS, rather than the slightly oversized adapters + cables.

I wasn't being sarcastic, mind you guys. I really envy fjc for his prose. I apologize if my remarks sounded as criticism in disguise, that wasn't the intention. I really wish I had the time, dedication and opportunity to develop the skill myself. Sorry if I interjected, this after all is a thread about "APT Hard Disk Preparation and Utilities" and I for one don't desire in the least for fjc to withdraw his contributions. At the same time I do not wish a8w to stop sharing his tools either. There's place for both, the world is beautiful because of its variety and not in spite of it. So please fjc and a8w keep on sharing Thanks.

Aside from the issues and based on the quoted pass alone I have to say you have an uncommon ability for extraordinary prose. It's very rare to see such property of language and richness of vernacular even more so among developer and retrogames fan. Except from prose/poetry authors generally speaking the English language, be as it may "simple" and direct it's rarely put to fruition which such complexity, or at least it is among the circle of my acquaintances. Not knowing any better I'd think you've got german or latin blood, both ancestries with languages capable of complexity and generous use of hypotaxis. Once more aside from the issue tackled, I admit I enjoy reading your posts just for the use of the language alone. Have you ever thought to program one of those text based adventures of old and use such uncommon skill? For a moment, no offense meant, your posts reminded me of the dialogues between Burt Schlubb and Douglas Klump of "Sin City" origin written by the great Frank Miller. Hats off to you, sir.

I thought MyIDE2 would be enough [and with the ROM version of the OS is actually quite good], then I realized I also wanted to play the games that require >128KB of RAM hence U1MB, as I wanted to flash U1MB (and there are ATRs to flash) I thought that thru SIDE2 it would have been smooth sailing so I ordered U1MB+SIDE2 in bundle, it turns out those bootable ATRs don't work as flawlessly (depending on the tools that generated them). In the end SIO2SD would have been cheaper and likely more compatible albeit slower ... oh well, live and learn, didn't know all the gotchas.

I got both, SIDE2 to really shine almost requires U1MB, that is because many games are big enough to require the extra mem, with MyIDE2 some of said games use bankswitching within the card (see R16 support). Also ATR support from SIDE2 is only thru U1MB. On the other end MyIDE2 needs its own MyBIOS to really work well, although FAT32Loader can work in many cases. And that MyBIOS is its issue, as without burning it into an EPROM (or U1MB OS Slot) the Flash version resides in RAM (as OS RAM) and many games don't like that, the ROM-able version of MyBIOS (called R2) has much better compatibility. Regarding ATR support, SIDE2 requires U1MB for that, while MyIDE2 has 2 modes, via MyBIOS and via FAT32Loader, compatibility is OK (MyBIOS has better compat than FAT32Loader) but as soon as the game has custom SIO routines it gets tricky and messy and it doesn't work .... "Seven Cities of Gold" being one example, Sijmen (the author of MyBIOS) attempted a quick hack on it to make it to work but it ended up locking further on .... how many ATRs like that are there? Not sure but I found quite a few and it's annoying .... SIDE2 + U1MB seems to have similar issues with ATR once custom SIO is in the picture, so it's a wash. Also multidisk ATR support on MyIDE2 is only thru MyBIOS and the partition/image space [depending on what you are trying to achieve] which is even more confusing [way too many ways to achieve one goal]. I ended up with both because I wanted U1MB to experience all games that require 128MB of RAM or more [mind you there's not much really] and because it allows OS flashing but at the time I sensed that flashing it from MyIDE2 would have been problematic [and it is due to SDX and MyIDE2 clash], so that is why I also got SIDE2, I was hoping to share the same CF among the 2 but it didn't work. In my case my first CF couldn't be recognized by PBI (U1MB way of booting ATR thru SIDE2) although it worked fine on MyIDE2, end result is that I couldn't boot/mount ATR from SIDE2, everyhting else worked on SIDE2 [XEX loading from FAT32]. The second annoying part is that APT support among the 2 devices is non existing, meaning the APT partitions created on SDX for MyIDE2 are non usable on SDX from SIDE2/U1MB and viceversa, not sure where the bug is but the CF card layout for the APT part is not compatible, FAT32 can be shared so at least there's that. In the end I suspect that the most compatible way to play with ATR is SIO based although I personally will not venture there, it already costed me quite a bit to get both devices .... I wonder if a card could be built that uses both the cartridge slot and a cable to SIO so we can have our cake and eat it to and not require custom OSes, that would have been my choice.

Managed to update my U1MB on XEGS via XEX loaded via "L" over SIDE2 .... that's a mouthful .... anyway it succeeded. I was secretly hoping it would "fix" my other CF card via unexpected/unplanned side effects .... but it didn't, I'll live. Now onto waiting for the full SDX with the nice tooling in the CAR: device. Thanks for the continued development of the tool chain.

You probably already read it but: http://www.atarimania.com/game-atari-400-800-xl-xe-lifespan_2985.html http://www.atarimania.com/magazine_review.awp?id=11 I report it here: Anyone who still thinks electronic gaming is a mindless hobby should sit down to a few games of Lifespan. This multi-scenario action game is an analogy of a person's life experiences, from the cradle to the grave, with the ultimate objective of leading the longest, fullest life possible. Each game begins with the birth spiral screen, wherein the player is treated to a pretty light sequence. While waiting for the fetus to "develop", the gamer can move the joystick in any direction to add musical tones to the birth chorus. Gradually, the birth spiral fades away and the player becomes an infant in a playpen. The object of this screen is to isolate as many personality traits as possible (there are four altogether) to become as well-rounded a person as possible. To do this, garners move building blocks around the screen with their cursor, dropping the blocks near the corners of the playpen, thus keeping the free-bouncing personality traits from escaping. The more traits trapped, the sooner opportunities come knocking later and the longer the player's lifespan. The third screen brings the gamer's character to the threshold of adulthood - the opportunity gates. The gates are actually a dark, forbidding corridor filled with tiny points of light. Depending on the character traits trapped in early childhood, perfect and not-so-perfect opportunities whiz by on the screen. The best opportunities are those that look exactly like the player's character trait. Those with similar shapes but different colors (or colored alike but differently shaped) are decent opportunities, while those bearing no resemblance are the worst choices. The object of the screen is to locate the right opportunity, then enter it by passing through the center of its spiral. Successfully entering an opportunity leads to the next scenario, situations and conversations. Unsuccessful tries have a negative effect on the gamer's health. This screen is an analogy to the social process, in which players must make contact with common interests (depicted as colored squares on the grid) in order to enter conversations with their peers. This must be done while avoiding creatures that rob the gamer of common interests. When enough common interests have been acquired and the player successfully joins a conversation, it's time for the most dangerous screen of all - the experience corridor. Hurtling through the corridor at lightning speed, the player has to steer clear of the dark Worries, Fears and Doubts that threaten the health of the character. Large, bright lights are Hopes, which can reverse some of the debilitating effects of failure. If the player is strong enough to cope with life experiences, he or she is rewarded with an extra character dimension and a beautifully animated Insight before returning to the earlier screens to continue play. The real payoff comes at the end in the form of a brilliant sound and light show, the electronic version of one's life flashing before his eyes. The better the player, the more spectacular the finale. It's impossible to detail all the intricacies of the game in just one review. But it's a refreshing change to see a game that emphasizes aesthetics above scoring, without sacrificing a iota of playability in the process. John O'Neill, artist turned game designer, has succeeded in what he set out to do - to produce a great game that appeals to the psyche as well as the trigger finger.

A merry Christmas to Lotharek, Candle, FJC and AtariGeezer that had to put up with all my woes (and a hefty dose of attitude) during this period. I've been a SW developer myself for many years and I've grown quite an ego and a propensity for early diagnosis, at a point I thought I could actually read minds thru hindsight .... of course I was by far wrong, unfortunately those rare occasions in which my guesswork proved correct reinforced a sort of bad attitude ... oh well, to each his own. Once more thank you for putting up with me, if I don't hear from any of you before then also Happy New Year.

How do you do that? If I select a random ATR (marked D1) then the flasher (marked D2) then deselect D1, and try to launch D2 I get a "D1 not mounted" error at the bottom of the screen of SIDEloader. Do you keep an "empty" ATR as selected D1? Also when you say it doesn't work as D1, what happens in your case?

Candle just gave an explanation http://atariage.com/forums/topic/218960-u1mb-side2-on-xegs-issues/page-3?do=findComment&comment=2891241, maybe it could be worthy to have the TheRomGen generate ATRs with boot sectors as an option for people like me that only have access to a SIDE2 device. I don't know how much work that would be or how hard, but at least we now know what could be needed, and also why they don't quite work for the time being.

So to make it clear the theromgenerator ATRs cannot currently boot from U1MB+SIDE2 because they require SDX to be still on while SideLoader turns it off for compatibility with pretty much everything else? And they never worked directly unless booted from a SIO or after being in SDX already? I like that this mystery is now not a mystery anymore. I'm really looking forward to a flashing solution for U1MB that works with the combo U1MB+SIDE2 only. In any case we should document that for now TheRomGen flashers do require SIO. Somehow I cannot believe I am the only one that stumbled on this problem, am I the only one flashing from SIDE2?

I don't mean to rub you the wrong way but I still believe there's some secondary SW incompat. The fact that the DaneElec card wouldn't work well under "PBI boot" only may be a symptom. Granted it is possible that the DaneElec card itself could be a little out of standard as well so I won't push this any further, we're talking about 8US$ shipping included and I can use it just fine with MyIDE2 and any non "PBI boot" related "work" .... sorry meant to say "play". The only issue left that escapes my understanding are the TheRomGen flashing ATRs locking up. Maybe they were meant to be booted from SIO, not sure, but as far as I am concerned it's the last not well understood issue. Also why would it work upon HELP+RESET followed by Q is beyond my knowledge. Be as it may I already mailed both Lotharek and Candle that I don't hold the U1MB/SIDE2 HW responsible for my woes ... which really means I won't be returning them any time soon. I am looking forward to your new releases, after all if I get it right you are "the guy" we owe to to get PBI support at all on these devices, so "hats off" to that for sure.

ATRs on a Transcend CF over SIDE2 were fine already, my issues were with the previous CF I was attempting to use (a DaneElec CF), with the exclusion of TheRomGen flasher ATRs. Those ATRs "PBI booted" on Transcend CF but locked up before any message on screen at a blue background, not sure if they were supposed to be run on real SIO only. Anyway the change has obviously been a different CF to get ATR recognized at PBI time. Limited to the TheRomGen flasher ATRs only I've noticed the combination reported above. Namely let them lockup, press HELP+RESET then at the U1MB setup screen simply press Q to quit. Wait a little, at this point U1MB SDX takes over and somehow it boots the flasher ATRs which this times around doesn't lock. [During the tests I had SDX on, SIDE HW on with button, PBI 1, XEGS stock OS from slot 4 and XEGS mode jumper on, none of these settings was touched or changed during the experiments]