Jump to content

trub

Members
  • Content Count

    170
  • Joined

  • Last visited

Community Reputation

83 Excellent

About trub

  • Rank
    Chopper Commander

Contact / Social Media

Profile Information

  • Gender
    Male
  • Location
    Poland

Recent Profile Visitors

8,258 profile views
  1. @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.
  2. 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.
  3. 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.
  4. Just mount this as D1: and boot. SDX flasher starts automatically.
  5. 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.
  6. For all interested, the updated alpha version of SDX 4.49e (dated December 2, 2020) is available at the link in the post above.
  7. I can only confirm this 😒 Currently both windows A and B are set regardless of the type of the cart.
  8. 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.
  9. 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.
  10. 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.
  11. Although not shown in the linked photos, mono is also very much involved in the project :)
  12. 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).
  13. 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.
  14. This is planned (I say cautiously that for version 4.60 )
×
×
  • Create New...