WinXP Lockup

[NitroSniper]

Anyone experience a totally lockup when they press the X button in the TS2.0 client? I couldn't even Ctrl+Alt+Del. Doesn't happen every time .. but still rather a strange problem.

-NitroSniper
:rolleyes:

[CleanAir]

Same happens to me all the time, and two others are experiencing the same problem (but it doesn't crash every time for them).

[NitroSniper]

Its certainly a weird one.. it just happened when i clicked minimise aswell. There has to be some major problem.

-NitroSniper
:rolleyes:

[jmk]

just had the same prob when i go to click the X

[NitroSniper]

Did any of the beta testers have this problem in the beta version of Ts2 ? .

-NitroSniper
:rolleyes:

[jmk]

i never experienced this problem b4

[NitroSniper]

Ahhh.. might have found a fix for it.. If you make Ts2.0 run at normal process priority (Options -> Other Tab). The minimise and close problem doesn't happen at all :)


-NitroSniper
:rolleyes:

[jmk]

dont think thats a fix , its a work-round really :)

[NitroSniper]

lol ... TS2 seems to have quite a few workarounds to problems .. Hope someone is making notes to fix the problems *wink* *wink*

-NitroSniper
:rolleyes:

[woutur]

Problem stated in the FAQ section.

[Nick666]

The same for me BUT:

In "Sound Driver" u first have to switch form DS to Wave or vice versa.
Then WinXP will freeze if u close Teamspeak with the "X".

[mb4guns]

Same problems, it starts when u switch to high prior mode and reboots, after lauching windows feerze compleetly wehn pressing minimize or close button. On normal prior mode it works just fine, altought I really like to use high priore....

[ready]

Same problem..


Avoid the X

[*X2K*Wakko]

Make sure u do not run it in realtime... that screwes it up, second hit ctrl+alt+del goto process priority and set it to below normal this will fix that prob and reduce game lag

[woutur]

Listen people.... U can use realtime just stay away from the buttons. Use the menu to close TS down...

It is stated in the FAQ!

[Bassman]

Ok, i got a fix for it.. because i have seen the same problem with another program..

Put the compatibility to Windows 98/windows ME

for the guys that don't know how to do that..

- right click on the shortcut and select configuration/settings ( i don't know what's it called since i work with a different language version)
- Go to compatibility and select windows98/windows me in the dropdown menu.

when you start teamspeak client everything should work fine..
you can put it on realtime and close with the red X
without crashing the windows..

[Sexbomb]

Originally posted by Bassman
Ok, i got a fix for it.. because i have seen the same problem with another program..


Yep, namely Teamsound. :D Just what's up with voice comm programs under Windows XP that they like to hang up 'puters if you try to click on the close/minimize buttons?

[Bassman]

Yeah you're right , it was teamsound frow team5150.. !!

[CleanAir]

Only problem is that it doesn't switch to realtime when set it to run in the Win98/ME compatible mode... you'll have to do it in the Task Manager.

[N. Werensteijn]

Try this patch. Install it over your current TeamSpeak.exe

It set priority 1 notch lower. I hope that solves the lockups.

http://www.teamspeak.org/files/TeamSpeak_patch14.zip

[CleanAir]

Just wondering why it doesn't crash when closing using the menu. Do you call different cleanup functions?

And thanks: It hasn't locked up my system as of yet :)

[N. Werensteijn]

Nope its the route the close requests takes :)
I dont exactly know whats wrong. The problem may lie in the delphi libraries or even the windows interface itself. One or both were not realy ment for realtime operation i guess.

I run a win2k machine here, and it works without problems on runtime. (but it might also be that my hardware is better suited for realtime programs)

[CleanAir]

I have tried several windows programs set to realtime priority (using task manager) and all of them could be closed normally via the title bar. So it's probably not a generic Windows problem.

Maybe you could send me a Delphi "Hello World" program so we could check if that is already locking up the computer when set to realtime? Or you can test it yourself on a WinXP machine if you have one.

If you're wanting to investigate further, you could display a message box when clicking on the X button, that way we could see if it crashed because you clicked or afterwards.