On Sat, 25 Dec 2004 16:49:46 +1300, SnapafunFrank wrote: > Rodolfo Medina wrote: > > >> Does anybody have any experience about Wine, how to install it and how to > >> make it work?
I'm not an expert because I've never really had any problems using wine. However, I did notice a couple of things in your post. I have no idea how important they are, however. > >> I installed Wine in order to run MS Word with it, > >> since *unfortunately* in job applications it is usually requested and used > >> the .doc format > >> and neither kword nor Open Office kwriter nor even abiword manage to > >> properly read and edit MS Word documents. I've found that MSWord doesn't properly read and edit MSWord documents on Windows systems either. Check your documents out on another MSWord installation -- same release, same Windows, but maybe a different printer installed. Things move around, especially in-line graphics (supposedly anchored) on any document and pagination in large documents. OTOH, I've had excellent results working with MSWord documents on Linux systems with OpenOffice.org Writer (OO). I now do all MSWord stuff using OO (I get it in MSWord, open the file in OO, do whatever needs to be done, and convert it back to MSWord). No one has noticed the difference. I had no problems getting MSWord to work under Wine. I just refuse to use it because it's such crummy word processing software. > > That means just Wine: then I tried to install MS Office 2000 with WineTools > > with no success. Here is the whole procedure I followed: > > > > > ---------------------------------------------------------------------------- > > - > >> From Wine web site: www.winehq.org I downloaded the file > > Wine-20041201.tar.gz. Any particular reason you are installing from source instead of installing the rpm? The only problems I've ever had with wine were connected with installing from source. I learned a lot about it (because it found a number of things wrong with my system which forced me to correct them), but now I do all the installations from binaries. > > Some fake Windows directories must be created, to hold any .ini files, > > DLLs, > > start menu entries, and other things your applications may need to install. > > Where would you like your fake C drive to be placed? > > (default is /home/rodolfo/.wine/drive_c) Just for the record, is where you're trying to install MSWord also a C: drive from its point of view, or is it a D: drive? Remember, wine is going to act as if /home/rodolfo/.wine/drive_c is the real C: drive and any time the installation process or MSOffice asks for something on C:, that's where it will go -- not to /mnt/windows. > > Configuring Wine for a no-windows install in /home/rodolfo/.wine/drive_c... > > err:wave:OSS_WaveOutInit /dev/mixer1: No such file or directory > > Xlib: extension "XFree86-DRI" missing on display ":0.0". > > /home/rodolfo/.wine updated successfully. This was one of the problems I had when installing from source. I was not able to get wine to run correctly until I resolved all the /dev issues connected with the sound system. You need /dev/mixer1. > > Created /home/rodolfo/.wine/config using default Wine configuration. > > You probably want to review the file, though. The critical things in this file are to have your paths correctly set so that wine knows exactly where to find the mount point for each drive and to correctly identify your installed printers (the name that's in /etc/printcap). I found it had already set up the necessary DLLs for MSWord to work properly. > > , and the installation was over: it lasted more than 30 minutes! The rpm installs in just a few moments. > > At this point I didn't know how to run MS Word. In the Wine mailing lists > > there were two different opinions: It's the same as from a Windows box. > > 1) enter the directory containing the file winword.exe > > (that was '/mnt/windows/Programmi/Microsoft Office/Office') > > and do '$ wine winword.exe'; but this didn't work; I assume you checked this, but was winword.exe there? Also, is /mnt/windows really drive D: from MSOffice's point of view, or does it think it's on drive C:? > > 2) use WineTools. Then I tried this second solution: > > snip > > After the installation your system.reg will be replaced! > > You will loose all registry keys of installed programs (except for DCOM98)! > > This is a full automatic installation of almost all components. > > You can add additional components later by using the uninstaller. > > Continue anyway? > > > > I chose 'no'. This was a mistake. I assume you were installing a fake windows drive in /home/rodolfo again. You should have let it replace the system.reg you already had there. There is no big deal about backing it up in case you get nervous. The registry files are critical to getting the whole thing to work correctly. > > If you are asked for, select drive D: for installation. What does wine think is drive D:? What does MSOffice think is drive D:? Are they the same physical partition? They should be, and if you haven't installed MSOffice in /home/rodolfo/.wine/drive_c, you should install it on drive D: whatever both MSOffice and wine think that is. > > Mounting of the CD failed. You should do it manually. Was the CD drive already mounted for some reason? Are you using supermount? The suggestion you received to turn on the wine debugging tools is a good one. deedee Registered Linux User #327485 Visit "WordStar & GNU/Linux" http://www.wordstar2.com Also, see WordStar Users Group Community http://www.wordstar2.com/WordStar_Users/index.php -- _______________________________________________ Find what you are looking for with the Lycos Yellow Pages http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10
____________________________________________________ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com ____________________________________________________
