>We've recently had a disturbing number of indexes getting corrupted on 2.6 files. While I'm used to not trusting, say, clipper indexes. We rely on Foxpro indexes to be correct.
>
>The only recent change I can think of was getting two win98 systems for processing. Recently when reindexing a large file (3MM) on one of the new win98 machines, foxpro inserted hi-ascii characters after the tag name listed in the window echo. The actual tag was not effected, as far as I could tell, but it made me suspect win98 as the source of my problems.
>
>Anyone else experienced similar problems.
>
>The machines are also our first PII's (Pentium II, 300Mhz, 128RAM), which, by the way, are not always faster than our Pentium 150's. But I'd much rather blame Microsoft than Intel. The files are on a Novell 4, PII server, 100BT, all 3COM cards and hubs.

Are you by chance using Novell's Client for IntraNetWare or Client32? If so, try either using Microsoft's Client for NetWare, or, if you insist on using a Novell Client, try turning off write caching and packet burst at all workstations. I've been told that disabling packet burst is unnecessary; my experience, and that of the networing staffs of several clients, from tracking down a large number of problems which only surface on NetWare environments is to either not use the Novell Client or to turn off the options I listed above.

hth,

Ed