I was able to solve the problem. I referenced an old version of a macro that had a different number of inputs and outputs that the newer one, which was used by the updated network. The extra tabs were hidden (ctrl-h), so I missed it when I looked at the network in the VPE. The difference is clear in the .net file. Anyway using the right version of the macro made the problem go away.
So, this might be an obscure tip for anyone that runs into this problem... Lloyd A Treinish/Watson/[EMAIL PROTECTED]@opendx.watson.ibm.com on 08/24/2001 03:22:00 PM Please respond to opendx2-dev@lists.berlios.de Sent by: [EMAIL PROTECTED] To: opendx2-dev@lists.berlios.de, opendx2-users@lists.berlios.de cc: Subject: [opendx-dev] ui core dumps when reading a big net I have some complex nets that I recently updated on a Linux system (OpenDX 4.1.0) and then moved to both AIX (4.0.9), other Linux (4.1.3) and Windows (4.1.1 and 4.1.3) systems. I have done this before without problem. However, one of the nets no longer works on Windows. The other nets work fine, and all of them work on the other platforms. The UI core dumps when reading in the net reporting "internal error detected at node.c:2393". I have run into this occasionally in the past, which usually forced me to hand edit the .net file, when somehow the VPE corrupted the file. A quick look at the code implies that the error might be a problem with settings for the caching options. Of course, trying to find which node in the graph is the offending one might be tough... Does anyone have any simple suggestions before I trying some harder ideas? Thanks.
