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.

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.

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.

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.

With this update the installation process has been simplified somewhat, in particular the need modify HTTPD.INI to set the server variables has been eliminated – you just need to install ISAPI_Rewrite 3, configure php.ini to load up request_uri.inc, and you’re set.

Request_URI for Windows 1.1 retains backwards compatibility with ISAPI_Rewrite 2.x for those of you who’d rather not switch to the new (and much-improved) version 3.x.

Download Request_URI for IIS 1.1

The full instructions for installing and configuring Request_URI for Windows can be found at the original posting. Please post any support questions in the forums.

NeoSmart Technologies is not affiliated with Helicon software in any way.

While that’s a stunning number of Vista-only OEM machines running Windows XP, Mr. Kenney seems to have forgotten about those of us that dual-boot. As champions of dual-booters everywhere, we’ve got to put our two cents in here.

If you keep in mind the type of people who would install the Windows Sentinel tool and take part in such a geeky program you’ll realize that it’s not too out there for a good number of these people to be the kind that run multiple operating systems on their machines.

Obviously not all of Windows Sentinel’s (only) three thousand subscribers are included in the numbers above (it’s highly unlikely that even 80% of the 3000 subscribers are using hardware that only comes from the OEM with Windows Vista installed). And of the percentage that are using late-model hardware, a hefty percentage dual-boot.

We don’t have any numbers as far as the number of dual-booters out there, but they’re certainly not few enough to be discounted. Keeping that in mind, it’s rather unprofessional of InfoWorld to claim that 35% of all Vista users will downgrade to Windows XP. Obviously big numbers make for better headlines, but this is the kind of stuff that can damage stocks and ruin jobs – you don’t want that on your conscious, at least, not without good reason.

Not that we’re suffering from any delusions or hallucinations with regards to Windows Vista’s relatively shoddy performance and stability, but you’ll agree that it’s a rather far cry to go from “a lot of people have reservations about upgrading to Windows Vista” to “a lot of people will take the time and effort to remove Vista from a PC and put Windows XP in its stead;” especially keeping in mind that Vista’s been out for two years now and there’s an (unfortunately) increasingly-large number of Vista-only products out there on the market.

More data from InfoWorld and the Windows Sentinel service would certainly be most-welcome in giving a clearer picture of what the actual numbers are and where end-users stand in this OS mess.

Richard Stallman: legendary founder of the Free Software Foundation, purveyor of the GPL, defender of open source. And – as of today – expert FUD manipulator.

Obviously someone was seriously pissed off at the abundance of (largely positive) press coverage Bill Gates has been receiving as he stepped down from his final roles at Microsoft.. and it appears Mr. Stallman just couldn’t bear to let the man he hates more than any other step down without getting that last word in.

In an article by Richard Stallman published on BBC today, Stallman pulled back no punches bashing not only Bill Gates, Microsoft, and makers of proprietary software everywhere but also took the incredibly cheap shot of accusing the Bill & Melinda Gates Foundation of working to ruin the very countries they’re trying to help:

Gates’ philanthropy for health care for poor countries has won some people’s good opinion. The LA Times reported that his foundation spends five to 10% of its money annually and invests the rest, sometimes in companies it suggests cause environmental degradation and illness in the same poor countries.

Never mind the fact that those are unsubstantiated rumors following money trails several-hundred pockets deep – what does the Bill & Melinda Gates Foundation have to do with Free Software? Is Stallman so desperate to make Mr. Gates out to be the bad guy that he’d sink this low?

Stallman, one of first people to accuse people of spreading FUD to further their opinions, doesn’t stop there:

Gates is personally identified with it, due to his infamous open letter which rebuked microcomputer users for sharing copies of his software.

It said, in effect, "If you don’t let me keep you divided and helpless, I won’t write the software and you won’t have any. Surrender to me, or you’re lost!"

Here Stallman is referring to Gates’ now-famous letter asking people illegally copying, distributing, and using Altair Basic to stop. Stallman somehow neglects to mention that – regardless of whether morally acceptable or not – Microsoft had the legal right to demand payment in exchange for their software. Ignore for a second whether or not Bill Gates and Microsoft were in the right or in the wrong to ask for payment in exchange for their work – is Richard Stallman seriously suggesting that it’s right to illegally obtain copyrighted software?

It’s one thing to say that Gates should never have charged for his software and another to say that it’s OK to use it without paying. Gates chose to ask for money, users (as Richard Stallman himself has advocated on many occasions in the past) should be looking for an alternative if they don’t want to front the cash.

