wine users - May 2012 - Creating a working desktop shorcut for Rosetta Stone 3.4.5

Has anybody had any luck making a working desktop shortcut for Rosetta Stone
3.4.5?  I can get the program to run smoothly, but whenever I try to create a
desktop application launcher, no matter how I set it up, it always flat out
doesn't work, or it throws some sort of fatal error inside of Rosetta Stone.

I've tried setting it to the wine prefix, then a command path.  I've
tried crating a link in the .wine folder and then moving that link to the
desktop.  No matter what I try, I can't seem to get it working.  This is not
a new problem, but I wonder if anyone has any new solutions to it.

When you create your link you need to make sure the working directory
of that link is set to where the .exe is. Most windows programs care
about it while linux ones don't (that's why it doesn't get set
usually)

Otherwise you can just write a small shell script setting the correct
working directory (cd ~/.wine/...) and calling wine. Then you can just
make a link to that script to make it all work easily. (this also let
you do more things like redirecting logs to file, ... if the need
arise)

2012/5/28 Guan <wineforum-user at winehq.org>:
> Has anybody had any luck making a working desktop shortcut for Rosetta
Stone 3.4.5? ?I can get the program to run smoothly, but whenever I try to
create a desktop application launcher, no matter how I set it up, it always flat
out doesn't work, or it throws some sort of fatal error inside of Rosetta
Stone.
>
> I've tried setting it to the wine prefix, then a command path.
?I've tried crating a link in the .wine folder and then moving that link to
the desktop. ?No matter what I try, I can't seem to get it working. ?This is
not a new problem, but I wonder if anyone has any new solutions to it.
>
>
>
>
>

M C wrote:
> When you create your link you need to make sure the working directory
> of that link is set to where the .exe is. Most windows programs care
> about it while linux ones don't (that's why it doesn't get set
> usually)

To describe the situation more technicaly,
you could say that windows programs are badly designed
and they crash/disfunction because they don't check where the program was
launched from.