[QUOTE=mciahel;2103670]You should be able to find the link to KC03 in the firmware announcement thread. ;)[/QUOTE]Yes, I was having difficulty in locating the file, but now I have downloaded it (TS-H652M_KC03.exe) and will apply it to one of my SH-S182M drives with the -NOCHECK option activated.
I foresee only one potential problem, that you anticipated: how far down the drive ID string does the DLA utility parse? That answer no one will know, until the drive is flashed, the system reboots and I see the DLA Tab in the drive’s Properties Box.
DLA’s README.TXT warns the utility will fail to initialize a second drive, if it is identical, [I]or substantially identical[/I], to the first. Unfortunately Samsung has seen fit to put the unique part of the ID string at the very end, and not the beginning. I take DLA’s (Roxio’s) warning (in italics) to mean their utility doesn’t parse very far.
Should KCO3 create an ID string with a similarly “generic” front-end, and if DLA still fails to differentiate between the two drives, I am once more faced with altering the beginning of the ID string on one drive. Having read the comments you directed me to, on what appears to be some form of Patch Guard built-into recent drives, I won’t do this without expert advice.
I do have some ideas on a work-around, but it depends on how rigorous the checksum algorithm is, on TSST drives. If it comes to that, unless you say otherwise, I think it will be best to start a new thread to explore these ideas, with a revised title to reflect the new direction, as we will have taken the firmware-substitution remedy to its conclusion.
Hope I have good luck,