Install option in busybox was intentionally disabled so if you want a symlink to something create it as follows.
ln -s busybox <applet>
and it will work as expected in most cases.

Latest builds: http://icarus.robertpendell.com/busybox/latest/
All builds: http://icarus.robertpendell.com/busybox/

Note: There is an experimental folder. This links to the git entry in the all builds list. The builds are from the git repository and may be unstable. I have done as much as I can though to get the configuration of the git build to the stable one. Certain applets may be depreciated and unavailable though.

P.S. – The only reason why they are being hosted there is because the compile environment also resides there. Just makes it quicker to post.

Update (5/17/2012): The above urls have been defunct for quite some time. Just finally got around to striking them out. I also discourage actually doing any symlinks to busybox on android devices as it may cause issues. Most apps with do busybox now anyways which works universally across devices assuming the build has the particular applet compiled in.

Google Account
Wordpress.com — You must have an active blog to use OpenID with this provider
Facebook
Twitter — Janrain Engine prompts for an email address to finish registration. This was during testing when I had anonymous comments off. This may be different now that was turned back on.
OpenID (That’s any site that supports the protocol)
Windows Live Login

The last one was kinda a pain. I had to setup a privacy policy to meet their requirements.

Eventually I will likely have the headers completed. This will fill a mobile gap but this app will not allow commenting. You will still need to go through the website like normal for that. Feed.nu plans on spreading to iOS eventually so I will have a version for that platform at that point.

Want a beta version? Let me know.

Right now I have 2 email only domains (elite-systems.org and elitesystems.org), 2 experimental domains (esminefield.com and esminefield.net), my primary domain (robertpendell.com) and a domain used for short urls (rplnk.com). bit.ly takes care of the back end hosting for the short urls and gmail takes care of all email for me.

Law firm AbingtonIP has revealed that it’s currently “investigating” what it calls the “convenient” Xbox Live bannings over modded consoles.

The firm believes that it’s no coincidence that Microsoft banned “tens of thousands” of users after receiving its money for Gold memberships, post release of Halo 3: ODST and Call of Duty: Modern Warfare 2. Therefore, the law firm is considering a suit in order to get the membership fees refunded to subscribers along with a “refund for the prorated sums”.

Now then I know of at least one person affected by the huge “ban wave” that went through.  Having followed along with the underground community I know what kind of impact this has made.  Many people have answered back after being banned by stating that they were going to get a Playstation 3 console.  It is also seen that most people who do mod their console are paying customers for XBox Live and also pay for XBox Marketplace content like arcade content, game addons or map packs, and videos.

Quote Source: http://www.neowin.net/news/gamers/09/11/19/firm-considers-class-action-over-xbox-live-bannings

Update: The following instructions were updated on 5/7/2010 because some of the directions were wrong. I found on my last cloning job that the entry that maps the recovery entry and the options for that entry are different by one character. Usually incremented up one it is the 8th character in most cases. I show it below in the examples but the actual command string examples fail to show that and I don’t indicate it in the base command lines. I have corrected that below.

After a drive clone (and possibly in other scenarios) you may end up being unable to boot the “Repair Your Computer” option. It may give you an error that it failed to locate the specified partition or device. Here is what you need to fix the issue. Just to show you what I am referring to I will give you a screen capture of the result when you try and use that option after a clone. The issue was replicated under a 2 drive scenario using vmware. One was a 40GB and the other was an 80GB.

Before we get started we need to open an adminstrator command prompt. If you don’t know how to do it then you can do it by clicking on Start and at the bottom type in ‘cmd’ and you can either do Ctrl+Shift+Enter or you can right-click on the cmd entry that now appeared and choose ‘Run as Administrator’. This will remain true for any of the following instructions. You may open a new one as needed.

First you need to list all entries (and I mean all of them) from bcdedit:

bcdedit /enum all

Next you need to find the identifier to the installation that is affected. For each entry in bcdedit they have their own repair options. Look for the one that has the description of your boot entry. As an example here is mine.

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    Windowssystem32winload.exe
description             Windows 7
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {9989caf8-c72d-11de-998a-d8acbaea39b0}
recoveryenabled         Yes
osdevice                partition=C:
systemroot              Windows
resumeobject            {9989caf6-c72d-11de-998a-d8acbaea39b0}
nx                      OptIn

Note the recoverysequence line because that is now our enum (enumerator). I will refer to it as <enum> where you need to insert it. Don’t note the braces. Just the letters, numbers, and hyphens. The recoverysequence and resumeobject lines will always match the identifier for the operating system in question. You will also need note the part on the line that says osdevice and what it shows right after the equal sign (=). I will reference it as <drive> where needed. I have bolded the relevant parts. In this instance we will make note of 9989caf8-c72d-11de-998a-d8acbaea39b0 as our recovery enum and C: as the drive itself.

Now then further down (and in fact right below) you should see this. It should have the recovery enum as noted above.

Windows Boot Loader
-------------------
identifier              {9989caf8-c72d-11de-998a-d8acbaea39b0}

