wildstar87

I am using the SRAM expansion, if I switch it off, Self Test works fine on the memory. I would have expected at least the Atari/Compyshop to work, but it crashed as well. The failure has been intermittent in how it fails, yesterday when I tried this, it failed to a black screen, but the day before, I was getting garbage all over the screen. Seeing what reifsnyderb said about what he has noticed in his OS modernization, I guess it isn't uncommon for it to crash. I'll have to run the extended memory tests through a program, but when I did test it a few years back with the extended memory tests, it was working, though I can't recall if I ever went through and tried the Self Test from the OS itself.

The Jeff Popp 600XL video mod, puts all the video circuit stuff back in, including the monitor port, but this was only made with NTSC in mind, since all the PAL machines already had the monitor port installed w/circuitry. Oddly enough, I've been looking for the actual Jeff Popp mod, and while I find references to it on Atariage, I haven't been able to find the actual instructions, w/bom component locations. Are you trying to put PAL video into an NTSC 600XL? My first thought would be to find the Jeff Popp mod, then compare the NTSC schematics with the PAL schematics in the video section, it might be the same, or a few components might need to be changed. The other issue is converting all the other chips, crystals to being PAL compatible, otherwise the video won't work right. Mytek's UGV is also an option, instead of trying to put the original video circuit back in.

I built this a while back, and verified functionality, then life happened, and stuff got set aside. I'm going back to this, and noticed that the self test when going through the Ram test, it gets so far, then I get garbage all across the screen. It has passed other memory tests, Syscheck, Xram, so it seems to be working. I know the self test in the 130XE is kind of broken, I believe it just keeps testing only the first 64k, but it should still work the same shouldn't it? The garbage/crash worries me a bit, and makes me wonder if something is wrong, or if everyone sees this?

I think RTFM is what I needed, I didn't notice the specific installation instructions, just the picture with wiring on the main TKII page. I had assumed that the function keys would be picked up by the TKII directly, but it seems I missed the part that the Function keys actually have to be tapped into, in order for TK-II to control those. Just doing the piggyback isn't enough, correct? I have to run wires to those header locations for the function keys, and tap into traces on the motherboard. The other two boards that I had these in, were designed with TKII in mind, so already have those in the layout. This is the first time I put it in a stock motherboard. The example pictures showing the install in the 1200XL threw me off, because I thought the function key header locations didn't seem to be used there, helps if I count pins, they are being used, it's the three pins that are part of the PIC programming pins that aren't connected. Still appreciate the replies, even though it was my dumb ass mistake..

So I've run into a problem. The function keys don't seem to work. The main keys are fine, inverse works. The F-EMU is TK-II. Any ideas?

Yeah, I have programmed other TK-II chips for 1088XEL, and the 130XE Remake board, so I know it works, just wanted to see if you knew a way. Thanks!

Mytek, I just built one of these, and am using a Pickit3 to program. This is more of an issue with MPLab that I thought you might know the answer to. I'm using the MPLab IPE to program, and it passes Programming/Verification step, but when I manually Verify, it always fails. I did find this note, https://microchipdeveloper.com/faq:2334, however I don't see any settings to add a delay, I'm guessing this is part of the firmware code itself. Any other way to fix this verify failure? I've never seen this work ever, even in the lab I work in, where we use the programmers with more features and more expensive. The checksums are the same between the hex file and what is read off the device, and it usually works, so I'm not too horribly worried, just wanted to know if you have a trick, or just don't worry about it, if it passes the Programming/Verify step.

Do you have the mfg part# of the Din5 you used for this? It looks like it matches both the wiring, and the mount solder points. I've only found ones that match the wiring points, not the two mount points. I used hot glue to reinforce the port, but I'd rather have the solder mounts.

Yeah, I'm not sure why he does it that way, though based on anecdotes on Atariage, I think (this is just my opinion), is that he wants to sell stuff, but he doesn't want to sell THAT much stuff at once. If the website was easier to navigate and find stuff, he would have more orders to process. It's his business, so he gets to run it the way he wants it, but if nothing else, I wouldn't want to run it that way, I mean he does update it, with all the customer quotes, and his stories and everything, that just makes updating even more complex IMO. I mean, I think it's all manual editing, nothing programmatically generated, though I could be wrong. I'm an old curmudgeon now, and I have things that I want a certain way, that younger people think me strange about, so I can somewhat understand, but I find it hard to find stuff, having to literally read between the lines. Don't get me wrong though, I'm glad he's still around, and you can find stuff for relatively reasonable prices, especially with the topic of this thread being the point. I remember hearing about Best Electronics back when I was B.R.A.C.E. back in the 80's.

