Posted by
Jeff Brandenburg on
URL: http://imagej.273.s1.nabble.com/Re-ImageJ-startup-times-Win2K-WinXP-tp3702357p3702360.html
Didn't you see the note about ImageJ Genuine Advantage? :-)
Actually, I believe Wayne added code some time ago to deal with a
Windows problem where new images opened in new ImageJ processes instead
of opening in the existing instance of ImageJ. When ImageJ starts up
on Windows, it checks to see whether there's already another running
instance listening on this local port, and hands off the startup
arguments if so. Right, Wayne?
The code in question is in ij.ImageJ.main(), if you're curious.
On Jun 30, 2006, at 11:52 AM, Jim Passmore wrote:
> ImageJ Interest Group <
[hidden email]> wrote on 06-30-2006
> 06:08:51
> AM:
>
>
>> It could be to do with the firewall specifically. The newer versions
>> of
>> ImageJ listen on port 57294. If the firewall is blocking this port it
> would
>> introduce a delay. Try configuring the firewall to allow ImageJ to
>> use
> that
>> port.
>>
>> Jon
>
> Now I'm curious. Why is ImageJ listening to a port at all? Am I
> missing
> something?
>
> Jim
>
>
> ----------------------------------------------
> Jim Passmore
> Research Associate
> Sealed Air Corporation
>
[hidden email]
> 864-433-2927 voice
> 864-433-2205 fax
> ----------------------------------------------
>
--
-jeffB (Jeff Brandenburg, Duke Center for In-Vivo Microscopy)