Search the Community
Showing results for tags 'ros'.
Found 2 results
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.
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: