Jump to content


+AtariAge Subscriber
  • Content Count

  • Joined

  • Last visited

  • Days Won


acadiel last won the day on February 1

acadiel had the most liked content!

Community Reputation

2,183 Excellent

1 Follower

About acadiel

  • Rank
    River Patroller

Contact / Social Media

Profile Information

  • Custom Status
  • Gender
  • Location
  • Interests
    TI-99/4A Hardware hacking

Recent Profile Visitors

19,786 profile views
  1. Gotta love Fred. I wrote the operational spec and he had it developed out within two weeks. He’s pretty amazing! The sidecar DSR that allows you to use the cart space as a file system will have space left in it (banks a plenty) - so if we want to use any other space in there as “standalone DSRs”, we sure can in the future. So, plenty of opportunity for expansion!
  2. Starting the TI-88 ALEX (ALgorithm EXercise) binder. Here's the first two sections. 1981-CH1-TI88-ALEX-Outline.pdf 1981-CH0-TI88-ALEX.pdf
  3. ROMDisk is meant for more than just TI BASIC. It's meant to work as a device DSR (by adding a simple DSR ROM) for anything that needs to address a static set of files on a "disk". It could be anything from TOD files for TOD, Adventure files for Adventure, E/A editor and assembler (even though this is duplicating functionality of Tursi's E/A complete), an executable on cartridge that needs to talk to data files, you name it. Literally, you can use up to 2MB of cartridge ROM for a "disk drive" for things that don't change. This could make more accessible data files for programs for less experience programmers, for example, who want to program something large. From Fred: Hi all, Just a quick message about the progress I have made with the RomDsk DSR. See also the enclosed pictures. The DSR is now operational, it maybe need some fine tuning but that depends on the further plans and ideas. The size if the DSR is now 4Kb ROOT @ >4000-4FFF (>90C2 bytes) and 4 Banks @ >5000-5FFF of which 1 bank is empty (Bank 0 basic calls size >0B26 bytes, Bank 1 init and character definition size >0644 Bytes, Bank 2 is empty is 2 Bytes, Bank 3 is file functions >0C1A Bytes). Level 3 functions implemented: open, close, read, rewind, status, load. Level 2 functions implemented: read sector, read direct file information. Device names implemented: DSK1, DSK2, DSK3, DSK The standard TI file handling can be uses, i.e. DSK1.FILENAME, but also by using the volume name of a disk image, i.e. DSK.VOLUMENAME.FILENAME (b.t.w. this is not an option DM2K can use because .VOLUMENAME is a sub directory name for DM2K) Used some basic functions from another DSR (TiBus) I'm currently working on and because this is a RomDsk DSR the prefix is ROM (this als prevents all kind of confusions on my test system): CALL ROMDSK - shows the status of the found DSK images CALL ROMDIR - shows the contents of a DSK image CALL ROMEXE - load and executes a E/A option 5 program CALL ROMPWD - print working directory After power up for the very first time the working directory is DSK1. after that the working directory is whatever device name was used for the last time. The CALL ROMDIR and ROMEXE can use the following (meybe not much use for this because there is not really a directory structure): CALL ROMDIR("DSK1") CALL ROMDIR(".") CALL ROMDIR CALL ROMEXE("DSK1.FILENAME") CALL ROMEXE(".FILENAME") . is this directory + the file name: .FILENAME .. is previous directory + the file name: ..FILENAME ... is current device name + the file name: ...FILENAME In this case the . .. and ... all results in the same because there is no directory structure. To Prevent empty gaps between DSK images I have added an offset (in number of 256 byte sectors) at the rom table. This is because an DSSD disk (720 sectors) ends at a 4Kb boundary. If a second DSK image is added to the ROM module then it is not needed to add 4Kb of unused space to let the second image begin at the start of a bank. Because the DSR is calculating the Bank# and offsets it is only nescesarry to define the Bank# of the first DSK image. The Bank# and offset of the second and third DSK image can then be calculated by using the Bank#, offset and disk size of the previous DSK image. This prevents a lot of headaches ;-) DR#IDT EQU >A55A DiskROM identity DR#END EQU 0 Data type end of table DR#DSK EQU 1 Data type is DSK image DR#BIN EQU 2 Data type is binary data DR#TBL EQU >7F00 Address of DiskROM table DR#FDT EQU 22 Offset first data type DR#TYP EQU 0 Offset data type DR#BNK EQU 2 Offset bank number DR#DOF EQU 4 Offset in bytes of the data in this bank DR#SZE EQU 6 Offset data size in bytes (2B( DR#LEN EQU 10 Length of this record * For the fist disk images the bank number must be defined and the image * starts at the beginning of a bank; data offset is >0000 sectors. * * For the seconds and third disk image the bank number and data offset * kan be calculated by the RomDisk DSR. In this case the bank number * must be defined as >0000. * * The offset of the data in a bank of a disk image is in multiples of * 256 bytes (whole sectors). For other types of data the offset in a * bank is in the range of 0 to 8191 bytes. * *----- HEADER -----* DR$TBL DATA DR#IDT DiskRom table identification (2B) DR$TTL TEXT 'DiskROM' Title (16B) BYTE 0,0,0,0,0,0,0,0,0 DR$VRS TEXT '1.00' Version (4B) *----- DSK 1 -----* DR$TYP DATA DR#DSK Data type (2B) DR$BNK DATA >0001 Data bank number (2B) DR$DOF DATA >0000 Data offset (2B) DR$SZE DATA >0000 Size in bytes (4B) binary data, Not needed for DSK img. DATA >0000 *----- DSK 2 -----* DATA DR#DSK Data type (2B) * DATA >0017 Data bank number (2B) (disk size DSK1: 720 sectors/32 sectors per 8Kb =22.5 banks == >16+Bank# DSK1 = >17) * DATA >0010 Data offset (2B) (0.5 bank is 4Kb is 16 sectors [16 * 256 = 4096 bytes = 4Kb]) DATA >0000 Data bank number (2B) must be calculated DATA >0000 Data offset (2B) must be calculated DATA >0000 Size in bytes (4B) binary data, Not needed for DSK img. DATA >0000 *----- DSK 3 -----* DATA DR#DSK Data type (2B) DATA >0000 Data bank number (2B) must be calculated DATA >0000 Data offset (2B) must be calculated DATA >0000 Size in bytes (4B) binary data, Not needed for DSK img. DATA >0000 *----- END -----* DATA DR#END Data type (2B) *---------------* For now the device names are fixed DSK1, DSK2 and DSK3. If this need to be variable (more DSKx names) then I suggest that we add this to the above table. This can be some index number (1, 2, 3 .. n) or an ASCII character so that DSKA and DSKR is also possible or the complete device name (max is 7 characters per TI specification).
  4. @Fred Kaal and I have developed something almost exactly like this. (Except this is a read only file system for cartridge ROMs.). The DSR is operational and has been prototyped on one of Fred’s existing boards. @ksarul just needs to develop the final hardware. It’s called the ROMDisk. :-) Dunno if Fred is here and wants to speak up on it, but he’s done an amazing job. We just need to get the sidecar hardware out for the simple pass thru DSR ROM for it. And the utility support program to build the rom images. Why? Because you can run any combination of assembly from the ROM and have support files (BASIC programs or data files) located on the same ROM. How many programs have “support files” like Adventure? The little DSR “dongle” so to speak is a stripped down IDE DSR and will be pass thru. Very minimal.
  5. I just got an email from Joerg Warner over at Datamath.org - "OMG GOLDMINE". This reference with all these part numbers (and designers), once consolidated, is going to be pretty awesome.
  6. Fourth part of the Art Hunter binder. This is the last set of "loose" parts that aren't part of the TI-88 content. This appears to be some kind of checklist (70 pages worth) for TI Calculator chips. Enough for tonight 🙂 1970s-TI_Calculator_Chip_checklists.pdf
  7. Third part of the Art Hunter binder. Here's a bug report for the TI-55 Calculator in 1978. 1978_TMC-1503D-TI-55-Algorithm_Checkout_Bugs.pdf
  8. Here is the second part of the Art Hunter binder. A late 1970's database of ROM numbers for Mainframe (Home Computer) and Calculator ROMs/GROMs/CROMs. 1970s-TI-Calculator_Div_Chip_Number_List_Art_Hunter.pdf
  9. This is the first part of the Art Hunter ("TI-88 Alex binder"). Almost 80 pages of GPD/Chip designations and release dates, including some interesting ones for the Home Computer (referring to Pre-School, which was Early Learning Fun before they renamed it). There is also reference to TMC 1985 (Handheld Unit Transmitter), which is the only place I've seen that part SKU in print so far. 1970s-TI-Chip_GPD_Releases_Art_Hunter.pdf
  10. Someone paid a lot for this.... hopefully someone here?
  11. I think it rather interesting. Did they put the cassette lines on the port in this model?
  12. Directly from Steven Reid: "The problem ended up being documentation on one of the bits in IOCNTL being inverted. One bit controlled SLEEP vs HALT when IDLE was executed. It was documented wrong. Change 1 bit and the Wafer tape would have been fine... but discovery made it too late to save it from the axe. Sad. :("
  13. The interesting part is that those four papers were grouped together. That’s why I scanned them as such. :)
  14. The folder I'm in is almost an inch thick... mostly with timing diagrams where they extensively (and I do mean extensively) tested the Wafertape drive to fix a defect. The TL;DR of why the WaferTape wasn't released? The CPU had a bug in it and didn't work with the IDLE instruction. I've attached the relevant memo/assembly below that speaks to that fact. Edit: By the time this bug was identified, TI pulled out of the Home Computer market, and canned whatever work was remaining on the CC-40 and peripherals. From discussions with engineers around this time, the TI-74 reclaimed a lot of this work in 1984 and beyond and was launched within the Calculator division. 1983-Waftertape-failure-root-cause.pdf
  15. No idea what these are, but this is the second part of the mylars and hand drawn routing. This is the last part of the CC-40 documentation. I do have one HUGE blueprint, which even my scanner isn't large enough to scan. Will need to see if I can locate a poster sized scanner somewhere. Up next: Wafertape! Unknown- Mylars and Schematics.pdf
  • Create New...