Apparently this feature has been on around for DX on Windows for a while. I see this behavior with an old version (4.1.1) on an NT machine with 1.5 GB RAM. I just chalked it up to having an old version that couldn't handle more than a 1024 MB. It wasn't critical for my applications on that machine and I run bigger DX jobs on Unix machines with a lot more memory.
Please respond to [email protected]
Sent by: [EMAIL PROTECTED]
To: [email protected]
cc:
Subject: Re: [opendx-users] Windows rabbiticity
More info on our other conversation:
After setting the Environment Variable "DXMEMORY" to "1000", when I
start openDX by clicking the openDX application icon or shortcut, the
server will autostart as expected. However, double-clicking .net
icons still causes the "Connection to server localhost has been
queued" message (and no running server until I hand-start it). Still
mystified by that, but this is just FYI, as I know you said you
aren't having this problem. The error dialog appears on top of the
openDX logo window after the UI has opened up. I tried setting the
ENV VAR first as a user ENV VAR, then today, redid it as a system ENV
VAR, rebooted, and tried again. Nope, same (mis)behavior. As before,
the solution is to open the Connection:Start Server:Options dialog,
set memory to 1000 then the server launches and runs. This only seems
to be a problem when launching by double-clicking a .net icon as with
the ENV VAR in place, launching openDX by clicking the icon starts
the server with the designated amount of memory (checked via the
Message Window's startup message).
The obvious big advantage to clicking .net icons, is that DX then
"homes" to that startup directory instead of to the Program
Files/OpenDX directory as when launching from the openDX icon. The
latter necessitates navigating/changing filters to get to the data
directories for the current project.
--
Chris Pelkie
Managing Partner
Practical Video LLC
30 West Meadow Drive, Ithaca, NY 14850