Who Richard Stallman thinks he’s kidding, we don’t know. But he’s obviously crossed that line that shouldn’t be crossed; apparently desperate enough to stop Microsoft the minute he senses an opening… even if it means spreading FUD, making pointless accusations, and generally talking nonsense to get his point across. This isn’t any way for a respected figure in the open source community to act, especially not when it comes to someone who has – whether Stallman likes it or not – contributed as much to the tech community as Bill Gates has.

Whether or not MinWin is the very same kernel that went into Vista or not is officially unknown at the moment; but what we do know is that Shipping Seven is either one huge fake, or else that the Windows core programmers at Microsoft are so stupid that they don’t know the first thing about coding, kernels, operating systems and compilers.

The post at Shipping Seven is littered from beginning to end with fallacies, lies, and incorrect deductions that anyone with even the most basic coding skills would know better than to ever post, especially not when attempting to pass it off as the work of some of the more talented coders out there.

Here are some of the more-glaring factual errors in the post that completely strip Shipping Seven of any authenticity or authority it may have on the topic of Windows 7:

How many times has the Ubuntu or Mac OS X kernel been rewritten?

Correction: OS X is powered by a rewrite of the XNU kernel which is a modified version of the Mach kernel which, in turn, is a complete rewrite of the original BSD kernel. And, of course, Ubuntu isn’t an OS in and of itself, rather it’s just a distribution of Linux.

While it can be argued that not every developer at Microsoft is expected to have intimate knowledge of the inner-workings of other operating systems, no one in their right mind would believe that the Windows kernel programmers don’t even know what kernels their strongest competitors are currently using.

We spent a boatload of time during Windows Vista making everything ‘componentizable’ – So that we could (by creating some xml files that our build process uses) create a boatload of different versions of Vista (and Server 2008).

….

You already have MinWin – It is the core system components that Windows Vista needs to function; everything else on the system depends directly or indirectly on it. It is the last thing you could (theoretically) uninstall.

So, if you really really want it, you can get it, I suppose – you probably could (using the command line) uninstall almost every single Windows Vista system component, including the user interface. I don’t know what the hell you’d do with just a kernel and a kernel loader on your machine, though.

Assuming you can get past the way that the post was written (with references like “using the command line” which indicate a general lack of knowledge about computers in general; treating the command line as if it were a “god mode” that can be used to do just about anything), there’s still the matter of factual inaccuracies – and inconsistencies in the article itself.

You can’t change/modify/revert pre-build settings by running commands in the command line. Components that are integrated at compile time simply cannot be removed by running a bunch of commands afterwards – especially not from within the resulting OS itself.

Anyone that’s ever manually compiled a Linux kernel knows this. You can’t strip ext3 support from the kernel after it’s already built any more than you can add Reiser4 support to the kernel without re-building it. As a matter of fact, anyone who’s built anything at all should know this – the same rules apply to any other program as well. For example, you can’t remove PHP support from Apache if you’ve compiled mod_php directly into the binaries.

Shipping Seven is a big, fat fraud. It’s written by someone with only the most basic knowledge of computers, zero knowledge of coding concepts, and absolutely no experience with kernels and operating systems. Shipping Seven is most likely written by the equivalent of script kiddy, eagerly awaiting the first leaked builds of Windows 7 to appease an inner itch – most likely all the while lamenting his lack of involvement in the Longhorn beta. It isn’t worth the time it takes to read, and definitely doesn’t deserve even the questionable authority it now has on the topic.

The entire 8.x line has been of sub-par quality to date (8.3 and 8.4 in particular, which seem to crash randomly on a large percentage of Vista machines), hopefully the 8.5 release can provide a much-needed boost in terms of quality and stability.

It’s obviously too early to tell if the 8.5 releases addresses these issues, which are not listed in the release notes, but it’s possible that some of the causes of the problem have been resolved as a result of one or more of the bugfixes in this version.

iReboot isn’t by any means a major application, but it’s gathered a pretty strong following over the months, mostly by people interested in boosting productivity (or increasing laziness) to the max. But there was one flaw in iReboot that made all the hard work we put into making it as unobtrusive and minimalistic as possible almost meaningless: if you had UAC enabled, iReboot will not run automatically at startup, no matter what you do.

This behavior comes as a result of the architecture that Microsoft used to secure Windows Vista, which doesn’t allow for applications requiring admin approval to run at startup. It doesn’t matter what your application does or if you absolutely trust it beyond the shadow of the doubt, Windows Vista simply won’t let an application that runs in elevated privileges mode to launch at startup – end of story.

