kozak6 wrote:Oh goddamnit.

They done fucked up.

Sound only plays through the right channel, and whatever the hell they installed has a wimpier processor, a 1.25 GHz one instead of the 2.08 GHz one that it is supposed to have.

Never trust a computer store! Always tell them exactly what you want them to install and double check when you get your computer back. That's why I always fix my own computer and only order parts... If I were you, I would seriously complain about this and demand they install what was supposed to be installen in the first place, without charging anything!

Apparently, they seem to think Windows is misreporting it.

Still looks like we are going to have to take it in to get the headphone jacks repaired or replaced. Probably going to take another damn week.

Looks like I'm going to have to do some old school console gaming.

Hmm.

Now my computer thinks that it is the year 2003.

The plot thickens!

they installed has a wimpier processor, a 1.25 GHz one instead of the 2.08 GHz one that it is supposed to have.

Apparently, they seem to think Windows is misreporting it.

---------------------------------------------

kern wrote:
ive never heard of a pc Case being warranty sealed. would make me suspicious theyre tryna hide something. how the heck do u upgrade anything, or even check the PC has what it says it has by way of hardware?

tchr wrote:
for some "brands" it pretty common to warrany seal the case. "void if broken", and its crap, but that make syou loose your warranty when you install hardware of your own...

But annother thing? what hardware can you possibly have that you cannot find thru the system without opening the case? Smile

for this sort of reason.

iirc one chip/mobo manufacturer a few yrs ago actually coded the chip to misreport itself to the OS, to give impression of higher proc speeds, and thus save money.
its like counting your money when u get ur wages, in the old days of paypackets, what it says on the front isnt necessarily what it has on the inside.

So you dont void your warranty, ask to be there when they take the lid off. and if its a lesser spec CPU offer to administer it to the technician, as a suppository

Oh no.

I think my computer might be doing it again.

...although I dont get a crash, Im having a similar issue with my mouse (cord-bound optical MS-Tech [no-name]). When playing Nexuiz for a while (sdl or glx, no difference), my system does no longer respond to mouse movements, even when exiting Nexuiz. One thing that sometimes helps is moving the mouse around wildly (still in Nexuiz) - some might have seen this ingame lol . If that doesnt help, last chance is: Pull the plug and plug the mouse back in (PS/2) - and get fragged while doing this.
Im sure this has to do with Nexuiz, as Im not running Windows, but Debian (somewhere betweeen stable, unstable and experimental distribution - mostly testing though). I dont remember exactly, but I think this didnt happen in Nexuiz 1.2 or 1.5.

...I somewhere here read something about setting "GL_FINISH 1" could help, but didnt in my case...

What specs are you running? Could you try with another game?

And more important: could you try another mouse (preferably a USB mouse)?
I suspect it might be a hardware issue.

DrDoom wrote:...although I dont get a crash, Im having a similar issue with my mouse (cord-bound optical MS-Tech [no-name]). When playing Nexuiz for a while (sdl or glx, no difference), my system does no longer respond to mouse movements, even when exiting Nexuiz.

I am quite sure this does not have to do with Nexuiz.

However, to rule out the only way using which Nexuiz could stop mouse pointer movement, exit Nexuiz, and start it again and quit immediately using the console. (For the last step, you can use ANY fullscreen game). If the mouse pointer still doesn't work, it isn't Nexuiz's fault. To go a step further, press ctrl-alt-backspace (this forcefully ends your X session). If THEN the pointer still doesn't work, it IS the mouse's fault...

My guess is a partially broken cable or plug (loose contact). Try another mouse.

uhm, well....

I only get mouse problems when running Nexuiz. No other app/game behaves that way. And Im pretty sure my (good old) mouse is still ok - Im using it every day without any trouble, except in Nex'. Another mouse, hmm, I have a kind of adapter to plug the one I have in as an usb-device... dont think that will help, but Im trying.
I remeber I had a similar issue with other OpenGL- and SDL-based games. The effect You describe to exit and restart the app/game did work back then, but I didnt encounter that behaviour for quiete a while now, only in Nexuiz.

specs...
Im playing Nexuiz compiled from cvs/svn, which I update&compile every few weeks...
My system basically is a Debian (mostly) testing, with kernel 2.6.17 and libc6 2.3.6-15 (all debian packages).
sdl-libs versions:
sdl-image: 1.2.5-2
sdl-mixer: 1.2.6-1.1+b1
sdl-net: 1.2.5-7
sdl-sound: 1.0.1-9+b1
libsdl1.2-dev: 1.2.10-3
sdl-gfx1.2: 2.0.13-2

Xorg: 7.0.22 - Ill skip the 100 packages for each X-component here...

and of course the nvidia-driver: 1.0.8762-2, same as kernel module, the kernel module was compiled i686, gcc 4.0.4 20060507 (prerelease) (Debian 4.0.3-3), same as version as used to compile the kernel.

I really dont think this is a hardware-issue, as I would have strange effects in other apps as well, so Ill omit my hardware-specs here, but If You really want to hear about that, Ill post them too.

DrDoom wrote:I remeber I had a similar issue with other OpenGL- and SDL-based games. The effect You describe to exit and restart the app/game did work back then,

Yes, what I was describing happens when ANY OpenGL fullscreen game/app crashes.

but I didnt encounter that behaviour for quiete a while now, only in Nexuiz.

If Nexuiz, running without root privileges, can "disable" your mouse even across X server restarts (Ctrl-Alt-Backspace), something is totally wrong with your operating system and you should report it as Linux kernel bug.

If Nexuiz can disable your mouse just for the running X session, starting and exiting helps.

Can you try starting gpm as console mouse service (then you have a mouse pointer on text-mode consoles) and when it happens again, press Ctrl-Alt-F1 and check if the mouse works there? If it doesn't, it is either a hardware problem or a kernel problem. If it does but restarting the X server doesn't work, it could as well be a bug in the X server's mouse driver or a not completely protocol conforming mouse.

BTW, the only pointer movement affecting functions Nexuiz uses are XGrabPointer (all events to the Nexuiz window), XWarpPointer (jumps to a given position) and XDefineCursor (used to make the pointer disappear). So when it happens again, look with ps if there are any Nexuiz processes left, and if there are, kill them with -9. That removes any effects that XGrabPointer and XWarpPointer could cause. After that, run xsetroot and move your mouse, even click around wildly. It should work again. If not, it isn't Nexuiz's bug but something more serious.

However, I still believe that it is a cable issue - note that you move your mouse a totally different way in FPS games than in most other applications.