>>>3 simple step to regenerate the file read error. I experience a file read error if you do the followings. (p.s. this is nothing to deal with the cable connection)
>>>
>>>1. Prepare a peer to peer network server using ipx/spx protocol in windows 95.
>>>2. Start a basic redirector service from the dos/prompt without starting windows 95 and connect to the server.
>>>net login /y
>>>net use h: \\yourserver\yourdirectory /y
>>>
>>>(assume you have a foxpro table locate in . )
>>>
>>>3. start foxpro for dos and just open the file
>>>
>>>And lets wait for 10 mins. Be patience, 11 mins to safeguard the server disconnect you. Workaround: Microsoft has acknowledged the problem and released a patch that you CANNOT find it. (From the knowledge base: search by "ipx/spx timeout" and read more about it)
>>
>>
>>I'm not actually getting disconnected. A couple of users who appear to be at the end of a physical segment are getting low priority on the network and during times of high traffic, packets are lost and foxpro says, "what the...??!!"
>>
>>I should check the KB to see if MS has acknowledged this as an issue.
>
>Hi Matt,
>
>I was just reading your thread on error 1104 (error reading file) and was wondering if you found what your problem was. I have the same issue on my newly installed NTServer 4.0 network. My app worked fine on our previous novell 3.12 network, but now that we have migrated to NTServer I'm getting these pesky errors when users are idle on my app for...say 10-15 minutes and then try to continue using my app. My network people are not very much help on this and I was looking for some info. Do you have any suggestions for me?

John,

1. Make a 150 MB files in server in some directory.
2. Copy this data from server to workstation (for example, using cut and
paste command in w95 shell). Run those copy commands
simultaneously in all workstations in network.
3. The copy process will never be successful in all stations:
sometimes you get error message selected network resource or drive
will no longer available.
Sometimes the copy process stops without any message. However,
if you look for the copied directory size, it is less than 150 MB.
The error occurs at random intervals: sometimes at beginning,
sometimes after some minutes.
Making a Win 95 computer as server with
coaxial cable connections solves this problem.

Andrus