I am running X-windows using Cygwin for remote access to other machines.
I tried turning the firewall on/off with apparently no effect -- the following
are exceptions to the firewall anyway: McIdaasADDE, mcidasv, mcservl
Here is the output from mcservl:
C:\Program Files\McIDAS-V>cd adde
C:\Program Files\McIDAS-V\adde>cd bin
C:\Program Files\McIDAS-V\adde\bin>mcservl
McIDAS interactive ADDE server
Remote connections blocked
PORT= 8112
PATH= /cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS:/cygdrive/c/WINDOWS/
ystem32/Wbem:/cygdrive/c/progra~1/pcgrads/win32:/cygdrive/c/WINDOWS/system32/Wi
dowsPowerShell/v1.0:/cygdrive/c/Program Files/QuickTime/QTSystem/
MCPATH= (null)
Waiting for connections...
I then exited the Cygwin X-windows that were running (and X server) to see if that helped,
that did not -- still blocked.
I added Windows Remote Management to the Firewall Exceptions list...that did not help either.
I tried adding port 8112 to the Exceptions and that did not work -- but I am not postive
I added that exception correctly -- tried using TCP then UDP.
Suggestions?
Error connecting to ADDE data set
Re: Error connecting to ADDE data set
Mike, please take a look at this post regarding Cygwin:
viewtopic.php?f=24&t=338
McIDAS-V should be started only after you are sure that all other Cygwin processes have been halted. If other processes are using cygwin1.dll, quitting the X-Server may not unload the library from memory.
Dave
viewtopic.php?f=24&t=338
McIDAS-V should be started only after you are sure that all other Cygwin processes have been halted. If other processes are using cygwin1.dll, quitting the X-Server may not unload the library from memory.
Dave
Re: Error connecting to ADDE data set
I restarted my computer and started McIDAS-V first (and only!) with the same problem.
I am guessing that something is grabbing the dll file on startup -- but I have no idea what.
Mike
I am guessing that something is grabbing the dll file on startup -- but I have no idea what.
Mike
Re: Error connecting to ADDE data set
Mike, one last thing you can try for Cygwin testing:
If you search for all "cygwin1.dll" files on your computer (using Windows "Find File") and are comfortable with the process, you can rename/move them so that the one in McIDAS-V/adde/bin is the only one left, then restart Windows. This will guarantee that the McIDAS-V binaries load the correct version. If this works, you may choose to replace the previously moved files with the one from McIDAS-V and see if your Cygwin X-Windows client still works. It is easy to get into version problems with cygwin1.dll, so please only proceed with this if you are comfortable with it!![Smile :)](./images/smilies/icon_e_smile.gif)
If you search for all "cygwin1.dll" files on your computer (using Windows "Find File") and are comfortable with the process, you can rename/move them so that the one in McIDAS-V/adde/bin is the only one left, then restart Windows. This will guarantee that the McIDAS-V binaries load the correct version. If this works, you may choose to replace the previously moved files with the one from McIDAS-V and see if your Cygwin X-Windows client still works. It is easy to get into version problems with cygwin1.dll, so please only proceed with this if you are comfortable with it!
![Smile :)](./images/smilies/icon_e_smile.gif)