#1 GUI locks computer

[Hector Sosa, Jr]

My computer locks up whenever I try to run the GUI. I
have to do a hard reset (reboot button) when this happens.

The steps are:

1) Start ClexusMUD.ServerApps.GUI.exe
2) Click on Start button
3) Wait 3 seconds
4) Computer locks

This is repeatable every time.

My system is:

AMD Athlon 2400+
512 Megs RAM
Windows XP Pro SP1
NET Framework SDK 1.1
Visual Studio 2003 Architech

I haven't tried doing this from inside Visual Studio yet.

[Bruce Markham]

Logged In: YES
user_id=897859

Hector Sosa:

Well, first of all, its good to see that it downloaded, and
initially executes okay. At least it can find its dependant
assemblies and such.

Frankly, I have no idea what could cause this. See if the
Console program executes, considering they both use the
same Server library.

And if you don't mind, try running it from inside Visual Studio
and see if you can trap an error.

Tell me how things turn up.

[Brian Peyton]

Logged In: YES
user_id=638248

Are you sure your computer locks? From what I've seen the
server shouldn't do that. Try opening the server project
and doing this (cross posted from the forums).
I have a little fix for this. In cserverapp.cs there's a loop:
do
{
//Network systems refreshes, updates, and pulses
pvNetworkSystem.AcceptNewDescriptors();
pvNetworkSystem.PulseOutput();
pvNetworkSystem.PulseInput();
pvNetworkSystem.ClearDeadDescriptors();

} while(pvKillNow==false);

Just add
Thread.Sleep(2);
to somewhere in that loop.

And report what happens.

[Bruce Markham]

Logged In: YES
user_id=897859

Praise be to thee, revision17!

It did not occur to me that loop was causing that problem.
My development machine has a much slower processor than
Hector Sosa, and though that loop eats 100% of my
processor, I still manage to be able to do other things in the
background. I have been aware of the speed problem though.
I just didn't think of it when Mr. Sosa filed his bug report.

In my next mini release, I will attempt some alternate timing
of that sequence of subsystem calls. I will make some of the
sub-tasks event driven, and that main loop will perhaps be
set to execute as a single set of instructions, on a timer
driven event.

Thank you revision17. Mr. Sosa, please still report the results.
Though revision17 addressed an important issue, there is no
reason to believe that yours is fixed, until you try something.