We’ve written an HTML 5 Video Viewer for YouTube, and you can use it to browse YouTube in true 21st Century HTML5 quality. And it’s super-simple to use.

Flash has been the bane of online websurfers ever since the 90s, especially on platforms where Adobe doesn’t bother to go the extra mile to ensure that their proprietary, binary implementations are stable and efficient. On Linux and Mac OS X, the flash implementation takes up over half the available CPU and at high-resolutions stuttering occurs. HTML5 poses the answer providing a way for browsers to use the native implementations to render videos directly in the browser without resorting to ActiveX and 3rd-party browser plugins… it just has yet to be embraced.

But now you can uninstall Flash and enjoy your online videos in peace. Just go to http://neosmart.net/YouTube5/ and enter the URL of a video to watch it in the embedded HTML5 viewer. Yes, you can skip, skim, pause, resume away to your heart’s content.

Even better, we’ve written a GreaseMonkey/UserScript to add a link to all YouTube video pages that points to the HTML5 version, leaving you with no excuse to still use the Flash interface!

All modern browsers that support basic HTML5 are supported. You’ll need to have an MP4 decoder installed on your PC. Happy viewing!

Update:

It’s been brought to our attention that Firefox does not support streaming MP4 content due to licensing restrictions, and as we mention above, an MP4 decoder is a minimum requirement.

With Windows 7 released and currently making its way to shelves in time for the holiday season, we’ve taken this opportunity to upgrade our copy of the official Windows System Recovery Discs for compatibility with Windows 7.

If you’re like most PC users, you probably got Windows 7 with a new PC or laptop. And if you’re like 99% of the population, you get your new machines from one of the major manufacturers. Dell, Acer, HP, Toshiba, Lenovo; who all have one thing in common: they don’t give you a real Windows 7 installation disc with your purchase. Instead, they bundle what they call a “recovery disc” (that’s if you’re lucky – otherwise you’ll have a recovery partition instead) with your machine and leave it at that.

It doesn’t matter that you just paid a thousand dollars for a machine that comes with a valid Windows 7 license – your computer manufacturer just don’t want to spend the money (or perhaps take on the responsibility) of giving you a Windows 7 installation DVD to accompany your expensive purchase.

The problem is, with Windows 7, the installation media serves more than one purpose. It’s not just a way to get Windows installed, it’s also the only way of recovering a borked installation. The Windows 7 DVD has a complete “recovery center” that provides you with the option of recovering your system via automated recovery (searches for problems and attempts to fix them automatically), rolling-back to a system restore point, recovering a full PC backup, or accessing a command-line recovery console for advanced recovery purposes.

Thankfully, Microsoft seems to have realized this problem, and have thankfully made a recovery disc for this purpose. It contains the contents of the Windows 7 DVD’s “recovery center,” as we’ve come to refer to it. It cannot be used to install or reinstall Windows 7, and just serves as a Windows PE interface to recovering your PC. Technically, one could re-create this installation media with freely-downloadable media from Microsoft (namely the Microsoft WAIK kit, a multi-gigabyte download); but it’s damn-decent of Microsoft to make this available to Windows’ users who might not be capable of creating such a thing on their own. You can make your own copy from Windows 7 Ultimate Edition, but now you have an easier alternative.

NeoSmart Technologies is hosting a copy of the Windows 7 Recovery Disc for your convenience. It’s a 143 MiB download (165 MiB for the 64-bit version), and in the standard ISO format, ready to burned directly to a CD or DVD. Don’t wait until your PC crashes to download a copy! Download and burn your recovery disc today, so that when the time comes, you’ll be ready!

What it does: The Windows 7 Recovery Disc can be used to access a system recovery menu, giving you options of using System Restore, Complete PC Backup, automated system repair, and a command-line prompt for manual advanced recovery.

What it doesn’t do: You cannot use the Windows 7 Recovery Disc to re-install Windows – it only fixes (not replaces!) Windows.

