Hi Brant,

The problem is the XP machine. Ypu must use this as your server and your data corruption will disappear. Microsoft changed networking features (there are probably others in UT who could explain exactly what MS has done) in XP and because of this, using as a workstation to a WIN98 server will cause your corruption.

Regards
Doug Johnston



>Folks:
>
>Please be patient, this is my first. I have a network of 20 machines running Win98SE, basically bare systems. Machines are all P3 750s with 256MB RAM, sufficient HD. NICs are all 100Mb, AOpen or 3Com, with 24-port HP hub. The server is a similar machine running Win98SE (so peer-to-peer). The software application is FoxMed, a medical practice management system from HealthTec Software, written in VFP6. We have had NO data problems since Dec 1999 in this network. Only the occasional SPOOL32 error common with Win98SE. The users have to end-task and reboot after the spool error. Machines typically stay on 24/7. Network protocol is NETBEUI for file sharing, set as Default Protocol in Network Properties. Many of the machines also have TCP/IP for internet access, via router (DHCP) and cable modem. All machines started with Norton Antivirus.
>
>Enter Panda Antivirus Platinum on some machines. Still, NO data problems, except some long repetitive print jobs seem to get lost.
>
>Enter one new P4 computer running WinXP Pro SP1. The XP computer has hibernation disabled, NO offline synchronization, running NETBEUI off the XP CD. We now have data corruption that appears to be related to the XP computer. The corruption does not show up in a single hard error, just finally creeps in until there are fatal VFP errors. The XP computer frequently gets an error opening a memo file when switching datasets in FoxMed. Switching closes one DBC and tables and opens a new set of about 15 attached tables. These data problems all clean up with a pack and/or reindex.
>
>Things I have tried.
>1. Removed NETBEUI completely from all machines in the network, all file sharing over TCP/IP. This left many orphaned sessions when the user got a SPOOL32 error.
>2. Found the tuning parameters for MSTCP and set the timers to remove the orphaned sessions.
>3. Changed to a newer set of drivers for the printer, set mode to RAW instead of EMF. Many fewer SPOOL32 errors.
>
>Some groups (like Visual AccountMate dealers and the Pervasive SQL people) have always warned that VFP in a LAN is very unstable, that 20 users is way too much traffic. But I have not experienced this, until recently.
>
>The lady who uses the XP computer can work fine when she is alone in the network, just when she starts interacting with data being shared by the Win98SE computers.