Be happy to Sidki. Here's my first go at it. If anyone has changes or suggestions, finds errors, etc. please contribute. Perhaps members will try this install on their Linux distros and can provide more input.
Please let me know if you have any questions.
The following instructions are based on running Proxomitron on openSUSE 11.1 and KDE 3.5.10.
For other
Desktop
Environments (ie. KDE4, XFCE, GNOME, etc.) the basic concepts should be similar. There are so many distros, with a multitude of
DEs, and such enormous configuration possibilities that these instructions may need to be tweaked for other systems.
Proxo runs in Linux under Wine (or a similar translation layer). For more information about Wine visit:
WineHQ -
http://winehq.org/
Wine: Wikipedia -
http://en.wikipedia.org/wiki/Wine_(software)
Wine-Doors: Wikipedia -
http://en.wikipedia.org/wiki/Wine-Doors
Wine should be available for installation from a distribution's repositories. If not, it can be compiled and installed from source. If further assistance is required then consulting the distro's docs and forums and online searching may prove valuable.
On openSUSE the default root installation automatically includes these directories:
/usr/bin/wine, /usr/lib/wine, /usr/bin/X11/wine, /usr/share/wine, /usr/share/man/man1/wine.1.gz and
/home/<xxxx>/.wine (where
<xxxx> is the user directory name).
Wine-Doors could also optionally be installed (see above link).
Once Wine is installed, download Proxomitron.exe to the /home directory, where 'exec' needs to be permitted in /etc/fstab (since /home is designed for user access it should be ok by default).
When left clicking on the .exe for execution your distro will probably ask you to tell it how to open the .exe file. Tell it "wine" (without the quotes). Linux cannot and does not know how to handle Windows executables by default. That's definitely a feature! Again, these details may vary between distros.
Wine should install, using the familiar dialog boxes as it does in Windows, in a location similar to this:
/home/<xxxx>/.wine/drive_c/Program Files/Proxomitron Naoko-4.
This is where the user accessible Proxo folders, configurations, and other files reside.
Create symlinks to the Proxo executable as desired if not automatically created as they are with KDE 3.5 on openSUSE (file locations may need to be bracketed something like this:
env WINEPREFIX="/home/<xxxx>/.wine" wine "C:\Program Files\Proxomitron Naoko-4\Proxomitron.exe" (quotes needed because of blank spaces).
The distro should natively know how to do this. 'env WINEPREFIX=' tells the distro to open (execute) the file via Wine. This is performed automatically when installing/linking to KDE's 'K Menu'.
Other programs installed to run under Wine will be similarly located. Take a look in the Wine directory and become familiar with it. You'll find the 'Windows' structures located here
/home/<xxxx>/.wine/drive_c/windows.
Notice that '.wine' is a hidden directory. This can be made visible by default, if desired.
A distro can be configured to associate the .exe file extension (and/or others) with Wine. This is strongly
NOT recommended for security reasons.
Proxomitron can be made to load automatically at boot. Under KDE 3.5 simply symlink from "The Proxomitron.desktop" in
/home/<xxxx>/.local/share/applications to
/home/<xxxx>/.kde/Autostart. Check with your DE & distro for something similar.
Under openSUSE/KDE 3.5 Proxo runs as it does under Windows with the icon displayed and functional in the taskbar's notification area (aka system tray). Desktop and menu links were created automatically, so openSUSE's Wine/Proxo install was simple and straightforward. Again, details may vary from distro to distro.
Proxomitron should run fine in a user account. If it doesn't then there is a problem.
If problems are encountered try executing Wine and/or Proxo as user in a console/terminal (try root, if necessary, afterwards). This will provide information that may help resolve any issues.
So basically: On openSUSE 11.1/KDE 3.5 install Wine then install Proxomitron. Configure Proxo & the browsers appropriately.
There are other other Wine related methodologies that the user can learn over time.
Do not run as root (always good advice)!!!