Why you need it: If you bought your PC from a major retailer, you didn’t get this CD with your hefty purchase.

Download Links

Windows 7 Recovery Disc 32-Bit (x86) Edition

Windows 7 Recovery Disc 64-Bit (x64) Edition

Please note that the above links point to .torrent files. Torrent files are like a shortcut, they tell a download manager on your PC where to download the actual files from. Downloading large & important system files with torrents is highly recommended since torrents are protected against corrupt downloads and tend to be faster when well-shared.

(All torrents are currently being seeded by 100mpbs servers, they should be blazing fast).

You can download the Windows Vista recovery discs from here.

Instructions

1. Download the appropriate .torrent file from above that corresponds to the version of Windows 7 you have installed.
2. Download and run µTorrent.
3. Open the .torrent file you downloaded with µTorrent. (File -> Add Torrent)
4. Select where you want µTorrent to save the 7 Recovery Disc.
5. Wait for it to download.
6. Burn the .iso file that µTorrent downloaded to a CD using these instructions.
7. When you want to use the recovery center, put the CD in your drive and boot from it. This is usually done by pressing F8 at startup, or changing the boot drive order in the BIOS.

Support

Please don’t ask for help below, it’ll get real cluttered real soon! Open a support thread at http://neosmart.net/forums/ and we’ll help you resolve your problem ASAP.

To open JavaApplicationStub, you need to install Rosetta. Would you like to install it now?

Personally, I try my best to avoid legacy Mac OS apps and haven’t found the need to install Rosetta on OS X 10.6 Snow Leopard as of yet. Whether you have need of Rosetta for your other applications or not, there’s no reason you should be running your Java-based applications through the Rosetta environment — they’ll run just fine on native Intel Java on OS X… with just a little bit of a prod in the right direction.

Java applications are CPU agnostic (hence the “write once, run everywhere” Java motto). The Java applets you download and use can theoretically be run on any PC machine that supports Java; be it Intel, PPC, ARM, SPARC, or more. The native Java virtual machine will translate the “Java bytecode” into the equivalent machine assembly that your PC uses and understands, and therefore, Java code written for legacy Mac OS should run just fine on Snow Leopard

If there’s no problem with running older Java applications on Snow Leopard, why am I seeing this dialog? you ask. Well, the problem isn’t with the Java application itself, rather it’s an issue with the Java loader, which as a tiny native Mac OS application that simply launches the Java virtual machine and points it to the JAR file that contains the Java applet in question. If you have an old Mac OS application, chances are, it’s shipping with a PPC version of the Java Stub Loader, and that’s what’s triggering Rosetta. The good news is, it’s easy to fix, since the latest Intel-based Java stub loader on Snow Leopard can run any of your old JAR files easy as pie.

1. Open Finder, and browse (command+shift+G) to

   /System/Library/Frameworks/JavaVM.framework/Resources/MacOS/

2. Copy the file “JavaApplicationStub” to the clipboard (command+C)
3. Now browse to the folder that contains the Java application in question.
4. Right-click the Java application, and select “Show Package Contents” to view the actual app files in the OS X app bundle.
5. Open the “Contents” subfolder, and then the “MacOS” folder.
6. Paste the “JavaStubLoader” file from the keyboard to here, and accept the overwrite prompt. You may need to enter your password when prompted as necessary.
7. You’re done!

Note that in the video, PCWizKid is using EasyBCD 1.7.2, which is the latest stable version of EasyBCD… But there’s a secret 2.0 version out currently in beta — we recommend you download yourself a copy and be the coolest kid on the block. It’s been rewritten for stability and reliability, and will feature a ton of new Windows 7-only features for your itching, tweaking fingers.

Follow us on twitter @neosmart to keep up with the latest NST news, developments, and releases!

4Chan, a group of immature script-kiddies that anonymously post online and organize “attacks” against various groups, organizations, and websites, are it again. This time, it’s not the Church of Scientology they’re attacking, but innocent children. As the BBC reports, members of 4Chan have been uploading videos containing explicit sexual content in droves to YouTube today, specifically targeting children.

