From: bobkil@ibmpcug.co.uk (Bob Kilgore)
Newsgroups: comp.sys.mac.system,connect.audit
Subject: MACX PROBLEM!
Summary: MACX failed after three weeks normal operation, why?
Date: 16 Jul 92 20:04:07 GMT
Organization: The IBM PC User Group, UK.
X-Disclaimer: The views expressed in this article are those of the author
	alone and may not represent the views of the IBM PC User Group.

Hello all;

At some point you must say, "heck! I don't think I can solve this one" and 
ask for some help.  System configuration:

MAC-IIci, 5 meg. RAM, 32 meg. HD (SCSI-0), 44 meg. Ext. Disk (SCSI-7), 
col. monitor, 2 Ethernet cards, (Cabletron DNI).
System, v6.0.7 (9 Oct. 1990) now 1,377,725 in size, Finder 6.1.7 running 
with Multi Finder.  Inits include, File Guard 2.7.4c9 (15 June 92), Virex 
1.84 (4 Dec 90) and others.
Note: the two Inits are dictated by the company and I cannot remove them.

A few months back we received the Pathworks package from DEC, and 
installed it on a VAX.  The full installation was done on this MAC to test 
the various functions and there impact on the network.  Everything appeared
to work fine, except the MAC.  Had multiple hardware and software 
problems.

On the primary Ethernet address, the DEC-Net software changed it from the 
Cabletron assigned address to an aa:00:04 etc. address.  there was no 
indication that this is a problem.  Even if DEC-Net is removed the address 
remains the same until the system is re-installed. 

The part of Pathworks that I intend to keep, and use, is MACX, the 
workstation software.  I use this with a SUN Sparc-II and it worked very 
well for about three weeks.  With no change in the MAC, I attempted to 
start the X windows server and received the following message;

The connection tool "MacTCP Tool" does not support the "local address" 
macro used in the command "iwstb1.setenv".  The other two packages that
support TCP, Intercom and MAC240 work fine and have never been a problem.

A number of inquires were made, DEC had never heard of such a message, The 
distributor knows nothing about MACX, etc. etc.  And, there is a complete 
listing of error messages in the MACX documentation, except this message. 
Took out all inits. except the two I can't touch, took out all control 
panel doc's. etc. no change.  Moved the software from the first MAC, to
another, including all the coms. drivers, and it worked perfectly. 

Back to the original MAC.  Opened the command to edit, selected 'hosts'
and entered the IP address of the host.  Clicked on 'OK' and received the
message;

Internal Error: Could not load the MAC TCP Domain Name Resolver.

Very true, I enterd an address, not a name, as there is no name server 
yet.  When attempting to back out, I received the Bomb message for 
'unimplemented trap'.  Clicked on 'Restart' and system died a complete 
death.  Thanks for the 'restart' switch, it seems to be the most usefull 
piece of hardware on this system.

What TCP drivers do I have?
Mac TCP Tool, MacX 1.1.7, 25 Sep. 91
MacTCP, 1.1, 2 Oct 91
MacTCP DNR, no ver. 14 Jul 92
MacTCP Prep, no ver. 14 Jul 92

Question, obvious! How do I make this beast work for more than a few days?

Thanks for any assistance, my E-Mail address is in the UK, but I am actually
in Belgium.  How about that for a long distance call.
BOB
bobkil@ibmpcug.co.uk
Newsgroups: comp.sys.mac.system