From mpullen@bacon.gmu.edu Wed Nov 4 11:35:38 1998 Received: (from mpullen@localhost) by bacon.gmu.edu (8.8.5/8.8.5) id LAA06724; Wed, 4 Nov 1998 11:35:35 -0500 (EST) Date: Wed, 4 Nov 1998 11:35:35 -0500 (EST) From: Mark Pullen Message-Id: <199811041635.LAA06724@bacon.gmu.edu> To: Alejandro.Avella@Colorado.EDU Subject: Re: Using models from OPNET 3.5 in version 4.0a Cc: mpullen@bacon.gmu.edu X-Sun-Charset: US-ASCII Content-Length: 1927 X-Lines: 68 Status: RO Alejandro, Thanks for the information. I will post it to our webpage so others can benefit. Mark > From avella@ucsu.Colorado.EDU Wed Nov 4 00:46:07 1998 > Date: Tue, 3 Nov 1998 22:46:52 -0700 (MST) > From: Alejandro Avella > To: Mark Pullen > Subject: Using models from OPNET 3.5 in version 4.0a > MIME-Version: 1.0 > > > Mark, > > I was able to "port" your models to OPNET 4.0A. The > instructions on how to do it follow... > > -Alejandro > > ---------- Forwarded message ---------- > Date: 03 Nov 98 18:30 -0500 > From: opnet@mil3.com > To: Alejandro.Avella@Colorado.EDU > Subject: RE> Using models from OPNET 3.5 (TSC 46398) > > > Dear Alejandro: > > OPNET release 4.0 utilizes new formats for models, and is therefore > incompatible with models from previous releases. This is solved with the > included utility "op_cvmod", which will update models from OPNET version > 3.5 or ealier format. > > If you are reading a 3.5 model into the 40 tool and are receiving an error > such as: > > Network model () could not be read. > The file appears to be corrupted. > Use m3_manfile to verify if file is corrupted. > > The command to check this is: > > unix% m3_manfile -header_print -m > > This will tell you if the file is indeed corrupted, or the file is of > version 3.5 or earlier. If the file is not corrupted, but of an earlier > version than 4.0, then you should update your models to the 4.0 format by > executing the following: > > unix% cd > unix% op_cvmod -all > > This and other major new release features are documented in the External > Interfaces Manual in the chapter Release Notes. > > If you still have problems with converting your older models to the new > format, please contact MIL 3 Technical Support. > > Sincerely, > > Pradeep > Technical Support, > MIL 3, Inc. > >