The videos uploaded by members of 4Chan consisted of children’s clips that start off innocently enough, showing cartoons and other rated-G material usually targeted at children around 5 years old, but soon enough change to videos of adults engaged in sexual activity. 4Chan has the uncanny ability to strike a nerve, driving even the most liberal of internet users to condemn their behavior as pure evil. The problem is, the anonymous 4Chan members are perversely motivated by this sort of response, and cannot be shamed into bringing an end to their disgusting activities.

This isn’t the first time 4Chan does something that can only be described as pure evil. In March of 2008, 4Chan members flooded an internet board for victims of epilepsy with fast-moving and colorful images intending – and succeeding – in bringing about photosensitive seizures in visitors to the site. The last attack was carefully planned to occur just over the Easter weekend, guaranteeing less moderator activity on the forum and giving the attackers a bigger window of opportunity to maximize their damage.

The difference between the behavior that 4Chan engages in and what just about every other script kiddy organization on the web does is that 4Chan doesn’t do it to prove a point. They don’t do it just to prove they can, they do it to hurt. And the malicious intent makes all the difference. The internet isn’t the best place to pride yourself in holding the moral high ground, but in cases like this, it’s near impossible to understand just what it is that makes people like this tick.

Obviously there is no clear solution to bringing about the end of groups like 4Chan, but someone needs to do something, or else we’re all guilty of standing by and letting evil go.

If you’re like most people, the answer is not much. But there are people out there that really care, and with good reason. If you’re the FBI, Oprah Winfrey, or one of the million other celebrities currently on Twitter, you probably don’t want someone out there passing themselves off as yourself while posting fake updates to an account literally millions are watching.

Some people to whom money is not an issue already pay thousands of dollars for meaningless SSL certificates – something tucked away in the corner of your browser window that no one pays much attention to. But imagine if Twitter were to start offering “verified accounts” that have been authenticated as belonging to a particular person or institute… how many of these celebrity accounts would suddenly turn into cash cows for Twitter?

Right now, it looks like that’s what Twitter has in mind. In a recent blog post, Twitter co-founder Biz Stone talks about the upcoming limited release of “verified accounts” in order to curb fraud amongst accounts claiming to belong to celebrities. There is no mention of charging customers for this service, but the way it’s worded, that is pretty much taken for granted as a future step in the process:

The experiment will begin with public officials, public agencies, famous artists, athletes, and other well known individuals at risk of impersonation. We hope to verify more accounts in the future but due to the resources required, verification will begin only with a small set.

And later:

When we do start testing Account Verification, we will be sure to provide ample methods for feedback. Initially, verification will not be tested with businesses. However, we do see an opportunity in that arena so we’ll keep you posted when we have something to share.

That’s not to say this isn’t a good idea though. Has Twitter finally found a way to make some serious cash without alienating its userbase, providing “additional features” no one really needs but can make them plenty of cash from the more high-profile accounts currently on the site? God knows Paris Hilton, et. al. would be willing to pay the cash, while the rest of us rely on word of mouth, links back from official websites, and common sense to give our followers the confidence they need to trust the updates we post.

Follow me on Twitter @mqudsi.

Back in 2008, Apple introduced the new Mini DisplayPort standard as the only video output method on the new MacBooks and LCDs. Mini DisplayPort is a freely-licensed VESA standard [1] and has now been adopted by a number of other display manufacturers, and is a miniaturized version of the original DisplayPort interface.

This week, the fourth revision of the HDMI high-definition video output connector was revealed in the form of HDMI D, weighing in at a mere fraction of the original HDMI connector size and intended for use with mobile and embedded high-definition video devices [2]. The new HDMI connector is expected to ship later this year, and is in direct competition with VESA’s Mini DisplayPort interface.

