Bizarre Computer Problems

[Toets]

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!

[kozak6]

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.

[kozak6]

Hmm.

Now my computer thinks that it is the year 2003.

The plot thickens!

[kern]

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

[kozak6]

Oh no.

I think my computer might be doing it again.

[DrDoom]

...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.

[DrDoom]

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

[Ed]

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

[KadaverJack]

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

[divVerent]

...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.