Users of iReboot were quick to point out that this is a major drawback that made it almost useless – after all, it’s far less productive to have to manually run an application when you want to reboot than it is to wait for that startup screen to appear and select the OS you want. So we set about finding a solution.

We’ve just released iReboot 1.1, a UAC-free implementation that doesn’t require admin approval, elevation, etc. past the initial installation. And, yes, it does run automatically at startup too!

The Gory Details (feel free to skip below to the download links!)

In order for iReboot to be of any use, we had to get around Microsoft’s UAC limitations. For iReboot, it was of the absolute importance that it run at startup, and that it be allowed system access from normal user accounts. On Windows XP – where everyone runs as an Administrator and there are no annoying UAC prompts – it was a non-issue. But on Windows Vista, the new architectural requirements for running applications in elevated privilege modes made it near impossible.

While digging around for possible solutions, it became clear that the only possible fix would be to split iReboot into two parts. One would run in the background as a service, running under the SYSTEM or LOCAL SERVICE accounts and having privileged access to the OS without requiring admin approval or UAC elevation, and with the second half running as an unprivileged userspace client program which interacts with the service backend to get stuff done.

The resulting application has an installer – which requires admin privileges, of course – which installs and launches the background service. The background service has full permission to do what we need to get operating system XXXX to be the default option for the next boot, but – in line with the Windows Service Model – cannot be interacted with by end users.

The installer also adds a normal UI application which sits in the taskbar (from where end-users may interact with and use iReboot) and communicates with the backend service via a custom API which must not require the execution of any privileged code. The service can do whatever it wants (well, whatever we want it to do, but lets not get picky here!), but the client program must only perform actions which normal, unprivileged users have permission to execute.

By using a standard inter-process communication API we avoided the need for any special actions on behalf of the client application, effectively separating logic (residing and executing on the backend service, free from the many limitations of UAC) and presentation/design (the client application, bound to obey UAC’s every wish).

The Bottom Line

Anyone running Windows XP or Windows Vista – with or without UAC and/or admin approval mode enabled – can now run iReboot at startup and use it to boot into whatever OS they like (in conjunction with EasyBCD, of course!).

But getting this far wasn’t easy. With Windows Vista, what should have been 100 lines of code maximum ended up being a dozen times longer, split across two different processes, and requiring way too much man-hours to write the most minimalist and to-the-point piece of software we’ve released to date.

Perhaps most importantly though, is the fact that Windows Vista’s newly-implemented security limitations are artificial at best, easy to code around, and only there to give the impression of security. Any program that UAC blocks from starting up "for good security reasons" can be coded to work around these limitations with (relative) ease. The "architectural redesign" of Vista’s security framework isn’t so much a rebuilt system as much as it is a makeover, intended to give the false impression of a more secure OS.

With the current Windows Vista security models, Microsoft can claim that Vista blocks system-modification tools from running at startup; but the truth is, there are still many ways to get them to run. At the end of day, our experience with iReboot and Vista’s security implementations brings us to the sad conclusion that with Windows Vista, Microsoft has made ISVs’ jobs more complicated without actually providing any any further protection for end users from malware authors – which certainly isn’t the best way of going about this task.

Anyway, the fruits of our efforts:

Download iReboot 1.1 (248 KiB)

[support] [donate] [changelog]

The "good news" is, if you’re on Windows Vista SP1 x86, DEP doesn’t get in the way as often. And for when it does, Windows Vista x86 lets you disable DEP and continue along on your merry way. But Windows Vista x64 isn’t as forgiving – even after you use a program like EasyBCD to disable DEP entirely, you can’t stop hardware-based DEP or exempt software from the protection list on 64-bit operating systems.

Adobe has yet to provide an official (or even an unofficial) response on the matter; but seeing as Adobe hasn’t properly touched the Audition code-base since buying out Cool Edit Pro, it’s probably safe to assume we won’t be seeing an update anytime too soon. (for instance, Adobe Audition 3.0, released in Sep. of 2007, still doesn’t have that omnipresent 3.0.1 patch out yet).

A program’s executable code is split into multiple sections depending on what’s stored in it and what it’s used for. Some of these sections are marked as "no-execute" in the extended x86 instruction set. However, an incorrectly-written program will either incorrectly try to run code that shouldn’t be executed or else mistakenly mark executable code as "no-execute" – both of which will cause DEP to interfere and get Windows to kill the process.

The interesting thing here is – why didn’t Windows Vista RTM cause DEP to fire as well? After all, if Adobe Audition is attempting to execute portions of its code that shouldn’t be touched, Windows should block the attempt SP1 or not.

