Jump to content

Search the Community

Showing results for tags 'ramdisk'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Atari Systems
    • Atari 2600
    • Atari 5200
    • Atari 7800
    • Atari Lynx
    • Atari Jaguar
    • Dedicated Systems
    • Atari 8-Bit Computers
    • Atari ST/TT/Falcon Computers
  • Gaming General
  • Marketplace
  • Community
  • Game Programming
  • Site
  • Classic Gaming News
  • The Club of Clubs's Discussion
  • I Hate Sauron's Topics
  • 1088 XEL/XLD Owners and Builders's Topics
  • Atari BBS Gurus's Community Chat
  • Atari BBS Gurus's BBS Callers
  • Atari BBS Gurus's BBS SysOps
  • Atari BBS Gurus's Resources
  • Atari Lynx Programmer Club's CC65
  • Atari Lynx Programmer Club's ASM
  • Atari Lynx Programmer Club's Lynx Programming
  • Atari Lynx Programmer Club's Music/Sound
  • Atari Lynx Programmer Club's Graphics
  • The Official AtariAge Shitpost Club's Shitty meme repository
  • The Official AtariAge Shitpost Club's Read this before you enter too deep
  • Arcade Gaming's Discussion
  • Tesla's Vehicles
  • Tesla's Solar
  • Tesla's PowerWall
  • Tesla's General
  • Harmony/Melody's CDFJ
  • Harmony/Melody's DPC+
  • Harmony/Melody's BUS
  • Harmony/Melody's General
  • ZeroPage Homebrew's Discussion
  • Furry Club's Chat/RP
  • PSPMinis.com's General PSP Minis Discussion and Questions
  • PSPMinis.com's Reviews
  • Atari Lynx 30th Birthday's 30th Birthday Programming Competition Games
  • 3D Printing Club's Chat
  • Drivers' Club's Members' Vehicles
  • Drivers' Club's Drives & Events
  • Drivers' Club's Wrenching
  • Drivers' Club's Found in the Wild
  • Drivers' Club's General Discussion
  • Dirtarians's General Discussion
  • Dirtarians's Members' Rigs
  • Dirtarians's Trail Runs & Reports
  • Dirtarians's Wrenching
  • The Green Herb's Discussions
  • Robin Gravel's new blog's My blog
  • Atari Video Club's Harmony Games
  • Atari Video Club's The Atari Gamer
  • Atari Video Club's Video Game Summit
  • Atari Video Club's Discsuuions
  • Star Wars - The Original Trilogy's Star Wars Talk
  • DMGD Club's Incoming!
  • DASM's General
  • AtariVox's Topics
  • Gran Turismo's Gran Turismo
  • Gran Turismo's Misc.
  • Gran Turismo's Announcements
  • The Food Club's Food
  • The Food Club's Drinks
  • The Food Club's Read me first!
  • The (Not So) Official Arcade Archives Club's Rules (READ FIRST)
  • The (Not So) Official Arcade Archives Club's Feedback
  • The (Not So) Official Arcade Archives Club's Rumor Mill
  • The (Not So) Official Arcade Archives Club's Coming Soon
  • The (Not So) Official Arcade Archives Club's General Talk
  • The (Not So) Official Arcade Archives Club's High Score Arena
  • Adelaide South Australia Atari Chat's General Chat & Welcome
  • Adelaide South Australia Atari Chat's Meets
  • Adelaide South Australia Atari Chat's Trades & Swaps
  • KC-ACE Reboot's KC-ACE Reboot Forum
  • The Official Lost Gaming Club's Lost Gaming
  • The Official Lost Gaming Club's Undumped Games
  • The Official Lost Gaming Club's Tip Of My Tounge
  • The Official Lost Gaming Club's Lost Gaming Vault
  • The Official Lost Gaming Club's Club Info
  • GIMP Users's Discussion


There are no results to display.

There are no results to display.


  • AtariAge Calendar
  • The Club of Clubs's Events
  • Atari BBS Gurus's Calendar
  • ZeroPage Homebrew's Schedule

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start










Custom Status



Currently Playing

Playing Next

