ivop

Release fast, release often. Let us get crazy on your .rmt file! Vinscool releases almost all his .rmt files. They might look like abracadabra to the unschooled eye, but I found them very inspiring!

I ordered them here: https://www.aliexpress.com/item/4000490392119.html They where packaged very well. No bent pins.

@emkay Or share the .rmt on AtariAge instead of just YouTube videos. Nobody learns from YouTube videos.

I received the edge connectors! Now it's time to layout the backplane PCB

Later in the thread, there's also DUP.SYS

Like. But your recording process needs some work. Your display runs at 60Hz, while the emulator runs at 50Hz

Yes. I'm one of them. Using Linux since 1995. Stack of Slackware floppies FTW Now on debian mostly, and devuan for lower end machines. Well, Windows vs MacOS vs GNU/Linux, or iOS vs Android/Linux, are the new Commodore vs Atari vs Spectrum "wars"

Yes, most of the times it's the opposite: https://www.phoronix.com/scan.php?page=article&item=2990wx-linwin-scale&num=1 And scales horribly. Top-500 Super Computers. Check the OS (family) statistics. It's 100% Linux. 500/500. https://www.top500.org/statistics/list/

True. If you select a H device, you specify a local path that that will be an emulated Dx: drive. That's PCLINK.

That's exactly what I meant. DOS simulation at sector/block level, i.e. SIO reads. Similar to how Aspeqt/Respeqt does the H: device. DOS 2.5 reads the VTOC and directory sectors through SIO. The H simulation creates sectors 360-368 on the fly.

Keep in mind that H: devices are simulated ATR disk images. The emulator simulates the directory sectors, and tries to determine which file you are trying to load, and then produces 125+3 sectors that keep loading that file. That's DOS 2.5. MyDOS should be similar, but subdirectories make it more complicated. And larger sector links. SpartaDOS is a whole different beast. IIRC there were also changes made to the FS specification. The spartaDOS 1.1 file system is considered obsolete. The FS between 3.x and 4.x should be the same IIRC. But opening four files from Basic, and start noting and pointing, reading and writing, and I'm pretty sure both H: device simulations will fail horribly even with DOS 2.5

True, but... you claimed it was common BITD. It was not IMHO. But sure, it's a freaking great demo that uses an underutilized asset that was there back in '81!

@Faicuai The 8088Mph is indeed a great demo! But that was not a common setup BITD. Did you know people that connected an NTSC television/monitor to their CGA card with tv-output? Note that all the extra colors are created by either NTSC artifacting or flickering screens (not seen on the youtube video). On a plain CGA monitor, this would look, ehm, different.

Definitely. I used LAX #$00 in both of my C64 sizecoding experiments. The only LAX imm that is stable

Yes, more or less. If it's not needed for speed, I agree, don't use undefined opcodes for no reason. But if it helps to get that extra vertex on screen, do it! It's the exact same hardware that was sold by the millions. AFAIK there's no, or not much, specific 65C02 code was written for the Atari. There is for the 65C816 though, but nobody expects that to run on stock hardware

I actually went the opposite way last Lovebyte compo, and made a few C64 entries Only a few people are complaining some software doesn't work on their non-standard CMOS 65C02 or 65C816. Always the same people. Ignore them. If your hardware is non-standard, perfectly fine NMOS 6502 code will sometimes not work. I got thanked for not using undefined opcodes in AtariSid 6, but if that would have improved performance, I would have used them

Agree in how they sound. Even though SID can go high, somehow the external filter circuit muffles all the high overtones. On resolution however, I disagree. The 16-bit frequency register is the complete opposite. You need high resolution for the bass notes. Notes are only a few Hz away from eachother. The higher notes need less resolution. You are not going to hear the difference between A6=1760Hz or A6=1755Hz. But A1=55Hz. If you're 5Hz off there, you are playing either B1 or G1(!). Now, SID has a frequency register that is lineair. POKEY on the other hand has a clock/n divider. Much more suitable for music, as the relation between frequency and pitch is exponential.

Looks like either 3mm or 4mm diameter. Be sure to get a sunken head. And perhaps 1 or 2 mm longer. The other side of the shell should be able to handle that.

https://github.com/ivop/sizecoding/tree/main/lovebyte2021 There are several methods of doing "real" music. I'm considering writing a piece about that. From do-re-mi-fa-sol to pokey music in 256 bytes

Her stitching looks like properly stitched baseball caps. Not the knock-offs. I did not actually. Thanks for bringing this to my/our attention

Cool! Here's a link: https://www.ebay.com/str/papanannysfunstuff Edit: My 1200XL is "stored" in a box. I'd really love an 800XL or 600XL version Might get a(n) SNES version. My house is pretty dusty

coke | nose > keyboard

This. A powered and buffered CART/ECI or PBI hub, and perhaps more, is the way to go IMHO

That's not odd. They just added a comment to the people to clarify that the aformentioned issues are indeed ironed out and included in this design.

I remember that. It was also dubbed in Dutch. Very popular indeed.