KORG TRINITY & TRITON (KARMA) Synthesizers – HxC COMPATIBILITY STATUS/Observations/Tips & Tricks/Questions & Requests

HxC Floppy emulator support for all others Keyboards/Samplers...
Post Reply
synthfuldwarphus
Posts: 2
Joined: Wed Dec 20, 2023 11:35 pm

KORG TRINITY & TRITON (KARMA) Synthesizers – HxC COMPATIBILITY STATUS/Observations/Tips & Tricks/Questions & Requests

Post by synthfuldwarphus »

KORG TRINITY & TRITON (KARMA) Music Synthesizers – HxC Compatibility Status / Observations / Tips & Tricks / Questions & Requests


INTRODUCTION

1) The Korg Trinity and Triton series (including Karma) synthesizers, despite their use of common MS-DOS format floppy disks, have had multiple compatibility issues on Gotek devices with factory and aftermarket firmware for many years, even after Gotek firmware programmers have attempted to fix the issues. There are multiple threads on many different forums about difficulty and frustration users have had with this, going back a decade or so.

2) Further, the Trinity and Triton seem to have somewhat of an unusual floppy drive hardware protocol. The most basic, inexpensive Goteks with SFRKC30.AT2 board/32KB RAM/Artery AT32F415 MPU and stock, factory Gotek firmware oddly do not even power up when connected to only the Trinity/Triton floppy power cable (although the very same Goteks do power up connected to floppy power only on other synthesizers like Yamaha A4000, Kurzweil K2500, and Ensoniq SQ80).

The Trinity and Triton deliver some power over their 34-pin floppy data cables, but even with both data and power cables attached, this stock Gotek in Triton would only work if the USB flashdrive was inserted before powerup, and even so would stop working if the USB stick was removed and reinserted while power remained.

I know that older, stock STM32 Goteks (factory firmware) basically worked with Tritons (for reading, at least), so maybe it's an Artery issue. (I've previously flashed and mod'ed rotary knobs, OLEDs, and speakers on mulltiple STM Goteks. These are my first A415 Goteks.)
3) After flashing these four A415 7-segment display (“7seg”) Goteks with HxC v5.2.1.2 and no added CFG file, they all powered up with just the floppy power cable on Trinity/Triton. Strange...


COMPATIBILITY SUMMARY

4) Despite all of the above, HxC Gotek A415 drives are currently FULLY compatible with both of these Korg series, using the very convenient HxC v5.2.1.2 Imageless Mode (uses GPT GUID partition scheme on flashdrive); just copy files directly into partitions on PC like with any flashdrive - without disk imagefiles or formats or additional software for image writing or management.

5) The above compatibility includes diskimage changes on the Trinity, and error-free writes onto USB flashdrives on the Triton, both previously problematic areas.

6) Further, on the Triton there is working support in Imageless Mode for reading large “superformatted” (sufo”) “eXtended High Density” (“XHD”) floppy partitions (and some success writing). I used 4.5MB superformatted partitions, more than triple the size of an HD floppy!

7) Operating system updates also work fine. (Trinity must use HxC Indexed Mode with HFE-format Trinity-OS diskimage files, successful on a GPT-partitioned USB flashdrive, and I'd imagine MBR-partitoned would also work).


HXC-GOTEK SETTINGS

8) Regarding jumpers on HxC-Gotek device, I believe I used only S1 (as recommended by HxC-Jeff/jfdn and other firmware due to “autoselect”) and avoided both the JC jumper and the arrays of jumpers claimed necessary by some users.

9) HxC's Non-Gated Mode setting, specifically added to enhance Trinity compatibility, now seems completely superfluous, since disk image changes on Trinity work perfectly without it.

10) Diskimage changes appear to be facilitated by the default HxC automatic eject/delayed-insert feature (“Auto Select”, I suppose). Immediately upon changing diskimages with Gotek buttons, the 7seg flashes “-” (1 dash) signifying diskimage ejected, and after you settle on another diskimage selection for about 5 seconds, it flashes “- - -” (3 dashes) signifying diskimage auto-inserted.

