Jump to content

baktra

Members
  • Content Count

    753
  • Joined

  • Last visited

Community Reputation

637 Excellent

About baktra

  • Rank
    Dragonstomper

Contact / Social Media

Profile Information

  • Gender
    Male
  • Location
    Prague, Czech republic

Recent Profile Visitors

13,696 profile views
  1. The mini-dos was included to actually operate cassette. You could save or load your TBXL program in the Turbo 2000 file format using the DOS. It also installed a T: device, loading and saving from tape using the Turbo 2000 system. At the time, it was quite useful for tape-only users (600 bps vs 2270 bps). Now, it is obsolete, of course.
  2. No there is not. There is a work-in-progress cross-compiler https://github.com/mgr-inz-rafal/tubac. The project appears to be on hold for two years. Or you can switch to FastBASIC that you probably already know. That would be my choice if I start any project from scratch.
  3. The latest commit to the master branch brings few enhancements and fixes Limited support for wildcarding. This way, one can dump multiple files in one directory. Consult the readme.md to see how to use it and engage common sense. The options (including file system choice) are shared for all wildcarded disk images. Dump header The dump begins with dump header. The header displays the disk image name and options specified Directory listing (DOS2, DOSIIP) The directory listing didn't display all human readable characters for inverse-video file names. Summary reports Summary reports are displayed at the very end of the output and not after each ATR disk image processed. This is useful when wildcarding. Boot sectors of 256 bytes You can specify the BOOT256 option to assume that the first three sectors are stored as half full 256-byte sectors. Use for disk images with this "anomaly" Architecture Internally, the command-line "front-end" was separated from the dumping "back-end". Not that I intend to create a GUI or something similar.
  4. I believe it was: java -jar atr1prnt.jar file.atr FS-DOSIIP NOSECTORS
  5. The epoxy fill increases the power supply's tendecy to overheat. At least the electric parts are under bigger strain. And the parts cannot be inspected. All original power supplies are today beyond their expected lifetime, so a failure is something expected. I don't know if to keep it, but I would not use it. At least I would check the output voltage regularly, or get some external overvoltage protection. If the PSU blows, then it blows, but shouldn't take the computer with it.
  6. Originally for internal use, I have created a command-line tool that dumps ATR disk images and also dumps and checks the file system inside. It is heavily inspired by the look and feel of the DSN1PRNT utility for the Db2 database from IBM and provides similar output. The tool is available at: https://github.com/baktragh/atr1prnt The supported file systems are: Atari DOS 2 (all densities), and DOS II+ (from S. Dorndorf). Other file systems (MyDOS, SpartaDOS) might come later. The tool requires Java 8 or newer to run. The atr1prnt.jar with executable code is located in the dist/ directory of the repository. That's all you need to download. Why I wrote the tool? Few reasons... I wanted to learn everything about the DOS 2 and DOS II+ file systems. I needed a tool that tells me if an .ATR file is OK. I need textual output for "forensic" analysis using tools that compare plain text (e.g. diff). I need to see the inside of a file system in a compact form. A sample output is attached. DUMP.TXT
  7. I don't think so. The CTB files hold compiled machine code, so the information needed to get the source code back is lost.
  8. I would put one extra variable to the equation. Shipping the final product to the "customers". How easy is to do it. I don't have experience with all of BASICs mentioned above. dmsc's FastBASIC has cross-compilation, you can ship .xex or .atr. TBXL has AUTORUN capability, you can ship auto-booting .atr. TBXL source code is available, so you can adjust the startup experience. TBXL has a compiler too, however it doesn't compile every program. My favorite would be dmsc's FastBASIC and its cross-compilation capability. It has potential for growth, is actively developed, and you can develop with all niceties provided by PC or Mac. It is using CC65/CA65 behind the scenes, so you might want to take a look at those too.
  9. Time to load the latest version of the game from tape is approximately 11 minutes 🙂
  10. That sounds like the most reasonable advice. If possible, do not flood the limited SIO addressing/command space if not absolutely necessary.
  11. I have re-freshed the attachment. You might need to download "Visual C++ redistributable" from Microsoft.
  12. Well, I am attaching a binary for Windows (.NET). atrcompiler.exe unpack atr_file atrcompiler_pre_r.zip
  13. Other "devices" using those interrupts are data recorders upgraded with RAMBIT TURBO TAPE (INTERRUPT) or TURBO 6000 (PROCEED). But these are very rare. And example of such interrupt handler: https://github.com/baktragh/turgen_tape_loaders/blob/master/gb_rambit/modern/rambit_mono_modern.asm
  14. Another possibility is to use AtrCompiler. This works from batch. You have to compile it yourself. The project doesn't provide any binaries yet.
  15. I am afraid you don't. To extract files from .atr, you need a different tool. You can try ATR Tools, for example.
×
×
  • Create New...