Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

551 Excellent

About baktra

  • Rank

Contact / Social Media

Profile Information

  • Gender
  • Location
    Czech republic

Recent Profile Visitors

13,163 profile views
  1. Ta make the long story short, the ChainLoader2, BlockLoader, nanoTBL and nanoBTAPE binary loaders shipped with Turgen System are carefully designed to load 95 % of the games shipped as .xex files, so use the "BlockLoading" and "ChainLoading" conversions without much fear that it will not work. In very most cases, it will work. Of course, some files are not loadable. Do not try the Stunt Car Racer, for example. This way - Enabled (command control), one can set up Altirra 3.20 to test wave files with the following systems: Turbo 2000 (CZ/SK), Super Turbo (CZ/SK), B-TAPE, TURBO TAPE, KSO Turbo 2000 (variant with input from SIO port only!), Atari Super Turbo and compatible systems (ATT and Unerring Master), Hard Turbo, Lower Silesian Turbo 2000, Turbo ROM Plus. Is this list complete?? b Other settings are for more "exotic" systems. The Enabled (proceed sense) is for the Turbo 6000, and Enabled (Interrupt sense) is for the Rambit Turbo Tape. Always ON is self-explanatory and suitable for Turbo Blizzard, until Phaeron includes the "Enabled (Data OUT sense)" option.
  2. It is good to hear this. Any information on this almost forgotten system would be great. So far, I solved the Turbo 6000 support with "brutality and ignorance" so typical for the development of TS. The "Compatible binary file" conversion is based on my crude understanding of the file format used by the Chaos Loader (but it works), and the "Binary file" conversion is just my own file format paired with the very same loader that I just violated to do what I wanted (load almost any binary load file). At least my crimes against Turbo 6000 are documented in the GitHub repository mentioned above and someone can refine my findings.
  3. I have decided to do a favor to the German users. The Turbo 6000 will be included in the Wizard for Binary Files. Still the limitations for the original Turbo 6000 file format and the Chaos loader are bit elusive. The disassembly is available in the github repository. If someone really has nothing better to do...
  4. Of course not. For every binary loader, you will find a bunch of .xex files that the loader will not load. The point is, every binary loader must reside in the computer's memory at certain addresses. The "Blockloader" resides at 0x0800 - 0x0A2E. These are the least-likely addresses to be used by binary load files. If the binary load file occupies or uses the same addresses as the loader, then the loader is destroyed during the loading and the loading fails (typically, the computer hangs). So, what you can do to save your time? Use the "Check Loader" button. If it will not tell you that the loader will be destroyed for sure, the probability of successful load is high. Use the Altirra emulator to check your WAVE files. Set it up for turbo tapes, and use F1 for warp speed. If it loads, then it loads with the real computer in 99.9 % of cases. This is also applicable for binary loaders used in SDrive, SIO2SD, and Universal cartridges (UnoCart etc). These loaders are very tiny and keep their profile low, yet there are .xex files that will not load anyway. For more information, refer to my (rather long) post at Atari Sector.
  5. Haha. Commando+ is a massive game that requires 256 KB of RAM, so extensive tape loading time is nothing unexpected. The Altirra emulator indicates the wave file works, however. You can shorten the loading time by using the Super Turbo plugin and transfer speed around 3500 bps, if your data recorder can handle it.
  6. You would have to update the rest of the BASIC code and possibly machine code to tolerate/process the data you have inserted. That doesn't seem to be an easy task.
  7. Now you can try the beta version. Few things polished, including documentation. turgen_system-8.6.13beta-bin.tar.bz2
  8. I am just few more commits before releasing Turgen System 8.6.13, a new version of a tool for authoring Atari cassettes. Since I am creating a post at AtariAge, it can only mean one thing. There are enhancements in the Standard plugin that generates the standard tape records. The version's code name is Flash of the Neglected. In this case, the neglected refers to the standard tape records that were added to TS way too late. So what you can expect? The TSCBL binary loader is used instead of the old and rugged STDBLOAD 2a. With TSCBL, you have this: The loader displays program title (up to 34 characters) Customizable background color Customizable text luminance (allows for more reasonable foreground/background combinations for displaying the program title). This is new. The loader can hide the cursor. This is new. The loader can set silent I/O The loader allows cold start when you press SELECT+RESET. This is new. The user interface of the Standard plugin was polished and allows two extra functions You can enter hexadecimal ATASCII codes in the program title field. This way, the loader can display characters not accessible on PC keyboard. You can enter $HEX$ 20 FC 10 45, for example. You can convert the binary file, but omit the loader. This is useful when you intend to use your own loader, but you still need to elongate IRGs after blocks that hold INIT vectors. There are also other, general changes Minimum duration of the leader tone is now 14 seconds, a safer value The default signal amplitude was reduced to 75 % for both WAVE files and direct audio output. This value reduces the risk of clipping in the recording chain. Behold the new face of the Standard plugin
  9. There is the Tape Image Extractor function in Turgen System. Allows to extract a .XEX file from a .CAS file. The catch is that it works semi-automatically only on .CAS files that contain a binary loader followed by a .XEX file. In any other case, manual setting of the extraction is needed. Theoretically, it would be possible to write an extractor that would recognize the most common systems for storing .xex files to tape and perform automatic extraction. However, xrbrevin is going to use a disk to tape copier with his data recorder, so this is not that relevant.
  10. The key is to shift gears as described here.
  11. 1. Starquake. Never got the courage to play it. 2. Alchemia. Boring, but I love the overall look and feel of the game. 3. Shamus. Playing that is total madness.
  12. Then we keep fingers for you. Please share with us your solution if you can.
  13. Hello, It depends which way you would like to create the real tape. If it is with PC and an ordinary cassette recorder, then you can read about Turgen System or a8cas. Both programs work similar way. You give them a .cas file, and they will give you a .wav file. Then you connect your ordinary cassette recorder to your PC with a cable, play the .wav file through a media player for PC while recording it with the ordinary cassette recorder. So it is then just matter of cassette recording skills. Success depends on equipment you have on hand. Good tape decks work like a charm, cheaper consumer electronics need some convincing or fine tuning of the process. If you want to use just Atari and data recorder, I don't know of any software for Atari that would record a tape directly from a .CAS file. I considered writing a step-by-step guide several times in the past, but users of tapes are a rare species now, so I always dismissed the idea. Perhaps it is time I reconsidered again and gave it a try. Just take into account that recording tapes is a tedious job and loading times are just terrible. Atari engineers decided that the standard transfer speed will be 600 bps. Not so bad for 1979, too bad for later years.
  14. It is possible. There has been software for copying .xex files from disk to cassettes. One of the oldest examples is the Nudmehi Software Boot Cassette Maker (requires Atari 400/800, but there is a version patched for XL/XE machines around). When it comes to modern ones, there is for example the SITRE system. Both programs will load .xex file from disk to memory and then write it to the cassette together with a small binary file loader. http://atarionline.pl/v01/index.php?ct=utils&sub=5. Magnetofon&tg=Boot Cassette Maker#Boot Cassette Maker http://www.vitoco.cl/atari/sitre/index.html Software for copying files from one cassette to another cassette, e.g. CASDUP. This is exploitable, because SIO2PC can be used for (limited) cassette emulation. Another possibility is the "studio way", generating signal on PC and recording it to tape using ordinary cassette recorder or tape deck.
  15. C compilers in general perceive inline assembler as an obstacle for optimization, that's no way to go. You can give the opt65.c a try, there is nothing to lose. It is very dated, though.
  • Create New...