Jump to content

trub

Members
  • Content Count

    171
  • Joined

  • Last visited

Everything posted by trub

  1. Currently, after replacing the battery, the driver should be forced to load with the /F option (SIDE3CLK.SYS /F). Then the time can be set with DATE and TIME commands. This will be corrected in the next edition of SDX (along with other fixes).
  2. @tschak909I am aware of this SIO command and already tried it However, for now I want to keep the TTR generic. Perhaps I will add a command line switch invoking CP/M for FujiNet/ATR8000. @DrVenkman By holding the keys (e.g. Ctrl+Shift =, apparently on the real hw) you may cycle thorough different colors. For example, one may get an amber-like dumb terminal feeling I had some problems with configuring the WS 4.0 supplied in the Big RunCPM ZIP. So I downloaded another copy and then it was able to configure it for ADM-31. There were no problems with WS 3 tough.
  3. I was asked for it, and here it is TTR 0.1 for R1: (aka Trub Terminal R) is ready for testing at trub.atari8.info/cpm/TTR.ZIP It is in fact a converted TT with the Indus CP/M routines removed and using CIO (via RS232 R1: driver) instead of the Indus-specific protocol. Remarks: - requires S_VBXE.SYS (or RC_GR8.SYS) for 80-column display - Lear Sieger ADM-31 terminal emulation (as in Commodore 128, Kaypro and other CP/M systems) - 9600bps communication speed (currently fixed) - can also be used with Atari 850 (presumably PR: connection too) to communicate with other devices (apart from FujiNET) Usage: 1. Connect the device (FujiNET, Atari 850) to the SIO port (preferably disconnect the others). 2. Install the R1: device driver (preferably RS232.COM for SpartaDOS X). 3. Launch TTR. 4. (FujiNET) Write ATCPM <Return> to run the built-in CP/M. 5. (FujiNET) Execute EXIT command to shut down CP/M before closing the terminal. 6. Full-screen software e.g. WordStart, Turbo Pascal, etc. should be configured for ADM-31 (or ADM-3A) terminal to get full benefit from the terminal. 7. Back to DOS: Ctrl + Shift Q 8. (VBXE) Adjust font colors (Ctrl + Shift -,=) and background (Ctrl + Shift 9,0), e.g. you may have pink fonts like in C128 CP/M 9. (VBXE) Save color settings in the configuration file with Ctrl + Shift S Let me know in case of problems.
  4. Once I prepared a terminal prototype for XEP. However, I had to abandon it, because the speed of displaying characters through the joystick port is 15.7 KBit, while communication with CP/M-enabled drive is 19.2 KBbit. This causes characters to be lost. So the Indus CP/M performance should be slowed down to work properly with XEP. I don't think it's worth the effort.
  5. Just mount this as D1: and boot. SDX flasher starts automatically.
  6. Thanks for the info. I will update the clock driver accordingly. However, it seems that the clock chip can also be initialized currently by forcing the driver to load (SIDE3CLK.SYS /F) and then setting TIME & DATE. @KPeterI am unable to reply to your email, because either mine or your email account is blocked by the server. However it seems that your problem with finding the link is solved by helpful @Frankie.
  7. For all interested, the updated alpha version of SDX 4.49e (dated December 2, 2020) is available at the link in the post above.
  8. I can only confirm this 😒 Currently both windows A and B are set regardless of the type of the cart.
  9. First, I assume that you have read the "Using BASIC XE Extensions" section in the SpartaDOS X manual. Second, we are investigating this problem, but it may be related to Basic XE's incorrect handling of NMI interrupts, which may result in the incorrect operation of VBLK and DLI interrupts when using extension routines.
  10. We do not normally do this, but here is a SDX 4.49e (alpha) development version for SIDE3 available for download. We usually release versions after good testing, even beta versions. So, you use this version at your own risk, and since it contains work-in-progress code, some things may not work. And it is not just about SIDE3 support. Therefore, the official version 4.49e will not be available on our website until this work is completed. Please also note that we develop SDX in our spare time as a non-profit hobby.
  11. TD is the same (from 2016). Please provide the image with the newer date for comparison. However the problem is not with the TD, but with the SDX driver for the clock chip in SIDE3. Unfortunately, I don't have a working SIDE3 at the moment to update it. Also, the SDX version 4.49e placed by the manufacturer in SIDE3 should be considered an alpha version.
  12. Although not shown in the linked photos, mono is also very much involved in the project :)
  13. Sure it can be done. However, I think it would be better to patch DPB for drive C (it now set for 90k disk in the second drive, so of questionable use nowadays).
  14. TT simply calls SIOV OS procedure to access the B: drive, so the speed depends on OS. You get high speed if OS itself supports this or if the high speed handler is hooked to the OS vector (such as SIO driver in the FJC's Ultimate1MB firmware). However, after reading the data, TT still needs to send it to Indus CP/M via SIO. A double transfer is then needed: drive B: -> TT -> Indus CP / M, which results in poor performance.
  15. This is planned (I say cautiously that for version 4.60 )
  16. I thnik you should use File -> Save Firmware -> Save Ultimate 1MB Flash. Then select the file as the default firmware for Ultimate.
  17. The extended driver INDUSX.SYS is being developed. It will enable track buffering and will have some additional features. We plan to include it in the SDX Tookit with the next release.
  18. trub

    trub

  19. TT uses SIOV to read (write) from D2: when B: is accessed. If you have OS or PBI driver with hi-speed SIO, it is used to get the data. However, TT then transfers the data further to the Indus drive which supports 19200bps by default.
  20. TT supports CP/M drives B: and C:. They are both mapped to Atari D2: drive with 256BPS disk (B:) or 128BPS disk (C:, rarely used). TT works well under SDX, but Indus drive (D1:) should be directly accessible. So, you have to deactivate any hard disk partition mapped to D1: to let the SIO floppy respond. I have also successfully used ATR disk image on IDEPlus as CP/M B: (mapped as D2: with ATRM utility). The speed is still not very impressive, since the protocol requires passing control commands between Indus and TT through SIO.
  21. This version has bugs, you need to upgrade it to 1.20 as they say in the Indus GT Service Manual (pt. 4.14): "If the EPROM in the drive you are working on has a version number of 1.00 or 1.10, then it should be replaced immediately with the latest version of the device. The latest version to date is 1.20."
  22. Which ROM version is displayed by the tool ? Can you hear the bell when the display reaches FF ? Are there any other drives connected ? Note that the drive should be set to D1: (see jumpers at the back).
  23. Here is some information for CP/M newbies. CPMTOOL utility performs two basic actions: 1. Testing the SRAMCharger using different memory configurations. The drive must be operational, since the tests are executed by Z80 CPU at the drive side. In case of an error, its code is displayed ( 1-8 ). See my site for description of the error codes. 2. Restoring the missing parts of sectors 1-3 with the original contents of CP/M code. CP/M double density discs use full capacity of these sectors (unlike Atari discs or ATR files which only hold 128 bytes). So after copying the CP/M disks to e.g. ATRs, upper halves of the sectors 1-3 are lost and must be later restored using this utility. Nezgrar, rdea6, thank you helping me with the links
  24. Note that the physical disks should be then patched with CPMTOOL to restore the missing parts of sectors 1-3.
×
×
  • Create New...