His entire description, kind of reminds me of Best Electronics website.. You get an entire backstory, and tangents, on the thing you want to purchase.

Looking for an unmodified 600XL case, or case bottom. Don't care if it's dirty, but would like it to be undamaged. Looking for one in the US, as shipping overseas can be expensive.

FYI, I have 8 of the PLA10AN1522R0R2B chokes available, I ordered them in bulk a while back, because there wasn't any other way to get them. I'll let them go for $3ea+shipping costs. So if you are interested let me know,

I'm also interested

JLCPCB usually has the best prices IMO. Interesting, I've been racking my brain on how to make a mount for the Stackpole backplate that doesn't short the PCB, I was trying to come up with a mount that didn't use the backplate. If I am understanding correctly, you are going to use the existing screw holes that hold the plastic keyboard portion down to the membrane as mounting holes. I'm assuming you will use some sort of spacer (to avoid shorting) between the back of the PCB and the Stackpole plate? Do you think it can be done, without having to add spacing between the plate and the top case (to make enough room for PCB in between)?

I'll have to look that up.

That's it! Thanks!

I'm trying to remember the name of this game, you were up against a supercomputer/robot, with nuclear war being the outcome. It had like a hexagonal play board, it was turn based, kind of chess like. I thought it was named Colossus or something like that, but it wasn't the Colossus chess game. It was definitely more of a strategy game, I just remember when the computer was thinking it took a long time. I don't remember much else.. Any ideas?

