I see, then replace that program to a proper one :-). That was the worse
thing in MSDOS: every app programmer felt that he/she is an OS developer as
well so broke the app layer in every way they could. (erm, even myself wrote
a FAT driver those days to access files faster and to be able to see hidden
viruses on the system :-)

But seriously, if the app does not support accessing to files on a network
drive I suggest not to use that in this occasion.

Tamas


On 12/09/06, Alan B. Pearce <A.B.Pearce@rl.ac.uk> wrote:
>
> >OK, so  what's wrong with opening a file in a mapped drive?
>
> Some programs get real funny if they cannot "get at" the drive data in the
> same manner as they can on a local machine. I have seen this happen with
> programs that attempt to look at the drive properties, presumably to look
> for how much empty space there is, and if the drive type is not what they
> expect, then they baulk. A network drive is reported as a different drive
> type to a floppy, local hard drive, or CD.
>
> --
> http://www.piclist.com PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist
>



-- 
unPIC -- The PIC Disassembler
http://unpic.sourceforge.net
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist