Multiple instances

[jjanis]

I have a problem with 2008. Whenever I double click a file another instance of AutoCAD software opens. I have to wait for the software to open again and again. Has anyone else encountered this and how can I fix it? thanks

[jaberwok]

Set SDI = 0.

[jjanis]

I already tried that and it doesn't work for this problem.

[jaberwok]

See if this thread helps.

[irneb]

Jabberwok, that's probably exactly what's happening here. If you have the acad.exe assigned to a DWG it will always open a new instance of acad.

See this thread instead: http://forums.augi.com/showthread.php?t=98023

[jaberwok]

Hmm, maybe, maybe not.
The most important part seems (to me) to be the DDE message "%1" (takes you back to the days of DOS ). Acad could open multiple files in one application window for several releases before the DwgLauncher function was introduced.

[irneb]

That might have been true (not sure DDE was available in DOS though, I think you're referring to Win95 or even Win3). Maybe you are thinking of the %1 which was (and still is) a placeholder for the 1st argument to a BAT file.

The if you simply use %1 as an argument to call an EXE then it's as if you typed it all into a Console DOS prompt. If you use DDE, then windows opens the EXE and sends it a command to open the file.

Anyhow, that's how it's supposed to work. For some reason we picked up that (at least 2008 ) caused multiple sessions with either the normal BAT like call or the DDE method. Maybe ADesk changed something there? The only way I can get a MDI session running is using the Launcher or opening through ACad itself.

[Ed Jobe]

If you have the option shown below enabled, you can get the same behavior.

[jaberwok]

Maybe you are thinking of the %1 which was (and still is) a placeholder for the 1st argument to a BAT file.

I was. It was supposed to be a jocular aside.

[jaberwok]

If you have the option shown below enabled, you can get the same behavior.

The same as what?
I have had "single-click to open" set on every machine I've used since starting with NT4 (that must be the best part of 100 machines). I've not noticed any effects on SDI/MDI behaviour.