Except for the date of Mqueue (I have 8/30/1999) I am running the same stuff,
Mqueue 4.24A and 3COM905 with Net.ether905 ver 4.24J. I’ll send you the copy of
Mqueue that I have to see if it matters.
Other items before going into your code:
- Check the settings of the 3COM for half vs full duplex and make sure your
hub/switch supports full if the card and driver are set for it.
- Run the 3COM diagnostics - both on the card and the echo test. During the
echo test check for bad connections on the network cables.
- Check netinfo for errors. I’m not an expert at reading netinfo’s output so
someone else would have to help there.
Since you said you have other network software running these checks might be a
waste but these items have specifically hurt me in the past with Mqueue’s.
If the above doesn’t show anything then we need to start looking at your code.
Make sure dumper is running then run two separate programs - one send to a
mqueue and one receives from the same mqueue and just run them. (Cut and paste
the routines you use in your other code.)
I hope some of this helps…
KenR
Donald Backstrom wrote:
Mqueue is V4.24A dated Feb 23, 1998. We are using 3com 905C NICs. The driver
I believe was beta-ish as it needed to be modified from the version for
3com905B. The version we are running is 4.24J dated November 26,1999.
“Ken Recchia” <> rectech@nctimes.net> > wrote in message
news:> 39CF5823.8D28FD9D@nctimes.net> …
The first place to start is run sin ver and check for Mqueue 4.24A and not
4.24B. (A is newer and better.) Next check your network drivers are the
latest.
Donald Backstrom wrote:
Is anybody out there using Mqueue having this problem? This is the first
major job we have used it on and it is letting us down, crashing a few
times
each day. It is sharing life with smb, tcp/ip, photon and is operating
on a
small network of 4 machines. I have not been able to do anything to
cause it
to crash, it just does it sporadically, so I am not sure where to start.
Any clues?