VESA is the international governing body for computer graphics standards, and has been designing video output standards since its conception in the late 80’s [3]. HDMI is a private group formed in 2002, and licenses its interfaces out to manufacturers at four cents a device + a $10,000 yearly fee.

HDMI doesn’t have many (if at all) advantages over DisplayPort, besides support for the xvYCC color space and Dolby audio codecs (as a part of the licensed technology). However, despite the licensing costs, HDMI has proved popular mainly due to its original mass adoption as a result of being signal-compatible with the DVI interface [4].

The new HDMI-D interface is smaller than the Mini DisplayPort, though both have the same maximum resolution/bandwidth and similar power requirements. The numbers are as follows:

References

1. The Case for VESA DisplayPort
2. HDMI-D Press Release
3. VESA – Wikipedia
4. HDMI FAQs
5. Mini DisplayPort Specification [PDF]

Windows Vista Ultimate Edition’s "Ultimate Extras" have been a constant source of derision and anger from Vista users ever since its release 3 years ago. If the blog posts are to be believed, millions of users purchased Windows Vista Ultimate Edition in the hope that the added-value "Ultimate Extras" package – which was left un-described and of unknown worth at the time – would turn out to be a good investment.

Ultimate Extras are a couple of the minor Ultimate Edition exclusives that Microsoft used as a selling point to get users to purchase the most expensive version of Windows Vista. It was originally marketed as something similar to the ancient "Plus! for Windows" package that was quite popular back in the days of Windows 98; except it never really panned out that way.

Ultimate Extras was something of a hoax for the first couple of years, bringing nothing more than animated wallpaper and extra cards game to the table. Since then a couple of new themes/sounds have been added to the package along with a couple of other lame games – all of which made Vista users feel all the more "tricked" into purchasing a more expensive version of Windows that they, in all honesty, didn’t need.

Well, it looks like Windows 7 will be doing away with the Ultimate Extras though it’s anyone’s guess what the final SKU lineup will look like and what the selling points and feature-sets of each of the editions will stack up to. But here’s to hoping that Microsoft learns from (even more) of its mistakes and provides something of real worth with the more expensive editions of its latest OS offering.

The reply turned out to be longer than I’d originally intended, so here it is as its own post.

I’ll try to be as objective as possible in this reply:

The most important thing for frustrated end users to keep in mind is that Mozilla/Firefox cannot be held responsible for cases where incorrectly written plugins and/or extensions cause Firefox to abuse system memory – that’s the trade-off between empowering developers and keeping the code squeaky clean.

Most of the cases reported are indeed caused by one or more extensions or plugins gone awry, doing something they shouldn’t be doing, or something they don’t know how to do properly. Some of the most popular plugins for Firefox are notorious for their memory leaks; but few users realize just how dangerous they can be, and that the Firefox devs cannot really do anything about it.

At the same time, there can be no doubt that Firefox has some memory leaks in the codebase itself. They’re clearly not easily reproducible and they don’t happen very readily nor often enough because the developers have clearly spared no effort in their attempts to address this problem for once and for all. But they’re there, nevertheless.

No matter how you look at it, the fact remains that under certain circumstances, doing certain stuff on certain machines in certain ways for certain people, Firefox still leaks memory. A lot. On Mac, Windows, and Linux. Yes, on clean installs too.

Now as a systems developer (Mac, Windows, and Linux w/ their respective native APIs; embedded systems; .NET and more with years of experience), I must say that of all the bugs and problems I’ve ever encountered, there is nothing that “cannot be fixed.” To say that this behavior is out of Firefox’s hands because it’s not their code that’s causing the problem is simply not true.

I’ve experienced memory leaks like this (and worse) in my own code in the past, largely due to stupid mistakes and silly oversights. It takes extreme persistency to make memory leaks go away – a willingness to spend 24 hours on-end & non-stop crawling through code, memory dumps, and stack traces to try and find out where things are going wrong. It requires remote debugging on allegedly-affected machines. It requires reading through dozens to hundreds of sometimes clueless users describing in the most general of terms what they were doing when things went wrong. In short, it requires a lot of effort and very little recognition and a hell of a lot of hair-pulling.