I had to take notice of the dashes and figure out their function on my own since the only passing mention of this Auto Select feature in HxC documentation I could find is at:    Settings    > Hardware and firmware settings > Original 7 Segments Gotek Menu > Menu 5 - Auto select delay,    01-08 : Delay (number of seconds) at https://hxc2001.com/docs/gotek-floppy-e ... e-settings.

(Note, in the HxC docs, the above setting is absent on the “OLED/OSD/LCD Gotek Menu -> ...some of the available parameters” list. So, without possessing an OLED-equipped HxC Gotek myself, I cannot determine whether Auto Select is actually available on an OLED/Rotary mod'ed Gotek in Normal Mode, especially since I believe the rotary pushbutton acts as a manual image eject/insert.)

11) Although HxC defaults to Auto Select Delay “04” (feels like 5-6 seconds), both Trinity and Triton HxC Goteks change disk images perfectly even when set at the quickest “01” delay , so...

12) ***TIP #1:Navigate to Menu 5 - Auto Select Delay on your HxC Gotek and set it to “01”, for much quicker diskimage auto-inserts.

13) There was also confusion in forums regarding Trinity's (annoying) “Medium Changed – [OK]” prompt seemingly appearing randomly. It's actually not random; as designed, the prompt always appears when refreshing the disk directory after a disk change. However, if you refresh BETWEEN diskimages to clear the directory and trigger“<no disk>” (emulating a refresh without any disk inserted), Trinity treats the following diskimage as “new” medium, not a “changed” one, thereby avoiding this prompt. (Triton thankfully doesn't have this “medium changed” prompt.) So...

14) ***TIP #2: To avoid the annoying Trinity Disk Mode “Medium Changed - [OK]“ prompt: A) On the Gotek, select a new diskimage. B) IMMEDIATELY (during the Auto Select delay BEFORE HxC “- - -” AUTO-INSERTS your selected diskimage) tap anywhere on touchscreen    to refresh/clear directory/trigger “<no disk>”. C) WAIT AT LEAST 2 SECONDS (until AFTER your selected diskimage “- - -” auto-inserts) and tap screen anywhere again to refresh. D) Wait a few seconds until the new image's directory appears.


UPDATING TRINITY & TRITON OPERATING SYSTEM ON HXC-GOTEK - BACKGROUND

15) The final compatibility test was updating the OS, which flashes ROM on both Trinity and Triton. I was hesitant to risk test-updating my Trinity and Triton for the sake of this post... er, article, since each synth was already running the respective latest OS, and updating the OS is quite the critical operation, involving some extra uncertainty with Gotek and HxC.

16) First, updating OS can potentially brick the synth; just look at the (subtle) language in Trinity's service manual (yeah, the one that's supposed to facilitate seasoned pros FIXING the things):

“!!!! MOST IMPORTANT !!!!

YOU MUST NOT SHUT YOUR Trinity DOWN WHILE 'WARNING!! Don't touch me' IS DISPLAYED ON THE LCD SCREEN.

IF THE POWER IS KILLED AT THIS TIME, THE SYSTEM WILL NEVER WORK AGAIN.”


17) Second, it was difficult to predict whether HxC would properly emulate the diskimage changes and subsequent auto-reading prompted by the obnoxious drive “knocking” (stepper motor, heads?) behavior unique to the OS update procedures on both Trinity and Triton. If not, and the incompatibility surfaced midway into the OS update... well, see above!

18) Third, and finally, the only forum claims (two, exactly) of “successful” HxC-Gotek Trinity-OS updates online were confusing and contradictory.

One user post says to use HxC Non-Gated Mode, but that the Trinity-OS disks are “not standard” format and needed to be “generated raw” by a VM DOS machine because Img2dsk and DiskImage would not do it! However, in reality, the OS disks are downloaded from Korg's website in standard MS-DOS format and write just fine to real floppies using a common external USB-connected floppy drive (I’ve previously done that myself).

