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? Code snippet below.
fname = Str( ii )
kill fname
f1 = freefile
Open fname For binary As #f1
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
Hi!
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
This may be similar to issues I'm having on my local drive as well.
For some reason, after a while, any files I write/copy/move/open in an
editor/ ..., wind up being unviewable at all. They will show up in a
directory listing, but any attempt to open/copy/move/edit/anything at
all simply
On Mon, Sep 1, 2008 at 6:24 AM, iw2evk [EMAIL PROTECTED] wrote:
Hi at all,
Tury have released the new multilanguage version of E word processor.
Include multilanguage support, large files handling, save files in .rtf and
Html, more new features.
Suggestion ,support and traslation are
Hi,
I did some testing:
a) Connection between FreeDOS 1.0 and FAT32 drive in Windows XP:
I used my FreeDOS 1.0 machine and MS Client 3.0. I entered:
net use I: \\laptop\usbstick
to map a FAT32 USB-stick connected to my Windows XP laptop to be the
local drive I: in my FreeDOS laptop.
Hi :-)
a) Connection between FreeDOS 1.0 and FAT32 drive in Windows XP:
(works, nice)
b) Connection between FreeDOS 1.0 and FreeDOS 1.0
You could also try FreeDOS server and Windows client...
The command dir results indeed in:
unimplemented internal dos funktion INT2F/120a
RBIL says
I was afraid it would be difficult to repro, because it used to work fine for
me as well, and I can't figure out what I did to change it. I've been messing
around with my startup and logon scripts in attempt to speed up the testing we
need this for, and I don't know exactly when this started
I have just reproduced the 'dir' problem with two computers,
both running FreeDOS on real hardware, and MS-Client.
FreeDOS kernel date:2007-12-08
Hard disk: 2MB, FAT16
Memory management: HIMEMX.EXE + JEMM386.EXE
Protocol: NetBEUI
A 'dir' command in the client
