I've been using Directory Opus 9 for over 2 years. I had created some toolbar buttons to start Take Command and Take Command Console (powerful alternatives to CMD.EXE). With Directory Opus 9 the "Start in" directory always defaulted to the directory of the current lister. I upgraded to Directory Opus 10 and now the same toolbar buttons default to starting in C:\Windows\System32.
I modified my toolbar buttons to prefix "cd {sourcepath}" (without the quotes) before invoking Take Command. For example:
cd {sourcepath}
"C:\Program Files\JPSoft\TCMD11x64\tcmd.exe"
now gives me the behaviour I had with DOpus 9 (which didn't need the "cd {sourcepath}").
Is this a change/bug in DOpus 10, or should I have always been explicitly specifying a "Start in" folder with DOpus 9, previously?
It's a change to bring Opus into line with what later versions of Windows do, and for for security reasons. (Not sure but I think it may only be done on Vista and Win7.)
(Having System32 as the CD makes it less likely programs will pick up the wrong DLLs by mistake/trickery, and also ensures the CD is read-only for UAC and standard-user accounts. Also some things now assume System32 will be their starting directory as that's what Explorer does.)
The Prefs. -> Misc. -> Advanced: def_func_cd_sourcedir setting can be used to get back the old behaviour if you need it (but it's better to update anything that depended on it, as you've done).