Please show me the documentation that says how to use the VGA core, and where it's located. I just looked again, Does anyone actually read what I said? I guess not. Thank you Drac030 for twisting what I was saying, I was very clear on what was happening, I just thought it might be a difference in communication, but I guess you were being defensive and sarcastic the entire time, good to know. Also, you didn't really address the actual stuff I was talking about, so how are you any different. "It just works, why are you having a problem" seems to be your attitude. If I was asking you to fix the problems without giving you repro steps, your responses would be understandable, but I didn't ask you to fix them, and I already explained why, but you see what you want to see I guess. This is a great example of why VBXE is NOT a good solution for me. Candle again mentioned the VGA core, but still no information on where to obtain it, and what documentation there is. I was actually holding out a little hope with his reply, but based on the rash of shit I'm getting for bringing up valid issues, I'm not even motivated any longer. I'm assuming it's buried in one of the many threads of VBXE somewhere on this forum, or another forum. Nonetheless, not readily or easily accessible. Let's go through what's on Lotharek's website shall we? Installation manual, I have used this for installation, it's fine Release CORES - Description on the utilities, FC.Com, and DCFG.com, inside the current folder, a readme that tells you what cores are available, and their notations. No mention of the fabled VGA core, or board mods to use it, and of course the different variation of cores available. None of this can change the palette to NTSC, and I never needed to change to the GTIA or Rambo versions. Release DOCS - Programmer's manual, the only mention of VGA Cores with the note "VGA cores are currently deprecated, and not actively developed. Limitations they had were too severe to justify their existence.", a list of the available cores, no VGA or NTSC core listed. Does talk about RGB palette modification, but nothing about how to permanently change it (because it can't be without a recompiled core). A lot of of what I assume is useful information for programmers. Release EXAMPLES - Code examples for VBXE, not useful for the aforementioned issues CORES 1.26 - This is just a duplicate of the Release CORES, not sure why this is linked under a different heading. Note, absolutely nothing under the FAQ tab, where some of this could be noted. I'm not an idiot (but clearly some of you think I am), I've looked at all of this stuff. You all seem to be conveniently leaving out the issues that I was actually addressing, and my experience with it. I'm happy that it all works just fine for you all, or that you don't care about NTSC palette, but there are some of us that do care about that. U1MB being a solution, yes great, you have to buy another >$100 device just to get the palette to be changed "permanently" upon bootup (but thank you FJC for doing this!). I have tried this in my 1088XEL (which I built myself), and that solution works fine, but that isn't the machine that I have VBXE in, and I don't want to buy it just for this reason, and quite frankly it's not something that you should have to do. I've been working in (as in a job) and around the computer industry for 30 years, dealing with hardware and software, I've been working professionally (as in a job) in an EE Tech for 15 years. Not that I should have to justify my knowledge base, it kind of pisses me off at myself that I even feel like I have to mention it. I was replying to the 55five66six about whether or not it's worth it, I'm sure he read what everyone said, and will make his own decision. As for the rest, I'm done, you can go beat someone else up, I said what I wanted to say. I'm beginning to feel like FJC on the Rapidus issue. 55five66six I wish you luck on your decision, this was actually a great example of what you can expect with VBXE.

I get it, and I'm not unreasonable, everyone has stuff going on in their lives, for most people this is just a hobby, not a business. That being said, all misunderstandings could have been resolved with a little communication (such as you did right now). Last I heard (in the linked thread) was that you said if a palette was decided on, that you could put out a core that would do this. After the palette was decided on, questions about when we might see a changed core on the same thread were never answered, PMs were ignored/never read. I was unaware that you didn't have the capability to do this, as you didn't mention Electron having to do the actual decision/work. I also know you are not responsible for the sales side of things, so I don't blame any of that on you, but I think it is disingenuous of Lotharek to sell this device, without even mentioning any of these known issues that are brought up over and over again. If nothing else but to save himself and you from the frustration of having to deal with unhappy customers. Just a note saying that if you are used to NTSC colors, that this will not be the same as it is based on PAL, and that a monitor/device that can understand 15Khz RGB like ST or Amiga. The official documentation such as it is, on Lotharek's site is all that I know of, the only mention of VGA cores that I saw, was that they had been deprecated, and no longer available. I would be happy to read any documentation, and experiment on this myself, if such information was readily available, such as where the VGA core file is, and what modifications need to be done. If there is a thread that has this information, please let me know which one, and I will try to find this information myself. I know you made mention of the VGA core before, but that's all it was, was a offhand comment that it was out there. I don't expect hand holding, just pointing at a webpage, or thread, or pdf would have probably been sufficient. This still doesn't help with the palette issue until when/if Electron decided to change it, but it would go a ways for me to get more satisfaction out of what has so far been an exercise in frustration.

Yeah, I was in that thread as well. The solution is good if you have U1MB, but for the machine I have it in, I don't have U1MB on that system, and don't really want to put it in that machine either. When I was looking for a video solution to hook up to a modern monitor at the time, there were only 2 solutions (essentially still are), add the 80 column capability, and it seemed a no brainer. Reality has been much less rosy for me. Anyway, I think I've beat this horse dead enough today. If Simius were to add enhanced video equivalent to VBXE (hell even work it so he can use the current driver), I think he would have a solution that would be the slam dunk, not that he can keep it in stock now, due to the chip shortages.

Point of interest, look at the start date on that thread.

I'm talking like 3-4 months ago, with 4.49

As I said, I don't know exactly at this point, it might have been Format not Fdisk. When and/if I get it working again, I'll let you know what I find.

Honestly since I don't have it working right now, I couldn't tell you exactly I ran into, but I think it might have been like Fdisk, Date/Time bar, the menu system, some other stuff. I wasn't using it enough at the time to warrant contacting you about it, and I never want to abuse that sort of thing. I appreciate that you make yourself available, I know it's not something you have to do. Also, having been in a large software company, I'm well aware of the difference between nice to have fixes, vs show stopping bugs, so didn't think it was that important at the time. Nonetheless, it colors my experience with VBXE, which is why I mentioned it.

This is another confusion, there are so many types of RGB, and they all seem to be non-interchangeable. Component RGB (YPbPr) is not the same as RGBs which is what the VBXE outputs, along with Atari ST, Amiga. It is also not the same as RGBI (Digital RGB) used by CGA. What VBXE outputs is 15Khz RGBs (Analog RGB). From what I have been able to determine, the closest example would basically be a VGA signal, which is also Analog RGB but with a higher refresh rate, that's why some of the older Multisync CRTs could display both 15Khz RGB, and VGA. There are some LCDs that support this, but I don't think any of them officially support 15Khz. There is a list here http://15khz.wikidot.com/, but even if you get one on this list, it may not work as expected, I tried with two different models on this list. Trying to get an 15Khz RGB CRT is prohibitively expensive nowadays, as prices on Ebay, or other sale sites are taking advantage of the retro demand. The only other option other than those is some type of scaler. https://www.retrorgb.com/, has a bunch of information on this stuff.