Then, another user post instructs to instead use HxC ImageLess Mode for Trinity-OS for simplicity because it requires no software, yet then states you must write OS diskimages to USB floppy partitions with Rufus utility software. However, from what I can tell, any diskimages needing to be burned with Rufus directly to flashdrive will be incompatible with Imageless Mode. Further, the posted vaguely claims the USB flashdrive partiton order apparently must be adjusted somehow for this OS update, whereas my experience is that Imageless Mode floppy partitions were automawtically named in order.

19) So, it really wasn't clear which HxC imaging mode, disk image format, and image writing software to use to get Trinity-OS updates right. Use MBR or GPT thumbdrive partitions? Or maybe try a separate thumbdrive for each OS disk? I wasn't going to risk destroying my synths for an unnecessary upgrade test based on vague, contradictory internet “advice”. However, I realized I could run some more tests for reassurance...

20) I had previously successfully run the Trinity's and Triton's built-in service menu full “Extend FDD” floppy diagnostics on HxC-Gotek.
However, the Trinity service menu has an alternate “2DD Tiny Test” floppy diagnostic (that according to Trinity’s Service Manual, tests a double-density floppy instead of an HD one, for some reason). At the beginning of this test you are instructed to “Test diskchange – Please eject a disk and insert it”, and immediately after you change Gotek diskimages and “-”/eject flashes on the Gotek, the test recognizes a disk eject, and the Gotek green activity LED flashes quickly (mirroring the “knocking” on a real floppy drive between OS disks, described earlier)! Then, immediately once Gotek flashes “- - -”/insert , the green LED lights steadily, and the test accepts this as a disk change and commences!   

Alternately, I tried completing this Tiny Test by removing the USB flashdrive when prompted to change disks (instead of merely changing Gotek diskimages), which was also successfully detected as a disk eject and started the green LED flashing. When I then reinserted the flashdrive, it was successfully detected as a disk insertion turning the green LED steady.

So, with both methods, this successful test seemed to demonstrate that HxC-Gotek could indeed accurately emulate the “knocking” auto-reading disk-change behavior between OS disks on Trinity.

Triton's “Disk Change” diagnostic test similarly detects disk inserted and then ejected, and HxC-Gotek again passes the test both with image swaps and removing/re-inserting the USB flashdrive.

With these successful tests for reassurance, I proceeded to try an actual OS update, on Triton first.


UPDATING OS PROCEDURES

21) Luckily Korg still has older versions of Triton-OS on its website, so I could test a “downgrade” (the only way was down). Also Triton's OS update process feels less precarious because of greater visual feedback and its apparently flashing the ROM in smaller chunks. Using HxC Imageless Mode with a GPT 16 x 1.44MB floppy partiton USB flashdrive (prepared with HxC firmware archive Imageless Mode 1.44MB setup file), I copied the three unzipped Triton-OS disks' files to three separate floppy partitions (I actually used partitions 10, 11, and 12 - so loading into partiton 1 is not necessary).    Powered Triton pressing [ENTER] + [LOCATE] for update mode and all went perfectly, changing Gotek diskimages when prompted, twice. After OS v2.5.0 was flashed successfully, I flashed back to v2.5.3 again. Perfect!

22) Trinity OS update was next. However, it was a bit more problematic. The Trinity would not recognize HxC Imageless 1.44MB floppy partitions as OS disks after I copied the files from the two Trinity-OS disks into the partitions (like I did successfully on Triton). I first tried copying just the two special files contained on OS Disk 1 and the single special file from Disk 2, and then also attempted copying the “IndexerVolumeGuid” file or folder (not sure what this is). Neither worked.

