When AREV goes into background index processing the keyboard is locked up and user has to sit there until backgound process completes. At times keyboard is locked for several minutes and user assumes the system is froze and reboots. Never had this problem with AREV 1.12 since any keyboard activity would interrupt the background process.

TIA for any help with this problem.

I assume that you are using a network and not stand alone. I ran 2.03 for several years on a standalone with no problem with indexing.

could you give more data - network type, etc.

Dale

Shouldn't have a problem with this. We have Arev 2.03 and it's okay. Is just the PC doing indexing locking up? Have long have you been using 2.03 (2.03 is old)? What operating system are you running?

[email protected] onmouseover=window.status=imagine … ;return(true)"

Symmetry Info

Ray Chan ~ Symmetry Info

If at all possible, set up a dedicated indexing machine, and disable the background indexing on your user's computers. I'm running 2.03 with the NLM, and I see this keyboard lockup problem too, however since nobody uses the computer, it really doesn't matter.

If cost is an issue, the indexer can even be a computer from your "junk" pile. I'm using a Pentium-100, running Dos 6.22, and it does the job just fine. Just make sure it is reliable.

Tom Ayers

ARev 2.03 should behave the same way. Are you sure it's background indexing running? An explicit INDEX.FLUSH call from an RBasic program usually cannot be interrupted.

This client has been running 2.03 since last July. The network system is Lantastic with a mix of Win98, Win95, Win3.1 and MS-DOS workstations.

Have had other clients running 2.03 since it first came out using Novell NOS and MS-DOS workstations. No problems on these system.

Thanks

Running 2.03 on a Lantastic NOS with a mix of Win98, Win95,Win3.1 and MS-DOS workstations.Have installed NPP network driver.

Thanks

View this thread on the forum...