Known Issue on Windows 2000
So as I was informed in a comment by “Lighty2K” over here, apparently the process view and process kill tools that I am using in a few of the scripts do not run under Windows 2000. There were 2 other tools I was using at first from the old sysinternals guy that seemed to work OK but for those to run there was a EULA that had to be agreed to before each run. I have nothing against the EULA but it was just a step in the process that kinda got in the way during the scripts, and it also wrote the EULA agreement to the registry. Since Lighty 2 Go in meant to be portable I didn’t like the idea that there were settings left behind on the PC you were running Lighty 2 Go from.
I will continue to see if there are any other options that can address this.
If there are Windows 2000 users that would like me to re-build v0.4 with the PsTools for them and don’t mind the EULA etc. add a comment to this post and I will package it up for you.
Filed under: Lighty2Go
It was quite an adventure trying to replace the “XP-only” taskkill.exe and tasklist.exe with pskill.exe and pslist.exe. You seem to ran into the same EULA problems with the new “MS” version of pstools. A long thread on sysinternals forum mention that “-accepteula” switch will prevent the EULA pop-up. However, Clean-Up.bat has to be modified to remove the leftover registry keys. This is totally annoying and goes against the idea of portable software.
On the same forum, many “annoyed people” stated that older “pre-MS” version of PsTools does not include this new EULA “feature”. These old version was not easy to find since sysinternals removed them from their server and google cache no longer has the old sysinternals page. It did manage to stumble accross
PSTools 2.34. This the lastest version of PsTools before the Microsoft take-over. Needless to says, pskill.exe v1.11 and pslist.exe v1.26 work like a charm on win2k without the EULA popup and registry keys. Another bounus is the smaller filesize
Another possible optimization for Lighty2Go is using my-small.ini for MySQL. Memory usage for mysqld-nt.exe get reduced from 13.5MB to 4.5MB.
without_my-small.ini
with_my-small.ini
Once again, thank you for making this portable LiMP Stack availble. It is sure look a lot better than the previous WAMP tool:
Previous WAMP tool
BTW, the new site layout is very nice but the old color scheme is much easier on the eyes. It is not very comfortable viewing orange text on white background when you have a BRIGHT monitor
WOW –
Thanks for all the news and for the digging for the old PsTools version.
Was exactly what I was gonna go searching the net for, you saved me some time.
my-small.ini is something I’ll check out – like I mentioned before there is a lot of config to be added and changed, just had to get it working in a portable mode first. Keep the suggestions coming.
Sorry that the new colors are tough for you, yes the other one was a bit better, but I couldn’t stand the tiny little comment boxes. Stay tuned it may change again.
So I’ll re-package v0.4 tonight with the old pstools and release v0.5.
Thanks again ….
OK Lighty2K – version 0.5 is ready and I’ll be posting about it shortly.
Thanks again for finding the older pstools and the suggestions.
Also – I gave some play to my-small.ini and was able to cut the memory footprint of mysqld-nt but only by like half. I was able to get it from 12~13MB down to around 6~7MB but not all the way down to the 4.5MB you were getting.
I’ll continue to work on the config and test, but if you are interested in posting your my-small.ini that would be helpful to have for comparison.
That was a quick update
After looking all over the net for the taskkill.exe and tasklist.exe replacement, guess what I found in the “\Lighty2Go\LightTPD\bin” directory?
Process.exe
LOL, it works great for killing a process. It can’t quite list a single process.
The only line that I added to the default my-small.ini is:
skip-innodb
I thought the OS may make a different so I ran it on a WinXP machine. It goes from ~12MB down to 3.5MB. It does go up to ~5MB after a few test installations of wikis and blogs.
Yes process is OK for killing but the fact that it can’t show single processes is it’s downside. I think it can show a single process if you know the PID but that doesn’t really help much.
I’ll re-check my config of my-small.ini thanks for letting me know what you have.
So what wikis and blogs are you trying?
I am going to try WordPress, probably MT, media wiki, and something called activecollab but I’m looking for more ideas and suggestions of things to try.
Just trying a few basic tool to get some feedback on using it in a small intranet environment. The LiMP and other WAMP are great for demonstrationof these online tools. Since MS Office is widely use, a majority of the people won’t touch any of these tools unless it has a WYSIWYG editor (their exact quote is: “Something like MS Word”).
Dokuwiki is very easy to install but has no WYSIWYG.
Pmwiki is also nice after adding WYSIWYG.
Mediawiki is excellent since most people use it for info. On other WAMP tools, it works significantly faster with a PHP accelerator.
Wordpress is very very easy blogging.
Serendipity is also quite good.
If you can get the new Movable Type working on LiMP, please post instruction.
The collaboration tools are getting a lot more attention. One of the reason for this is centralization of information. It is very hard to get information out of an unorganized email box, lol. One thing that suprise me is people love the Learning Management System (LSM). If you replace the word course with project, you get a killer online collaboration tools. The learning path works very similar to Power Point, which is a major plus. So far, Atutor, DokeOS and Claroline has been getting very positive feedback. They are also very to install.
The new activecollab looks great. I wonder if it still going to be free.
Omnium Software 2007 look very good. I can’t get it to install because of all the PEAR requirement.
If you can write up a few instructions for getting some of these tools to work with LiMP (some has addtional requirement like GD, Perl, etc), it would be a great help.