wildstar87

I know this machine's video worked before, but I'm not getting anything out of the 5-pin DIN, except audio. The machine is definitely working, I can load something from Dos, typing in a memorized command, it's happily making SIO noises, and self test audio works as well. However, I put a UGV in thinking it might be an issue with the monitor port for some reason, maybe a bad 4050. UGV is connected directly to an S-video jack, and is not going through the DIN5. I know the UGV is working, as I have tested in in 3 other machines. I still get no video even with UGV, so thought it might be the Antic, and swapped that for a known working good, but still no joy. I'll start tracing down signals later, but was hoping maybe someone ran into something like this before?

Saw the warning about upgrading to JED 1.3, I did update to 0.69, seems to be working ok. Some questions, is there a compelling reason to go to 1.3? Is there a method to tilt the odds more to success on updating? I bought my SIDE3 from Vintage Computer Center, which sadly is no more. If I do have problems, I don't seem to have the vendor I purchased from, to talk to regarding this. Who would I talk to about getting the JED updated, if it is inadvertently bricked? Brewing Academy?

How do I update the SDX Image in SIDE3? Tried loading the Side3.rom in SDX Imager, but that didn't work, I'm guessing because it isn't JUST SDX that is in the .rom file. Maybe UFLASH? EDIT: Nevermind, I think I just figured it out. I just checked back on that other thread that I quoted.. lol..

I'm now trying to setup SIDE3 in a standalone functionality (no U1MB), in Altirra and running into the same issue where it doesn't use the config.sys that is on the D1: on the SD card. The Fast Boot setting doesn't seem to have any effect on this. Searching through some threads I found this: I did try to use the MERGE command, either standalone, or with MERGE DEFAULTS, but seems that it still isn't using the config.sys on D1: (SD Card). Is this a case where the config.sys on the CAR: image probably has to be modified, or might I be missing something?

I just remembered seeing that earlier today, literally right now before I saw your reply. That was it. Again thanks a lot!

Thanks a lot, that did it! I have the XEL-CF3 device installed, it's coming up as D1:, and I have a config.sys file in the root, but it isn't reading it during boot. I even setup Config.sys, and Boot Drive to D1: in the U1MB setup page, PBI hard disk is enabled.

Wasn't sure if I should post this here, already did in the Altirra thread, but I figured @flashjazzcat might know the issues that I'm running into. I've run into a REALLY strange problem, and I know I have done this in the past. I'm trying to setup a 1088XEL system to match the one I physically have, to test stuff out. I've checked the Enable Ultimate 1MB under memory, and put the XELNOGOS.ROM in as a U1MB Firmware, under the Firmware Manager. When it boots, I have no keyboard, so I can't change any settings in the "bios". If I try loading the ULTNOGOS.ROM instead, and reboot the system, the keyboard works in the "bios" settings. Any ideas why the keyboard would fail using the 1088XEL firmware, and not the U1MB firmware? It's using the exact same keyboard settings, so it can't be that.

Thanks, I was trying to use the Virtual hard disks, it doesn't list any of those options. Probably because I was having issues formatting floppies, so was just using the pre-created SDFS floppies, and those seemed to work (w/o formatting), so I think I had the same mindset on this, and didn't try that option (seems stupid of me now). I seem to have gotten past the floppy formatting issue, by changing the Default write mode to Read/write, the default is Virtual Read/Write (prohibit format), though I did change that specifically when in Disk Drives, mapping the drive images. On another note, I've run into a REALLY strange problem, and I know I have done this in the past. I'm trying to setup a 1088XEL system to match the one I physically have, to test stuff out. I've checked the Enable Ultimate 1MB under memory, and put the XELNOGOS.ROM in as a U1MB Firmware, under the Firmware Manager. When it boots, I have no keyboard, so I can't change any settings in the "bios". If I try loading the ULTNOGOS.ROM instead, and reboot the system, the keyboard works in the "bios" settings. Any ideas why the keyboard would fail using the 1088XEL firmware, and not the U1MB firmware? It's using the exact same keyboard settings, so it can't be that.

I must be missing something here, how do I go about creating a Virtual Hard Disk in Altirra? According to one thread, that I can't seem to find any longer, there is a menu command under System, Create VHD, which doesn't seem to be there. I've scoured the help file, and done searches in the forum, mentions of VHD, but I didn't see how to create one. Trying to setup SIDE3, and can select a directory, but I don't see how to specify size, and I sort of got it working, but it doesn't save anything to the drive. I'm sure I'm missing something. The other problem that I'm running into, is when I try to format a floppy in Spartados X, as soon as I try to specify Unit#, I was getting an Altirra Error dialog, but now it just hangs, with a graphic line corruption, either way trying to format a floppy didn't seem to work for me. Any ideas?

So you're the one who has been snatching these all up. I actually had to pass on the first one, I wasn't sure about the discoloring/staining on the top, curious if it cleaned up? Seller said they couldn't easily clean it off.

You might just want to consider getting a programmer. I ended up getting a TL866II+ a number of years back. I guess there is a newer version https://www.aliexpress.us/item/3256804232971223.html?spm=a2g0o.store_pc_allProduct.8148356.24.76463ee3kEP3eo&pdp_npi=3%40dis!USD!US %2479.99!US %2471.19!!!!!%402103231116866941569922646ef5d4!12000029681183274!sh!US!834105329&gatewayAdapt=glo2usa It can program the roms, and I use EEPROMS instead of the UV EPROMS, much easier since the programmer can erase and program those. It's not that expensive and can test DRAM/SRAM as well. It also saved my butt on a 1MB firmware update that bricked it, I was able to pull the chips and reflash them directly. For the 1050 you would most likely need a rom adapter like this https://www.go4retro.com/products/23xx-adapter/ because finding that small an EEPROM I found impossible. You can flash your own OS and Basic roms, and cartridge roms as well. I really only bought it for a single use case, but as I've gone down the rabbit hole with A8s, I found more and more use out of it. With the additional adapters for the different packages, it can do a lot. There isn't that much to know, you get the rom file, and program it to the EEPROM. The only real issues, are because the ones that are available, are larger than the original Roms, you have to use an adapter, and basically fill the rest of the EEProm with the same code a few times, or get more fancy and have an adapter that can select more the one set of code, so for instance, you could have the both the OEM Atari code, and US Doubler on the same rom, with a switch/jumper to select between them.