But it can be done.

C++ is an incredibly powerful language. If you know the code you’re developing and the systems you’re writing it for, there’s nothing you cannot fix. Dynamic memory allocation is the biggest gift/curse in the world, but in C and C++ if you can allocate something that means you can free it. Even if you don’t have a mechanism to find out where it is and how it got there. But you just have to be cunning enough to figure out how to track them down and set them free, taking care to know when and where to do so safely…. and you have to be familiar with every single routine and how they work; which is obviously extremely difficult with codebases as large and complicated as Firefox’s.

There are even workarounds for the memory leaks (assuming they can be isolated) if the developers aren’t willing or capable of doing the aforementioned. If you’re dealing with leaky libraries that you can’t fix, in the very worst-case scenarios you can hook into them at runtime, access the functions you need, reserve the memory required, get the job done, copy only what you need, then free it right back. All of it. You can have helper threads or processes handle this stuff then wipe them and their memory spaces clean when they’re done to complete the memory insulation.

There’s a lot of stuff that can be done, and none of them are easy. But the journey of a thousand miles begins with a single step, and developers and evangelists denying a problem exists isn’t the way to go about addressing the matter at hand.

At the end of the day, Firefox is a great browser and any complaints about its performance and its shortcomings are only out of a sense that it can do better – that it has to in order to remain at the top of its game in a cutthroat market of only the most intense of competition.

In the article, Ben Goodger, lead Chrome UI developer, states

[Google avoids] cross platform UI toolkits because while they may offer what superficially appears to be a quick path to native looking UI on a variety of target platforms, once you go a bit deeper it turns out to be a bit more problematic.” [... Your applications end up] speaking with a foreign accent.

But there’s something we’re not getting here. Obviously given enough brilliant programmers and a good team lead to keep the different codebases in sync, going with native APIs is the better approach. But the reasons Goodger is offering aren’t very convincing.

The problem is…. Google’s Chrome for Windows doesn’t look native. In fact, it’s about as far from native Win32 as you can get. We had originally explained away the non-win32 looks by assuming it was because Google wanted an interface that was consistent across the different platforms and different at the same time from any of the operating systems native UI toolkits: in line with Google’s vision of turning the browser into an OS, regardless of the platform beneath.

A non-native UI that looks the same on Mac, Windows, and Linux would be the answer to such a browser OS. It would indicate that Chrome is its own product – from the codebase to the user experience – and that to the end user it shouldn’t matter what OS you’re on. And that in the future Google could ship a standalone (OS-free) browser that looks like Chrome and acts like Chrome, regardless of the platform beneath?

Otherwise there is no good explanation for the horrendously-different user interface that comes with Chrome. It requires learning the tips & tricks to a whole new UI, and forgetting a number of “niceties” you may have been accustomed to (such as pressing the ’spacebar’ to OK pop-up dialogs, etc.).

With the preliminary screenshots of Chrome for Mac, the platform Chrome runs on begins to peek through.

Does this mean that Google’s vision of Chrome as its own OS has come to pass – with Google now content to just launch a cross-platform browser without attempting to lull users away from the platforms they’ve come to love?

Whatever the case, it’s sure to be interesting watching and waiting to see what Google has planned for its users. Whether its a cross-platform browser experience that’s different enough to be the same across all platforms while retaining a feel of the platform or if it’s paving the way for the OS to come it’s quite obvious that the gears are now in motion and something big just might happen.

And the two companies that have impressed us with their support? Pubmatic and Assembla – both excellent startups that we highly recommend in their individual fields. Pubmatic is an ad-revenue optimization service that intelligently chooses between different ad providers to maximize your ad impressions and CPM rates. Assembla provides quality hosting of SVN and other services that cover all aspects of the software development cycles for teams & small companies.

