@The gauge:
Well, i don't really know what do you want to hear about.
What i'm meaning is that SF ONLY patches the Windows Kernell if it finds optical drives connected to IDE. When remotely mounting, SF looks for another devices searching the SAME "protocol", and because is across a lan, no other devices are found to compare with. The same thing happens with SCSI drives. SF hides almost every CDB commnad for reading CD, cause most computers on this world have drives conected to standart IDE. I think Windows IDE drivers are not safe enough to SF, so it patches it in order to properly hide what it is doing.
Secondly, respecting what some people call "spin" test, SF can send some commands to any drive ( mounted or not) about speed. Remember SF loads even before Windows loading is complete, so SF can easyly find which unit is virtual and which no.
Well, about that electronics i have seen ( with some laughts (excuse me, it's only so funny for me
), well, the problem is windows, not the IDE (hehe) If you neutralize that, how will windows recognice your HD and so one? Only by avoiding SF loading with windows, you could try something that (:?) I do not recommand it.
Well, don't think if properly replied to.
good luck!