Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

73 Excellent

About trub

  • Rank
    Chopper Commander

Contact / Social Media

Profile Information

  • Gender
  • Location

Recent Profile Visitors

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


  15. 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.
  • Create New...