>>>We have just installed a dedicated server as above on a very small system (server + 2 workstations) Every so often, quite unpredictably we get a "Network Error - cannot read from Drive E" on one of the workstations that's running Win95.
>>>We have tried everything we can think of, including changing NIC, applying Patch26, removing Hub and going back to "Daisy Chained" RG58 cable.
>>>If we use the orginal Pent II 266 Mhz as the server it all works fine. Seems it must be the speed of the new dedicated server.
>>>Anyone else having this type of problem and know of any workaround?
>>
>>Hi Richard,
>>
>>Any chance that the application was compiled on a machine with an E: that was also used for temp file?
>
>Hi George:
>Errrr NO...but the machine on which it is compiled does have an E: drive mapped to another computer, which coincidentally also has FPW26 on it.
>I'll try unmapping the drive and recompiling. I know that FPW is very "picky" about drive letters.
>Thanks for the suggestion.
>Regds RM

Hi Richard,

Well, it's a shot in the dark but I'd suggest the following. First, make sure that the configuration file has a line in it reading something like TMPFILES=C:\WHATEVER\ Where the "whatever" is an existing directory on the C: drive. Second, recompile the application, and check the "Rebuild All" checkbox. It sounds like FPW is looking for a non-existant drive during load. This might solve the problem.

hth,