> Does anybody have an idea why I might be able to write a new file
> to a network drive (mapped with ms client), but not be able to
> turn around and read that same file?
I have a similar question.
I recently set up a local area network to run a DataPerfect
data base. The system uses MS-Client and FreeDOS in both server
and clients.
The client can access the server and run the database fairly well
(it crashes occasionally though). But it cannot do a 'dir'
command to see the shared folder of the server. The error message
is: "unimplemented internal dos function INT2F/120s".
Apparently this is a known bug. While searching the internet
about this, I found the following. The context is different, but
the essential problem sounds similar.
(quotation begins)
comp.os.linux.network
Google Groups Home
Newsgroups: comp.os.linux.network, comp.os.linux.networking,
comp.os.ms-windows.networking
From: "Wiggs" <[EMAIL PROTECTED]>
Date: Fri, 16 Jan 2004 17:36:21 GMT
Subject: DOS MS Client v3 and EFG80
Hi All.
Hope someone can provide a solution for a problem I'm
having with my LinkSys EFG80 NAS. The device works great
when used as a file server in a home and small office
network with Windows 95 on up to Windows 2003 servers and
Linux workstations, however whenever I attempt to boot a
workstation client from a network boot disk w/ MSClient
for DOS v3(MSDOS 5 on up), it fails. It loads TCP/IP,
binds the protocol to the adapter, sees the shared on the
server and maps the share to the specified drive via NET
USE, but if I attempt to list the directory (DIR) the
redirector (I'm assuming) complains of an extended error
123 and lists nothing in the directory even though I know
there are files that should be listed. Tried using a LAN
MANAGER client boot disk with same results as well.
Now here's the weird part. I can copy a file from a local
drive to the remote directory. When I run a directory
listing via DIR the newly created file magically appears
as the only file in that directory. If I attempts
repeated directory listings the file then dissapears and
the extended error message reappears again. The most
amazing thing is that despite the error message I can run
any program from the remote share if I know the path and
filename (including the extension) and copy files from
the server. I can't however use any navigation in DOS
applications because they are unable to see any directory
structure on the remote directory. (ie# If I'm using
ghost to image a hard drive) I don't have any of these
problems if I attempt to connect to a workstation share
or a different samba server using this boot disk.
I determined that the EFG80 does indeed use a linux
kernel and samba as an SMB server but I'm unaware if
there are any issues or even which version of Samba it
runs. Anyone know? Where there any issues with DOS
clients and Samba servers and more importantly any work
arounds?
(quotation ends)
Any clarification will be appreciated!
Regards,
Marcos Florence
Sao Paulo, Brazil
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
