I get this message (see uploaded image) when running the installer in the scripts folder.
This is a Vista 32bit OS.
64bit binary then.
why you still on 32bit?
I get this message (see uploaded image) when running the installer in the scripts folder.
This is a Vista 32bit OS.
Sorry about that. I thought I had created a version that would work with 64bit & 32bit systems.
I have created another version for 32bit systems that also works on my 64bit W7 system.
I'll let you know as soon as Ronski has made it available for download.
If that still doesn't work, I could provide a plain zip file for unzipping & then running the updater program
O.K. Ronski has now replaced the program (same download link) with the 32bit version that should work on all Windows versions from XP upward.
23/06/2014 23:19:50.61 - **** ERROR!!! - ini_parse() - Couldn't open ini file for reading ****
hmm I not got it yet, is now no way to get the 64bit version?
23/06/2014 23:19:50.61 - **** ERROR!!! - ini_parse() - Couldn't open ini file for reading ****
Was that a one-off or is now it a constant issue?
The updater program should have read your original ini file & then updated it with your existing settings plus any new/missing v 3.0.0.0 settings.
That messages suggests that the ini file is missing, locked or corrupted.
If it's not completely missing, could you post it for me to have a look?
Why do you want the 64bit version, you said yourself that the 32bit version will run fine on 64 bit? It was only the installer file that was 64 bit the programs contained within are still 32 bit.
The logging/graphing programs are all 32 bit anyway.
It's only the updating program that I changed last night from 64 bit to 32 bit.
It works as 32 bit at my end (W7 64 bit system).
It does seem to have been a one off and I don't see any errors to-day.
As for the ini file I can't find or see one for HG612_Modem_stats, also checked in the C:\User\Name\AppData\local can see DSLstats configuration file and others.
Which location should it reside ?
it will run but isnt ideal.
since you compiled it I suggest distributing both versions from now on, as 32bit has to run on a emulation layer. The vast majority of people run 64bit now days anyway.
It does seem to have been a one off and I don't see any errors to-day.
As for the ini file I can't find or see one for HG612_Modem_stats, also checked in the C:\User\Name\AppData\local can see DSLstats configuration file and others.
Which location should it reside ?
It is named HG612_stats.ini
It has to reside in the Scripts folder otherwise you would see the error message every minute.
Do you have the view option set as "Hide extensions for known file types" in the folder options menu?
If so, you are likely to see more that one file named HG612_stats, but with different icons, one of which will be the ini file & another will be HG612_stats.exe
Everything looks O.K. there :)
I wonder if the hickup was down to timing, I'm not sure what checks BE1's update program does, but if the logging was not turned off then it is possible the INI file was being read by one of the logging programs when you tried to update them.
I've spent over 5 hours tonight rewriting the update code in the GUI to handle all the major parts of the programs, so I am progressing. Should be able to get a fair bit more done tomorrow night, then it's just a case of fine tuning it.
There is a Microsoft article & hotfix available here:-
http://support.microsoft.com/kb/2461249/en-us?sd=rss&spid=14019
these issues will become more frequent now microsoft have abandoned service packs :(
many hotfixes are not on windows update, 100s of them if not 1000s. They usually get rolled out in service packs instead.
Just want to see if thoses exit_2_Instances errors comes back before I install the hotfix, just me being over cautious :D
However, as there is only a split second between each instance starting, both instances can occasionally be deleted, especially if some other program has slowed the PC down. e.g. an anti-virus program hogging a lot of CPU resource.
these issues will become more frequent now microsoft have abandoned service packs :(
many hotfixes are not on windows update, 100s of them if not 1000s. They usually get rolled out in service packs instead.
What no service packs :( I always looked forward to SP day and installing them, though I can see why as if you don't have enough battery left in your laptop or someone turns off the Desktop during the service pack installation then it's hello Black Screen of Death :no:
HG612 Modem Stats v 3.0.0.0 - Updating existing programs
Microsoft Windows [Version 6.3.9600]
Modem type = HG612
The location for the ongoing log folder WAS specified
**********************************************
Continuing will extract the updated programs to the Scripts folder
The original programs will be renamed.
e.g. GRAPH6_2014-07-16-0115.exe
**********************************************
Continue? [Y]es / [N]o
Programs_update = 0
Existing [GRAPH6.exe] modified 2014-06-22-1727
Updated [GRAPH6.exe] modified 2014-06-22-0146
*** New file is older than original file ***
*** NOT Updating [GRAPH6.exe] ***
Existing [graphpd.exe] modified 2014-06-22-1727
Updated [graphpd.exe] modified 2014-06-22-0146
*** New file is older than original file ***
*** NOT Updating [graphpd.exe] ***
Existing [HG612 Stats logging GUI.exe] modified 2014-06-22-1755
Updated [HG612 Stats logging GUI.exe] modified 2014-06-18-1918
*** New file is older than original file ***
*** NOT Updating [HG612 Stats logging GUI.exe] ***
Existing [HG612_current_stats.exe] modified 2014-06-22-1727
Updated [HG612_current_stats.exe] modified 2014-06-22-0146
*** New file is older than original file ***
*** NOT Updating [HG612_current_stats.exe] ***
Existing [HG612_Run.exe] modified 2014-06-22-1727
Updated [HG612_Run.exe] modified 2013-03-15-0037
*** New file is older than original file ***
*** NOT Updating [HG612_Run.exe] ***
Existing [HG612_stats.exe] modified 2014-06-22-1727
Updated [HG612_stats.exe] modified 2014-06-22-0147
*** New file is older than original file ***
*** NOT Updating [HG612_stats.exe] ***
Existing [SET_HG612_DATE_AND_TIME.exe] modified 2014-06-22-1727
Updated [SET_HG612_DATE_AND_TIME.exe] modified 2014-06-22-0147
*** New file is older than original file ***
*** NOT Updating [SET_HG612_DATE_AND_TIME.exe] ***
*************************************************
Extracting updated Modems.txt to Editor folder
*************************************************
Removing all files from the Temp folder
Removing Temp folder
Press a key to exit.....
Microsoft Windows [Version 6.3.9600]
Is that Windows 8.1?
I don't have that version for testing anything.
It seems almost all your existing programs have the time stamp 2014-06-22-1727. i.e. newer than the actual updated programs:-
Existing [HG612_stats.exe] modified 2014-06-22-1727
Updated [HG612_stats.exe] modified 2014-06-22-0147
*** New file is older than original file ***
*** NOT Updating [HG612_stats.exe] ***
I'll assume that however you installed the original programs, it actually changed the file modified dates to the time they were installed.
Following the attempted update, you should have a file named Updated_Programs.zip in the Scripts folder, containing the real updated files.
You could try unzipping that file to the Scripts folder & allow the existing files to be overwritten.
Even if the modified dates are changed again, you should at least then have the real updated files.
To check which versions you have, right clicking on say HG612_stats.exe, then clicking Properties & then clicking the Details tab should show something like shown in the attachment to this message.
i.e. :-
File version 3.0.0.0
Product version 3.0
Date modified 22/06/2014 01:47
Please let me know if that works.
also to BE I will test medium on my rig this week.
Is it enough to just say works or you also want logs even if works?
I'm not seeking to start a firewall conversation in this modem stats thread, I'm just curious to know if isrunningvb.exe really does occasionally seek access, or if the 'funnies' are even 'funnier' than I think.