A couple of days ago, Kaspersky antivirus began flagging the ad-frames from Pubmatic as possible attempts to download a virus. Kaspersky is, of course, famous for its high false-positive counts (though it’s protection is great, nothing is without its cost). Pubmatic support staff were incredibly quick to respond to our queries, and immediately contacted all the involved parties to resolve the problem in a timely fashion.

As for Assembla – we’d been using their SVN hosting for a couple of years now. It’s thanks to them that we were able to develop software efficiently back before we had our infrastructure and development set up and going. They’ve recently overhauled their accounts system and have suspended free accounts, and they’ve been nothing short of wonderful helping us migrate our data to our own servers (data portability is a sensitive topic these days – but Assembla clearly knows how finicky developers are when it comes to ownership!) and helped us wrap everything up nice and clean.

Thanks to both these great companies for their wonderful customer service and their dedication to their userbase. If you’re looking to outsource your development services or for a better ad management system, there’s no one we recommend more than Assembla and Pubmatic.

The Official Windows 7 Wallpapers are now available for download from the NeoSmart Image Gallery. Only several wallpapers have been released accompanying various Windows 7 builds thus far, but we’ll keep adding new ones to the gallery as they’re shipped.

Here are some of our favorite new wallpapers:

You can see these and more at the gallery here, along with the old Windows Vista ones here and here.

We’re taking hundreds of screenshots of Windows 7 and its new features & components even as we’re posting this – keep your eyes peeled, they’ll be joining our extensive collection of Operating System screenshots in the same fashion as the Windows Vista screenshots were added: build-by-build with all the little details covered in true geek fashion.

But it looks like someone may have been a bit to hasty to pull that switch (perhaps itching to get some of the limelight Microsoft has been receiving for adding OpenID to all Live ID accounts just the day before yesterday)… because whatever it is that Google has released support for, it sure as hell isn’t OpenID, as they even so kindly point out in their OpenID developer documentation (that media outlets certainly won’t be reading):

1. The web application asks the end user to log in by offering a set of log-in options, including Google.
2. The user selects the "Sign in with Google" option.
3. The web application sends a "discovery" request to Google to get information on the Google authentication endpoint. This is a departure from the process outlined in OpenID 1.0. [Emphasis added]
4. Google returns an XRDS document, which contains endpoint address.
5. The web application sends a login authentication request to the Google endpoint address.
6. This action redirects the user to a Google Federated Login page.

As Google points out, this isn’t OpenID. This is something that Google cooked up that resembles OpenID masquerading as OpenID since that’s what people want to see – and that’s what Microsoft announced just the day before.

It’s not just a “departure” from OpenID, it’s a whole new standard.

With OpenID, the user memorizes a web URI, and provides it to the sites he or she would like to sign in to. The site then POSTs an OpenID request to that URI where the OpenID backend server proceeds to perform the requested authentication.

In Google’s version of the OpenID “standard,” users would enter their @gmail.com email addresses in the OpenID login box on OpenID-enabled sites, who would then detect that a Google email was entered. The server then requests permission from Google to use the OpenID standard in the first place by POSTing an XML document to Google’s “OpenID” servers. If Google decides it’ll accept the request from the server, it’ll return an XML document back to the site in question that contains a link to the actual OpenID URI for the email account in question.

This is shown quite clearly in the following image (courtesy of Google, ironically):

As you can see, steps 3 & 4 are not part of OpenID and leave Google’s implementation of OpenID, such as it is, incompatible with everyone else.

Google actually mentions this in passing:

Starting today, we are providing limited access to an API for an OpenID identity provider that is based on the user experience research of the OpenID community. Websites can now allow Google Account users to login to their website by using the OpenID protocol. We hope the continued evolution of both the technical features of OpenID, as well as the improvements in user experience. will lead to a solution that can be widely deployed for federated login. One of the companies using this new service is www.zoho.com.

