Good explanation Brian , I'm talking to Marcos and seeing his efforts with Fdos group and when he replaced the server for a MS-DOS and worked I think that problem stated clear : Fdos Kernel has a problem. FDOS developers are aware and trying to work on that, when we'll have (and if) nobody knows . After all nobody said that Fdos was 100% trust-able and stable, it's a project in constant developing stage , so we might expect little issues. I think one the main concerns of Marcos' project is that they need free software (or free licenses) there, as it's a public health center and there is no money to spend on IT. So we have to avoid MS solutions because it will not be a usable solution, But he's on the way. There is also another Dos Option (DR-DOS 7.01) which in this specific version is free for non-commercial use,which may fit if Fdos guys couldn't solve , something that I didn't believe. But Brian, could you mention a couple of combinations (server/client) which do you know that works , I think it's a great opportunity to have it recorded here at the forum, the same way as the Windows 7 issue when it appeared. It's always good to know that we still have options to let DP running fine.
Rgds.
Fabio

Em 19-06-2012 00:54, Brian Hancock escreveu:
I have run DP over many many different server and networking client
combinations, with up to about 40 simultaneous connections and not ever had
a problem unless I was running share.exe on the client or a setting on the
client networking software was to enable network caching.  For a short while
one of the Novell Netware clients for Windows 3.x had client caching of
network reads and writes turned on by default, and this was the only time
that I have ever had DP data corruption. The major corruption over that
period was with the STR file which keeps track of the consecutive numbering
of records, and I kept getting duplicates, but I also got other random
corruption problems with TXX and the index file. The other application that
I know of which suffered badly with this setting was Lotus Notes. Once the
culprit was found and caching turned off everything worked fine.
Regards
Brian


_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf

Reply via email to