-
Sorry for the delay in responding.
No, I didn't try turning it off and on again, but I can.
Actually, now that I did a C/A/D, I'm seeing that it is running (see screenshot), I'm just not seeing a SYSTRAY icon for it (which it may or may not have - is it supposed to?). I could have sworn one was there before.
Anyway, I guess I can close down the "Stand-Alone" one? I just like to see what's going on with it.
Is there any harm in leaving both of them running? Pete
-
Senior Member
I recall that the StandAlone was more like a model (doesn't do anything) of the real one.
-
It doesn't seem that way here - the "stand alone" shows you when it runs a test (I think - at least that's what it looks like it's doing), gives you all kinds of cheerful messages when it's happy and seems lonely when it doesn't have anything to do.
That's okay - I'm going to run both until someone tells me otherwise.
Thanks all. Pete
-
Senior Member
I should clarify. Running the standalone client is a model that'll show you what the real thing will look like. The Testing Console is the real stuff.
-
Junior Member
-
Senior Member
Yeah, good point . I didn't read enough books about it.
Enlighten me (the differences between the two)? : D
Even though the Stand-alone client has "Non-Service Version" logo on the window title.
-
I don't know what - if anything - changed, but the "Beta testing service Console" is now working correctly on my wifes' computer.
Starts w/Windows, shows in SYSTRAY and accurately logs the tests as they happen without my having to open the stand-alone client to see that. Pete
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules