[Ecc2] Beta GUI

[HotRod9mm]

Looks like Jeff Gilchrist is at it again. He helped with the Eccp-109 GUI


GUI Beta v0.1


Thx Jeff.............

[DutchMaster]

Very usefull if you're running the client as a service.

But running it with a normal client it won't give you more then some stats and eyecandy.

If it was possible to close the client from the GUI it would be a great addition. In this case it would work like the ECCp GUI.
Invoking the cfg file to change priority would be also a welcome feature.

[eweruk]

"Note: If you are using the ECC2 client in Service mode, you can use ecc2GUI to start/stop the client and monitor its progress. To enable this ability, you need to check the "Client Installed as Service" checkbox in ecc2GUI. The components and options not available to the Service client will be disabled in the GUI."

Looks like it is available. I am going to test on a couple machines.

[DutchMaster]

Yeah that is right. I wasn't clear about it I meant in non-service mode:

This currently only works whent he ECC2 Client is installed as a Service. To stop a non-service client, make the ECC2 command prompt window visible, select that window and press CTRL-C to stop the client so it saves its current progress properly.

If it could send a ^C signal to the child window, that would be great. I mean allot of people raised without command line utils, just are used to close the window by clicking on the [X]
It would be nice if this would get more user friendly. Its still beta offcourse.
Anybody know how to send a ctrl+C signal to the client window in C++ ?? Jeff couldn't figure it out, so he would be interested on this.

[eweruk]

Another tid bit of info:

"The only way it can get information is from the output files that the ECC2 client produces. So you need the latest version that creates the ecc2-109.spd file to get benchmark info."

"Running as a Service causes PLIST and DPLIST to go to the System32 folder by mistake."

"I will put out a new release of ecc2GUI in the next day or so that fixes a bunch of problems. Since Jay is going to fix the problem of the dplist file showing up in the SYSTEM32 directory, I have put in a check that if it can't find the dplist file it will just not display the last DP found information. That should suffice until the client is fixed."

Nice, I like it.