Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by mellis

  1. I have a question for the OS X users out there: Assuming SIO Server's double-density bug was fixed, is there a single additional feature that would make it more usable for you? Folder imaging was mentioned earlier. To me it seems running a Win32 compatibility layer is a bit heavyweight for a peripheral emulator.
  2. Hi folks. I really don't want to hijack this AspeQt thread, but I will post a few bits to contribute to the turn the conversation has taken. I wrote SIO Server to scratch an itch I had a few years ago. It was designed to satisfy my own personal requirements, and then I released it to the public just in case others might derive some utility from it. Until recently, SIO Server has had two active users that I know of. The double-density bug is definitely in there (and fixable), but I never did get around to correcting it because it wasn't a problem for my personal use-case and there were other peripheral emulator solutions that everyone seemed pretty happy with. SIO Server is actually two programs: the GUI process and the communication daemon. When the GUI launches, it spawns a priority-elevated communication daemon as a child process. The daemon and the GUI communicate with one another using piped I/O. The approach minimizes CPU usage and helps to ensure that the priority-elevated daemon can continue to communicate even if the host system is delayed updating the GUI. Although I am a long-time Mac OS X (née NEXTSTEP)/iOS developer, the GUI is written in Java in order to facilitate porting the app to other POSIX-compliant OSes. The core of the communication daemon was written in portable, POSIX-compliant C by Belboz, and I added many enhancements to it. The communication daemon has been tested on Mac OS X and Linux systems, and it can be launched from the command line. In short, I never got around to fixing the double-density issue or to creating a Linux build because: I was happy with the software (for what I needed), nobody else was terribly interested, and I've had little time to spare anyway. That said, I am glad to see that the program has proven helpful in some way: as a troubleshooting tool.
  3. I was on the Atari 8-bit and ST roundtables on GEnie. My handle was old enough that it was [FIRSTNAME]-[LASTNAME], not the usual [iNITIALS].[LASTNAME] that came to be used later on. Good times.
  4. Nice write-up, Algus. Best has been my choice for Atari parts since the early 1990s.
  5. One thing I enjoy reading about in the forums is various installation strategies for Atari modifications. I recently completed the Easier 7800 Composite Mod (thanks Puppetmark and Underball!), and I'm pretty satisfied with the modification itself and the installation, so I figured I'd share some pics too. Here is the bottom side (component side) of the prototype board: Here is the top side (circuit side) of the prototype board: I used wires with connectors so that the board can easily be removed. This is helpful because once installed, the 7800 logic board cannot be removed without first removing the composite board (the yellow RCA connector extends though the hole in the back of the 7800 case plastic thereby preventing the board from being lifted). Now with the board installed and connected (yes, there is clearance for the RF shield): And finally, a shot of the back of the system (8mm headphone jack is on the left, and the composite plug is on the right):
  6. I probably should have included a link to the application, huh? Sorry about that. Download it here: http://www.ellissoftworks.com/sioserver/SIO%20Server.app.zip
  7. I've got one you can try. It is designed specifically to work with the FDTI-based adapters. Documentation is available here. The linked documentation explains how to build a cable. Here's a screenshot from the documentation:
  8. Pac-Man did become the pack-in when they changed from 4-port to 2-port systems.
  9. According to Curt's atarimuseum.com site, the expansion port was included by Warner Atari (pre Tramiel) with the intention of (maybe) eventually adding support for laser disc games.
  10. FWIW, the upcoming 7800XM module does not require an early 7800 with the expansion port. I mention this because, in the video, you seem to lament that you don't have that port when you allude to the 7800XM.
  11. We Atari 5200 fans don't take kindly to folks referring to it as a "5600".
  12. Can't wait to see the case mods you make to accommodate a wire wrapped board .
  13. I have one of those, and mine is autographed by Jack Tramiel. In my 9th grade English class, we had a writing assignment in which we were to write to a celebrity of our choosing and request an autographed item for display in the school's trophy case. Being an Atari geek, I chose to write to Jack. I suppose he felt that would be a good opportunity for some free advertising, because a few weeks later a banner like that one arrived. He had signed the lower right quadrant, starting at the right edge of the rainbow stripe.
  14. When you visit the site on your iPad, you can view the desktop version of AtariAge (the way it looks on your laptop) if you click on "View Desktop Version" along on the bottom edge of the page.
  15. Typically, MRS stands for "Material Resource System" or similar. That comment seems to imply that only single drive 1450s were going to be offered initially. Surprising. I would have held out for a dual drive unit, as buying a 1450 to then turn around and hang a 1050 drive off of it seems kind of counterproductive.
  16. I would encourage folks to first try using the Retro-brite process described in the 8-bit section. If you do it right, it will restore the case to like new condition -- key caps and all. If you run into issues, you can always fall back on this technique after first trying Retro-brite.
  17. I shed a single tear when I read the title of this topic.
  18. I feel obligated to post a dissenting opinion here. I'd love to see you continue to employ the early Mac look - it's very classy and appropriate for a GUI running on a machine of that era.
  19. This is a good idea. You should allow the application to request a heap cleanup, as you propose. However, I would like to suggest that, in the event that a memory block request cannot be fulfilled, your memory manager should automatically run a garbage collection cycle in a last-ditch effort to satisfy the request before returning from "malloc". That way, you get the best of both worlds, and apps that don't properly request a GC cycle will function nevertheless.
  20. Hmmm... never thought of that. It's a WIP name we were throwing about. It's also the name of an early linux variant that wound up become the basis for one of the Apple OS's. The Mach kernel was developed by researchers at Carnegie Mellon University. Mac OS X is based on Mach, and it has nothing in common with (nor does it have any ties to) the Linux kernel, which employs a monolithic design. The GNU/Linux OS and Mac OS X are similar in that they are both POSIX-compliant OSes that employ a GNU userland. However, that all runs atop their two very dissimilar OS kernels.
  21. That document details precisely what Landon was describing in his blog. Perhaps, as you say, the design was planned for the EST and then scrubbed due to cost cutting. Such a pity.
  22. Funny. The developers I work with the most all use Macs. They're the best UNIX workstations around.
  23. Computer: Mac Pro, eight-core Assembler: CA65 (the assembler bundled with CC65) IDE: Xcode (configured to compile and link using the CC65 toolchain) Video capture: EyeTV PVR-250 (S-video/composite in)
  • Create New...