BeWine FAQ

Faq in HTML, last updated 9/19/00

If your question isn't answered here, you may try looking in the Wine FAQ, the Documentation directory in the wine source (http://www.winehq.com/wine/documentation/), or ask on the BeWine mailing list. Frequently asked questions will get added to this FAQ (what a coincidence!). You can find the latest copy of this document at the BeWine Web Site.

Section 1) Getting started
1. Q. What is the address to the mailing list?
  A. You can join the list by sending mail to bewine-subscribe@wiw.org. Send mail to bewine@wiw.org once you are on the list.
2. Q. I don't want to be on your stupid list anymore! Take me off!
  A. Send mail to bewine-unsubscribe@wiw.org, and you will be unsubscribed.
3. Q. What do I need to download to start helping?
  A. First, you need to download and install X for Be. Check the files page for the latest version (http://bewine.loungenet.org/files.html).
  You'll need to download and install cvs and autoconf from ftp://ftp.ninemoons.com/pub/geekgadgets/be/i586/snapshots/current/bin
  To make sure CVS updates properly, you should put the following in your ~/.cvsrc file:
  
  cvs -z3 diff -u update -PAd
  Read http://www.winehq.com/dev.html for instructions on how to use the CVS tree, and start keeping up with the daily releases over CVS.
  Apply the appropriate patches from the BeWine files section (http://bewine.loungenet.org/files.html).
  Check the To Do list on the BeWine site, and get coding!
4. Q. A new patch set just came out. How do I update to it?
  A. First, get the latest source from the CVS server. Run 'cvs update -PAd' in your wine directory. Then, apply the patches from the patch set. Once they are applied, run 'autoconf' and 'autoheader -l include'. You will then have the latest source.
Section 2) Problems
1. Q. I just upgraded my version of X, and now it doesn't work!
  A. You will want to erase all old traces of the previous X installation before you install the latest X. A few directorys moved around between versions, and you're probably trying to use the old ones. Delete all the X11, X11R6.3, X11R6.4 directorys you can find, and look in your UserBootScript and UserSetupEnvironment files for references to the old X directory. The new X package will re-create these references in the correct places.
  If you insist on keeping your old X directory, keep reading.
2. Q. The configure script can't find my X directory!
  Q. When I try to start X, I my screen flashes, and I get a Kill Thread error!
  A. Make sure you have a link in /usr to /boot/apps/X11R6.4. The listing should look something like this:
  
  $ pwd /usr $ ls -l lrwxrwxrwx 1 users 0 Oct 28 17:20 X11 -> /boot/apps/X11R6.4
  This link should have been made after you reboot the first time after installing X. If it's not there, you can make the links by typing this in a Terminal window:
  
  mkdir /usr ln -s /boot/apps/X11R6.4 /usr/X11
  you'll probably want to add these commands to /boot/home/config/boot/UserBootscript, since the root directory gets recreated every boot.
3. Q. I made all the links like you said, but X still doesn't start!
  A. Make sure the X bin directory is in your PATH, and make sure the lib directory is in your LIBRARY_PATH. Also make sure your DISPLAY is set to whatever machine you want to display on (most likely your machine).
  
  export PATH=$PATH:/usr/X11/bin export LIBRARY_PATH=$LIBRARY_PATH:/usr/X11/lib export DISPLAY=127.0.0.1:0
  (127.0.0.1 is your local machine. Insert the IP of another machine if you want apps to go there instead.
  You can add these commands to /boot/home/config/boot/UserSetupEnvironment or /boot/home/.profile as well, so you don't have to type them in every time you open a new terminal.
4. Q. X has a [Green, Yellow] tint to it!
  A. This is caused by X not correctly detecting and using the workspace correctly. It should be fixed in the latest 6.4.3 patch, so please let us know if it still happens after using this patch.
5. Q. The X server seems to start (I get the patterned background) but nothing happens after that. What's wrong?
  A. Start X with the startx script. It will launch twm, xclock, and a few xterms for you to play with.
6. Q. My middle and right mouse buttons don't work in X!
  A. Yeah, we know. This is hoped to be fixed in an upcoming version of X.
7. Q. How can I display an X app from my [linux,FreeBSD,Solaris] machine on my Be machine running X for BeOS?
  A. On your Be machine, after you start X (make sure either a window manager is running, or you can see the patterned black and white background), run
  
  xhost x.x.x.x
  where x.x.x.x is the IP of the machine you want to receive programs from. For example, if your other machine is 192.168.1.1, run
  
  xhost 192.168.1.1
  On your other machine, after you start X on your Be machine, run
  
  export DISPLAY=be.machine.ip.address:0
  where be.machine.ip.address is the address of your be machine. For example, if your Be machine is 192.168.1.5, run
  
  export DISPLAY=192.168.1.5:0
  Then run the program you want.
8. Q. I get wierd errors when I'm trying to apply the patches to wine!
  A. Make sure you are running off the latest version of the source, which can be found in the CVS tree. Also make sure you read the instructions for the patch, you may not need to apply it!
9. Q. Wine doesn't compile!
  A. It should compile, with the latest set of patches. You might want to check out the documention in the patch, just to make sure there's no known problems. They should mostly compile "out of the box", so if they don't, please let us know on the mailing list.
10. Q. Wine compiles, but it doesn't do anything!
  A. Yeah, we know :) Check the project page for more information on what needs fixing.
Section 3) Future plans
1. Q. Is there a way to use wine without X?
  A. Not currently. The plan is to get wine working with X first, then to code a native graphics system. If you have the knowledge to do this, you are welcome to start, as the wine graphics system is fairly modular.
2. Q. Does BeWine run on PPC versions of Be?
  A. No, BeWine currently only runs on x86 based hardware. Even though it implements an in theory hardware independent version of the Windows API, the Windows binaries contains x86 instructions, that will need to be run on x86 based hardware. However, there is work being done on a CPU emulator that will make it possible to run x86 binaries on non-x86 based hardware, but that is far in the future.
3. Q. Can I get some screen shots of BeWine?
  A. Not yet, since BeWine doesn't even run yet. Once it does, though, we do plan to have screen shots. We do, however, have some screenshots of X being run on Be. You can view them on the screenshots page

Please contact Doug Clements for FAQ maintanence.