Hmmm... I think you are missing the most important point of Kroozbox. (maybe you should read the manual
)
If I understand you, you first enter the movies in PVD and then move your hard disk to your PCH.... ouch - not good - it defeats the purpose.
Kroozbox is build to deliver the movie to the PCH through the network. Do NOT unplug your hard disk from your computer where Kroozbox is running, just leave it there. Selecting the movie from kroozbox will deliver it to the PCH.
Now, there are situations where the movie you enter in PVD might not be find at the same drive/location by Kroozbox. For instance, on my system I use PVD on my personal computer that sees the movies on drive "m:". The database is physicaly located on a hard disk on my home server that is using "e:" as drive letter (where the movies are). Kroozbox is also running on this home server. In essence, the PVD database have the movies entered on drive "m:" but Kroozbox must get them on drive "e:".
There are multiple ways to adjust this. The simplest way is to adjust the value of "dbaseMediaRoot" and "localMediaRoot" in the corresponding kroozbox.properties. In my example, I would set "dbaseMediaRoot = m:/" and "localMediaRoot = e:/". You could adjust that and have "localMediaRoot = USB_DRIVE_A-1:/" or something like that. But you would miss some of the important feature of Kroozbox (delivering to multiple medias, etc) and you would have to alwyas move your hard disk (yurk).
You could also use the "mediaLinkPathTable" and/or the "mediaPathTable" correspondance tables, but these should be use for more complex re-mapping where you have multiple hard disks on different drive assignments or exotic network.
But I think that in your case, you just have to plug and play.... isn't it working properly when you start the movie ? (from browser or PCH).