candle

which part you haven't understood? or you're merely reporting issues back? if you're expecting issues to be fixed overnight then no - it won't happend check again in a month - perhaps there will be something to fill your needs then

honestly? peculiar wording... think honestly on how stereo pokeys are possible isn't it that the other takes half of the space base one occupied? how this works with your logic, or your being honest?

they are there because in course of development i found SOME games using this obscursion methods, not all of them, and most importantly, i didn't imagine, that sane person, would use such methods novadays

sure, you skipped your powdered frog pills again...

bounty bob uses custom banking scheme, developed for protecting atari 2600 games repeated pia adresses - resulting in what you can observe here repeated pokey adresses - resulting in lazy birds and game unplayable at all if there is something more than single pokey on the bus if there was a wast amount of games that would use that banking scheme, or coding "standards" this would be noticed, and fixed, but there are none the other example i know of was road race, and i took care to make it playable when releasing u1mb board according to all available literature pokey address range is 0xd200-0xd20f, PIA is 0xd300-0xd303, remaining space is simply the result of address decoder being cheap, and there is no advantage of using remaining space for addressing these chips other than obscuring the code

what you see there is PLL retrived pixel clock not in sync with video signal generated by VBXE, and pixel data crawl from one discrete point of sampling time to another it is also possible that your scaller assumes low-res display data - 480x288 for modern "standards" and there is not enough time slots to accuratly capture VBXE output check if you can enforce 640 or 800 pixels wide horizontal resolution you either need to change PLL phase or try to auto-adjust it using white text on black background as your test pattern whatever scaller's software allows sorry for being too technical

what are the odds? XXL proposing replacing 6502 tasks with modern CPU...

i would keep the one, that given software was released at, others might not be as legit, or function diffrently

sure, whatever

Sikor's offering is no use for any serious cartridge because of various features inside mostly big latch in the upper part of the case making usability very limited being psychically smaller the only way would be to have it heavly cnc machined before it would become usable and you would still need to use micro-sd card that i dislike i do not see any point in using micro-sd card if device is big enough durability of this connector type is already limited due the size of features it uses, and i need to keep in mind that this sd card will be removed and reinserted countless times during its use its not set and forget solution, or should i embed it internally and you would rather use sio to put new things on it? as for fit for 1200xl this was misunderstanding between what Jon communicated (making it narrower by 0.5mm) with what was done - making narrowed part narrower even more by that 0.5mm

by all means please continue! there is a lot to be learned by doing this - especially about how funny USB HID class can be implemented by some keyboard manufacturers in some keyboard models filling reports bacwards, out of order, etc

USB keyboard interface is part of simplestereo v3 & v4 boards (you can also use regular PS/2 or even IKBD (Atari ST/TT) keyboards), there will be also stand-alone version provided there are quite few gotchas when doing this, but this is pretty strainght forward once you have USB host stack ready

nice!

resistance test strip to confirm if conductive coating is up to the specs

I'm using switching mode power supply all the time -if it's of decent quality, and not older than 2-3 years it should pose no problems, older ones, especially if used on day-by-day basis, tend to have dryied out electrolitics, resulting in excessive ripple voltage that tends to stabilise when the psu gets to its working temperature, but results are intermediate faults of all sorts

side3 is guarateed to work with a power supply giving anything in range of 4.2-5.5V - this was tested, athough ripple voltage above 0.2V should not be present

it seems there is none i was hoping someone has Atari StarWars dumped to VGM format, but i didn't get any responses

I was postponing my answer, since lotharek is still on his vacations, and there is a lot going on in Poland unrelated to all this, but still keeping me distracted Anyways. From my experience based on units Lotharek sent me to investigate their abnormal behaviour it comes down to bad U11 chip on SIDE3 cartridge this is 74LCX04 chip and can be replaced with exact the same chip or 74LVS04 chip, but doing this by yourself would void the warranty - so i'm not advising anyone to try this best would be to return it to Lotharek, unless he would agree on something else depending on which gate would fail results might be as follow: loader doesn't start, athough you can use side3 as mass storage under SDX and using PBI BIOS - RD5 control fails atari doesn't start, but SIDE3 led flashesh during power up - CCTL control fails some cartridges will fail to load, that are supported - RD4 controls fails nothing works - PHI2 control fails Some people, that are known to copy other's people work and sell it prevent me from releasing schematics for SIDE3 hardware - this was the case for SIDE2 that was cloned, Ultimate1MB, and even VBXE I don't like this anymore than any of you, and I'm all for the right to repair, but some people don't know how to behave in modern world, thus my decision

Jim, starting this project i went for a shopping and bought every card type/brand i could in two towns - I didn't care for anything but just availability and to have a test sample i could use and check for i've ended up with 20 cards ranging from 16GB to 64GB - i didn't want to spend more than $20 on a card, so bigger ones wasn't my target then i gathered every card i had laying since stone age and asked friends to help me with my quest result were 16MB cards, 128MB cards (MMC, MMC+) and all were tested for read/write performace and surely they were some mishaps in the way, but always it was a software isue and card was simply requireing some kind of special handling during the init or during the usage phase to work reliable some had to have chip select signal brought high (deselected) then low (active) before each command, otherwise they would not work at all (Kingston) others had to be clocked eight times before they release the bus after being deselected (ie SanDisk) others did require full protocol-dependand initialisation phase with no shortcuts made - especially if they were of older type (MMC) Jon brought to the test table another ones he could find locally and this was our test sample surely we can't have them all, yet it always been, and i belive it will be a case of some special initialization or handling between commands to make them working Roy, Use some kind of SSD migration tool to migrate your data between CF and SD card - you could use DD for *nix systems, or some other software for Windows

2GB cards are on the edge of SD card specifications - this is largest allowable size for their specs, and special measures have to be taken for multi-sector transfer support as done by SIDE3 on both hardware and software layers

I just wonder, why anyone would want to compromise preformance of their mass storage device using old SD cards, when new 16GB card costs $3 use at least SDHC cards 2GB cards are probably the worst choice since special handling might be needed for those, and only few were tested (I have only one)

yes, this is expected behaviour

to disable SIDE3 on power up simply turn Atari power on while pressing SIDE3 button if case of some misshaps inside flash memory, you'll be able to recover from SIO

really? as for beta testing - it was 10 months in beta testing and active development, and Jon keeps delaying release of U1MB bios and drivers for a month right now last thing that did change was SanDisk card support it was very nice of Jon to accuse me of something that was a part of our private conversation over the forums - grown ups do things like this i guess