Found 5 results

  1. Horizon Ramdisk User Manual HORIZON RAMDISK USER OPERATING MANUAL 5-3-2020.pdf ROS (Ramdisk Operating System) and ConFiG, for Horizon Ramdisk (scroll DOWN for most recent version) CFG8 ROS v838.dsk - stable release - ROS v8.38 - bugfixes, 3200 sector OS support, ubergrom cartridge compatibility, VDP bugfixes - CFG v8.38 - adds additional device recognition support and supports 3200 sector drives, CRC error checking ROS841.zip - testing/beta 1/12/2020 - ROS 8.41 fixes to allocation routine (appending files) ROS CFG 842-TEST.zip Test. See post 256 and prior for additional details. 1/25.2020 - ROS 8.42a and CFG 8.42. - ROS 8.42a - all known allocation fixes implemented. Powerup changes. VDP-based boot tracking removed. - CFG 8.42 - Changed load address. Safety confirmation before deleting/formatting a drive. TIPI device detection (8.38a). Forced size to 8192 bytes to overcome TI Disk Controller load opcode bug. ROSCFG842c.zip - 16 Feb 2020 Latest changes include the new format/delete warnings, CRC message indicators, character set/font fix, and RAMBO pagemap corrections. When you update ROS, saving the drive info will also save the CALLs, color, and powerup status. Earlier ROS 8.42x versions can co-exist with 8.42c though I do not recommend mixing and matching. Retain your original files for v8.38 and v8.42 in case you need to revert to a prior test release. CFG is -two- files (CFG1, CFG2). ROS842 does not contain an embedded CRC as I will only place that into the release version. I have attached the 40 column MENU 7.39 as modified by OPA; it is now patched to work with ROS842c. Unlike BOOT, this menu must be on the first drive and associated with the first CALL to autostart. You cannot run this from EA5 or any other loader (I may remove this restriction in the future). (Typically, the file is renamed to MENU on your ramdisk) [Atrax Note: MENU WILL run from the second of two RAMdisks provided that you have it turned off on the first HRD and it is called MENU on the second HRD and turned on.] If you have a device in your PEB that CFG will not recognize, let me know and I'll look into adding it to the inspection routine. ROSCFG842C 3-14-2020-fixed.zip 3.14.2020 Distribution files now include programs and source originally found on ROS8.14F distribution disk Embedded CRC validation code has been written into ROS Some minor code cleanup User manual nearly complete Source code cleanup nearly complete Re-uploaded to fix CFG1/CFG2 oversight. ROSCFG842C 3-27-2020.zip Replaced CFG with 3.27.2020 version CFG: Powerup setting now saved and restored properly when re-loading ROS CFG: Removed Myarc floppy controller detection; CorComp w/MG EPROM was incorrectly identified as Myarc Basic Instructions: 1. CFG is loaded via Editor Assembler Option #5 or compatible. It will attempt to detect an RAMdisks (and other devices) in the system then present you with options to configure and/or set up the ram disks. 2. ROS is loaded from within CFG; ROS is /not/ a standalone executable program. 3. ROS 8.32 and higher should NOT be mixed/matched with earlier versions of ROS or CFG. Drive allocation calculations have changed and may cause 'bad things' to happen. 4. The 1990 user manual for ROS/CFG 8.14F is mostly applicable to these versions. A manual update will happen later this year. ROS bugs: 1. Saving a program or copying a file that exceeds available disk space may corrupt the drive and/or next adjacent drive. Offending code identified; solution in process. [RESOLVED 8.42] 2. De-allocation of a severely fractured file may result in wiping the drive. When assembling files via ramdisk, point your Object and List files to different drives. Writing records to two or more files in succession will interleave the file each time an allocation unit (1 or 2 sectors, depending on disk size) is required to increase the file size. TI file architecture only allows for 76 fragments. Research required. [RESOLVED 8.42] 3. RAMBO mode not tested; awaiting 4000B availability. 4. With two RAMdisks in the system, if the first ramdisk has a defined call in user slot 1, and that file doesn't exist on the ramdisk, the system may lock if you try to launch the nonexistent file from BASIC/XB. This is a special use case error that I will look into as time permits. 5. Corcomp (MG EPROM) may show up as Myarc FDC due to same link subprograms. Review for possible fix. 3-18 =========================================== Original Post: Instead of cluttering up another thread here's one for RAMDisk related info. Last night I was experiencing file corruption when saving Extended BASIC files to my Horizon RAMdisk. The filename was getting copied into the file I was saving, trashing code at seemingly random spots. As I was putting together an email to Gazoo, it dawned on me that I had removed my Myarc floppy controller from the system. Without the FDC, the VDP memory pointer at 0x8370 was not modified, because there was no need for any floppy buffers. Well... ROS uses the 0x8370 pointer to determine where to copy its last used filename and corresponding drive number into VDP memory. ( I believe this is primarily for boot tracking purposes but may also be for convenience). Without a floppy controller in the system, we had extra VDP RAM up to 0x3fff available for system use. ROS was dumping the filename directly into VDP where my program was located! The "corruption" is not limited to XB since the ROS routine is executed for all file IO. Had I not been testing file transfers between systems, requiring me to inspect the files for changes, I might have missed out on finding this dependency. Therefore, for anyone out there using a RAMdisk, it is good practice to keep a floppy controller in the system I do not know if the Myarc hard/floppy controller sets VDP similar to the floppy controllers, that is a test for another day.
  2. I'd like to do a little experiment using the TiVi edtor I'm currently working on. What is the largest DIS/VAR 80 file you were able to load and browse on the TI-99/4a? I'm trying to get my hands on some big DIS/VAR 80 files and with "big" I mean that it should be at least > 100 kilobytes. If you have such file and don't mind posting it (as a disk image). I'll try to load it on the TI-99/4a. For further details on the editor see here:
  3. I'm using my HDR ramdisk a lot while developing my TiVi editor. It's a real time saver. It's especially helpful when dealing with large files (which is kinda my primary purpose why I started working on TiVi). Today I read the updated documenation the InsaneMultitasker provided as draft. In there I learned that with ROS it's possible to use data buffers that reside in CPU RAM insead of VDP RAM. That is something I really want to try, because even with a RAMDISK reading a large file (think >100 kilobytes) takes some time. Now my challenge is; How can I easily detect from assembly language if I'm dealing with a "high-speed" disk device compared to a "slow" disk device ("floppy"). With a high-speed device I mean: CF7+, Nanopeb TIPI HDR ... I see differents possible paths here: CRC checksum on DSR space (but won't work with RAMBOS? Self modifiying code, configuration stored here too?) Check on some specific device feature? Actually I think that the CRC checksum logic would work quite well (I already did a test program on that about a year ago), but I'm not sure about HDR. Thinking about it would be cool if there is some unified way to detect device capabilities accross devices. For example a standard where there's a device "capabilities" file that is automatically created when the device is formatted. That file could then be processed from TI-Basic, assembly language or any other language supporting file I/O. Any ideas?
  4. If anyone can use them, the attached ATR has several utility programs I've written. SORTDISK will sort the directory of any ATARI DOS disk (including DOSXL). Since Atari DOS stores the file number in every files data sectors, it will rewrite each file with the new file number. I am working on a new version that does not require data sectors to be rewritten FIXDISK will repair disks of common problems. Opening a file for output and not closing it can cause hidden directory entries that chew up space on your disk. Run this utility on your disks and if there are any errors it will report on them and repair them. If there are lost sectors on your disk it will give them back to you. UNDELETE will undelete a file as long as the data sectors in the file have not been reused by another file. If so, it will tell you that the file cannot be undeleted. RAMXL is very cool (if you are running on an XL machine). When using DOSXL, external commands such as COPY, DUPSK, etc. have to load into memory every time you use them. Rename RAMXL.COM as AUTORUN.SYS. On a DOSXL disk, change the extension of COPY.COM to COPY.MEM. You can rename up to four files (such as DUPDSK.MEM, INIT.MEM). When you reboot your disk, RAMXL will search for file with the MEM extension and store them beneath the OS. Now, to run any external command, prefix it with RUN 2300. For example, to copy a file your would key in RUN 2300 COPY <File A> <File B> Or to run DUPDSK you would key in RUN 2300 DUPDSK Finally, a hidden utility. Atari DOS will only let you store 64 files on a disk, even if it is a double density disk and has lots of room. This ATR was created with a utility I call DOS CD (capacity doubler). It will allow you to store up to 128 files on a DD disk. If you boot from this disk and then create new disks using INIT to rewrite your DOS files, the new disks will also have DOS CD on them. I hope someone finds this stuff useful. Utilities.atr
  5. I'm looking for help identifying contributors to the Horizon ramdisk hardware (not software) for some documentation purposes. Here's what I think I know: Ron Gries did the original HRDs, Bud Mills laid out the HRD2000, HRD3000, HRD3000B, and HRD4000 (?), Ron Walters may have designed the PHOENIX mod (?), Gary Bowser may have designed the RAMBO mod (? and the circuitry that "unhides" the upper 2K of ROS or was that someone else?), John Guion may have designed the 32K expansion mod (?), and I've also seen mention of Dave Romer, John Culow and the 99'er users group? Please correct any/all of this if you know the history and certainly if I'm missing someone.
  • Create New...