Yeah, sorry, I don't currently have the expertise in 3D modeling to do anything like that. Maybe if it's simple enough, you could talk to Screamingattheradio, to see if he can create the plunger, that seems like it would be less complex, than the stem he created for the switch. Not sure about the keycaps though. If he was willing to do it, he would need to have physical examples of each, I think.

I think a Resin 3D printer would have the resolution you would need. Screamingattheradio's 130XE Mechanical keyboard project, initially had replacement stems specifically for the Kalih Box Switch. Apparently JLPCB also does 3D printing on both Resin, and FDM printers as well. I think all you would need is a 3D model of the plunger.

I ended up buying another 600XL, so I don't need this any longer, thanks anyway!

Tried your OS, but got exactly the same behavior. It always fails in the same place, it gets through to 3 and a half lines, then in Compyshop mode, the screen goes blank, in Rambo mode, I will get garbage across the screen, sometimes stationary, sometimes scrolling, in what seem to be large graphic characters, with some being letters/numbers, lots of random colors, and random blinking. But it works just fine if I turn the extended memory off. I've flashed a new GAL, which verified fine, so did the original GAL, SRAM memory chip tested out fine on my TL866II. I did find a bent pin on the OS EEPROM when I went back to switch to the Original Mask Rom, I thought that was the culprit, but nope, still failing exactly the same way. Switched out one at a time, Sally, GTIA, Antic, PIA. No changes, and Simtest seemed to pass, didn't run any other memory tests, and didn't jumper over those pins on the GAL yet, I'm getting tired, and a bit discouraged, so I'm done for the night.

I kinda figured something like that, but wanted to make sure. The extended memory test runs through, but doesn't seem to have as extensive reporting as the base memory, just one line, with the address numbering counting. I wasn't even sure if if passed, it just went to ED, but I'm assuming if there were any failures, it would call them out.

Is it normal during Simtest, when checking base memory, for the display to get a bit corrupted during parts of the test? The corruption flickers a few times, then the display is back to normal.

Not sure if ABBUC can just run boards whenever, or if they just had a run of boards and that was it. I think Santosp might have released gerbers to ABBUC for them to run boards to sell, but never released them publicly that I know of.

I mistakenly referred to the GAL as a PIC, because I was thinking Microchip/Atmel, and I associate Microchip with PIC, because they make the PIC micro. Anyway, was referring to the ATF22V10C (Technically a PLD). Which pins are you talking about jumpering over? 14,16 for CI? I'll also try reflashing and verify. Also just checking to make sure, everyone is using Sram13.Jed from Hias (https://www.horus.com/~hias/atari/#sram512k), right? No, Santosp isn't going to release the Gerbers, unless something has changed.

Bypassing the GAL kind of misses the point though. I'm trying to solve the self test crash when the extended memory is turned on. It works fine if it is turned off. So for all of you replying, the Atari built-in self test memory test just works when the extended memory is turned on? No problems? As I said, it seems to otherwise work, passes memory test programs, just the onboard self test (which is apparently broken anyway) crashes to either black screen, or fills up with garbage at some point in the test.

I figured, but the switch you had on the bom is actually on the higher side current rating, 100ma, vs 25ma of others, so just wanted to make sure it wasn't that way for a reason. Thanks

The switch listed in the BOM is on backorder, trying to find a substitute, what's the minimum current and voltage rating?

If that's all you are doing, then what @Beeblebrox just said is probably the better way to go. I'm assuming the PAL case all lines up (never seen one in person), I think if I remember correctly, the 600XL just use the one MB design, and left the PAL stuff unpopulated, along with the video circuit. On the NTSC versions, most people just remove the channel switch, since you have to, to put the monitor port in, and make a hole where the switch used to be. It can be done really clean with a step drill bit, and if you are careful, essentially looks stock, with the only difference visually between the PAL/NTSC cases being the printing below the port. BITD, Jeff Popp did the mod on the 600XL I had at the time, and just kinda chopped a hole out of the plastic.

I think I have another PIC around here that I could make a new GAL, don't have another SRAM chip, though I could test it in my TL866 to make sure it's functional. I'll have to go over the board again, but pretty sure there aren't any shorted/lifted tracks, or other artifacts.

The 130XE Remake board is basically setup as a 65XE with the first 64k being the standard DRAM circuit, then it also has the Hias 512k SRAM expansion on board (https://www.horus.com/~hias/atari/#sram512k), which has switch configuration for 64k only, 256k Compyshop, 256 Rambo, 512k Rambo. A PIC microcontroller is used as an "EMMU" to drive the extended memory, though I don't think it has any relation to the 130XE EMMU in functionality (I could be wrong on that). There is a variation of this in Mytek's 576NUC+ project, which is essentially the same circuit, but with a few slight changes done by tfhh, with also the first 64k being SRAM, instead of DRAM. I'll have to try your new OS, it looks pretty cool, and give Simtest a shot, though I believe the extended memory works just fine, since I did test it back when I initially finished this board with xRam and some other programs.