Kitz Forum
Broadband Related => Router Monitoring Software => Topic started by: meteosat on February 20, 2014, 11:31:18 PM
-
Hi folks,
Not able to unlock the modem at the moment and would like to remove the monitor stats program. The trouble is that on boot up of the Windows 7 computer two log files appear on the screen (actually I'm asked which prog I want to view them, but they are the router stats log files.
I have tried a re-installation and switching off monitoring - yet still they come!
Cheers
-
That's a new one on me.
Nothing is actually installed as such when using the programs, so there is no uninstall program.
You should be able to simply disable or delete the task (HG612 Stats Program), either through the program's GUI or directly in Task Scheduler.
The programs & all folders can then either be left in-situ for future use or deleted.
I have no idea whatsover as to why any log files appear on booting up.
It's certainly not a feature of any of the programs.
Just for interest, what are the names of the log files that appear?
I wonder, have the logs or shortcuts to them somehow ended up in your Startup folder?
-
Thanks - this is the first few lines of the two files I get at each bootup.
When I save it in notepad it wants to save as 'program'
Files (x86)\HG612_Modem_Stats\Ongoing_Stats\ERROR.LOG_file_ERROR.TXT
Files (x86)\HG612_Modem_Stats\Ongoing_Stats\ERROR.LOG_file_ERROR.TXT
19/02/2014 15:37:06.25 - In [HG612_stats.exe] - After ini_parse(). ERROR.LOG status = 0, Files (x86)\HG612_Modem_Stats\Ongoing_Stats\ERROR.LOG_file_ERROR.TXT
19/02/2014 15:37:06.26 - ERROR.LOG successfully opened. Status = 1, Files (x86)\HG612_Modem_Stats\Ongoing_Stats\ERROR.LOG_file_ERROR.TXT
19/02/2014 15:37:06.48 - ONGOING-ISRUNNING-153706-345.TXT - There are 1 instances of HG612_stats.exe running. Status = 1, Files (x86)\HG612_Modem_Stats\Ongoing_Stats\ERROR.LOG_file_ERROR.TXT
19/02/2014 15:37:06.48 - ONGOING-ISRUNNING-153706-345.TXT - ** Continuing as there are only 1 instances of HG612_stats.exe running **. Status = 1, Files (x86)\HG612_Modem_Stats\Ongoing_Stats\ERROR.LOG_file_ERROR.TXT
19/02/2014 15:37:27.54 - ONGOING-ISRUNNING-153706-345.TXT - Now in exit. Status = 1, Files (x86)\HG612_Modem_Stats\Ongoing_Stats\ERROR.LOG_file_ERROR.TXT
19/02/2014 15:37:27.56 - ONGOING-ISRUNNING-153706-345.TXT - *** WSACleanup has completed. Files (x86)\HG612_Modem_Stats\Ongoing_Stats\ERROR.LOG_file_ERROR.TXT
19/02/2014 15:37:27.59 - ONGOING-ISRUNNING-153706-345.TXT - *** About to free(txbuf). Files (x86)\HG612_Modem_Stats\Ongoing_Stats\ERROR.LOG_file_ERROR.TXT
19/02/2014 15:37:27.60 - ONGOING-ISRUNNING-153706-345.TXT - *** txbuf has been freed. Files (x86)\HG612_Modem_Stats\Ongoing_Stats\ERROR.LOG_file_ERROR.TXT
19/02/2014 15:37:27.62 - ONGOING-ISRUNNING-153706-345.TXT - *** About to free(rxbuf). Files (x86)\HG612_Modem_Stats\Ongoing_Stats\ERROR.LOG_file_ERROR.TXT
19/02/2014 15:37:27.63 - ONGOING-ISRUNNING-153706-345.TXT - *** rxbuf has been freed. Files (x86)\HG612_Modem_Stats\Ongoing_Stats\ERROR.LOG_file_ERROR.TXT
19/02/2014 15:37:27.65 - ONGOING-ISRUNNING-153706-345.TXT - *** Now checking for resyncs - There are 1 instances of HG612_stats.exe running. Files (x86)\HG612_Modem_Stats\Ongoing_Stats\ERROR.LOG_file_ERROR.TXT
19/02/2014 15:37:27.67 - ONGOING-ISRUNNING-153706-345.TXT - ONGOING-ISRUNNING-153706-345.TXT DELETED - Status = 1, Files (x86)\HG612_Modem_Stats\Ongoing_Stats\ERROR.LOG_file_ERROR.TXT
19/02/2014 15:37:27.67 - ONGOING-ISRUNNING-153706-345.TXT - *** Scheduled Current_Stats logging is switched ON.
Can't see anything in the startup folder either for user (name) or public.
Cheers
-
That is very strange, I can confirm what BE1 said, nothing is actually installed (as in written to the registry) when you install the programs they are just copied to the directory of your choice.
Going by what you posted it looks like something is triggering one of the error log files to be opened when you boot , the Files (x86)\HG612_Modem_Stats\Ongoing_Stats\ERROR.LOG_file_ERROR.TXT text looks like part of the directory name, I say part because one would expect it to be Program Files (x86). This is not stored in the log files, so no idea where that is coming from.
Did you copy the program files into the Programs Files (x86) folder?
You can also look in System Configuration to see what is starting at system startup, press the start button and type System Config and you should see it appear in the list, select it then select Startup and see what is listed.
Also try deleting the HG612_Modem_Stats folder and it's contents, as you haven't logged any stats there's nothing to be lost. Also ensure the scheduled task is deleted, either from the GUI tasks menu, or directly from Windows 7 Task Scheduler.
-
Thanks for working with me and the suggestions.
To clarify:
I installed the package on my D drive - as the C is an SSD and I keep as much as possible away from it.
Hence when I was going through the setup procedure I altered the file paths to all read to the D drive.
There's no sign of a scheduled task.
I have been doing numerous selective startups now with msconfig, and have narrowed it down to about four possible progs, but as such none of them are directly related, which deepens the mystery.
I'll keep working at it, but don't want to completely stress the computer out with endless re-boots!!
And yes, I have removed the complete folder, unless it has written something to the C drive?
there are no new files being produced, just these two that keep appearing on boot-up - or at least they did until I enable selective boot-up (All the services produced a clean boot-up)
Cheers
Cheers
-
Which programs did you de-select via Msconfig that stopped the files appearing?
-
This is a real long shot, but is it possible that one programme associated with the log files is retaining a log in some sort of temp file. For example notepad++ can do this if you've viewed a file and not closed the file in notepad++ before closing down the program itself.
I've had this happen several times accidentally if I've been coding in my usual program, but for some reason I wanted to check the source with an external editor. The file will still be there next time you open notepad++, even if the file has been deleted. Notepad++ will throw an error warning to you next time you open it, and even ask if you wish to retain/recover the file.
APTdifference is another programme that can do similar. May be worth checking which ever program's you would use to view log type files, to make sure it hasn't got a local cache of one of hg612s error logs.
-
Please see attachments for what comes on the desktop on bootup
The remaining startup items are:
1. DownloadStudio
2. SPIrunE (Creative sound I believe)
3. LWS Logitech webcam
I selectively added items until the problem happened again
The file isn't notepad specific, its just that I use notepad to see it.
Cheers
-
Just to add two other things...
I have tried a system restore to about a week before installing HG612 stats. That has no effect.
It appears from my work with msconfig that either of two items will trigger the file appearance: Download Studio or LWS (The Logitech webcam s/w)
I can certainly live for the moment with those deselected from the bootup tab, but it doesn't get me to a final solution which is aggravating and puzzling.
I will wait for a few more reboots to confirm that the file doesn't randomly reappear.
cheers
-
Could it be download studio downloading the file from somewhere?
Any idea where the file is located, if you choose save as in notepad does it reveal where the file is located?
Certainly a strange one this.
-
I have now located the issue, though I am not sure if my solution doesn't beg the question as to why and what remains!!
I'm grateful for the suggestion to do a 'save as' - which led to me tracking the errant file down as below.
In the root directory of the D drive where all the files were unzipped there was I noticed a single file - marked as 'file' rather than application etc. This file was identified as 'program'. It was identical in size to the text files that were appearing on the desk top on bootup.
I deleted this file and have had no subsequent episode (so far!) of the appearance of the bootup files.
So far so good! But what remains is still causing me some head scratching. It looks as if the file was generated by the prog and then written to the root directory. I cannot be 100% sure if the bootup issue was happening with the program still installed, but I tend to think it was as I think I went for the uninstall because of seeing the errant files - but I could be wrong.
But why on earth that particular file was being called up by other progs on bootup remains a mystery - perhaps a Windows quirk?
Any further thought from those in the know as to why that error text was placed in the root directory with the name 'program' would be gratefully received!!
But thanks in any case to all who have chipped in
-
Just as a test I saved a text file to the root of my D drive and renamed it just program. On reboot nothing happened.
It's certainly a mystery, and I don't like mysteries :no:
-
Although the file I saved, I saved as a text file, the 'program' one in the root drive wasn't identified as a txt. I still have it and could e-mail it if it would help.
Cheers
-
It wasn't identified as a text file because it had no file extension, it would just be listed as type 'File' without a file extension. File extensions by default are hidden for known file types.
Can you Zip it up and attach it to a post here presuming it's small enough and has no confidential info in it?
-
It's certainly a mystery, and I don't like mysteries :no:
Me neither :shrug2:
I would also like to see a zipped copy of the file(s).
-
Not a problem.
Please see attached zip file
Would really like to know how the file was produced, in case the stats prog has some service still running.
Cheers
-
So far so good! But what remains is still causing me some head scratching. It looks as if the file was generated by the prog and then written to the root directory. I cannot be 100% sure if the bootup issue was happening with the program still installed, but I tend to think it was as I think I went for the uninstall because of seeing the errant files - but I could be wrong.
But why on earth that particular file was being called up by other progs on bootup remains a mystery - perhaps a Windows quirk?
Any further thought from those in the know as to why that error text was placed in the root directory with the name 'program' would be gratefully received!!
DownloadStudio hasn't received particularly good reviews.
Spyware & malware have been mentioned:-
http://download.cnet.com/DownloadStudio/3000-2071_4-10266250.html
I wonder if it (or some other program) unexpectefly runs programs at boot time?
This line here, is actually a line of code from HG612_stats.exe after the variables have been populated:-
19/02/2014 15:37:06.25 - In [HG612_stats.exe] - After ini_parse(). ERROR.LOG status = 0, Files (x86)\HG612_Modem_Stats\Ongoing_Stats\ERROR.LOG_file_ERROR.TXT
The actual code is:-
sprintf(Error_log_not_opened_command, "echo %%date%% %%time%% - In [HG612_stats.exe] - After ini_parse(). ERROR.LOG status = %d, >> %s\\ERROR.LOG_file_ERROR.TXT", Error_log_opened, config.Ongoing_Stats_folder);
system(Error_log_not_opened_command);
%s is the variable for the path to the Ongoing_Stats folder.
I have managed to recreate a file with no extension, containing the same format of details that you posted.
In your example, it appears that you had set up the programs in the folder named "Program Files (x86)" on one of your drives.
"ERROR.LOG_file_ERROR.TXT" is just a debugging file that will be removed in release 2.1
It is coded in such a way as to log details via a Windows system call as that's the only way to record details before the normal ERROR.LOG file is opened.
ERROR.LOG status = 0 means that ERROR.LOG hasn't been opened yet.
ERROR.LOG status = 1 means that ERROR.LOG has now been opened.
As updating the debugging file is just a temporary measure, I didn't bother to build in the code to use folder/file names that include spaces as the default location for the program folder is C:\HG612_Modem_Stats (no spaces).
I used a folder name of "HG612_Modem_Stats\Ongoing Stats" (with a space in it to partially recreate the issue).
Once I remove creation of the debugging files, the rest of the programs can indeed use folders/files that include spaces in their names.
Because the folder "Program Files(x86)" has a space in its name, a file with no extension will be created using the first word in the folder name ("Program" in your case & "Ongoing" in the example I used to create the issue).
My example text file with no extension, named "Ongoing" contains this text:-
22/02/2014 18:53:30.18 - In [HG612_stats.exe] - After ini_parse(). ERROR.LOG status = 0, Stats\ERROR.LOG_file_ERROR.TXT
Stats is the remainder of the folder name Ongoing Stats (i.e. the part after the space).
So, I hope you could follow the above as it explains why you saw a file named Program with no extension being created.
I'm afraid I have no idea why on earth something opens it on your desktop on bootup though.
I can only imagine something is running on your PC (maybe malware/spyware) that tries to run programs from your Program Files(x86) folder at boot time.
Doing that is certainly not a "feature" of any of my programs.
The only thing that runs automatically after booting up is the scheduled task & only then if it hasn't been disabled or deleted.
Are you 100% sure it (or maybe a task from a previous version of my programs) isn't still running?
-
At least we now know why the file was created, but if it was our scheduled task causing it to be opened on boot, would it not then open every minute?
It's got to be something to do with those three programs if it's doesn't do it with those disabled.
-
Hi guys,
I am grateful for the fuller explanation of the workings of the program. I am considering eliminating Downloadstudio as to be honest it hasn't been all that useful.
Just to completely eliminate the scheduled task on boot-up line of enquiry - would the task be fairly clearly identified as with HG612 in the title or some such thing? I can see other tasks but no obvious connection.
I did run Hijackthis and Malwarebytes early on in the checking stage to eliminate if possible any viral infections, and I had a clean bill of health there.
Just to reiterate - the 'program' file was lodged in the root directory of my D drive - hence your comment:
'I can only imagine something is running on your PC (maybe malware/spyware) that tries to run programs from your Program Files(x86) folder at boot time.' isn't correct at that point unless I have missed your argument.
Just a last check on what name would be given to the scheduled task - and then I really don't want to bother you guys more - you have been more than helpful.
Oh - but can I clarify - the prog doesn't call up a particular service does it? When I was using msconfig without the bootup files but WITH all services, there was no issue.
Cheers
-
I have removed as much of Downloadstudio as I can manage - its seems to have sprayed itself around the registry!
Replacing the errant file brings back the problem. However removing the Logitech Webcam updater kills it again, confirming to me that there were in facet two progs which called up the file. Go figure!!
Cheers
-
Hi guys,
I am grateful for the fuller explanation of the workings of the program. I am considering eliminating Downloadstudio as to be honest it hasn't been all that useful.
Just to completely eliminate the scheduled task on boot-up line of enquiry - would the task be fairly clearly identified as with HG612 in the title or some such thing? I can see other tasks but no obvious connection.
It should be obvious. This is the task info from my PC:-
Folder: \
HostName: PAUL-PC
TaskName: \HG612 Stats Program
Next Run Time: 22/02/2014 21:42:00
Status: Ready
Logon Mode: Interactive/Background
Last Run Time: 22/02/2014 21:41:00
Last Result: 0
Author: Paul
Task To Run: "C:\HG612_Modem_Stats\Scripts\HG612_Run.exe"
Start In: N/A
Comment: This task runs the HG612 modem stats logging program every minute.
Scheduled Task State: Enabled
Idle Time: Disabled
Power Management: Stop On Battery Mode, No Start On Batteries
Run As User: Paul-PC\Paul
Delete Task If Not Rescheduled: Enabled
Stop Task If Runs X Hours and X Mins: 72:00:00
Schedule: Scheduling data is not available in this format.
Schedule Type: One Time Only, Minute
Start Time: 19:28:00
Start Date: 03/02/2014
End Date: N/A
Days: N/A
Months: N/A
Repeat: Every: 0 Hour(s), 1 Minute(s)
Repeat: Until: Time: None
Repeat: Until: Duration: Disabled
Repeat: Stop If Still Running: Disabled
I did run Hijackthis and Malwarebytes early on in the checking stage to eliminate if possible any viral infections, and I had a clean bill of health there.
Just to reiterate - the 'program' file was lodged in the root directory of my D drive - hence your comment:
'I can only imagine something is running on your PC (maybe malware/spyware) that tries to run programs from your Program Files(x86) folder at boot time.' isn't correct at that point unless I have missed your argument.
TBH, I was 'second-guessing' a little at that stage :lol:
The file seems to have been dumped higher up the folder tree than where it was intended it to go (due to it incorrectly not using a folder name that contained spaces).
When recreating the issue at my end, it stashed it in the folder one level up, the folder name at that level not containing any spaces.
Just a last check on what name would be given to the scheduled task - and then I really don't want to bother you guys more - you have been more than helpful.
By default, it will be named "HG612 Stats Program", as per the info shown above
Oh - but can I clarify - the prog doesn't call up a particular service does it? When I was using msconfig without the bootup files but WITH all services, there was no issue.
Cheers
No, it doesn't run as a service & it doesn't call up any services.
HTH.