Welcome to the WUDSN ursel home page

WUDSN ursel - or short WUDSN - is a demo group founded in 1991. There is an explanation why the group and the site are named like that, but that's a different story you can find in the FAQ. For the time being it should be sufficient for you to know that me, aka JAC! am one of the members ever since. I have created this web site to offer my tools and productions and to share the fun I have had for more than 20 years now with my Atari-8 bit computer and other classic computers. To learn more about me and what I'm doing, check out this personal interview that I gave for ANTIC - the Atari 8-bit podcast.

Atari 2600 - I have no memory

The Atari 2600 Video Computer System (VCS) is a unique and interesing thing. The purpose of this tutorial is to show interested people the history of the Atari 2600, explain the hardware design decisions and how they impact the way of programming - making programming the Atari 2600 a very unique experience and challenge. And I show and explain examples that illustrate how programmers adopted the limitations and strengths of the machine to create better and better graphics in the course of 30 years. The following picture from The Argyle Sweater nicely brings it to the point. Thanks a lot to Scott Hilburn for the permission to use it.

Atari VCS has no memory

 

Heaven's VBXE works - after 6 hours on the CRT battlefield

At Revision in April 2015 Heaven gave me his Atari 130 XE and his Atari 65 XE with VBXE 2.0 installed. The first one had broken down at the party, the second one has a VBXE built in but not adapter cable to connect it to a TV. While the Atari 130 XE worked fine after a little cleaning and re-soldering, the VBXE machine turned out to have an Atari ST monitor connector and a complex switch built in. I sat down for some hours and traced the different signals through all the wires, the switch and the connector. I found that the way the wiring was, the connector can server as FBAS-SCART and RGB- SCART at the same time, depending on the switch position. But I didn't have a proper plug for the connector, so I first had to order one. I had to learn the hard way that there are different types of 8-pin DIN plug with slightly different pin arrangement, none actually fully matches the Atari ST monitor connector.

Months went by and finally I got a working plug, but I was frightened by the thought of soldering SCART cables with 21 pins into the damn tiny DIN plug, no knowing where color meant what and which pin is actually which (plug vs. connector, front-view vs. rear-view, ST plug vs. VBXE pinout, before the switch vs. after the switch....). And guess what: How right I was. 

Today I was in the mood and decided to give it a try. 3 hours of soldering, measuring, desoldering, measuring, re-soldering, dozens of mapping lists and diagrams I finally made it. And then, when the cable was complete, I tested it. And it didn't work at all with my SABA CRT. So a started measuring, desoldering, measuring, re-soldering, checked the diagrams again and again. Then I tried the 2nd CRT (Goldstar). It gave a very dark b/w picture and no VBXE picture at all . The 3rd CRT (Grundig) gave the same result. Meanwhile I was 100% sure that the wiring was fine. CRT number 4 (Schneider) then gave a clear picture with greyscales - in red. IN RED ?!?! Back to the board, did I swap luma with red - no I'm not that stupid. Phew, no, I'm not. The 5th CRT (Sony Triniton) presented a totally distorted picture as it didn't detect that the input was on RGB and not FBAS. Finally I grabbed my (almost) last available CRT: The Phillips that had just left my living room before X-mas. I plugged it in and WHOOOA - it f-cking worked. It just worked and looked perfect. The cable had been correct right from the start, but it took 2 hours to find the TV that could actually handle RGB via SCART. Priceless. Merry Christmas Heaven, you'll get your present soon! Here's how CRT battlefield looked like.

Parnorama view of the CRT battlefield

Working hard on DIS6502

I finally managed to escape the real life daily job business and had a great week with sun, beach and DIS6502.You don't believe that? Check the commits. Again a lot of the monolithic plain C has been transformed into readable classes with clear interaces and dependencies. Now I feel I understand the code good enough to implement the new load/save for the new workspace structure.

Me at the beach bar in Italy

The!Cart Studio update released

Features:

  • The download now contains a "TheCartStudio.exe" for Windows users. This wrapper program comes with a proper icons, a version and location test for the Java Runtime and the required Java parameters to ensure enough heap memory is available.
  • The download now also contains a "TheCartStudio.sh" for Linux users. This script provides Java with the required parameters to ensure enough heap memory is available.
  • The download now also contains a "TheCartStudio.app" for Mac OS X users. This one is still very experimental and is not yet tested as I don't own a Mac OS X machine. But I wanted to get this version out now.
  • Online help has been revised. New sections and diagrams in now explain the overall workflow and creating and flashing workbooks. Also the different options to add files directly or via Maxflash Studio and MegaCart Studio are now explained.
  • The selected line in the extended menu now uses black text and a more constant and darker flashing. This reduces bending and artifacts on CRT TV.

Fixes:

  • Player missile graphics of the extended menu are now disabled correctly before an entry is started. That was an issue for example with Flop Magazine 56 Intro.
  • An exception that occurred with ATR files that do neither have a boot manager menu nor are DOS 2.5 disks is fixed.
  • New Atari software version 2014-04-07 included. It includes a fix for the CAR or MyPicoDOS when loading OSS modules.
  • The "-createSampleFiles" command now correctly creates separate folders "ROM-Correct", "ROM-Size-Too-Small", "ROM-Size-Too-Large".
  • Console output for error messages is now routed to "System.err", so the command line can properly distinguish between information and error messages.