Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 31 JUL 2002 01:09:46PM David Cooksley wrote:

We have a large, multi-site environment with users running Arev 2.12 over a Banyan network (each site running its own Arev executable). We are at the beginning of a project to remove Banyan and transition everyone to Windows 2000 workstations on a Microsoft network. We have built one W2K workstation with no Banyan client and installed it at one location. This PC runs a dedicated Arev application processing transactions from the users, so it is generally busy all day and is not swapping between applications. This W2K PC has been getting the scrolling "QUICKDEX.MFS loading" error several times a day.

Most of the discussions here regarding quickdex point to a memory or drive mapping problem. So …

1. Are there any PC configuration hints that will reduce quickdex loading errors on a W2K machine?

2. Our NT servers are designed to disconnect users if inactive for 15 minutes or so (to keep the number of open sockets manageable). Does this relate to the drive mapping problems when Windows swaps memory for different applications?

3. To make this harder to pin down, we are also having problems at this site with both Banyan and MS network users trying to access the same data files.


At 31 JUL 2002 02:34PM Curt Putnam wrote:

Obvious question 1st. Are you sure that your quickdex is < 64K?


At 01 AUG 2002 09:45AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:

The disconnect option very well could be the cause. Usually you will get this error if the connection to the server is dropped. Could there be a setting to just drop the socket?

Where is the data? Is it still on a Banyan network? If so, how are you accessing it without a Banyan client? It's been a long time, but is the lock service still required? I have memories of it being removed, but I think that was for the ARev 3 series.

You'll also get that problem if the path is swapped out from under you. Windows 3.1 was notorious for that.

If you're concerned about memory swapping, set the memory to protected in the shortcut.

The Sprezzatura Group

World Leaders in all things RevSoft


At 01 AUG 2002 03:40PM David Cooksley wrote:

The data files are on NT servers with Banyan "StreetTalk for NT" installed. We dropped the Banyan lock service long ago, and are running AREV with NNP locking.

All of the client PCs are going to be upgraded to Win2000, but it will take a while to get around to every desktop. During the transition, the new clients will be logging in via the NT network (no Banyan client) and accessing the data files with an NT share, while the old users will log in via the Banyan network and access the same data files through the "StreetTalk for NT" service.

Yesterday, we removed QUICKDEX from all data files in production at the site, and set the "memory protected" option on the one PC's default DOS pif. It was stable this morning, but I just found the AREV session halted with a "Memory allocation error - Cannot load COMMAND, system halted" error.

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/137ed85be7fdd38c85256c07005e472a.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1