One possible explanation is that Adobe Audition is attempting to run code from a core Windows library, but it’s accessing the code in a non-standard way that breaks when that library has been updated or modified. Or perhaps its determining the entrypoint for a library file dynamically, and something about Windows Vista SP1 makes it start at the wrong place.

Either way, it seems you shouldn’t be using Windows Vista x64 SP1 if you depend on audio or video encoding to make a living. The sad thing is, 64-bit operating systems were often touted as "the answer" to encoders’ needs, between the slightly-optimized processing of encoder instructions and the ability to support 4GiB+ of memory; yet here we are at square zero once more.

Update (April 21st, 2008)

Reader Mike B. wrote in letting us know that x86 versions of Windows Vista SP1 do not trigger a DEP alert at all, so it seems this is a problem exclusive to Vista x64 machines running SP1. If you are using Windows Vista SP1 x86, you shouldn’t have to worry about this issue. Thanks, Mike!

What are the most common causes of notebook sleep issues?

• A process running on the system does not allow the system to enter sleep mode.
• A hardware interrupt, such as some peripheral devices for example.
• An unstable driver which does not properly support sleep states or is just buggy.

I’ve owned several notebooks over the years, and almost every one of them have had an issue with sleep mode in one way or another, and over time I’ve learned a certain "practice" which ensures that sleep mode generally works when I close the lid of my computer…

1. Make sure that all of the latest updates are installed for your operating system (Windows Update on Microsoft Windows, Software Update on Mac OS X, your favorite package manager on Linux).
2. Close any running programs on the system (and exit any programs which are running in the notification area which is next to the clock on Windows systems).
3. Unplug all external devices (USB, FireWire, etc.) This includes your external keyboard and mouse if you’re using one, your printer, and whatever else you have plugged in. And no, your USB-powered rocket launcher isn’t an exception, even though it is really cool.
4. Use the "Sleep" option in your operating system to put the computer to sleep instead of the lid (Start > Turn Off Computer > Sleep on Windows XP, Apple menu > Sleep on Mac OS X).
5. Once the computer has gone to sleep, close the lid.

You’re probably wondering why it’s not a good idea to always rely on the lid of your computer to put it to sleep, and the answer is fairly simple. Notebooks have a sensor or switch which detects the position of the display (lid) and when the lid is closed to a certain degree it should trigger sleep mode… only that’s not always the case.

Some notebooks take up to one minute to fully go into sleep mode, and general habits have shown that you’re more likely to close the lid and immediately tuck your computer into its carrying case, which means you’re moving the computer around in mid-air before the hard drive head has gotten a chance to park, which could cause damage to the hard drive (and your valuable data). By using the operating systems "sleep" function and waiting for the signal that your computer is snoozing away (whether it be a flashing power light or a pulsating sleep light), you give the computer a chance to park the hard disk head and enter sleep mode correctly.

Mind you, some notebooks with older NVIDIA drivers on Windows Vista may cause your computer to go into a perpetual coma every time it falls asleep. If your notebook manufacturer hasn’t provided you with a newer graphics driver, I’d recommend consulting a sleep therapist LaptopVideo2Go.com, which has all of the latest NVIDIA drivers and modified INF files for installing them on any NVIDIA graphics card.

If you don’t already know what the Windows Vista Recovery Disc is and what’s used for, take a quick look at the original article – good luck catching up on the half-a-thousand comments there!

What it does: The Windows Vista 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 Vista 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 Vista Recovery Disc 32-Bit (x86) Edition

Windows Vista Recovery Disc 64-Bit (x64) Edition

Windows 7 Recovery Discs

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 being seeded by 100mpbs servers, they should be blazing fast).

Instructions

1. Download the appropriate .torrent file from above that corresponds to the version of Windows Vista 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 Vista 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.

The Windows 7 FactsCentral site is intended to be a one-stop information center, where info about available builds, verified facts regarding Windows 7, etc. are available in encyclopedia format (verses the chronological article-nature of posts here on The NeoSmart Files).

Over time we hope to expand the Windows 7 FactsCentral site to include end-user information regarding the upcoming version of Windows, including details about the OS architecture, hardware requirements, and detailed descriptions of new features available in Windows 7.

NeoSmart Technologies is looking for avid readers/contributors who’d like to try their hand at editing the wiki and keeping it up to date with the latest info – our current team is currently very thinly spread, and we look forward to adding new members to the team. If you’re interested in joining the NeoSmart Team, please send an email to Win7@NeoSmart.net and/or leave a comment below.