A few months ago,
in a thread about something else
you posted the contents of one of your shortcuts,
(maybe it is even the same program)
Within it you find the full and complete command that is executed when you click that shortcut:
Exec=env WINEPREFIX="/home/myuser/.wine" wine C:\\\\windows\\\\command\\\\start.exe /Unix /home/myuser/.wine/dosdevices/c:/ProgramData/Microsoft/Windows/Start\\ Menu/Programs/Gamestudio\\ A8/SED\\ Script\\ Editor.lnk
… full path to the program, parameters and all
This specific one is rather complicated
as it calls the program as if you opened the start menu in windows, then select the program, then click on it to start it.
… which is more complicated than it needs to be
anyway …
When you run it from a terminal,
as you did,
you can see the messages (probably quite a lot) which can help figuring out what went wrong.
You can (and probably should) first run
winecfg
and choose to run the wine app in a window instead of full screen
This might make it easier to act on the app when it does not work - just close the window …