I uploaded opendx-4.1.3-WIN32-setup.zip to ftp.sdsc.edu for David to provide
the new binaries through opendx.org.  The Executive problem is fixed.

1) Download (after is available from opendx.org)
opendx-4.1.3-WIN32-setup.zip.

2) Uninstall previous version using Control Panel --> Add/Remove Software

3) Unzip opendx-4.1.3-WIN32-setup.zip to a temporary directory and double
click on opendx-4.1.3-WIN32-setup.exe, then follow the instructions on your
screen....

Suhaib 


> -----Original Message-----
> From: Suhaib Siddiqi [mailto:[EMAIL PROTECTED]
> Sent: Monday, July 09, 2001 7:33 PM
> To: '[email protected]'
> Subject: RE: [opendx-users] FIXED: Problem in Opendx for windows/nt -
> Suha ib?
> 
> Greg,
> Never mind.  There was a problem with user.c.  I copied user.c and
> dx.mdf
> from my SGI workstation and recompiled the binaries. It worked.
> Thanks for hints.
> 
> I will upload the replacement Installshield Setup.exe for David
> tonight.
> Sorry folks for the troubles.
> 
> Suhaib
> 
> > -----Original Message-----
> > From: Gregory D Abram [mailto:[EMAIL PROTECTED]
> > Sent: Monday, July 09, 2001 6:30 PM
> > To: [email protected]
> > Subject: RE: [opendx-users] Problem in Opendx for windows/nt -
> Suhaib?
> >
> >
> > Oops, let one get away.  As I was saying, the dx.mdf included in the
> > MS
> > binary is OK, but the module is not in dxexec.exe, implying that its
> > not in
> > user.c - which is created by awkking dx.mdf!  So it seems like the
> > dx.mdf
> > that is used to create user.c, in the object directory corresponding
> > to
> > src/exec/dxmods, is different from the one that is in the lib
> > directory of
> > the release.  dx.mdf is created by passing dxmdf.src through the
> > preprocessor with -DEXECUTIVE_MODS and -DCPLUSPLUS_UI.
> >
> > The (intended) sequence is:
> >
> > dx.mdf is created in the dxmods directory from dxmdf.src by cpp with
> > -DEXECUTIVE_MODS and -DCPLUSPLUS_UI.
> > user.c is created in the dxmods directory from dx.mdf by awk.
> > dx.mdf is copied from the dxmods directory to the lib directory in
> the
> > install tree.
> >
> > So.  I'd guess that the dx.mdf in the dxmods directory in the MS
> > object
> > tree does not include the executive mods -  otherwise, they'd appear
> > in
> > user,c and would therefore be in dxexec.exe.  Check by grepping
> dx.mdf
> > in
> > the object directory it for Switch.  If it isn't there, then it
> needs
> > to be
> > recreated from dxmdf.src - as in the rule in localmk.in.  If it is,
> > then
> > does Switch show up in user.c?
> >
> > OK.  If Switch is found grepping user.c, I have no idea what could
> be
> > wrong.
> > Otherwise, if Switch is found grepping dx.mdf, you need to build
> > user.c
> > from dx.mdf - see the rule in dxmods/local.mk.
> > Otherwise, Switch is certainly in dxmdf.src - build dx.mdf from
> > dxmdf.src
> > (see the rule in dxmods/local.mk) and then build user.c from it.
> >
> > Good luck
> >
> > Greg
> >
> >
> > Suhaib Siddiqi <[EMAIL PROTECTED]>@opendx.watson.ibm.com on
> > 07/09/2001 03:33:52 PM
> >
> > Please respond to [email protected]
> >
> > Sent by:  [EMAIL PROTECTED]
> >
> >
> > To:   "'[email protected]'"
> >       <[email protected]>
> > cc:
> > Subject:  RE: [opendx-users] Problem in Opendx for windows/nt -
> > Suhaib?
> >
> >
> >
> > Greg,
> > The way I compile MSVC versions:
> >
> > 1) Compile using Cygwin, which creates all the files.
> >
> > 2) Use the MSVC Project files to compile MSVC version.
> >
> > If EXECUTIVE_MODS were not #define then this problem should show up
> in
> > Cygwin version too, but it does not?
> >
> > Can you suggest how to manually correct it?
> >
> > Suhaib
> >
> > -----Original Message-----
> > From: Gregory D Abram [mailto:[EMAIL PROTECTED]
> > Sent: Monday, July 09, 2001 3:13 PM
> > To: [email protected]
> > Subject: [opendx-users] Problem in Opendx for windows/nt - Suhaib?
> >
> >
> > There is indeed a problem with the current binary for Windows - the
> > one
> > built under MSVC, not the one built under cygwin.  It looks like
> none
> > of
> > the EXECUTIVE_MODS are there - I think that the rule to create
> dx.mdf
> > from
> > dxmdf.src in src/exec/dxmods must have been wrong.  When dxmdf.src
> is
> > passed through the preprocessor to create dx.mdf, the EXECUTIVE_MODS
> > #define wasn't set.
> >
> > Greg
> >
> > "Allard" <[EMAIL PROTECTED]>@opendx.watson.ibm.com on
> 07/07/2001
> > 11:48:24 AM
> >
> > Please respond to [email protected]
> >
> > Sent by:  [EMAIL PROTECTED]
> >
> >
> > To:   <[email protected]>
> > cc:
> > Subject:  Re: Re: [opendx-users] Opendx for windows/nt
> >
> >
> >
> > I have seen this too when I tried to run the windbarbs.net example
> > program.
> >
> > Also, I have experienced the problem with the sequencer which others
> > have
> > been experiencing when I try to configure the range of the frames
> that
> > I
> > wish to view.  When I keep the defaults (1-100), it works fine.
> >
> > I have also been getting errors relating to the keyboard.  For
> > example, if
> > I
> > try to highlight a directory name in the file browser and then hit
> > "backspace" to erase the name so I can put my directory in, the
> cursor
> > advances as if I hit the space bar.  I get the same result when I
> hit
> > "delete".  Also, "delete" won't work in the program editor window to
> > cut a
> > module.  I have to go to the menu and use the mouse.
> >
> >
> >
> >
> > -----Original Message-----
> > From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> > To: [email protected] <opendx-
> > [EMAIL PROTECTED]>
> > Date: Saturday, July 07, 2001 7:22 AM
> > Subject: Ad: Re: [opendx-users] Opendx for windows/nt
> >
> >
> > >
> > >                    "Gregory D Abram"
> > >                    <[EMAIL PROTECTED]>                    Til:
> > [email protected]
> > >                    Sendt av:                             cc:
> > >                    [EMAIL PROTECTED]        Emne:
> Re:
> > [opendx-users] Opendx for windows/nt
> > >                    on.ibm.com
> > >
> > >
> > >                    07/06/01 17:36
> > >                    Vennligst send svar til
> > >                    opendx-users
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >> I see 4.1.3 is available in binary form from OpenDX.org  - is
> there
> > a
> > >> problem with it?
> > >
> > >> Greg
> > >
> > >
> > >actullay, yes (see below), and it seems to be that I'm not teh only
> > one.
> > >
> > >Hey:
> > >
> > >I' m trying to install Opendx Ver 4.13 on Windows NT with Exceed
> 6.1.
> > I
> > >installed it using the wizard and updated the *.bat files, as
> > mentioned.
> > >dx seems to work, but I've problemen with some of the modules, e.g.
> ,
> > >trying to l open accumulate.net
> > >I'm geeting the following error list. Parts of the visualtion
> > actullay do
> > >work.
> > >
> > >Memory cache will use 224 MB (14 for small items, 210 for large)
> > >
> > >port = 1900
> > >
> > >Begin Execution
> > > 0:  worker here [263]
> > >
> > > 0:  ERROR:  Executive: function does not exist
> > >Begin Execution
> > > 0:  WARNING:  Function return values are ignored: Executive
> > >
> > > 0:  ERROR:  Executive: function does not exist
> > > 0:  WARNING:  Function return values are ignored: Executive
> > >
> > > 0:  ERROR:  Executive: function does not exist
> > > 0:  WARNING:  Function return values are ignored: Executive
> > >
> > > 0:  ERROR:  GetLocal: function does not exist
> > > 0:  ERROR:  ForEachMember: function does not exist
> > > 0:  ERROR:  GetLocal: function does not exist
> > > 0:  ERROR:  SetLocal: function does not exist
> > > 0:  WARNING:  Function return values are ignored: SetLocal
> > >
> > > 0:  ERROR:  SetLocal: function does not exist
> > > 0:  WARNING:  Function return values are ignored: SetLocal
> > >
> > >ERROR: GetLocal:  Operation not implemented: function does not
> exist
> > > 0:  opening file 'D:/PROGRA~1/Opendx/SAMPLES/DATA/cloudwater.dx'
> > >ERROR: ForEachMember:  Operation not implemented: function does not
> > exist
> > > 0:  WARNING:  /main:0/Collect:2 contains only NULL and/or invalid
> > inputs
> > >
> > >
> > >has somebody an idea
> > >
> > >Peter Gauer
> > >
> > >
> > >
> > >
> >
> >
> >
> >

Reply via email to