CrossOver Support - Community Forums

One application I use has an option to shell to the Command Prompt, but that appears to be a no-op when running in CrossOver. Further testing indicates that if a specific action command is sent to the command prompt (such as REN or ERASE), that action is in fact accomplished, but other commands such as PAUSE (which waits for any key) return immediately. In no case does a Command Prompt window appear.

Then I tried creating a link directly to the bottle's version of windows\system32\cmd.exe through Run Command, which sometimes opens the Command Prompt window, but sometimes is a no-op. The saved command in a Launcher for CMD.EXE never seems to do anything.

Running WINECONSOLE CMD seems to always open a Command Prompt, except when saved in a Launcher.

I'd appreciate any advice how to get CMD.EXE to open reliably.

Then I tried creating a link directly to the bottle's version of windows\system32\cmd.exe through Run Command, which sometimes opens the Command Prompt window, but sometimes is a no-op. The saved command in a Launcher for CMD.EXE never seems to do anything.

I think you have found a bug on our end there. I am filing a bug with our internal bug tracker on the matter.

One application I use has an option to shell to the Command Prompt, but that appears to be a no-op when running in CrossOver. Further testing indicates that if a specific action command is sent to the command prompt (such as REN or ERASE), that action is in fact accomplished, but other commands such as PAUSE (which waits for any key) return immediately. In no case does a Command Prompt window appear.

I don't have any suggestions about this, but hopefully someone else can chime in.

Thanks,
Anna