Suhaib,
I did what you specified, below. (i.e. opening in a DOS shell). If I
do that, and I wait awhile, I get the bug I was getting before:
Cannot open connect stream.
dTRANS(SocketINETGetAddr): tnamebysocket() failed
TRANS(SocketINETConnect): TRANS(SocketINETGetAddr) () failed
TRANS(Open): transport open failed for tcp/localpc:0
Error: Can't open display: localpc:0.0
This is the same bug I had before, but it comes up later, which is
strange. This would suggest that there is something wrong with the files I
copied oven from the ~/opendx/bin/Exceed as per the instructions in the
readme.
Mike
On Wed, 11 Oct 2000, Suhaib M. Siddiqi wrote:
> HOw about instead of double clicking on the batch file, you open a DOS shell
> (comamnd shell)
> and cd to opend\bin directory and type menu at the command prompt.
> See errors it returns. if nothing happen, then still it must have set the
> correct PATHS,
> now you can type dxui to see if DXUI Window comes up or reeeturns an error.
>
> Whatever errors you see cut adn paste them in your post
>
> Suhaib
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] Behalf Of Michael E
> > Lasinski
> > Sent: Wednesday, October 11, 2000 7:40 PM
> > To: [email protected]
> > Subject: RE: [opendx-users] Running on Windows 2000 with Exceed V6.2
> >
> >
> >
> > Sorry,
> >
> > By nothing I mean there is no display of the opendx windows. When I
> > try to run the batch file, I just double click on it. That brings up a dos
> > Window and starts up exceed. Before the errors would appear on the dos
> > window, but it wouldn't return to a command prompt. Now no error message
> > appears and it doesn't return to a command prompt. This suggests that
> > something may be running, but I can't see it. However nothing related to
> > Data Explorer appears on my status bar. (The bar on the bottom of the
> > screen where all of the current applications and open folders
> > appear). Also I run data explorer similarly on a different computer, and
> > it works to a point where the problem is with the DLL's. In that case
> > the command prompt window appears, but it never goes to the command
> > prompt, which for Windows 2000 is pretty standard. Is there anything more
> > you need to clarify my situation?
> >
> > Mike
> >
> > On Wed, 11 Oct 2000, Suhaib M. Siddiqi wrote:
> >
> > >
> > >
> > > > -----Original Message-----
> > > > From: [EMAIL PROTECTED]
> > > > [mailto:[EMAIL PROTECTED] Behalf Of
> > Michael E
> > > > Lasinski
> > > > Sent: Wednesday, October 11, 2000 6:19 PM
> > > > To: [email protected]
> > > > Subject: RE: [opendx-users] Running on Windows 2000 with Exceed V6.2
> > > >
> > > >
> > > >
> > > >
> > > > Thank you for the fix. Now I don't get that error
> > message. Instead now
> > > > Exceed starts to run, but I don't get the familiar menu of opendx (i.e
> > > > edit visual program, run visual program, etc.) I am curious
> > what is going
> > > > on now?
> > >
> > > Then what do you get? Nothing? No errors? Command prompt returns doing
> > > nothing
> > > after you excute a batch file?
> > >
> > > just get nothing as an explaination won't give any clues to
> > annyone to help
> > > you.
> > >
> > > >
> > > > In response to what Suhaib asked me, the files I copied
> > over to the
> > > > exceed directory, is everything in D:\OpenDX\bin\Exceed\user
> > as per what
> > > > is instructed in the readme. Now one problem is that I was unable to
> > > > install everything on C:. Instead I had to install everything
> > on D:. For
> > > > all the paths that I could find, I changed stuff to D:, are there some
> > > > things that are hidden from me that make installation on to
> > D: impossible?
> > > >
> > >
> > >
> > > Should not be... all you need is to edit batch files. Unless under
> > > Options, on your Win2K you have "hide files" options turned on.
> > >
> > > Suhaib
> > >
> > > > Mike
> > > >
> > > > On Wed, 11 Oct 2000, Lloyd A Treinish/Watson/IBM wrote:
> > > >
> > > > >
> > > > > I have seen this when DISPLAY is set to localhost:0.0. Try
> > setting it
> > > > > localpc:0.0. For good measure have /etc/hosts with
> > > > > 127.0.0.1 localpc
> > > > > 127.0.0.1 localhost
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > "Suhaib M. Siddiqi"
> > <[EMAIL PROTECTED]>@opendx.watson.ibm.com on
> > > > > 10/06/2000 07:30:18 PM
> > > > >
> > > > > Please respond to [email protected]
> > > > >
> > > > > Sent by: [EMAIL PROTECTED]
> > > > >
> > > > >
> > > > > To: <[email protected]>,
> > > > > <[email protected]>
> > > > > cc:
> > > > > Subject: RE: [opendx-users] Running on Windows 2000 with
> > Exceed V6.2
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > > I am trying to run opendx on Windows 2000 with Exceed
> > v6.2. I have
> > > > > > followed all of the instructions in the readme, but when I
> > > > start the menu
> > > > > > batch file, I get the error:
> > > > > >
> > > > > > Cannot open connect stream.
> > > > > > TRANS(SocketINETGetAddr): tnamebysocket() failed
> > > > > > TRANS(SocketINETConnect): TRANS(SocketINETGetAddr) () failed
> > > > > > TRANS(Open): transport open failed for tcp/127.0.0.1:0
> > > > > > Error: Can't open display 127.0.0.1:0.0
> > > > > > ----------------------------------------------------
> > > > > > Program finished - Press enter to close the console
> > > > > >
> > > > > > What exactly does this error mean?
> > > > >
> > > > > It means your Exceed has troubles starting X-server. Did you
> > > > first try to
> > > > > start
> > > > > Exceed X-server then use batch file to start OpenDX?
> > > > >
> > > > > > Just to make it clear, I did copy the
> > > > > > proper files into the exceed directory as well as edit the
> > > > .bat files so
> > > > > > that they have the right paths in them.
> > > > >
> > > > > Which files you copied to Exceed directory?
> > > > >
> > > > >
> > > > > Suhaib
> > > > >
> > > > >
> > > > > >
> > > > > > Thank you for your help.
> > > > > >
> > > > > > Michael Lasinski
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > >
> > >
>
>
