I suspect the answer to this is "you can't abuse perl that way on WinNT," but I'll post anyhow.
I'm distributing files across several machines on an NT network; for various reasons I need the status that the File::Copy module returns but can't rely on mapped drives. UNCs and IP paths (\\10.98.76.543\d$\usr\exe) don't seem to work with this module however; only local or mapped drives (which appear local to the machine) seem to work. So a regular batch file works fine with a UNC or mapped drive but won't tell me if there's a copy failure, while perl is feature-rich but requires code to check for/reestablish a 'local' drive. Can anybody confirm this and/or suggest a way around this? Thanks for your patience! Jeff -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