Eric Sachs, author of the blog post in question, doesn’t actually come out and say, but he does come very close.

Basically, Google has rewritten OpenID. Not only is it not exactly the same as the current OpenID protocol, it’s so different that existing OpenID relying parties won’t be able to use it. Only a handful of “partner sites” have been updated to understand Google’s perverted version of the OpenID standard, and anyone else hoping to authenticate via “OpenID” to Google’s servers will need to do the same.

But OpenID is an open, community-based standard. Stabbing them in the back by creating an incompatible standard “based on” the same technology and masquerading under the same name isn’t the way to go. Google may have the best interests of decentralized authentication in mind, and perhaps even the better protocol to boot; but this is no way to prove a point.

OpenID is on tenterhooks as it is, and cannot withstand any more efforts to splinter its adoption. Never mind the fact that almost all the big names adopting OpenID are joining only as providers and not as relying parties (rendering the whole basis of OpenID useless) – now even the provider side of things is chaos.

Thanks, Google. Good to see you’re still doing the whole “Do no evil” thing, the community really appreciates this kind of approach to improving de facto standards and pushing decentralized authentication!

You can now download ToolTipFixer 2.0 which has a number of changes and improvements based on the feedback we’ve received during the past year. First, for those of you that aren’t familiar with ToolTipFixer, it’s a nifty “patch” for a very frustrating bug in Windows which winds up rendering tooltips behind the taskbar, leaving them unreadable and generally annoying the user to no end:

ToolTipFixer sits silently and invisibly in the background, intercepting this problem and fixing it as it happens – letting you read those tooltips and use your PC the way you should be able to.

Now for the good stuff: the number one request we’ve had was to eliminate the Microsoft .NET Framework as a requirement for using ToolTipFixer. As a matter of productivity and preference, Microsoft’s .NET Framework has a special place in our hearts, but we realize that many people would prefer something a bit… lighter and as such ToolTipFixer 2.0 has been rewritten from scratch in C++ with no dependencies – not even the MSVC++ runtime libraries.

The second oft-made request was improvements to ToolTipFixer’s memory usage. This particular component is tightly-tied to the development platform of choice, and with the switch over to unmanaged C++, it’s become possible to further-tune the amount of memory that TTF uses and bring it down as much as possible, something that’s not in the developers’ hands when using the .NET Framework – which, with its automated garbage cleanup, makes memory usage highly variable at best.

TTF 2 has drastically improved memory management – it’ll take so little memory, you won’t even know it’s there (from 0.3 to 1.5 MiB in our extended testing, depending on OS and platform).

Then there are those 64-bit Windows users, and more of them than ever before. Just because you have 4+ GiB of RAM in that machine of yours doesn’t mean you can’t get rid of this bug too – ToolTipFixer 2.0 has full support for Windows XP/Vista x64!

And to save the best for last, ToolTipFixer can now be run in what we call “standalone mode.” During setup, you’ll have the option of either installing TTF the traditional way – as a system application sitting silently and invisibly in the background – or as a standalone module that you run only when you need it. Some people experience the tooltip corruption problem less often than others, and if it doesn’t bother you incessantly then you can choose to only run TTF when you need it!

Download: ToolTipFixer 2.0

Despite PC users’ widely-varying taste and preference in operating systems and platforms, gamers need Windows. In fact, one of the biggest reason people around the globe tend to dual-boot is their undying love for gaming and the fact that no other OS out there can boast the wide range of gaming titles and genres available for their platform like Windows can. The traditional choice faced by most non-Windows users has been to either install and dual-boot Windows or bite the built and buy a gaming console – ask us, we would know.

But this is all about to change, thanks to Microsoft’s reckless abandon for one of its few truly-loyal userbases.

When Microsoft first began its frenzied Vista marketing campaign in 2006, one of the points it focused on most and repeated over and over again was just how big of a gaming revolution Windows Vista was. Gaming was a large part of the Vista WOW campaign, but it has since failed to disappoint. But this isn’t an article about Vista, it’s about how Windows is poised to lose its gaming advantage if Microsoft doesn’t get its act together sometime soon.

