A month ago I finally got KC2 after getting tired to have to shut down the system just to connect or disconnect the disk drives I worked on. First impression was overly positive... until I connected 3.5" 120GB IDE HDD.
XP (SP3) Pro indicated that it found new device, told it was "disk drive" and announced that the new device was installed and ready to use. Even at that point I suspected something was wrong, as XP never idetified the drive properly... and I was right. Disk Managment did not find the drive at all, while Device Manager displayed only some orphan "disk drive" without any additional information. Drive was not usable in this state, so "safely" disconnected and tried again with same results.
I tried with a few older small units, but no go. Noted that while the blue LED indicated the KC2 was on, the red LED did not lit. Because the drive did some amount of communication with XP (that is, ZP reckognized at least something!), I suspected the drive was not getting the power it needed. After a few minutes I conformed the situation by powering the drive(s) directly from computers PSU with molex connector.
So, the problem still exist with KC2 (SCUPS-2000 200903010313). Now, I generally don't like to point fingers *cough*QC!*cough*, but I'm beginning to get annoyed to have power related problems and see where they point... again.
I do understand that sometimes bad things happen, but all these longtime problems with KC2 pointing to similar source of malfunction? And still not fixed in new product batches? Not only disappointing, but unacceptable.