W98 Server with W2000/XP Client

[infoplus]

On W98 Server with W2000 / XP Clients resulting in NTX corruption.
¿Any suggestion? Thanks

 

[JockMullin]

Hi, Infoplus

I would apply the opportunistic locking patches to the XP/W2K clients.

See thread288-555754 among many others.

A search on "opportunistic locking" will get you lots of reading material.

Jock

 

[Bozz]

I wouldn't use 98 as a server if I could use 2000 or XP. They may be a little bit slower at disk read/writes but they are much more stable as peer to peer servers. I you have a small workgroup, take a look at the Buffalo Linkstation NAS, it's cheap and reliable and works well serving my Clipper apps.

Ian Boys
DTE Systems Ltd

 

[GriffMG]

I would follow Ians' advice, perhaps looking at the Quantum Snap-on server instead of the Buffalo (only because that's what I have experience of).

Regards

Griff
Keep [Smile]ing

 

[pbsd]

A few years ago I had NTX corruption on a Win 2K server, so I did all the database operations locally on the workstation and then copied the database back to the server for storage. If you have multiple users simultaneously updating the db from the server, then this might not be possible without a lot of extra programming.

As a second thought, have you tried CDX indexes?

 

[Bozz]

Griff,
I started on Snaps too, but the Linkstation is a third of the price and works well.

Ian Boys
DTE Systems Ltd

 

[GriffMG]

Hmmm... Thanks Ian

Regards

Griff
Keep [Smile]ing

 

[jrumbaug]

Dear INFOPLUS

Did you find an answer. I have the same problem with a 98 server and a new XP workstation. The old 98 work stations are working OK. I have done the "opportunistic locking" patch. I have documented at least once, where a 98 work station wrote a file, but the XP workstation did not see it, even though a 2nd 98 station could see the files saved by the 1st 98. In fact, the XP had a scrambled index. I quit the program on the XP, restarted it, and then XP was seeing and pointing to the right files again. My current theory is that my indexes get corupted, when someone saves a file with the scramble XP indexes. I'm looking for an answer.

Jim Rumbaugh

 

[jrumbaug]

OK Wait a minute.. I may have answered my own question. A further search on this group for XP showed that I did the "opportunistic locking" correctly. I had followed a link to Microsoft and wound up setting SERVER paramaters, not WORKSTATION parameters. Thread288-555754 explains it better thatn Microsft did. I'll wait a few days and see if my problems comes up again.

Jim Rumbaugh

 

[jrumbaug]

OK, My problem is still here. I can now replicate the problem. If I save a file with a 98 machine, then save a file with an XP macine, the XP machine ovewrites what the 98 machine saved. I need to find an answer.

Jim Rumbaugh

 

[TonHu]

... If I save a file ...

What type of locking are you using in your app?

HTH
TonHu

 

[mbinfo]

I read elsewhere something about W98 having a FAKE lock system and not a REAL one.
Is that true? If it is, that's the cause of these problems.

My customers are allways recommended to change their servers to Linux or W2k or NT every time they show up with a W98.

Ulisses