If you installed the programs through Wine they will appear in Applications|
Wine| Programs menu. If you installed them through Wine-Doors, then they may
appear in the Ubuntu| Applications menu mixed in with your Linux programs.

To put a program shortcut onto the desktop or in the panel whether it is in
Linux or in Wine, right-click on the icon in the menu and choose either: Add
this launcher to panel or Add this launcher to desktop. The first one will put
an icon on the panel at the top and the second option will add an icon to the
desktop.

You can also add a Link or shortcut from the C: drive. Go to Applications| Wine|
Browse C:\ Drive. Then navigate to the proper folder and choose the exe file
that you want to make the shortcut or link to. Right click on it and choose Make
Link. The link will appear in the folder window along with the exe file. Just
drag and drop that link to your desktop.

Sorry I was not more clear, I did not do an install with Wine ,( i have
not figured that one out either ) I just copied and pasted the programs
folder from a win install>> None of methods you mentioned seem to
work...I get errors with the apps...

I did select "add Application" in wine but it does not seem to do
anything....is this only for installer exe?

I have a similar issue with a program I use..

The program is a stand alone .exe file - that runs without
installation.. Is there any way to include a shortcut to this file in
the wine menus and submenu's? Cori is having the same trouble I've
been having...

Will this help?
http://frankscorner.org/

You can't just copy your programs because of the way Windows works. Programs
have shared libraries called dlls and they are kept track of in the Windows
registry.

The only way to use Windows programs in Linux is to install them in Wine or in a
virtual machine.

Self executable exes will run only if you install Wine first. This gives the
basic Windows compatibility layer to run exe files. If Wine is installed then
clicking on it will cause Wine to run the file.

As I said to Cori, you cannot just drag Windows folders from a Windows machine
and expect them to run in Linux. Most Windows programs store information in the
registry and have libraries in the Windows sub folders that make it impossible
to copy them even from one Windows machine to another. This is intentional to
prevent copyright infringement.

Linux does not work the same as Windows. Suffixes such as exe are meaningless
and for the most part you don't need to append a suffix in order for Linux to be
able to use it. For example, my_text_file.txt is the same to Linux as
my_text_file. Try this with Windows and it will not be able to use the file.

If you have Wine installed then you can right click and create a link as I
mentioned to her. In this case you should store them in their own folders in
your home folder.

One sure could debate on the wisdom of the Windows registry...........

I spent many years with Amiga's where the programs called for needed
libraries that were kept in certain directories. No program ever had
to re-write a registry, nor a system library to use the system
libraries. The advantage is that random programs would never kill the
system libraries by installing it's own custom library while re-
writing the registry and cutting off the previously installed
programs to the libraries they required, as Windows does.

The result is that while Windows is constantly re-writing itself in
individual computers, with too-frequent internal mistakes gradually
crippling the computer, other OS's that use static libraries to
operate, say the hard drive, or the sound chips; fly along without
using longer and longer re-written or improperly crippled dll's. I'll
long remember with fondness the Amiga's 3rd party program 'Scout'. It
would run in the background and when a new program had a problem, you
would get a report that such and such library was looked for in such
a directory and failed to be found. It was a snap to find the stray
library or other element and move it to the proper system location;
then restart the program to see it working perfectly.

Unlike Windows where a program simply refuses to work and crashes on
the user without giving an understandable explanation of what failed
in the process.

I most strongly suspect that Microsoft mainly keeps the old registry/
dll design because of it's very lucrative and pricey Windows
Technician certification programs that must be kept in operation to
keep world-wide Windows based computers operating with their needed
constant individual OS repair.

I know the very technical can state the above in other terms. But the
essence is why Windows is such a flawed, self-destroying OS.

I give up arguing with people about Windows because the anti crowd will
always find a way to put dampers on any system, but dlls allow shared
resources for MS programs that other wise would be massive if every
piece of software needed its own.

Is my recall correct about Windows writing to them [libraries]
instead of leaving them as 'original' ??

I never quite understood why some other OS's were able to use static
libraries for such basics as accessing the hard-drive, or other
standard OS operations. While Windows insists upon customizing it's
dynamic libraries through programs modifying the libraries.

In both approaches, all programs share the libraries. But with static
libraries, they don't have to attach to them or modify them, to use
them. The programs just call for, and use the OS standard libraries
to interface with the computer hardware. Otherwise, the program does
what it must, manipulating data within its program; then calls for
the use of the printer through the printer library, or whatever
hardware it needs to use to get the results on the screen or out of
the computer in some manner.

The program wants to print, the OS says this is the printer to use,
here are the drivers to use, here is the port you will print through,
use the print library, send the data....... The program doesn't have
to attach to a static library at all, nor use a registry of where one
is; just send through it in the central library directory. This is
why you can re-locate a Mac or an Amiga program to another directory
or drive and it still continues to work.

Am I mistaken?