Search the Community
Showing results for tags 'Files'.
Found 4 results
Hello, I just looking for some info about copy files .atr or other files can be copied to real Disk on Indus GT Disk Drive. Is this possible?. If it is possible, how is the process? Comments, suggests i will apreciate. Thanks.
Hi, as some of us maybe already know, Chris Bobbitt from former ASGARD Software is sending around his findings from his very old Asgard Software Archive to us, to get it digitalized and to share it to the community. What a great move !!! Thanks to Chris, again. As I am one of the lucky guys getting some of this stuff here, my very first action was to make DSKs from the floppydisks he sent to me this week. I attach them here as a ZIP, including a small docu and some screentprints from my testings. I also add some pics of the first ship, as an overview for you. Regarding the amount of paper, it will take some time for me to make scans of that, of course. But, if you see anything very interesting here in the pics, just let me know, so I would do an immediate, selected scan for you. More floppydisks are on the way, to be handled quickly to pass through to all 99ers. I think this will be a big event for all of us, diggin´ through all this fine treasures Many many thanks and all tribute to Chris schmitzi
Hey all, Here is a question... so the TI disk system reserves space at the top of VDP memory for file buffers. You can reduce this by from 3 file support to 1 by calling the FILES subprogram, but it still takes up space from about >3B00 onwards. My question is... can you safely wipe out this section, say if you wanted to put the sprite pattern table at >3800 onwards? Obviously it would trash the sprite pattern table if you had to do a file load later on, but if you could restore the data from CPU memory afterwards it seems alright. Obviously it would be stupid to try and do a memory image load INTO this section...
Here is something I have worked on the weeking. It's some testfiles for un-crunching BASIC programs. The txt files are the LIST output of those programs, so they are matching exactly the way the BASIC INTERPRETER does the uncrunching of each basic line of the program. (Classic99 was used with LIST "CLIP" to generate those txt files) If you compare that to the available tools (TI99DIR, imagetool,...) you will see that all have some issues in recreating that same syntax. Example: Output from TI99dir of Line 4 of XBCMD1 4 ACCEPTVALIDATE("YN"):R$ Output from TiImageTool of Line 4 of XBCMD1 4 ACCEPT VALIDATE ("YN"):R$ while if you LIST the program in the TI99 you will see: 4 ACCEPT VALIDATE("YN"):R$ XBCMD1 contains examples for XB commands from A-P XBCDM2 contains examples for XB commands from P-Z XBCMD3 contains quote examples XBCMD4 contains all characters within strings from 0 to 255. Here the txt File fails for line 100 because it interprets some control character. The examples for XB commands are mostly taken from the XB Manual and are only extended by me if insufficient. I will create some more testfiles and add them as Unit Tests to Web99, so in case i touch the code, I immediately see if I broke some behavior. Feel free to do the same for your projects or use the files to manually test your tool during development. Btw: The programs can be loaded, but running them makes no sense, their purpose is to find out if your Tool decodes a TiFile into the Basic Source Code the same way the Basic Interpreter does. Please provide feedback if you want to use it, so I can provide you with updates. unittest.dsk XBCMD1.txt XBCMD2.txt XBCMD3.txt XBCMD4.txt