Re: Using shared drives

[Richard Dawe]

Hello.

Stephen Larcombe wrote:
> 
> I have problems using the file utilities on my windows-98 based machine,
> while looking at files shared over a network with a Windows-Me machine.
> 
> The following is a screen capture of the problem:
> 
> C:\My Documents\UNIX\fileutil\bin> dir \\quyenp\c\autoexec.*
>  Directory of \\quyenp\c
> 
> AUTOEXEC BAK           426  01/12/03  18:40 AUTOEXEC.BAK
> AUTOEXEC NAV           208  17/01/01   2:29 autoexec.nav
> AUTOEX~1 BAT           413  27/10/03   5:14 autoexec.bat~
>          3 file(s)          1,047 bytes
>          0 dir(s)
> 
> C:\My Documents\UNIX\fileutil\bin> ls  \\quyenp\c\autoexec.*
> ls: //quyenp/c/autoexec.bak: No such file or directory (ENOENT)
> ls: //quyenp/c/autoexec.bat~: No such file or directory (ENOENT)
> ls: //quyenp/c/autoexec.nav: No such file or directory (ENOENT)
> 
> C:\My Documents\UNIX\fileutil\bin> ls --version
> ls (fileutils) 4.1
> Written by Richard Stallman and David MacKenzie.
[snip]

I'm guessing that you're using the DJGPP port of fileutils 4.1. This is a
known bug with the DJGPP port of fileutils 4.0 and 4.1.

This is both your lucky and unlucky day. I ported fileutils 4.0 and 4.1 to
DJGPP. I've recently stopped working on DJGPP and DJGPP packages. So this bug
is unlikely to be fixed. (DJGPP development is quite quiet these days.)

As a work-around, ls will work, once you've mapped the drive. E.g.:

    net use z: \\quyenp\c
    ls z:

Hope that helps, regards,

-- 
Richard Dawe [ http://homepages.nildram.co.uk/~phekda/richdawe/ ]

"You can't evaluate a man by logic alone." -- McCoy, "I, Mudd", Star Trek