At the very end we should see the next set of lines. You will note the ramdisksdipath line includes the recovery enum.

Device options
--------------
identifier              {9989caf9-c72d-11de-998a-d8acbaea39b0}
description             Ramdisk Options
ramdisksdidevice        unknown
ramdisksdipath          Recovery9989caf8-c72d-11de-998a-d8acbaea39b0boot.sdi

The issue on the last one is that it is supposed to be the recovery lines but it is otherwise blank. On the one right above the ramdisksdidevice says it is unknown. Note that this entry contains our options enum which is bolded above. Please keep that for record as we will need it during our instructions. In the above example it is 9989caf9-c72d-11de-998a-d8acbaea39b0. Here is how we are going to fix it.

Run the following commands and this will fix the first set of issues.

bcdedit /set {<recovery enum>} device ramdisk=[<drive>]Recovery<recovery enum>winre.wim,{<options enum>}
bcdedit /set {<recovery enum>} osdevice ramdisk=[<drive>]Recovery<recovery enum>winre.wim,{<options enum>}

So in my case I would run the following to try to repair the first part.

bcdedit /set {9989caf8-c72d-11de-998a-d8acbaea39b0} device ramdisk=[C:]Recovery9989caf8-c72d-11de-998a-d8acbaea39b0Winre.wim,{9989caf9-c72d-11de-998a-d8acbaea39b0}
bcdedit /set {9989caf8-c72d-11de-998a-d8acbaea39b0} osdevice ramdisk=[C:]Recovery9989caf8-c72d-11de-998a-d8acbaea39b0Winre.wim,{9989caf9-c72d-11de-998a-d8acbaea39b0}

Unfortunately even after running that you will still have the issue. When you try and run them please run them in the order above. If you get an error doublecheck your lines but otherwise you will need to reboot before you can try again. Once you do that though you should be able to find something like the following when you run our original command again. Note that there is a difference in the actual enum strings used for the recovery and option identifiers. It is mentioned earlier how to get those identifiers.

Windows Boot Loader
-------------------
identifier              {9989caf8-c72d-11de-998a-d8acbaea39b0}
device                  ramdisk=[C:]Recovery9989caf8-c72d-11de-998a-d8acbaea39b0Winre.wim,{9989caf9-c72d-11de-998a-d8acbaea39b0}
path                    windowssystem32winload.exe
description             Windows Recovery Environment
inherit                 {bootloadersettings}
osdevice                ramdisk=[C:]Recovery9989caf8-c72d-11de-998a-d8acbaea39b0Winre.wim,{9989caf9-c72d-11de-998a-d8acbaea39b0}
systemroot              windows
nx                      OptIn
winpe                   Yes

The rest of the lines (other than the 2 we did) will auto-populate into the list for you. After you confirm it you will need to reboot so the system can reload the BCD store. The next command will not work until that is done.

Once the system is rebooted you can run this command finally. It will fix the second issue.

bcdedit /set {<options enum>} ramdisksdidevice partition=<drive>

So for the second part I would run something like the next line.

bcdedit /set {9989caf9-c72d-11de-998a-d8acbaea39b0} ramdisksdidevice partition=C:

The last entry now should show something like this now.

Device options
--------------
identifier              {9989caf9-c72d-11de-998a-d8acbaea39b0}
description             Ramdisk Options
ramdisksdidevice        partition=C:
ramdisksdipath          Recovery9989caf8-c72d-11de-998a-d8acbaea39b0boot.sdi

Now then all you need to do is reboot and it should work fine now.

• Windows 7 is faster than Vista
• Windows 7 has less issues than Vista
• Windows 7 has less UAC prompts than Vista (but some are still present)
• Windows 7 has better hardware support than both Vista and XP
• Windows 7 has native and built-in biometric support (checked and tested with my upek brand fingerprint reader)
• Windows 7 uses less resources and has better memory management than both XP and Vista; Uses approx 33% – 50% on a normal day.  Even after extensive use doesn’t usually exceed 55%
• Windows 7 has virtually non-existent compatibility issues when moving from Vista.
• Going from Vista to Windows 7 is likely going to be fairly smooth unlike moving from XP to Vista.  XP to Windows 7 is still going to be bumpy but not as bad as the XP to Vista move since most companies are getting things out early this time around.

Now then I can’t really test performance of XP against Windows 7 but when I did XP against Vista I obviously found the latter to be slower on the same hardware.  Why?  Well XP is older so it will naturally run faster on newer hardware.  I did have a co-worker upgrade her netbook from XP to Windows 7 though and she reported a marked improvement in performance on it.  In addition she loved it more than XP so that was a very good thing.

On a Gateway P-7805u gaming laptop Windows 7 had an included driver for all devices except for graphics (expected) and media reader slots.  Oh wait it had half the driver for the media reader slots.  It also had a solution and that was to go to the Gateway site and download the proper driver.  The graphics it got from Windows Update but I would get the latest release from the OEM.