Started by Jeremy Collake, July 22, 2012, 05:05:57 AM
Quote from: neophil78 on July 23, 2012, 11:10:00 AMToo much weird things in the final V18.104.22.168 version !!! Though i'm doing a roll back to 22.214.171.124EX: it's the last application to load on startup, which is a bit strange for a soft which is supposed to control CPU ...
Quote from: Victek on July 23, 2012, 03:50:19 PMHow are you determining it's the last application to load? You have the core engine and the management console. I would think PL is already on the job when the engine is loaded and it doesn't matter exactly when the tray icon representing the console shows up. I don't know how to determine when the engine loads though.
Quote from: neophil78 on July 23, 2012, 05:36:32 PMEuh, as far as i know, the last icon to show up is the one of the last prog to have been launched (at least on XP, which is my OS)
QuoteThis is a warning that the System Tray Icon may take a while to show on startup. This is intentional. A lot of processing is done before the initialization of the system tray backing window is done. We also prefer to wait and let the system 'settle down' before invoking the GUI of Process Lasso. So, give it some extra time .
Quote from: neophil78 on July 23, 2012, 11:10:00 AMLink to Bitsum URL doesn't work from the GUI interface
Quote from: neophil78 on July 23, 2012, 11:10:00 AMHow can the program may decrease from about 50% size
Quote from: neophil78 on July 23, 2012, 11:10:00 AMP.S: are they specific .exe to allow by the firewall ?
Quote from: bitsum.support on July 23, 2012, 09:51:05 PMWhat browser are you using? That is strange. What is the name of your browser's EXE file (in case it is different in French by chance)?
Quote from: bitsum.supportRemoval of the 1MB English CHM Documentation from the Installer. For ENGLISH users there is the option to download this during install. For non-English users it is assumed they don't read English, so it isn't asked about. Instead, the online documentation is referenced - which has been translated to a couple other languages.
Quote from: bitsum.supportProcessLasso.exe, QuickUpgrade.exe, and plActivate.exe
Quote from: edkiefer on July 24, 2012, 12:01:50 PMyes, web links don't seem to work on these browsers (each set to default) , FF 3.6, IE8, Palemoon 12.3 .this is on ver 126.96.36.199
Quote from: neophil78 on July 24, 2012, 09:29:00 AMTrouble is also the same with PL 188.8.131.52 with one more: when checking if there's a newer version and if yes, a line "error:missing string" is appearing in the downloading/installing window ...Don't have this option and BTW the english CHM is present in C:\Program Files\Process Lasso\PROCESSLASSO.CHM (1169 Ko) perhaps a file which has not been removed when updating from V5 to V6 ??
Quote from: neophil78 on July 24, 2012, 09:29:00 AMDon't have this option and BTW the english CHM is present in C:\Program Files\Process Lasso\PROCESSLASSO.CHM (1169 Ko) perhaps a file which has not been removed when updating from V5 to V6 ??
Quote from: bitsum.support on July 25, 2012, 04:47:17 AMMissing Strings in Auto-Updater Download DialogGuidance is a proper/manual install of version 6. No need uninstall version 5, but best to install version 6. This is just to make sure the auto-update component is updated. In version 5, it is updated only if the GUI has access to update it at any point (yes, I was not that concerned with updating it, as it doesn't normally need updating). In version 6 I can force updates to it, as I have in all current builds so far, but will likely stop in the future so that people with firewalls won't be annoyed .For those running 2K/XP or running the GUI with elevated rights, this problem should take care of itself in the next update.
Quote from: neophil78 on July 25, 2012, 08:49:39 AMWith update 184.108.40.206 it now open the bitsum URL once in a new tab of browser and open as well once in a new window BTW i still get an "error: missing string" appearing in the windows when updating (french version still on XP SP3 and on different PC's)Cheers
Quote from: bitsum.support on July 25, 2012, 11:35:54 PMYes, the first build of .60, which lasted a few minutes, opened two links.. better than none I suppose ;p. I didn't want to make a big deal of it, and just uploaded a new build.Believe it or not though, these minor issues are very minor in comparison to prior major versions. In the past, when things get out of beta, I'd find out about problems I didn't know about. However, for version 6, things have been pretty smooth where it *counts*. I hope that perception isn't changed with the minor updates I've done. Now that the user can set the update check frequency, I figure I am at liberty to issue them as rapidly as needed ;p. That said, I will slow down, just making sure anything that might affect the perception of the product is fixed.The see-saw graph you once saw for instance - tracked it down in .61. It was all a matter of very unlucky timing for a random few people. It was otherwise benign, just a display issue, as the CPU % used was not actually spiking - it was an illusion.
Quote from: edkiefer on July 25, 2012, 11:12:40 PMsame here with missing string with .61 and I also did manual update .The web links work here now, just 1 new tab opens now for me .XP SP3
Quote from: bitsum.support on July 26, 2012, 08:13:45 AMA proper install over top your existing one should resolve any missing string errors during the brief update download dialog. They may also self-resolve. I have described it elsewhere, but basically the guidance is to do a proper installation of v6.
Quote from: edkiefer on July 28, 2012, 06:54:14 AMUpdate: confirmed .62 the string error is fixed .
Quote from: edkiefer on July 28, 2012, 08:36:53 AMright, I did DL the test build (.61+ ) .
Quote from: neophil78 on August 01, 2012, 09:18:06 AMSorry to bring a bad news but it's not fixed for me with the .64 version on one PC
Quote from: neophil78 on August 01, 2012, 09:20:30 AMWhere's a link to that test build ?
Quote from: bitsum.support on August 01, 2012, 09:30:00 AMThank you for the report. Most users reported the issue was resolved, so this is interesting. Is it possible that one PC was updating from an OLDER build? The fix occurred in .62, so if *that* PC was running anything less than .62, then it would still see the missing strings during the update download.The test build later went final. So, it is the final build ;p. A manual re-install will definitely fix up the issue for the *next* update, FWIW - though an automated update should have also fixed it fine. I should also mention to any readers that we are speaking of a cosmetic error in the auto update download dialog, one that has no other functional impact.