Moving on to another approach, it seemed from the HxC docs that Imageless Mode would also recognize IMG files, so I tried copying into the floppy partitions IMG diskimages of the Trinity-OS floppies created by RawWrite v0.9.0 (a modified, Win32 version of RawWrite available on Github) because of my experience that HxC doesn't like IMG files created by WinImage, for some reason. Anyway, this also failed because RawWrite's IMG files of my Trinity OS floppies were just 18kB too big for the 1.44MB HxC ImageLess floppy partitions. (I later read a forum post by Jeff/JFDN stating that this issue might be due to 84 versus 80 tracks read by RawWrite, but I certainly wasn’t about to lop off the last 18kB of OS diskimages and hope it didn’t brick my gear...)

23) I'm not going to complain about these various software tools, their terminology, controls, intuitiveness, and documentation... or lack thereof... but I really felt like an idiot. So, trying other options, it appears that HxC INDEXED Mode (which I had to use instead of Normal Mode because these Goteks have stock 7seg, and not OLED, displays) is SUPPOSED to work with IMG files by default, just like it does with HFE files, but even after I renamed the IMG images with prefix DSKA####, they still weren't recognized. Then I tried to convert the WinImage IMGs to HFEs using HxC Soft, and it still wouldn't recognize them. Finally, I tried converting RawWrite IMGs to HFEs using HxC Soft and it worked.

24) Formatted a USB flashdrive which remained in GPT scheme (not MBR) with one single FAT32 partition for use with Indexed Mode, copied to it the two Trinity-OS HFE-format disk images named with prefixes DSKA0000 and DSKA0001, also copied the Indexed Mode CFG file for HxC, powered the Trinity pressing [ENTER] + [RESET] for OS update mode, and hoped for the best...

25) Well, it worked! Trinity-OS v2.41 flashed.

26) And then I flashed back to Trinity-OS v3.1.2 successfully!

27) Whew!

28) To more fully debrief you: You must name the Trinity-OS Disk 1 HFE diskimage with prefix DSKA0000 because in OS update mode the Trinity immediately reads Gotek, which, as you know, powers up at image “000” (= DSKA0000), and will quickly abort the OS update if it doesn't find OS Disk 1 inserted, without any opportunity to change images on Gotek, and forcing you to turn off and start over.

After OS Disk 1 is read and you are prompted to insert OS Disk 2 with the Gotek activity light flashing / “knocking”, you then have the opportunity to simply change the Gotek to diskimage “001” containing OS Disk 2, and the Trinity will automatically continue updating its OS.

29) So, with diskimage changes, reads, writes, and OS updates working on both Trinity and Triton, what else is there to say? Quite a bit! (Some of which I'll leave for synth forums, where it's more appropriate…)


“SUPERFORMATTED” “XHD” FLOPPY PARTITIONS IN HXC IMAGELESS MODE ON TRINITY & TRITON

30) First, here's an excerpt from a decade-old HxC release announcement:

“14 July 2013: HxCFloppyEmulator 2.0.15.0

Raw Loader - Predefined raw formats added :

Special 2.5MB DOS EXHD Floppy Disk

Special 4.5MB DOS EXHD Floppy Disk.

Special 6.78MB DOS EXHD Floppy Disk.”



31) Second, another excerpt from much later HxC release announcement:

“31 August 2020: Firmware STM32 USB HxCFloppyEmulator v3.5.1.1a

 - Major release:    Image-less mode support!
                                      Mount USB stick's FAT12 partitions!

All floppy disk partitions size is supported: 720KB (DD), 1.2MB (HD),1.44MB (HD) and even non standard sized disks (2.5MB and more...)

The firmware supports... GPT partitioned USB stick:
                This format allows you to have up to 128 floppy disks/partitions on the USB Stick.
                This is supported by all current operating systems
                (Windows 10 and recent versions of macOS and Linux).

                Pre-partitioned USB stick GPT images are available  the Image_Less_Mode folder.”


