|
| | |
Group: Forum Members
Last Login: 6/24/2008 1:31:23 PM
Posts: 2, Visits: 2 |
| Hi all,
I'm trying to run two instances of Freelang's Spanish dictionary (I'd like to have one for Spanish-to-English and one for English-to-Spanish) on my 32-bit Vista Ultimate system, on which I run the "real" Administrator account (not a user account with admin priveleges). I've tried everything I can think of doing: I copied the "Dictionary" folder from program files to the C: directory so there'd be two instances. Then I renamed one of the executables "dictin.exe" (from dict.exe) so that the processes would have different names (it does show up in taskmanager as "dictin.exe" when I run it. After starting "dictin.exe", I used an autohotkeys script (winsettitle, Search words,,dictin) to rename the window to dictin. So, neither the process name nor the name presented to the window manager is the same as the default. I read somewhere that runas works better if you run it with a non-admin account, so I used a regular user account (symbic1) to execute the following from an administrator shell: (runas /env /user:symbic1 "C:\Program Files\Dictionary\dict.exe"). I know the dictionary tries to start, because if I'm not in the C:\Program Files\Dictionary directory I get a weird error message about missing string files. However, when I cd to the C:\Program Files\Dictionary directory and run the same command, nothing happens. I don't understand why it won't work: I'm running different executables with different names, which show up with different titles in the desktop environment, and I'm trying to run one as administrator and one as a regular user. I've even tried running the two instances on different processor cores, but of course that didn't work. Running the dictionary with the runas command works when no other instance of the dictionary is open, but it fails otherwise. Finally, omitting the /env parameter from runas makes the dictionary not run at all, regardless of whether there's another instance open. Does anyone know how to do this?
Thanks,
Kent Smith
|
| |
| |
|