I made a couple minor backports to v3.84.7, for anyone who needs them. I did NOT increment the version number, as v4 final is too close to bother people with an upgrade that they probably don't need. These improvements are to the default path selected when 'global path override' is used for the log and config folder, and some updates to hard-coded ProBalance exclusions.
Tuesday, 31 August 2010
Monday, 30 August 2010
The next beta version will, for real, have the long awaited graph tooltips over highlighted ProBalance events. Remember, it is the governor taking the action, so I had to get the inter-process communication code just right so that it was both time positioning accurate and asynchronous on the governor's end (so no blocking call). On the other side, the GUI's graph can't be stalling out in high load situations -- even if it has to go repaint events a second later than they occurred. Of course, the issue of multi-user systems with a single governor instance had to be handled too, as every instance of the GUI needs notified in such a case. I've got it perfectly designed now, simply. As always, when you find a simple solution, you know its the right one. So -- if you ever wanted to know why I put this off so long, just read above.. the feature is a good bit of critical design work that influences the efficiency of the software as a whole.
I've got it all designed and partially implemented.. it is just grunt work from here on ;). With all this overhead (which maybe some people didn't consider), I will provide an option to completely disable it.
Later, I'll add other tooltips to show general process information at any time along the graph, which is information the GUI already has at its disposal.
I'm also continuing code review and testing of version 4. There are a few bug reports remaining to be tracked down, but it won't take much longer to go final. My current goal is a release candidate this week. From there, the testing and my confidence level in the code will determine the final release date.
I've got it all designed and partially implemented.. it is just grunt work from here on ;). With all this overhead (which maybe some people didn't consider), I will provide an option to completely disable it.
Later, I'll add other tooltips to show general process information at any time along the graph, which is information the GUI already has at its disposal.
I'm also continuing code review and testing of version 4. There are a few bug reports remaining to be tracked down, but it won't take much longer to go final. My current goal is a release candidate this week. From there, the testing and my confidence level in the code will determine the final release date.
Sunday, 29 August 2010
As I clean up the beta and prepare it for final, the fixes come. One of the most important in this build is a fix to the new Task Scheduler integration of Vista and Windows 7. This allows Process Lasso to start at user login on the PC with highest rights and no UAC prompts. Unfortunately, non-English Windows users reported trouble from the start, with multiple reports of the error. I have now fixed this problem for those non-English users. The issue was simply that the 'Administrators' user group was not named 'Administrators', because it isn't English ;). MSDN had suggested the code I used, so I was a bit disappointed even Microsoft didn't consider this scenario.
Oh well, all is good now - I hope. If problems continue, report them and I'll fix them immediately.
Thank you to those who reported this anomaly in the v3.99 beta series.
Oh well, all is good now - I hope. If problems continue, report them and I'll fix them immediately.
Thank you to those who reported this anomaly in the v3.99 beta series.
Wednesday, 25 August 2010
I'm happy to report I finished the second beta tonight. This one is another large stride towards v4 final, and I'm glad to finally have it done. More work remains before final, but let me try to actually express what this new beta changes (since the last beta) in a somewhat useful and structured way.
First, the activation system has been expanded. This involved both back-end (server) and product work. I had to design it just right, to allow a variety of scenarios. You can now copy&paste the activation code right into the edit box. You also enter you name, which is shown in the About box that sports a new PRO bitmap as well ;). Unfortunately, for those that activated any previous build, you'll have to activate again. If you have ANY troubles, please email me immediately at support@bitsum.com and I'll fix them up ASAP.
This build also overhauls internal stuff you don't care about, but might if you're in a rare situation Specifically, inter-process communication stuff -- For example, so the core engine knows when 'you' told it to stop, or just looked to see if it was already running. However, this overhaul was only in relation to multi-user and governor as a service environments, and may not have actually improved any real-world situation.
Lastly, makes numerous cosmetic changes throughout. Some warnings are reworded, and may be reworded again. Some warnings added. Other minor tweaks made...
Many other little things were changed too, of course...
First, the activation system has been expanded. This involved both back-end (server) and product work. I had to design it just right, to allow a variety of scenarios. You can now copy&paste the activation code right into the edit box. You also enter you name, which is shown in the About box that sports a new PRO bitmap as well ;). Unfortunately, for those that activated any previous build, you'll have to activate again. If you have ANY troubles, please email me immediately at support@bitsum.com and I'll fix them up ASAP.
This build also overhauls internal stuff you don't care about, but might if you're in a rare situation Specifically, inter-process communication stuff -- For example, so the core engine knows when 'you' told it to stop, or just looked to see if it was already running. However, this overhaul was only in relation to multi-user and governor as a service environments, and may not have actually improved any real-world situation.
Lastly, makes numerous cosmetic changes throughout. Some warnings are reworded, and may be reworded again. Some warnings added. Other minor tweaks made...
Many other little things were changed too, of course...
I've completed the additions and tweaks to the activation system. This will be the one time you have to re-enter your activation code, at least if all goes as planned. On future upgrades, you will not have to enter it again. I had to account for many factors, such as update subscriptions expiring after a certain period and resellers who sell upgrades based instead on the major version number. Also, I wanted to include user names this time, so that customers can see their name in the About box.
Anyway, its all done now, and isolated onto a new server. As with the Forum, I decided it was best to keep the activation server separate from the main web site. The URL you'll see accessed is 'bitsumactivationserver.com' (port 80:http).
As for the release date, as soon as I fix a couple things, I will be publishing v3.99.15 beta.
Anyway, its all done now, and isolated onto a new server. As with the Forum, I decided it was best to keep the activation server separate from the main web site. The URL you'll see accessed is 'bitsumactivationserver.com' (port 80:http).
As for the release date, as soon as I fix a couple things, I will be publishing v3.99.15 beta.
Saturday, 21 August 2010
While I hope to add a few more things before final, I'm going beta with v3.99.14. It has enough of the features I added for the initial v4 release, and tests well enough in preliminary evaluation. So, welcome to the version 4 beta. At this point, I plan to meet my end of the month goal for Process Lasso v4 final. There is a lot of work between now and then, but I am currently on track to meet that goal. Enjoy ;).
Friday, 20 August 2010
I just uploaded v3.99.12, and will likely update v3.99.13 before this work-night is over. This new build was to correct a menu positioning error that caused watchdog context menus to be 'out of whack' in v3.99.11 (only). I wanted to address this problem real fast, before moving on to general polishing. Now that I only have 4 builds to create for each release, it is much less tedious. Some day I will buy a faster CPU that will further decrease the build time.
We're 90% of the way there now. The graph tooltips will be the last major feature to add, from there its all polishing and minor changes. I intend to add some new graphical images to better represent the massive internal changes that took place. Those who've tried the current alpha know a lot of work has gone into it.
Enjoy, and keep an eye out every day for new updates, lol ;). Actually, after tonight I promise I'll wait until at least Monday or Tuesday before publishing a new build. Some PECompact works beckons, and I feel obliged to work on it given my loyal PECompact supporters. Oh, then there is my marriage anniversary this weekend, that too ;p.
We're 90% of the way there now. The graph tooltips will be the last major feature to add, from there its all polishing and minor changes. I intend to add some new graphical images to better represent the massive internal changes that took place. Those who've tried the current alpha know a lot of work has gone into it.
Enjoy, and keep an eye out every day for new updates, lol ;). Actually, after tonight I promise I'll wait until at least Monday or Tuesday before publishing a new build. Some PECompact works beckons, and I feel obliged to work on it given my loyal PECompact supporters. Oh, then there is my marriage anniversary this weekend, that too ;p.
ictures say a thousand words.
I've added a new GLOBAL Watchdog option to divide *all* CPU thresholds by the number of CPUs on the target system. This lets you set a static value (e.g. 100%) and that value be relative to the total CPU count on the system to which it is applied. Its useful mostly for single thread apps. Consider the case of a single thread consuming every CPU cycle it can get. On a single core system, this is 100%... but on a dual core system, it is 50%, and on a quad core system it is 25%, etc..
This is the new Watchdog config dialog in v3.99.11 alpha, coming within hours:
Thursday, 19 August 2010
I have been mostly please with v3.99.10. Despite a couple more features needing to be implemented, I'm going forward with the move to beta. The numerous new features and optimizations are testing well, though more work does need to be done.
Why so soon? Again, my goal - v4 final by the end of the month. Whether I meet it or not, given my other workloads, I'm going for that goal. I want people to experience this massive improvement as soon as possible.
Why so soon? Again, my goal - v4 final by the end of the month. Whether I meet it or not, given my other workloads, I'm going for that goal. I want people to experience this massive improvement as soon as possible.
Lately a lot of these 'system tune-up' companies have added features they claim similar to Process Lasso's ProBalance. Let me urge caution, without being disparaging of anyone. It took years to refine the ProBalance algorithm, even though I'm an expert in this field. Put simply, it takes real world testing and feedback before you truly know if you've 'got it right'. I strongly recommend you disable any feature similar to ProBalance when found in other PC tune up software. After all, Process Lasso consumes almost no resources and will do the job better.
That's just my word of advice, and comes from me evaluating some of these new 'features' seen on tune-up utilities.. as well as experience with my own mistakes years ago. Since I am obviously biased, I do encourage you to try their mechanisms for yourself if you want.
I know something about software development and marketing -- but not much about business. I do know how the 'business type' operates though, and is why I intentionally try to avoid that mindset. What you're going to find is that most utilities are more interested in selling you something than actually doing anything for you. That's not always the case, and there are exceptions. Just beware, that's all.
That's just my word of advice, and comes from me evaluating some of these new 'features' seen on tune-up utilities.. as well as experience with my own mistakes years ago. Since I am obviously biased, I do encourage you to try their mechanisms for yourself if you want.
I know something about software development and marketing -- but not much about business. I do know how the 'business type' operates though, and is why I intentionally try to avoid that mindset. What you're going to find is that most utilities are more interested in selling you something than actually doing anything for you. That's not always the case, and there are exceptions. Just beware, that's all.
After assigning keys to all existing users, I've updated v3.99.10 alpha so that all builds are the same. Activating the trial build is the same as downloading from our Support area. This will make updates considerably easier.
In theory, registered users should see their activation codes when they go to get the upgrade. They'll then know what they mean when they install the software.
Anyone who has any troubles should contact support@bitsum.com. I know road to v4, and the transition to activation codes has been a tedious and confusing one, but we're almost there. There has been a lot of behind the scenes work to make this happen. After all, I don't just build software, I build the system and engine that processes orders for that software ;)
In theory, registered users should see their activation codes when they go to get the upgrade. They'll then know what they mean when they install the software.
Anyone who has any troubles should contact support@bitsum.com. I know road to v4, and the transition to activation codes has been a tedious and confusing one, but we're almost there. There has been a lot of behind the scenes work to make this happen. After all, I don't just build software, I build the system and engine that processes orders for that software ;)
Wednesday, 18 August 2010
All Process Lasso Pro customers should now have activation codes assigned to them. They are listed in the Support area. I also restructured the database and improved its efficiency by a few thousand percent, in case I ever get really huge ;). More database restructuring and work is needed, and some anomalies could exist. I'm building new scripts to try to catch any anomalies, but simply email us at support@bitsum.com if you discover one and we'll fix it right up. This includes things like you not getting an activation code, or your activation code no longer working.
All paid users of Process Lasso are now being assigned activation codes for the up-coming version 4. Due to me not perfectly making this transition, I have caused a lot of confusion (and headaches for myself). I apologize to anyone inconvenienced.
Soon when you login to the Support area, you'll see an activation code listed along with the download options. If you aren't asked for it, don't worry.
One finally caveat is that in v3.99.10 alpha there are still some inconsistencies with the activation code. The build thinks its activated in parts, and thinks its the old free build in others. I'm correcting all this in v3.99.11 (to be released tonight).
I'm SO SORRY for the confusion. I've still got much more work to do. I need to do some database redesign to improve server and lookup efficiency, and ease of code. Also, I've got to make sure everything works with regards to the timed update subscriptions.
Whew, well here goes... Wish me luck ;). So far about half of users have been assigned keys. In order to not overload the server due to my less than optimal database structure, I'm doing it in batches.
Soon when you login to the Support area, you'll see an activation code listed along with the download options. If you aren't asked for it, don't worry.
One finally caveat is that in v3.99.10 alpha there are still some inconsistencies with the activation code. The build thinks its activated in parts, and thinks its the old free build in others. I'm correcting all this in v3.99.11 (to be released tonight).
I'm SO SORRY for the confusion. I've still got much more work to do. I need to do some database redesign to improve server and lookup efficiency, and ease of code. Also, I've got to make sure everything works with regards to the timed update subscriptions.
Whew, well here goes... Wish me luck ;). So far about half of users have been assigned keys. In order to not overload the server due to my less than optimal database structure, I'm doing it in batches.
I completed many of the remaining functional additions needed to go to beta, but new features were added to my list at the last minute. So, I'm holding this new build in alpha stage. To be clear, it is a good new build, but I am just comfortable calling it beta yet. In theory, beta should be at least mostly feature complete.
This build finishes the third process watchdog type - CPU affinity change based on CPU utilization. It also makes quite a large number of other changes and fixes. One of them is a new Start Menu shortcut to help recover from a lost system tray icon (a bug I am tracking down). I've seen this occur in my test beds on rare occasions, so until I have fixed it I've added this easy ability to regain access to the GUI without having the manually terminate ProcessLasso.exe.
Much more work remains, but I intend to stay awake for as much of the next few days as I can and get this done. I want to begin testing this weekend.
Perhaps the big problem was trying to make such a large leap in version 4. I deviated from my slow, incremental development. We'll see if it pays off in the long run. I do know that it must be frustrating for users to have to wait for these new features to go final. However, most users can attest that my alphas and betas are generally stable and perform well. Of course, they are pre-release builds for a reason -- so use at your own risk.
When am I going beta? This week. Bet on it. There will likely be daily builds from here on out. The big stuff is done, its little things I'm correcting and adding from here on out.
Process Lasso
This build finishes the third process watchdog type - CPU affinity change based on CPU utilization. It also makes quite a large number of other changes and fixes. One of them is a new Start Menu shortcut to help recover from a lost system tray icon (a bug I am tracking down). I've seen this occur in my test beds on rare occasions, so until I have fixed it I've added this easy ability to regain access to the GUI without having the manually terminate ProcessLasso.exe.
Much more work remains, but I intend to stay awake for as much of the next few days as I can and get this done. I want to begin testing this weekend.
Perhaps the big problem was trying to make such a large leap in version 4. I deviated from my slow, incremental development. We'll see if it pays off in the long run. I do know that it must be frustrating for users to have to wait for these new features to go final. However, most users can attest that my alphas and betas are generally stable and perform well. Of course, they are pre-release builds for a reason -- so use at your own risk.
When am I going beta? This week. Bet on it. There will likely be daily builds from here on out. The big stuff is done, its little things I'm correcting and adding from here on out.
Process Lasso
Tuesday, 17 August 2010
As you know, every once and a while I have a sale on home prices. I figured now was a good time, so I implemented the typical reduced prices. If I could get a good boost of orders at these lower prices, perhaps they could remain permanent. Regardless, I hope it allows some people to purchase the product that couldn't otherwise.
We also have a brand new product page on Facebook. It just started today, so is empty, but won't stay that way for long (I hope).
We also have a brand new product page on Facebook. It just started today, so is empty, but won't stay that way for long (I hope).
Monday, 16 August 2010
Well the TrialPay experiment has went on longer than a month or so. It seemed most effective when I first started using it, but then went downhill. I suspect as its popularity increased, the value it offered to users was less and less. For this reason I've removed it form the main order page and put it on the 'cheaper short term licenses' page. It simply wasn't worth the extra licensing confusion ;(.
Sunday, 15 August 2010
I'll be mentioning the many new features coming in version 4 over time. There are so many, I don't know where to start. I mentioned before my optimizations to the icon loading. I rewrote this code from scratch, doing it the 'hard way'. The result is:
- Memory use by the GUI is reduced by 40-60% (depending on the number of processes). Yes, it seems amazing, but its true. I accomplished this by optimizing my storage of process icons in memory.
- Loading of the GUI is considerably faster with less hard drive accesses. In the older version, a lot of hard drive accesses were done to get process icons. My process icon optimizations have improved this substantially.
At present no competitor has done this, and they probably won't. It is one of those things that takes time and energy, and most businesses would simply say 'its not worth the effort'. That is why my little business is different. I do things not with business in mind, but rather pride in my craft. I love what I do, and that's why I do it. I use my software every day.
I've all mentioned this before, but I thought I'd mention it again. As soon as I launch v3.99.10 beta, I encourage all adventurous users to migrate to it. I need YOUR help in tracking down bugs and other anomalies. With luck, we'll be going final by the end of this month!
Friday, 6 August 2010
Those of you following the alpha versions have seem dramatic increases in functionality, and know much more is planned in the next release. I've held this next version a bit longer than usual, making more and more changes. It will be an official beta build, as opposed to alpha. Specifically, we are talking about v3.99.10 beta.
Despite what the version number may suggest, this is the code that will be version 4 of Process Lasso. This series makes some giant strides in functionality and even markedly decreases virtual memory use of the GUI (yes, even further).
It is past time for the evolution to end though. People need a new, fully regression tested final version. I intend to make this happen this month. The beta series will be short. I've been careful with my changes, and have recruited some help to ensure I don't miss anything. You can help too, by experimenting with this new version. I'll say that I run it on my own PCs, but can't make many other warranties given that its a pre-release version. Its up to you, but if you do participate - please let us know your feedback in the Forums.
Despite what the version number may suggest, this is the code that will be version 4 of Process Lasso. This series makes some giant strides in functionality and even markedly decreases virtual memory use of the GUI (yes, even further).
It is past time for the evolution to end though. People need a new, fully regression tested final version. I intend to make this happen this month. The beta series will be short. I've been careful with my changes, and have recruited some help to ensure I don't miss anything. You can help too, by experimenting with this new version. I'll say that I run it on my own PCs, but can't make many other warranties given that its a pre-release version. Its up to you, but if you do participate - please let us know your feedback in the Forums.
Thursday, 5 August 2010
For a while now I've planned to switch to activation codes in version 4. In fact, the early alpha builds allow that. However, this transition was not handled well, and therefore some confusion has been caused. The slow transition to RegNow also complicated matters, as they pretty much mandated use of activation codes, and generally had no option but to 'take over' our existing system. So, users who order from RegNow get an email that says 'here is your software and here is the activation code'. That's fine and dandy, except the proper procedure is to log in to our Support area and download your licensed software. The copy RegNow gives you is fine, and may or may not ask for an activation code (depending on which license you ordered). If it doesn't ask, no worries -- it is pre-activated.
Anyway, I am working diligently on clearing all this up. For now, know that unless you are asked for an activation code, don't worry about it. Mostly they are being granted for future use.
As soon as I assign activation codes for all existing users and make some modifications to the activation system, I'll be ready to fully start using the activation codes. This isn't wholly new technology, I've used it in overseas resellers and Server Edition builds for some time. However, it is new to home user orders.
Please bare with us, and I apologize for this confusion.
Anyway, I am working diligently on clearing all this up. For now, know that unless you are asked for an activation code, don't worry about it. Mostly they are being granted for future use.
As soon as I assign activation codes for all existing users and make some modifications to the activation system, I'll be ready to fully start using the activation codes. This isn't wholly new technology, I've used it in overseas resellers and Server Edition builds for some time. However, it is new to home user orders.
Please bare with us, and I apologize for this confusion.
Subscribe to:
Posts (Atom)