32) Third, and finally, see this excerpted table from HxC Docs → Usage → Emulation from USB Stick Partitions page → USB Stick Files List, Table 1. Table of USB Disk Pre-Partitoned Images (https://hxc2001.com/docs/gotek-floppy-e ... ition.html):

File // Description
gpt_usb_stick_16_4_5M.zip // 16 Special (255 tracks) HD 300RPM 4.5MB disks.
gpt_usb_stick_16_2_5M.zip // 16 Special (255 tracks) DD 300RPM 2.5MB disks



33) Putting the above three points together, HxC supports large, “superformatted” (“sufo”) eXtended High Density or Double Density (“XHD”/XDD”) MS-DOS diskimage sizes of 2.5/4.5/6.78MB and can also use prepared XDD 2.5MB (“XDD2” – yes, these are actually double density, see below) and XHD 4.5MB (“XHD4”) Imageless Mode floppy partitions on GPT-partitioned USB flashdrives DIRECTLY and NATIVELY within Windows, MacOS, and Linux WITHOUT ANY additional image writing or file management software necessary, which might in turn work on Trinity and Triton because they use the requisite MS-DOS floppy format.

34) With that in mind, I downloaded the pre-partitioned 16-image 4.5MB pack from the HxC file archive Imageless Mode folder and burned it to a USB stick resulting in a GPT (GUID Partiton Table) scheme with sixteen XHD4 (4.5MB) floppy partitions. Then I copied some files into them for testing on the Trinity/Triton.

35) On Trinity, the XHD4 partitions are basically unreliable and actually crash the Trinity, forcing you to reboot. If you have any previously unsaved sequence/song data in the Trinity’s RAM when this occurs, that data will be lost! In Trinity Disk Mode, the first 1.2MB to 1.3MB of data can be saved to XHD4 partitions properly without incident, but saves exceeding that cause the crash, showing text overlaid on the LCD, including “SYSTEM ERROR”, “Error code”, “FILESYS_MALLOC_ERR” (misallocation error?), plus many lines of hexadecimal code. (Any Trinity firmware specialists? Step on up to diagnose the codes and help revise HxC to prevent this... ;) ) Further, attempting to load from packed XHD4 partitions any data outside the normal 1.4MB or so will also crash Trinity. (Of course, there's no way to determine which of the files on the partition will trigger a crash.)

36) On Triton, reading/loading from XHD4 partitions seems to work flawlessly. I successfully tested loading into Triton about three floppy's worth of Korg PCG (Patch, Combination, Global data) files from one XHD4 floppy partition, was well as a single 4.1MB WAV format sample from another.

37) On Triton, saving/writing to XHD4 partitions was partially successful. When I tried export-saving the same 4.1MB sample from Triton's sample RAM back to a floppy partition, the progress bar made it to all the way to 100% but then returned “Error in writing to medium”. However, I then successfully exported and saved onto the XHD4 partition the same stereo sample as two separate mono 2.0MB WAV files, totaling 4.0MB. In addition, I was later able to simultaneously save four Program Banks totaling an additional 270KB to that same XHD4 partition in Triton's Disk Mode, filling the partition all the way to “Free Size: 34K” remaining! So, while I wouldn't always count on being able to write to XHD4 partitions on Triton, it might yet work with certain files.

38) Triton Disk Mode – Media Info tab page shows “Free Size: 4.4M” on empty XHD4 partitions, so the true extended size is indeed recognized. (Although “Total Size: 1.4M” is also shown on the same page.) Also, as you delete files files from the XHD4 partition from Disk Mode, Free Size will progressively increase all the way back to the full “4.4M”. (There is no media info view available from Trinity Disk Mode.)

39) I also successfully used an XHD4 partition in Triton's “Extend FD” diagnostic test, although the partition was reformatted to standard 1.4MB in the process. When I quick-formatted an XHD4 partition from Triton's regular Disk Mode it also reduced the partition to 1.4MB.

40) Note that Trinity uses FDC (floppy disk controller) chip UPD72070GF, while floppy-endowed (yeah...) Tritons (Silver “Classics”, Rack, Karma, Studios) all use HD62366, so that might account for Trinity's additional difficulty with XHD partitions. (Of course, Trinity has a different OS and CPU than the Tritons, too.)

