From newbie@vlug.org Mon Mar 3 01:24:28 2003 From: newbie@vlug.org (The MacDonald's) Date: 02 Mar 2003 17:24:28 -0800 Subject: [newbie] games on linux Message-ID: <1046654668.27502.4.camel@macdonald.bc.hsia.telus.net> I've been messing around with a red hat distro for a while now setting it up went ok . I really like the os I'd say I'm definitely not new to computers but linux is taking some getting used to I would like to play some of my microsoft games though. I have visited many sites on how to do this and I haven't had much luck except once I got wine to work with Diablo 2 but then it was gone again i would appreciate any help on how to get wine configured maybe I just need to do something I'm overlooking. From newbie@vlug.org Thu Mar 6 07:31:01 2003 From: newbie@vlug.org (Antony Hilliard) Date: Wed, 05 Mar 2003 23:31:01 -0800 Subject: [newbie] games on linux In-Reply-To: <1046654668.27502.4.camel@macdonald.bc.hsia.telus.net> References: <1046654668.27502.4.camel@macdonald.bc.hsia.telus.net> Message-ID: <20030306073101.4AE384BFB4@server2.fastmail.fm> Alison, I was waiting for someone more knowledgeable to post a reply but since it's been three days I'll bite. Running windows games under WINE is probably one of the most finicky hit-and-miss things I've ever tried to do with Linux. Windows has a *lot* of code, bugs, and undocumented features that the WINE team get to play catch-up with. Short answer: There's no magic bullet. Except, possibly this: http://www.transgaming.com/ I've seen a lot of positive comments on the web about WineX, TransGaming's version of Wine. They put a lot of development and debugging into it which makes a big difference. Apparently they are being good GPL citizens and giving their changes back to the WINE project so you can rest assured that your money is going to a good cause. As far as computer gaming can qualify, that is. ;) Cheers, -Antony=20 --=20 http://www.fastmail.fm - And now for something completely different=85 From newbie@vlug.org Tue Mar 18 12:39:45 2003 From: newbie@vlug.org (James Hofmann) Date: Tue, 18 Mar 2003 05:39:45 -0700 Subject: [newbie] Installation Woes References: Message-ID: <3E771391.1090409@verizon.net> Bob and Christine wrote: >Problems: > >1. Keyboard. The right shift key (a) fails to register the first key >stroke upon being depressed (b) subsequent key strokes are in lower case. >The left shift key is fully operable. >2. Even more serious, during last Sunday's install user and superuser >passwords were made IDENTICAL to eachother! > I did this for years, using a very simple password since security at that time was worth a whole lot less than simplicity. Changing a password takes only a few seconds once you get past typing it in every 30 seconds, especially the root password. > It should be noted that the >printer could not be made to operate at that time despite Owen's and Tom's >best efforts. Possibly this may also be involved in the subsequent crash >when making first fumblings toward GNOME from the root login. I typed >'startx', clicked on the Main Menu Button (footprint), dragged mouse to >Logout selection, then clicked on Yes in a separate window. That's when >all hell broke loose. > 'X cancel' causes no response in the separate window with a RED >TRIANGLE containing an '!', but a second separate window with a RED CIRCLE >WITH A HORIZONTAL YELLOW BAR permits me to depress a button entitled >'submit a bug report'. (Above the button is statement 'Application "gmc" >(process 849) has crashed due to a fatal error (segmentation fault). >Please visit GNOME Application Crash page for more info.) A partial bug >report follows: > > ...ssertion 'option menu != null' failed. >AUDIT: Sat Jan 25 01:58:39 2003: 807 X: client 5 rejected from localhost >Xlib: connection to ": 0.0" refused by Server >Xlib: Cllient is not authorized to connect to Server >xscreensaver: Can't open display: :0 >xscreensaver: initial effective uid/gid was root/root(0/0) >xscreensaver: running as nobody/nobody (99/99) > >xscreensaver: Errors at startup are usually authorization Did you read the >manual and the FAG? Specifically, the parts of the manual that talk about >XAUTH, XDM, and root logins? > > http://www.jwz.org/xscreensaver/man.html > >ICE error: Offending minor opcode =7 (protocol setup) > Offending sequence number =5 > Error: class =SetupFailed > Severity: =FatalToProtocol >Reason: A session shutdown is in progress. > >waiting for X server to shut down Gdk -Error**: X connection to :0.0 broken >(explicit kill or server shut down). > > Can't even guess at much here. On my system, "nobody" is a sort of special account. I think I would go through the "adding a user to the system" routine again. I would become root and then try to add a user from the command line with "adduser" command. In my humble opinion, "segmentation fault" always means a bug in the program, but perhaps you can work around it by having one's account as the program expected it to be. Did you get a proper home directory with some possibly hidden initialization files and directories. When you create a second user, do you get the same stuff in the new user's home directory? regards, Jim. From newbie@vlug.org Mon Mar 24 22:53:23 2003 From: newbie@vlug.org (The MacDonald's) Date: 24 Mar 2003 14:53:23 -0800 Subject: [newbie] webcam Message-ID: <1048546404.1270.6.camel@macdonald.bc.hsia.telus.net> Hey I was wondering if anyone new how to configure an intel webcam on rh 8.0 I tried a google search and didn't get too far any help would be appreciated From newbie@vlug.org Mon Mar 24 23:17:38 2003 From: newbie@vlug.org (Andrew Willard) Date: Mon, 24 Mar 2003 15:17:38 -0800 Subject: [newbie] webcam In-Reply-To: <1048546404.1270.6.camel@macdonald.bc.hsia.telus.net> Message-ID: On Monday, March 24, 2003, at 02:53 PM, The MacDonald's wrote: > Hey I was wondering if anyone new how to configure an intel webcam on rh > 8.0 I tried a google search and didn't get too far any help would be > appreciated If we knew which model of Intel webcam that would be helpful.... ?? http://www.intel.com/pccamera/ In the mean time there are a number of sites dedicated to cameras and Linux listed right on the VLUG Links pages: http://www.vlug.org/linux/links/Hardware/Cameras/index.html From newbie@vlug.org Mon Mar 24 23:46:00 2003 From: newbie@vlug.org (The MacDonald's) Date: 24 Mar 2003 15:46:00 -0800 Subject: [newbie] webcam Message-ID: <1048549560.1522.4.camel@macdonald.bc.hsia.telus.net> It's Intel model cs430 and I already went to the Intel site not much in the way of linux support there that I could find checked the VLUG webcam page I see a lot of other models unless there is some cross reference between this model and one that has written software that I can't find I appreciate the help thanks. From newbie@vlug.org Tue Mar 25 00:13:29 2003 From: newbie@vlug.org (Andrew Willard) Date: Mon, 24 Mar 2003 16:13:29 -0800 Subject: [newbie] webcam In-Reply-To: <1048549560.1522.4.camel@macdonald.bc.hsia.telus.net> Message-ID: <9B0D202E-5E56-11D7-990B-000502DF1D8B@shaw.ca> On Monday, March 24, 2003, at 03:46 PM, The MacDonald's wrote: > It's Intel model cs430 and I already went to the Intel site not much in > the way of linux support there that I could find Intel does not officially support the camera under Linux, which is stated on the 'Supported Operating Systems' page for that camera. If you had tried Google with the following "intel cs430 linux" you would have found the answer to your question within short order: http://spca50x.sourceforge.net/ > checked the VLUG webcam page I see a lot of other models unless there > is some cross reference between this model and one that has written > software that I can't find I appreciate the help thanks. The VLUG reference was simply to show that there is more than one place to look for information. And yes the Linux driver for your camera is based on the chipset within the device itself and not the specific model/make, you will notice that the driver is in development at the moment so don't expect a quick solution. From newbie@vlug.org Tue Mar 25 01:21:15 2003 From: newbie@vlug.org (Ken Murray) Date: 24 Mar 2003 17:21:15 -0800 Subject: [newbie] webcam In-Reply-To: <9B0D202E-5E56-11D7-990B-000502DF1D8B@shaw.ca> References: <9B0D202E-5E56-11D7-990B-000502DF1D8B@shaw.ca> Message-ID: <1048555275.2480.77.camel@pythagoras.linuxlords.net> --=-yTKPF5eNbLVzZ8JIUIUZ Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 2003-03-24 at 16:13, Andrew Willard wrote: > http://spca50x.sourceforge.net/ > The VLUG reference was simply to show that there is more than one > place to look for information. And yes the Linux driver for your > camera is based on the chipset within the device itself and not the > specific model/make, you will notice that the driver is in development > at the moment so don't expect a quick solution. I will pipe up and also say that just because a driver is "in development" does not mean you should expect a dismal failure. ;-) I am not familiar with the camera in question, but I did get my own 3Com Home Connect USB camera working quite well with a development driver.=20 It won't hurt to give it a try, and you can always submit reports back to the developer regarding successes and failures. Is it just me or has anybody else noticed that development/beta tools for Linux are often less buggy than their Redmond OS counterparts? --=20 Ken Murray ken@bcvnet.com http://www.bcvnet.com Website Hosting & Server Colocation GnuPG Fingerprint: 5403 7D09 A14D 508F 547A 34EF 34E1 E8F1 1222 E99C --=-yTKPF5eNbLVzZ8JIUIUZ Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQA+f68LNOHo8RIi6ZwRAnK4AJwPVg1Kj+C0ZRolvG3yT+vSGenIVgCfZGoy 6wuogRniUBA3jK3gh1Kh+rk= =Cz3Q -----END PGP SIGNATURE----- --=-yTKPF5eNbLVzZ8JIUIUZ-- From newbie@vlug.org Tue Mar 25 01:59:28 2003 From: newbie@vlug.org (Andrew Willard) Date: Mon, 24 Mar 2003 17:59:28 -0800 Subject: [newbie] webcam In-Reply-To: <1048555275.2480.77.camel@pythagoras.linuxlords.net> Message-ID: <697C4820-5E65-11D7-9ECA-000502DF1D8B@shaw.ca> On Monday, March 24, 2003, at 05:21 PM, Ken Murray wrote: > I will pipe up and also say that just because a driver is "in > development" does not mean you should expect a dismal failure. ;-) Even with the smiley who said 'dismal failure'? From newbie@vlug.org Tue Mar 25 02:21:56 2003 From: newbie@vlug.org (Ken Murray) Date: 24 Mar 2003 18:21:56 -0800 Subject: [newbie] webcam In-Reply-To: <697C4820-5E65-11D7-9ECA-000502DF1D8B@shaw.ca> References: <697C4820-5E65-11D7-9ECA-000502DF1D8B@shaw.ca> Message-ID: <1048558915.2480.117.camel@pythagoras.linuxlords.net> --=-j0cPsR2un3ePDW8O2i7j Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 2003-03-24 at 17:59, Andrew Willard wrote: > Even with the smiley who said 'dismal failure'? I was just trying to make my point that development drivers can often provide just the opposite. --=20 Ken Murray ken@bcvnet.com http://www.bcvnet.com Website Hosting & Server Colocation GnuPG Fingerprint: 5403 7D09 A14D 508F 547A 34EF 34E1 E8F1 1222 E99C --=-j0cPsR2un3ePDW8O2i7j Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQA+f71DNOHo8RIi6ZwRAjomAJ4lqhN/B28MU8fp8+7x+eaYV03DIACfYBiE O7g1gHj5feenetOAmX7szx4= =ZnPG -----END PGP SIGNATURE----- --=-j0cPsR2un3ePDW8O2i7j-- From newbie@vlug.org Tue Mar 25 03:09:52 2003 From: newbie@vlug.org (Andrew Willard) Date: Mon, 24 Mar 2003 19:09:52 -0800 Subject: [newbie] webcam In-Reply-To: <1048558915.2480.117.camel@pythagoras.linuxlords.net> Message-ID: <3F3F3498-5E6F-11D7-9ECA-000502DF1D8B@shaw.ca> On Monday, March 24, 2003, at 06:21 PM, Ken Murray wrote: > I was just trying to make my point that development drivers can often > provide just the opposite. By implying that my statement of 'quick solution' somehow meant that it would not work? What I meant was that the developers do not have all of the cameras features working... it may take some time before everything is implemented, I was not inferring that the camera didn't work with this driver.