Monday, August 30, 2004
LA3D viewer, second instance
> I'm using a Windows machine, and that's pretty much all
> that I have available to me. I can't seem to get Windows
> to launch a second instance of LA3D so that I can compare
> the two models side by side. I think that's a function of
> Windows, since it sees LA3D as already launched. Can I
> open a second viewer window from the first instance of
> LA3D (if so I couldn't figure out how), or load 2 CFM
> datasets simultaneously into the same viewer (which I also
> couldn't figure out how to do, if it's possible)?
Windows is fine as it is the officially supported platform for LA3D.
As my main machine runs linux, I myself test for that mostly. I had
incorrectly assumed that windows would start up a second program
instance just as linux does. Sorry for the confusion and I will update
the instructions on he web page to reflect this. Fortunately, there is
an easy workaround. Just install LA3D a second time, to a different
location and then launch the second instance from
there. Alternatively, to save diskspace perhaps, you could also just
copy the LA3D.exe file in the installation directory to, say,
LA3D_2.exe in the same directory and double-click on the copy. Perhaps
the LA3D developers come up with a proper solution soon.
> that I have available to me. I can't seem to get Windows
> to launch a second instance of LA3D so that I can compare
> the two models side by side. I think that's a function of
> Windows, since it sees LA3D as already launched. Can I
> open a second viewer window from the first instance of
> LA3D (if so I couldn't figure out how), or load 2 CFM
> datasets simultaneously into the same viewer (which I also
> couldn't figure out how to do, if it's possible)?
Windows is fine as it is the officially supported platform for LA3D.
As my main machine runs linux, I myself test for that mostly. I had
incorrectly assumed that windows would start up a second program
instance just as linux does. Sorry for the confusion and I will update
the instructions on he web page to reflect this. Fortunately, there is
an easy workaround. Just install LA3D a second time, to a different
location and then launch the second instance from
there. Alternatively, to save diskspace perhaps, you could also just
copy the LA3D.exe file in the installation directory to, say,
LA3D_2.exe in the same directory and double-click on the copy. Perhaps
the LA3D developers come up with a proper solution soon.
Comments:
<< Home
Thanks for the input. I ended up copying small groups of
files into a third folder (for instance, all of the Death
Valley faults), so that I ended up with a dozen or so
fault representations and alternatives that I could toggle
back and forth between.
files into a third folder (for instance, all of the Death
Valley faults), so that I ended up with a dozen or so
fault representations and alternatives that I could toggle
back and forth between.
The LA3D.exe that one downloads from SCEC launches an installer, so changing the name of the LA3D.exe to LA3D_2.exe won't help with the above mentioned problem. As the installation proceeds, you'll need to specify a new location for the second installation of LA3D. The default is C:\Program Files\LA3D_1.0.1, you could change this ti C:\Program Files\LA3D_2_1.0.1, for example. You'll also need to change the name of the Start Up Menu Folder, the default is LA3D, you can use LA3D_2, or something similar.
# posted by 
: August 30, 2004 8:21 PM
: August 30, 2004 8:21 PM
Thanks for the clarification. When I copied the actual LA3D.exe, not the installer, to secondLA3D.exe, I could run a second instance by launching the copy.
Post a Comment
<< Home