41) Incidentally, I also tested “XDD2” 2.5MB sufo floppy partitions on both Trinity and Triton, but it did not work out. You'll notice the slight inconsistency in the above HxC v2.0.15.0 release announcement versus the above Table of Pre-Partitoned Images in that the former states the 2.5MB partitions are high density “EXHD”, while the latter states they are double density “DD”. Since Trinity and Triton have specialized DD floppy diagnostic tests, it seemed the Trinity might behave differently (better) with this partition size if it were indeed DD, so I thought it worth a try. In reality, about half of the files I copied to the XHD2 partition using a PC were not visible on either the Trinity or Triton Disk Mode directory. And even some of the visible files crashed the Trinity upon loading. So, XDD2 partitions are out. (But they did, in fact, appear as double density on Triton with “Total Size: 720K, Free Size 2.4M”, so double density they are!)

42) Curiosity killed the cat? I can't help but wonder what would happen if you consolidated all three Triton-OS update floppies’ files onto one XHD4 partition and tried the OS update…

43) Finally, I performed all testing using a Sandisk 16GB microSD card (speed 4) and an old Kingston 2GB microSD card (no speed rating), both in mini generic microSD-to-USB adapters, plus a Verbatim Store'n'Go 2GB stick. The Verbatim stick returned some errors on Triton, even writing standard HD 1.4MB floppy partitions. I've read various posts stating Triton was sensitive to certain USB flashdrives, so if you get errors, be sure to try another flashdrive. The microSD cards in adapters performed perfectly.


QUESTIONS AND REQUESTS

44) Can we please have “XHD6” sufo 6.78MB pre-partitioned Imageless Mode setups added to the HxC Firmware Archive, since that size is supported yet absent for some reason?

45) Are XHD sufos LARGER THAN 6.78MB a possibility?

46) Can we please have a tutorial on how to create Imageless Mode sufo partitions and pre-partitioned setups of multiple partitions in all supported sizes (1.44/2.5/4.5/6.78MB)? That way, users can create custom setups generating MORE THAN JUST 16 floppy partitions in them, since GPT supports up to 128 partitions. (There's a way in Windows to unassign/remove letters from GPT drive partitions and instead use folders to access the partitions, alleviating unwieldiness from tons of separate partition drive letters being listed.)

47) I was able, though, to “clone” and append additional XHD4 4.5MB GPT partitions beyond the original 16 originally created by the Imageless Mode setup file on my USB flashdrive by using free Aoemi Partition Assistant Standard software on Windows, but it felt a bit “messy”.    I'm sure I could reformat on Triton itself one XHD4 partition down to HD 1.44MB and then clone/append that partition to create a USB flashdrive with a custom number of both sizes of partitions (for guaranteed and/or split-disk saves), but a way to create partitions from scratch (see request above) is preferable.

48) If a tutorial isn't practical or possible, then can we have Imageless Mode pre-partitoned setup files in all supported sizes (1.44/2.5/4.5/6.78MB) with MORE THAN JUST 16 partitions added to the Firmware Archive (e.g. 32, 48, 96, and 128 partitions)?

49) Also, is it possible to add to HxC Gotek firmware a GPT partitioning capability directly from the HxC-Gotek drive EMBEDDED MENU (e.g. Firmware Customization -> ImageLess Mode -> “USB Stick format function built-in disk image [1.44MB] [2.5MB] [4.5MB] [6.78MB] [?]”), along with either an embedded menu selection or else a firmware customization feature specifying the NUMBER of GPT partitions that embedded menu formatting will create (i.e., any number between 1 and 128, or else intervals like  16, 32, 48, 96, 128)? This would create a truly software-free solution, since you then wouldn't need the special Imageless Mode XHD pre-partitioned setup files, plus a burning application to prep the USB flashdrive.

