Hello, I downloaded Beos 5 Personal Edition last night (6 hour download) and this morning attempted to set it up. First I tried to set it up on my G drive and everything seemed to work great except I had no mouse pointer. I thought it was possible that it may use windows mouse pointers so I uninstalled Beos and reinstalled it on C drive where windows resides. Again no mouse pointer. I can't imagine Beos creating an OS without a mouse pointer so what am I doing wrong? This is my system. Intel Celeron 600 128 meg of ram nVidia Riva TNT2 PS/2 Mouse Kingston Ethernet Modem is disabled in Bios since I use a network. Windows 95 I read the hardware compatibility list prior to downloading and everything on my system is compatible. I have looked through the FAQ's, Online User Guide and BeBook and I did not find this covered anywhere. There must be some way to set a mousepointer. Any assistance would be appreciated. AC

Try hitting the space bar when you boot to BeOS. Select safe mode (check the first option and it will default to checking all of the items). If, while in safe mode, you DO see the mouse cursor, then there is a problem with you boot settings. I have had this problem on other systems. Next time you boot, select only the "Don't call BIOS" option and see if you can see the cursor again under normal boot conditions (that was the problem on my computer). If that is your problem, then head over to betips.net and look up the tip for making the don't call BIOS option permenant. If it is not the issuse, then keep trying other boot options until you get the one that is the problem and email me and I will tell you how to make it permenant.

I see the mouse pointer/hand....briefly, when the syatem just boots however, it disappears immediately I touch the mouse. I also am anxiously awaiting an answer to this strange situation. No mouse - no control - no fun! To Be or no to Be....Bill Shakespeare!!

I worked on a computer that had this simular problem. (windows 98) My mouse pointer would show in safe mode, with both a serial and a ps/2 style mouse.But when it came to normal mode, good bye mouse. I thought definitly driver conflict. Device manager quoted vmouse.vxd, code 8.But a little hard work and I discovered that the system.ini file could cause this problem. It has a number of boot settings within the file. But look for *displayfallback in the [boot] section, make sure it is set to 0 not 1. It should look like this *displayfallback=0. If there is any other displayfallback entries delete them. Make sure there is no other [boot] directories, other than the [boot.description] section, do not delete this entry. (also as a note make sure there is no text or code before the [boot] section, this could cause problems also.