Jump to content

Mr SQL

Members
  • Content Count

    2,751
  • Joined

  • Last visited

Community Reputation

1,102 Excellent

2 Followers

About Mr SQL

  • Rank
    River Patroller

Profile Information

  • Gender
    Male

Recent Profile Visitors

23,122 profile views
  1. My Heavy sixer is broken currently but I could try it presently; I have a new hex buffer chip I tried to put in but having some trouble getting the socket cleared with the braid. However I have an idea you may be charging the paddle capacitor and not discharging from the description, since the user had to pull the cart and power off to resolve.
  2. Looks like 85 Hz is working and the electron gun isn't getting reset early in the double image.
  3. Very cool! The new release of Gopher is awesome for SuperCharger development because of the real BIOS and SuperCharger debugging features. I used Stella and Z26 which have very good emulation of the BIOS but have developer side bugs that allow extra functionality not allowed on the real SuperCharger and I think this is what happened with the contest release files locking on the multicart. The emu is getting tighter but not consistent between the emulation platforms including the emulated stubs on multicarts not using the real SuperCharger BIOS.
  4. Yes pressing play on tape is classic and tape mixes are awesome! Only the SuperCharger is fully compatible with KC OS 12 released at SillyVenture, it locked in a loading loop on multicart during the demo party. SillyVenture 2020+1 Art Scene Videos - Atari 2600 - AtariAge Forums Place the five wav files in a repeating playlist to stream the data to the SuperCharger from your PC or iPod or follow the instructions on the thread to load them from a looping tape. You can also try KC OS online here in Javatari or play the ROM in Gopher which uses the real SuperCharger BIOS. Fancy carts are only partially supported but SuperCharger compatibility will improve as firmware upgrades more closely match the BIOS.
  5. Pretty interesting idea I'll have to try that To generate a full screen NTSC display we are limited to a maximum of 60 FPS which is double the framerate of classic CRT Television, the nonstandard Atari video signal not offsetting the encapsulated 30 Hz fields in the subcarrier so they become full frames. It is possible to subdivide the frame rate from this spec. STARBLITZ plays at 60,30,20,15,12,10,8.57 and 7.5 Hz sequencing for the video and audio with the frame rate matching the Hz on all but the 60 Hz mode. When it doesn't match we get another type of flicker called motion blur, there's a thread here on the BlurBusters forum with a parallel researcher taking 120,240 and 480 Hz experiments into the stratosphere with more powerful CRT kit.
  6. Very cool, yes it was definitely a 16K tape I remember and a pure text adventure. I also remember playing Zork the underground empire from disk and enjoyed the graphical Mark Data adventures like Black Sanctum that fit all in memory and could be loaded from either tape or disk.
  7. Very cool! I remember playing online adventure game modules hosted on Bulletin Board Systems. They were great fun even at 300 baud since they played in real time with the lackadaisical text scrolling a part of the experience, distinctive like a teletype.
  8. Both were great. I started with a 4K TRS-80 and a tape drive and found it to be a very reliable storage medium. Got a PET with a built in tape drive next which worked great for loading pet Space Invaders and the Scott Adams Adventure games. Later upgrade of the TRS-80 with 16K and Radio Shack Sands of Egypt and Raaka-Tu 16K adventures on Tape were also inspiring. Disks enabled sprawling modular programs that swapped in and out of memory from the disk, which could be helpful or annoying when it created excessive delays for each module. Zork required a disk drive to handle the expansive underground empire, but I believe there was a stripped down version that ran off of cassette for the C64. The ADAM commented on earlier was an interesting system hybrid because the high speed tape drive had an ISAM mechanism like the stringy floppy drive device enabling an indexed file system on tape. The SuperCharger for the Atari 2600 functioned similarly and could place an indexed file system directory on cassette tape, here's an example of a demo for Silly Venture 2020+1 to run an Operating System from an ordinary cassette deck using a 1 minute looping answering machine Tape. Interestingly for this thread theme, the demo actually got stuck in an endless loop "loading from tape" at the Silly Venture party due to compatibility issues with the revision of the multicarts firmware emulating the analog ISAM Tape drive from a concatenated binary ISAM file.
  9. The Atari 8 bit computers have an extra graphics chip, ANTIC, allowing frame synchronization and DLI's. You may find Flashback or SuperCharger BASIC a more familiar environment because it includes a soft ANTIC that can drive the TIA independently allowing you to synchronize your BASIC or Assembly program with the current frame and create display list interrupts that scroll sections of the screen in different directions and modes like the Atari 8 bit computers. Here is a recent example from SillyVenture2020+1.
  10. I think the text displayed on classic CRT Television was a big part of the formula for being mesmerizing and captivating for being new, and due to the more hypnotic qualities of classic Television in comparison to more modern displays. Apple II text or even ZX-80 BW text on a black and white Television precipitated a phenomena where people stared at and disappeared into the glow of the screen, this is now seen with cellphones. Users wanted to believe and step into Narnia, this was the market we designed for. I think the TI-99/4A, VIC-20 and the TRS-80 Color Computer had an edge early on through their larger text display that made the text Adventures friendlier and the interactive fiction easier to read. Great point, as parsers got more sophisticated like Eliza to translate full length sentences, it was important to keep the parser backward compatible with verb and a noun combinations for adventurers who had learned to navigate via the earlier adventure interface. Interesting Today that these were text games with a "Shell" for users to program them; relics from a bygone era when computers were for users to program with instead of e-shop.
  11. Interesting thread; this article sheds some insight on the initial punch card pilot where BASIC used punch cards just like the full FORTRAN implementations did initially: An Interactive BASIC with a Punch-Card Mentality – Troy Press If we separate the issue with the punch cards, BASIC is Tiny FORTRAN getting repeatedly streamlined with successive iterations for the early home micro computers. Of the two contemporary Tiny FORTRAN implementations Microsoft's BASIC is a fuller implementation than Atari BASIC, however Atari BASIC is better suited to graphic design.
  12. Mr SQL

    Movie Cart

    The video quality is fantastic! Would it be possible to create an AtariVCR Cart with the encoder and port for a usb cam to film movies right on the Atari or view video in real time? That would be very interesting for games and utilities. It could enable video conferencing capabilities for PlusCart for example, where text conferencing has already been implemented.
  13. Agree 100% therefore be careful about updating dasm, there's been a shift in perspective with the new release starting to turn some warnings into show stopping fatal errors that stop the binary from compiling, understanding it would break existing code (possibly your code). I think design considerations should cater to the programmer being informed while knowing it's not a problem like you stated. @Andrew Davie recently espoused treating every single warning as an error in an academic exercise for PlusCart development after expressing similar design sentiments and then having an epiphany to escalate the warnings to errors. There are clearly some different schools of thought on the subject, I abstracted the three tiny BASIC error types from DASM compilation with What handled as a non-fatal warning designing SuperCharger BASIC: How - syntax error code cannot compile What - ignored as warning/non-fatal error Out of memory - code cannot compile Here's an example of these errors from my SillyVenture 2020+1 KC OS demo compilation that exhibits a real error under PlusCart and UnoCart but works fine on the real hardware; the fatal error is happening only on the platform where developer design philosophy has shifted to treat warnings as errors; perhaps it's best to leave warnings as warnings but know about them to keep the focus on real errors?
  14. Great video! I like that the FPGA console has an AUDIO in for loading from cassette tape. Does this allow the Atari 2600 FPGA core to load SuperCharger tapes like the Gopher emu?
×
×
  • Create New...