there are some ways around this one, one is using a second thread to launch what you want, the second thread of course must start instantly (ie: delay like u encountered)
Win2k and Xp can use...
/run cmd /c start .
^ that well leave the dos box open tell . opens an explorer if thats delayed then the dos box is delayed
/run cmd /d /c start "" explorer "."
^ that fixes that
/run is mircs run command
cmd /d /c is a dos session
start "" is a dos command that starts other threads
explorer is well guess what that is lol
"." is the path
start can actually start any app so you might have
/run cmd /c start "" "C:\Program Files\Macromedia\Dreamweaver MX 2004\Dreamweaver.exe"
^ that lets mirc keep going even when Dreamweaver takes 10 seconds to start.
So you getting mirc to start a thread which itself starts another thread
[edit] hmmm just posted this and now discovered that calling dreamweaver directly from mirc doesnt freeze mirc up either, but i think the princible is still there, just i dont have a app that locks the pc up to test with.
Last edited by DaveC; 21/03/05 08:53 AM.
