Hi

I'm lucky enough to be supporting an old Fox DOS 2.6 application on a
network....

Everything was OK on a Novell server, but I had to move it to a Windows 2003
server. It runs much faster, but the Windows 95 and 98 clients are getting
"This device does not exist on the network. Reading drive F:" errors at
seemingly random times. They get thrown out of the application, but the
mapped network drive is still available.

The error can happen at any time, but seems to be linked to writing back to
a table. It doesn't seem to be anything to do with printing, and the network
printers aren't on the Windows network anyway.

The Windows 2000 clients seem OK... maybe my boss needs to get his money
out?

Any advice appreciated! I found a few reports of this on Google, but no
answers.

Thanks,
Jason

Does MS Knowledgebase article 297684 help?
http://search.support.microsoft.com/kb/c.asp

As far as I remember, UNC paths do work in Fox 2.x as well, e.g.
Use \\192.168.0.125\shared_data\customers.dbf
Set Path To "\\192.168.0.125\shared_data"
Use customers


hth
-Stefan

"Jason" <jason@--nospamplease--bluetattoo.co.uk> schrieb im Newsbeitrag
news:gPYFc.3093$Fc7.530513 (AT) stones (DOT) force9.net...

I have the same problem. If you sort it can you help me too please. Ratify.

Stefan,
UNCs work - as long as they conform to the DOS 8.3 format. Long names and embedded spaces aren't recognized. <s>

Rick

"Stefan Wuebbe" <stefan.wuebbe (AT) gmx (DOT) de> wrote

Right, how could I forget about 8.3 :-)

-Stefan

"Rick Bean" <rgbean (AT) NOSPAMmelange-inc (DOT) com> schrieb im Newsbeitrag
news:10gfio4d7aido9a (AT) corp (DOT) supernews.com...
Stefan,
UNCs work - as long as they conform to the DOS 8.3 format. Long names and embedded
spaces aren't recognized. <s>

Rick

"Stefan Wuebbe" <stefan.wuebbe (AT) gmx (DOT) de> wrote

I have solved this problem now. It is an error message from the OS if the
PC is disconnectd from the network unexpectedly for example by extracting
the network cable at a random point in the program's processing.
In my case the intermittant error, on some networked machines but not
others, was caused by the windows network properties TCP/IP gateway being
an old slow router for some machines (with the problem). When the gateway
was aimed at a faster / higher spec / non-faulty? router, Hey Presto
problem solved. A very happy Ratify!