Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[roseway]

Here is the entire event log --
... etc

I see now. I failed to realise that you were referring to what happens when you change the snapshot directory. I'll check that out. Sorry about the misunderstanding.

[roseway]

The Dslstats Version 4.54.5 is working well no issues with Hg612_Modem_Stats which is also running in the background on a stand alone PC, and the sampling speed is still great, have not updated to 4.54.6 will give this version a good seeing to before I update.

Cheers Roseway

Thanks NS. There's no need for you to change to v4.54.6, because the small change in that version only applies to the HG622.

[roseway]

had to setup a new server today anyway so updated .  both stats progs running fine here 

Thanks perry......

[roseway]

1) If you select HG622 from the drop-down list on the login page, it should automatically enable the HG622 workaround option. I just checked again, and it does here.

Surely that "tick-box" is redundant? 

I left it as a separate option because (a) some people will just fill in the details without selecting a particular model from the drop-down list, and (b) it's possible that there are other models in use which require the same workaround.

It is still my intention to autodetect this requirement, so user's don't need to do anything special, but it proved a bit problematical, so I haven't done it yet.

[burakkucat]

Ah, now I understand. Thank you. 

[broadstairs]

The dummy program is only run if you've set the option "HG612-Modem-Stats co-operation". Do you still want it to be a separate option?

No that's fine, I had not realised that was the way it worked....
Stuart

[Bald_Eagle1]

- improved the robustness of the program under error conditions, and added more logging
- (Windows only) when the HG612-Modem-Stats co-operation option is set, a dummy program called
  dslstatssampling.exe is run while sampling takes place. This can be detected by other
  monitoring programs to avoid clashes.

Thanks for adding the dummy program, Eric.

This is the result:-

Code: [Select]

There are 1 instances of dslstatssampling.exe running. Please wait for it to complete

 ****************************************************************
 * The modem is currently being accessed by DSLStats            *
 * Please wait a few seconds for it to complete                 *
 *                                                              *
 * HG612_stats.exe should automatically resume in a few seconds *
 *                                                              *
 ****************************************************************

 * dslstatssampling.exe is running, seconds waited = 0.50
 * dslstatssampling.exe is running, seconds waited = 1.00
 * dslstatssampling.exe is running, seconds waited = 1.50
 * dslstatssampling.exe is running, seconds waited = 2.00
 * dslstatssampling.exe is running, seconds waited = 2.50

   dslstatssampling.exe has now completed or timed out. HG612_stats.exe is resuming



What does DSLStats now do if any of my programs are running at the time DSLStats intends to start sampling?

[roseway]

What does DSLStats now do if any of my programs are running at the time DSLStats intends to start sampling?

If the "co-operation" option is set, it works as described before, missing out up to 5 samples in succession and logging the events. I could repeatedly check as you have done, but then the sampling could occur outside the time range which it's supposed to maintain, and this could cause other problems for your programs.

If the "co-operation" option isn't set, it presses on regardless, and deals with the consequences of any clash.

I will be reducing the timeout on dslstatssampling.exe to 10 seconds, because if sampling isn't complete in that time, DSLstats will abort that sample anyway.

Please do let me know if you would prefer any changes in this behaviour.

[Bald_Eagle1]

Cheers, Eric.

I had already added a maximum timeout of 12 seconds for my programs' checking for dslstatssampling.exe before carrying on regardless.
That situation should never really occurr, but it's there just in case.

As far as I can tell, I think we've now both covered everything necessary, including if the "co-operation" option isn't set & DSLStats was to start sampling just as my programs are accessing the modem.

[roseway]

Hopefully that's the case.

[NewtronStar]

I just had an error in Dslstats have to say it's my first ever unrecoverable crash with this program, nothing untowards in the event log.

I press ok but it crashes then I and re-run the Dslstats program and it fails to startup.

EDIT had to restart PC and still straight away I get division by zero when I run Dslstats going to remove this version and install version 4.54.4 

 

[NewtronStar]

Going back to old version did not fix the division by zero error, so I went into C:/USERS/MYNAME/APPDATA/LOCAL/DSLSTATS folder and removed the dslstats configuration file and restarted the Dslstats and it's working again 

[roseway]

Oh dear

I'll try to find how this could happen.

[NewtronStar]

Oh dear

I'll try to find how this could happen.

No worrys Roseway it could be the new Version's configuration data settings is incompatible with the older version settings thats the only way this could happen 

[les-70]

   Thanks for all the work, after a few days with this version I have no problems to report and all is running well.     There is one possible extra feature that I would use.  I often save the telnet connection stats and pbParams with a copy and paste to a text file.  If other do this as well it would be helpful to have a manual save option on these two tabs.   It is already an option on the snapshots tab.