GFEs in 100baseT Switched Ethernet using NLM 1.12 (AREV Specific) [Revelation On-Line Wiki]

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 09 FEB 1998 01:47:40PM Robert Hug - Applied Information Solutions wrote:

AREV Specific

I have recently installed a new network and have been receiving GFE's. Here's the setup.

Desktops:

   10 HP Vectra Pentium 200Mhz, 32Meg RAM

   10/100 3COM Ethernet Cards

   Win95 operating system

   Win95 "Disable write behind Cacheing on all drives is checked

   Newest Novell IntranetWare client

   Advanced Revelation database is called using a PIF that does not          'Always suspend' and uses a memory setup recommeded by          Revelation.

   Symantec's PCAnywhere V8.0 for Windows.  Always in Waiting          mode on the network.

   McGaffee's Virus Scanner resident in memory.

Server:

   Novell IntranetWare 4.11

   Revelation NLM 1.12

   Advanced Revelation 3.11 correct IPX driver loaded.

   Backup Exec 7.5 backup software.

At 09 FEB 1998 05:22PM Dave wrote:

Robert,

     Here are a few things to try and check. Download the turbos.exe patch from support.novell.com and install this this should take care of the gfe problem. I would also make sure that if you have a dedicated indexer running make sure it is not running during the backup process. I hope that this will help.

DaveRevelation

At 16 FEB 1998 06:41AM Larry WIlson wrote:

Geeze,

How soon they forget! First, get AREV 3.12, it's the only one that supposedly doesn't have the SELECT bug (according to JA). Second, take your virus scanner out of memory. Unless you're downloading files from pirate BBSs most of the day, it's eating time, caching frames and probably causing GFEs.

Lastly, I wasn't aware any NLM was bug free, but if this one is, I'll buy one!

Good luck.

Larry Wilson

[email protected]

At 16 FEB 1998 10:14AM Gary Gnu wrote:

Oh, yes, another thing, the bug, which was in the C portion of the LH code, is fixed in the NLM.

Gary Gnu

View this thread on the forum...