50) General Request #1: Can Imageless Mode diskimage selection be made to “loop”/“rollover”/wrap-around” at the extremes on HxC-Gotek 7seg drives (i.e. on a 16-partition setup, selection goes “014” > “015” > “000” > “001”, and conversely goes “001” > “000” > “015” > “014”)?

51) General Request #2: Please add an auto-off feature for 7seg Gotek displays! I'd say a 7s-10s delay (fixed or programmable) before auto-off would be ideal, and that the very first Gotek +button/-button/rotary button/+rotary/-rotary event when display is off should merely turn display back on and NOT change previously inserted diskimage. (Of course, disk activity/insertUSB/removeUSB should turn display back on, too). Thanks.

52) Does an OLED and/or rotary encoder mod'ed HxC-Gotek indeed have the ability to use the Auto Select/Delay feature that seems the key to successful disk change emulation on Trinity/Triton?
   
Well, I’ve said enough…

Except... that I hope this helps others get more out of their applicable Korg gear and HxC, and I’d love to learn of any refinements or things I missed in all this.

** LAST, A LITTLE DISCLAIMER AND FRIENDLY ADVICE: I WILL NOT BE HELD RESPONSIBLE WHATSOEVER FOR ANY DAMAGE TO, DATA LOSS IN, OR MALFUNCTION OF YOUR EQUIPMENT OR STORAGE MEDIA CAUSED BY THE INFORMATION HEREIN; THE GOTEK DRIVE, HXC FIRMWARE, AND TECHNIQUES DESCRIBED ALL INVOLVE AFTERMARKET MODIFICATIONS TO VINTAGE ELECTRONICS FOR WHICH YOU ASSUME ALL RISK! I would definitely run both the full “Extend FDD” plus either “2DD Tiny Test” (Trinity) or “Disk Change” (Triton) service menu diagnostic tests, as well as saving and reading a variety of files, large and small, that you have backups of, to ensure your HxC-Gotek drive and USB flashdrive are working to your satisfaction before attempting any OS updates. EVEN THEN, THERE IS UNFORTUNATELY A RISK YOU SOLELY ASSUME THAT YOU WILL RENDER YOUR EQUIPMENT USELESS AND POSSIBLY UNREPAIRABLE!!


APPENDIX OF REFERENCED THREADS:

Hope it's OK to put relevant thread links here, some to other forums:

DISKIMAGE CHANGES TRINITY HXC viewtopic.php?f=33&t=2045&sid=95d3959bd ... cec9549f81

JUMPER SETTING TRITON HXC viewtopic.php?p=24221&hilit=triton#p24221

UPDATING TRINITY-OS IN IMAGELESS MODE BY BURNING/RUFUS CLAIM NON-STANDARD OS DISKS/RAW COPY? http://www.korgforums.com/forum/phpbb2/ ... a6ba3b1d2c

AUTO-OFF 7SEG DISPLAY HXC viewtopic.php?f=33&t=3982

"EXHD" SUPERFORMATTED PARTITIONS - HXC RELEASE NOTES https://hxc2001.com/download/floppy_dri ... _notes.txt

GATED MODE DISKIMAGE CHANGES HXC, “MEDIUM CHANGED” MESSAGE, JUMPERS TRINITY viewtopic.php?t=2045

PHYSICAL PIN34 INTERRUPT SWITCH FOR DISKIMAGE CHANGES TRINITY https://www.soundonsound.com/forum/view ... 8&start=24

WRITE PROBLEMS TRITON viewtopic.php?t=4016

MORE WRITE PROBLEMS TRITON https://github.com/keirf/flashfloppy/issues/362

EVEN MORE WRITE PROBLEMS TRITON (KARMA) AND HXC IMAGELESS MODE SOLUTION https://forums.karma-lab.com/forum/show ... p?p=117391

IMAGING PROBLEMS TRINITY-OS https://www.soundonsound.com/forum/view ... 23&t=76597

7SEG DISPLAY AUTO-OFF viewtopic.php?t=3982
Post Reply