I'm not sure I quite understand your point three. Any hope of a bit more of an explanation?

A further complication (that I glossed over below!) is that the scripts that will refer to this mapped drive are actually invoked via a DCOM service that creates processes as the user.

Trying to run an evaluation of StarWind (2.6.4) and StarPort (2.6.1). I have two servers running under VMWare GSX (3.1.0). I've managed to export a read only HDD ok (as an SPTI disk) and on my client Windows XP machine I've managed to see that as a new physical SCSI disk via StarPort. However, when ...