The problem is that Windows – standalone or in a dual-boot – is quickly becoming the lesser-appealing option when compared to a gaming console… in large part thanks to Microsoft’s ridiculous, biased, and fairly infuriating decisions to release games for Xbox and then for PC.

A major part of the gaming/entertainment Vista PR that went out around the same time as the OS: Microsoft Announces Spectacular Windows Vista Title Lineup. Spectacular? Hardly so. Take a look at the Microsoft Game Studios release history for 2006 and 2007, you’ll find a great disparity between the number of titles MGS released for Windows verses those for the Xbox (360)…

If you ignore expansion packs (the Zoo Tycoon development team seems to love these), you’ll find that Microsoft Game Studios released a total of nineteen titles for the Xbox over these two years, compared to a mind-blowing six titles for the PC over that same period – half of which were either available on the Xbox simultaneously or years before!

But what does Microsoft have to say about the obvious deterioration of the Windows gaming market?

The Windows gaming world continues to evolve, and we believe in the future of that property.

-Shane Kim, Microsoft’s Vice President of Interactive Entertainment

Sorry Mr. Kim, but we find that a bit hard to believe. Mr. Kim’s statement came in response to the recent (shocking) news that Microsoft’s (PC game development) Ensemble Studios – authors of Microsoft’s Age of Empires claim-to-fame hit series – would be shut down for "fiscal reasons."

Obviously Microsoft is in a hard place here, needing to cater to both of the (competing) PC and gaming console markets at the same time. However, due to the serious 3rd-party hardware/platform competition in the gaming console market it seems that Microsoft’s decision has been to give Xbox the priority here.

It’s obviously not Microsoft’s job to develop games for its own platform – technically, all they have to do for either the PC or the Xbox is develop the APIs and provide 3rd party gaming developers with the tools and support they need to make it work. And 3rd party developers have not let anyone down, with astonishing numbers of titles being published for both platforms.

But if Microsoft wants to ensure that its platform retains its current hold on the PC gaming market they’re going to need to do a bit more to convince potential Windows gamers to stick to their platform and not go out and get a gaming console instead. It’s quite a logical choice to focus on Windows here – there are literally millions of Windows users who would be using something else if it wasn’t for Windows’ vice-like grip on the gaming market.

The fact is, PC gamers and console gamers aren’t the same market targets. It won’t kill Microsoft’s Xbox division to treat their Windows gamers with a little bit more respect than they’re currently doing – if not for the users’ sake then for their own.

But no matter what Microsoft Game Studios does or doesn’t do, it can’t actually damage the Windows gaming platform – all it does is create a scenario wherein another OS can work hard and potentially overtake Windows at its own game (pun intended!).

Mac OS and Linux both have a rare opportunity on the horizon – but for it to have any impact on the current PC gaming sector’s dynamics, they’ll have to put a bit more effort into the gaming scene than they’re currently doing. Something that requires this sort of centralized coordination is definitely not one of Linux’s strong suites, so the ball is now squarely in Apple’s playing field, and it’s up to them what they do with it.

Basically, Microsoft needs to watch its step. The incentives for PC gaming are at their lowest levels in years with even real-time strategy games – the PC’s long-standing forte – being developed first for the gaming consoles and then, possibly, for the PC (yes, we’re looking at you, Halo Wars!).

And then there’s Bungie – cross-platform game developers bought up by Microsoft years ago, authors of the internationally-acclaimed “Halo” series, and now released from Microsoft’s reigns with its sights set squarely on developing games for the Mac once more.

At the end of the day, Microsoft’s size is getting the better of itself once more; with its own divisions failing to compete with themselves they way they should. Microsoft needs to pick up on this slow degradation of PC gaming satisfaction and do something to buck the trend, or else they could suffer some serious consequences.