Windows Help Center

Damn, Bill, you have come a LONG way. Look at you there back in '82, you handsome devil. As part of our tribute, let's take a quick look back at the top ten greatest (and not so great) products created on Bill-time, shall we? Don't worry, it'll only sting a little.

Hits

It's really easy to simply remember "Internet Exploder" as the standards-breaking, web-forking, buggy, monopoly-causing app that helped shape Bill's old image as the evilest baron of all technology companies. But it's also the app that led to the creation Ajax-based web apps through the XMLHttpRequest spec, and the kludgey early popularization of CSS. Love it or hate it, IE's gotten more people on the web over the years than any browser, and that's definitely got to count for something.


Despite TiVo's DVR dominance and competitors that came and went over the years, Media Center has always been an underrated standout product. Even Bill admits that the company's long struggled with usability, but Media Center is a beacon of hope not only for 10-foot UIs everywhere, but also for the company's ability to create powerful, advanced, user-friendy products. Between its online integration, extensible plugin architecture, ability to stream shows to nodes around the house, and now CableCARD support, the only real downside to Media Center is the fact that you still need a full-blown PC to run it.


It was arcane and nigh-unusable to mere mortals -- but the early cash-cow was one of Bill's most strategic moves, and helped Microsoft define the concept of software licensing. It also helped launched Mossberg's career as crusader of user-friendly technology. But most importantly, MS-DOS was still the OS an entire generation grew up learning, so del crticsm.* for a second because our autoexec.bat and config.sys were so very well crafted, and extensively tweaking Memmaker for a few extra KB of usable RAM definitely ranks amongst our top most formative geek moments.


Word, Excel and PowerPoint certainly did well enough on their own, but when Microsoft combined 'em into the tidy (and pricey) package that is Office -- first on the Mac in 1989, interestingly -- it had a selling point that would prove irresistible to many a productivity-obsessed middle manager even today. The addition of Outlook and its support for the (for some) nigh-indispensable Exchange only further solidified its foothold in the corporate computing world, and that's where Bill knew the real money was. That's certainly not to say that it hasn't been without its share of problems and annoyances, though -- we're looking at you, Clippy.


Microsoft has always been a software company first, but it's been cranking out high-quality peripherals for over 25 years -- long before the Xbox and Zune were even a twinkle in Bill's eye. Not only that, but it's been a reliable innovator in the field, with a string of devices that were first, early, or just simply popularized technologies like the wheel mouse, force-feedback joysticks and controllers, the modern optical mouse, and the ergo-keyboard. The division has gone through some bumpy times -- the SideWinder line was killed off for a while there, and there've been some questionable designs along the way -- but it's been riding high as of late, and it doesn't show any signs of slowing down soon.


It took a few versions to come into its own, but by the time Windows hit 3.1, Microsoft finally had a product that was able to pull PC users away from the command line (for some of the time, at least) and give them a real taste of things to come. Windows NT may not have had quite the same appeal with the average consumer, but it did bring the operating system into the 32-bit world and pave the way for enterprise desktop computing as we know it today. (Plus, it had the NT file system (NTFS), which to this day continues to carry on the legacy in its own little way.) We really wish they'd made a sequel to the Pirates of Silicon Valley, because we'd love to have seen the dramatization of Bill overseeing the first popularized verions of Windows -- especially '95, which came out just a couple of years later.
When thinking of Microsoft and the new millennium, few people are able to keep the crinkles out of their nose. Thankfully, Windows ME wasn't the only thing that arrived in late Y2K, as Windows 2000 rushed in to rock the socks off of suits everywhere. The whole Win2K thing went over so well that Gates and company decided to base its next consumer OS, XP, off of it. Some may argue that the resulting product still stands as the last great OS to ship out of Redmond.


As two of the most ubiquitous projects to come out from under Bill's command, both Windows CE and Windows Mobile are almost impossible to avoid when it comes to handhelds or phones. What began as a mishmash of small components has grown into the adaptable -- though sometimes maddening -- mobile OS that resides on just about every kind of device you can think of. Really, we mean every kind of device, from PMPs to enterprise-level stock-keeping systems. The slimmed down and restructured micro-Windows is at the very least one of the more flexible offerings the company has ever produced. Say what you will about its usability, there's no denying the massive impact it's had on portability and convergence.


Back in 1999, Bill was all about multimedia convergence, and he said that a new gaming / multimedia device would be Microsoft's trojan horse into the world's living rooms with something coined the "DirectX-box." In 2001, the original Xbox entered gaming territory dominated by Sony's PlayStation with Nintendo's N64. But the clunky machine brought with it the first easy to use multiplayer console service, Xbox Live, as well as a developer-centric model that helped turn the tables. Of course, things look quite a bit different today: the Xbox 360 leads the former market leader's PlayStation 3 in spend and attach rate, and with the relative success of media and content sales on Xbox Live, it seems Bill's dream of dominating the living room wasn't just a pipe-dream after all.


It's hard to underestimate the impact of Visual Basic. While the average user might have never heard of the original VB that Microsoft released way back when, the simplicity of the language and its graphical toolset made just about any power user a potential app developer, powering the flood of third party application development Microsoft operating systems enjoyed throughout the 90's. Sadly, Visual Basic met its demise at the hands of more modern languages and toolsets, but with a legacy of making programming accessible to the masses, its place in the history books and in Bill's pocketbook is undoubtedly secure.

Runners-up: DirectX, Flight Sim, Portable Media Center, Solitaire and Minesweeper

Misses

Riding high on its previously-introduced sister products -- the Handheld PC and Palm PC platforms, now dead and transformed into Windows Mobile, respectively -- Microsoft's Auto PC initiative was promised to herald a revolution for in-car entertainment and productivity. There's no question it was well ahead of its time; in fact, many of the features debuted in Auto PC have gone on to become standard fare in today's cars. Problem was, when it launched your ride was already pimped with a mere CD player. In-car navigation, voice recognition, and MP3 support were still the stuff of science fiction in those dark days (particularly at the four-digit asking price), and the whole thing was doomed to a geeky, spendy niche. Though products were initially expected from several manufacturers, Clarion ended up being the only one to actually produce a head unit.

*The Auto PC lived on in spirit as Clarion's Joyride, but Microsoft's heart was no longer in the project and Clarion had switched to a generic Windows CE-based core to build the product.


Poor Bob. No one ever gave him a chance. Maybe it had to do with the fact that he was really annoying. And as it turns out, Bill was dating Melinda French, Bob's program manager. Which isn't to say there was any nepotism involved -- Bob suffered an early death in 1996 due to general hatred for the little bastard. Bill offered this to a column in January, 1997, "Unfortunately, [Bob] demanded more performance than typical computer hardware could deliver at the time and there wasn't an adequately large market. Bob died." Thankfully, Billinda's blossoming relationship lived on. Oh, did you hear? They're like the world's greatest philanthropists now.


Ask folks to pick one word to describe Microsoft's technology roadmap in the 1990s and you'll commonly get "Cairo" in response. Announced before Windows NT 3.1 was even released, Cairo was occasionally an operating system, occasionally a collection of new technologies -- it depended entirely upon who and when you asked -- but at its core, it was intended to guide Microsoft on the path beyond the architecture introduced by NT. After throwing countless dollars and man-hours at the ambitious project, Cairo was ultimately canned (though mentions of the storied buzzword continued even into this decade). Although Windows 2000 eventually became NT's heir apparent, the fruits of Microsoft's labor weren't entirely for naught, as various Cairo features found themselves implanted into various versions of Windows throughout the years. Even the WinFS file system can trace its roots back to the project -- fitting, because it too has become such an albatross.


When MSN Music -- Microsoft's effort to build its own PlaysForSure-based subscription music based store -- imploded, headstrong Bill did what he usually does: rebrand, and launch again. When he got up at CES 2006 and announced MSN Music would become URGE with MTV, we were all a little skeptical -- after all, the problem wasn't really the service, it was the overbearing DRM and the fact that consumers simply weren't ready for subscription music. Of course, eventually URGE died as well, and MTV shunted customers to Rhapsody America; naturally, Microsoft had a third PlaysForSure-based store waiting in the wings with Zune, which doesn't appear to be going anywhere any time soon.


UMPCs... what can we say? Sure, Scoble liked them, but even from day one we never saw the market potential. Fueled by an early and too-successful hype-generating viral campaign of Microsoft's own making, there was no way that these first generation Origami devices would achieve their promise. Overpriced, underpowered, desk OS-laden (with Microsoft's Touch Pack add-on), and poor battery life would ensure that UMPCs would need quite some time to live up to the wave of "ultramobile lifestyle PC"-hysteria they rode to market. And as UMPCs begin to fade, the shrinking niche between smartphones and laptops now looks toward to the sweet release of MIDs -- though that's already been two years... and counting.


What began as a collaboration between Microsoft and then-partner IBM blossomed into what looked like -- for a time at least -- the logical successor to the DOS / Windows empire. The advanced OS showed early signs of greatness with it's incorporation of the HPFS file system, improved networking capabilities, and a sophisticated UI. But cracks in the relationship between the two powerhouse corporations would ultimately lead to its downfall. With Windows 3 a sudden success, IBM's reluctance to go hardware neutral, and Microsoft's increasing displeasure with code which it called "bloated" (ahem!), the project was eventually swept aside by Gates and the gang to make way for what would become the omnipresent operating system you know and love and/or hate today.


When the concept of an information-enabled watch that automagically received content over unused FM radio subcarriers was first conjured up by Microsoft in the early part of the decade, it seemed like a fabulous idea. So much so, in fact, Bill personally took the project under his wing. But by the time it had launched, it was already doomed by a perfect storm of problems: the devices were uglier than sin and comically oversized, the bizarre ad campaign featured frighteningly hairy cartoon arms, and -- as the mobile web was just starting to pick up steam at that time -- virtually anyone who would've been interested in that kind of product had already discovered ways to get the same information from their phone. The underlying data network Microsoft built out to support the watches, MSN Direct, lives on to this day and sees plenty of use in Garmin's nüvi line, but will it ever be used to beam weather, news, and MSFT stock reports to wrists other than Bill's? Not bloody likely.


Depending on who you talk to, Windows Product Activation is a serious privacy violation, a headache, minimal protection against piracy, or all of the above. Lucky for us, Microsoft is finally seeing (some of) the folly of its overbearing ways, and has gone with a more permissive nagware method with Vista SP1. This as opposed to the regular method of routinely locking users out of their systems, which, wouldn't you know it, tended to hurt legitimate users more than pirates. Perhaps the best example of Windows Activation's legacy was the great WGA outage of 2007, which left 12,000 systems out in the cold due to a few downed servers at Microsoft. It didn't take long for the servers to bounce back, but any shred of reputation the service had at that point went out the window with the uptime.


It's not exactly clear what the point of Windows Millennium Edition was -- our guess is that Microsoft needed to keep up with that year-based product naming scheme it had going at the time, and cranked out this half-baked update to '98 in order to capitalize on the turn-of-the-millenium frenzy. Unlike the NT-based Windows 2000 released at the same time, Windows ME retained its MS-DOS-based core, while managing to somehow get even more slow and unstable than its predecessors 95 and 98. And to add insult to injury, it restricted access to shell mode, rendering many MS-DOS apps incompatible. Thankfully, Windows ME was only inflicted upon consumers for little over a year; it was replaced by indomitable Windows XP in 2001.


Vista doesn't suck. Let's just get that off our chests. In fact, it's a quite capable, secure and sexy OS when you get right down to it. Unfortunately, its problems just loomed too large for many folks to overlook. A multitude of delays and a rapidly diminishing feature list soured people right out of the gate, and once the dust settled people just weren't happy with the minor improvements they were getting in exchange for their hard-earned monies and fairly mandatory RAM upgrades. Mix that in with the standard driver incompatibilities of any Microsoft OS upgrade, and you've got a whole bunch of disgruntled downgraders on your hands -- and plenty of bad press to fill in any remaining gaps. Sadly, improvements to Media Center, aesthetics and even that quirky little sidebar got overlooked in the process. Microsoft's already scrambling to get Windows 7 together to capture the multitude of users that've decided to skip Vista altogether, let's just hope it's not too late.

Runners-up: Actimates, Pocket IE, Games for Windows - Live, Xenix (yeah, Microsoft actually did a Unix at one time!)

Hi,

Last 24 hours can be called most fruitful 24 hours!

I bought a HP notebook 15 days.. a monster with 2 Gb RAM and Claws of VISTA ,howevr i was unable to rum most of my old softwares with (especially Oracle 9i).

i tried Dual Booting (http://tarunreflex.blogspot.com/2008/06/dual-boot-vista-and-xp-with-vista.html) but failed becoz of new BIOS upgrade by HP and unavailability of USB floppy drive..( http://tarunreflex.blogspot.com/2008/06/install-windows-xp-on-sata-without.html )

Howevr i came across Microsoft Virtual PC 2007 last night ( http://tarunreflex.blogspot.com/2008/07/run-windows-xp-over-windows-vista.html )
and installed XP on Virtual PC running on Windows VISTA.

The installed addons and enabled Folder Sharing between host Os and XP and shared Oracle 9i 3 CD setup ( http://tarunreflex.blogspot.com/2008/07/download-oracle-9i-3-cd-set-up.html ).

The i started the installation proces.. as usual..

PROBLEMS:

1.) The file transaction_processing.dbf at C:\oracle\ora90\assistants\dbca\templates failed to be copied (checked error log created )
so i cancelled the installation of the file and proceeded further with installtion.

2.) due to unavailability of file transaction_processing.dbf at C:\oracle\ora90\assistants\dbca\templates DATABSE CONFIGURATION ASSISTANT failed to start.
I skipped that too.but i didnt exit the installation by pressing EXIT BUTTON. I waited and took following actions:

HOW TO FIX THIS PROBLEM

1.) Copy the file file transaction_processing.dbf at C:\oracle\ora90\assistants\dbca\templates from a good ORACLE installation (I copied it from my old laptop and pasted it in the right place) and started DATABASE CONFIGURATION ASSISTANT agn.
And whoa..
It worked.
I started Oracle tried few simple queries and it seemed good.howevr i havent tested many things but i think it will work out.
Feelfree to try and let me know of improvements and suggestions
I will b posting related post at http://tarunreflex.blogspot.com/.

Regards,
Tarun.Reflex

You've taken the leap into Windows Vista, but once in awhile, your heart yearns for the classic features and functionality of XP. Maybe you've got software that doesn't yet work in Vista, or maybe you just want to see how a web site looks in Internet Explorer 6. You could dual-boot XP and Vista, but switching between operating systems in that setup takes too much time.

Instead, quickly toggle between Windows versions with an XP virtual machine running inside Vista using the free Virtual PC 2007. Here's how.

What you'll need

1. A Windows XP setup disc with a license.
2. The free Virtual PC 2007 download.
3. About an hour, depending on how fast your computer is.

Now, lots of lifehackers say that other virtualization software, like VMWare or Parallels for Windows is better or faster than Virtual PC. That may well be true, but Virtual PC is free, which is just cheap enough for home use. Virtual PC is best suited for casual users who fancy an occasional foray into an older version of Windows.

This particular article is for running an XP virtual machine inside Vista, which is almost guaranteed to work reasonably well. Here's my logic: if your PC is beefed up enough to run Vista, it'll run XP just fine as a virtual machine.

Virtual PC can be used to run other operating systems inside Windows XP, also - but be warned: without a fast physical machine with lots of RAM, your virtual machine may be slow too.

Create a new XP Virtual Machine

Once you've got Virtual PC 2007 downloaded and installed and your XP disc at the ready, from Virtual PC's Action menu, choose "New Virtual Machine Wizard" and you're off. Within the VM Wizard, you'll set how much RAM to allocate to the XP virtual machine, and you'll also set up a new Virtual Hard Drive with a size you set that XP will use to store data.

The Virtual Machine Wizard, like most Windows wizards, is easy enough to work through.

Then

Install Windows XP

Now, you've got to install Windows XP onto your new virtual partition. If you've ever set up XP from scratch before, this'll be old hat.

You'll be prompted to format a "new partition," which is the virtual hard drive you set up earlier. Also, you'll be asked to set XP's date and time and other regional settings. The first time you click inside the XP VM, Virtual PC will attempt to "capture" your mouse pointer. Once it's inside the VM, you won't be able to move it out of the window without using a special key combination (Right-Alt, by default.) Here's the initial VPC prompt about mouse capturing:

This mouse pointer capturing business is really annoying, especially for someone used to using VNC to remote control computers. Happily using some extras for VPC, we can stop the Right-Alt madness. More on that later.

I completed XP setup in about an hour on my Acer laptop. Your mileage, as they say, may vary.

Run your XP virtual machine

Once setup completes, XP will "reboot" and start running inside a window on Vista. Here's what that looks like:

Now, there are tons of virtual machine settings and properties you can fiddle with to your heart's content. But before you do that, be sure to install the Virtual Machine Additions to your XP VM for a few must-have extras.

Install the Virtual Machine Additions

To get extra VPC features like sharing the mouse and folders between guest OS and host, start up your XP VM, and from the Action menu, choose "Install or Update Virtual Machine Additions" (the key command is Right-Alt-I). VPC will go through its paces and prompt you to reboot the XP VM.Once VM Additions are installed, you can move your mouse between your XP VM and Vista host without having to press Right-Alt to free the pointer. Additionally, you can share folders from the host PC to the VM. Check out the Settings area to do that.

While Virtual PC 2007 isn't the best virtualization software ever, it's pretty damn good for free, and it may be just the thing you need for a little retro XP action, fast.

Well, this is specially for people who recently invested thousand of bucks on branded laptops and desktops with VISTA preinstalled and now cant' run many of their older softwares (like Oracle and many more...).

So here is the way to dual boot Windows VISTA and Windows XP on a PC with VISTA preinstalled.

Step 1 - Partition the Drive:
Vista comes with a nice partitioning tool, so i'll be using it instead of partition magic this time around.
-right-click computer under the start menu and choose "manage"




-right-click the drive you want to partition, and select "Shrink Partition"
-The amount you shrink the partition is the amount of space used for the XP partition, so i would suggest making it at least 3-4GB in size, as a full XP installation will take 1.5GB on it's own.

-now right-click the unallocated memory and select new basic partition.



-Choose NTFS file system, this will save formatting before installation.
-name the drive anything you like, i chose "XP"
-click next on the rest of the screens and finish.

once the formatting is finished you will have something like this:



*this new partition is where your XP installation will go, so take note of it's location, in case there are multiple partitions on the drive (there will now be atleast 2).

Step 2 - Install XP:

wait while XP installs (I won't go into detail, there are many tutorials on this, and it is reasonably straight forward)



Now that XP has installed, it attempts to boot for the first time... all goes fine, video settings, networking, then the lovely welcome screen as usual.

You restart, expecting a boot loader screen... followed the tutorial this far, and now you seem to only have XP... well not quite, I wouldn't leave you hanging without giving you a proper dual boot.



here lies the only real issue with installing XP after Vista, but it's a quick fix if you have your Vista CDs/DVD handy.

The problem is that Vista and XP use different boot loader utilities in the MBR (Master Boot Record) of your hard drive. XP does not recognize Vista, but Vista will recognize XP, so we need to remove the boot loader that XP just put in with the old Vista boot loader. So restart once more, but this time with your Vista disc in the drive.

Step 3 - Fix Boot Loader:

Vista will load the GUI files, and then display the loading splash screen.

-Click "Next" on the first screen
-Once the "Install Now" menu (do not click Install Now) choose "Repair Your Computer":



-You will be prompted to choose the OS to repair. Don't worry if Vista is the only OS that shows up, even after a search.


click "Next"

-I realize there is a "Fix Startup" option, but it's been my experience that it doesn't work, and this method will.
-choose to open a "Command Prompt":



type in the command prompt the following 2 lines (separatly):
Bootrec.exe /fixMBR
Bootrec.exe /fixBoot



-close the prompt and restart
-now that Vista controls your boot loader, the process is mostly finished, now we need to inform Vista that XP is installed, as to enable the boot loader selection screen.
*There are programs such as VistaBootPRO that will do this for you, but it requires .NET framework, etc, so I did it the manual way.

Step 4 - Edit boot.ini:
In Vista, the boot.ini is not editable directly, as the file itself is hard to locate, so we will be modifying it through "Boot

Configuration Data Store Editor" bcdedit.exe:
(Just as an explanation, the loader type for XP is an NT Loader, hence the use of ntldr)

-first open a command prompt with administrative privilages (right-click and choose "run as administrator")
*Note the following 2 answers from bcdedit for each item are acceptable:
"The Operation Completed Successfully"
"The Specified Entry Already Exists"
Be sure to type each line carefully (replace C in the first line with the drive containing your Vista installation):
bcdedit –set {ntldr} device partition=C:
bcdedit –set {ntldr} path \ntldr
bcdedit –displayorder {ntldr} –addlast
bcdedit -set {ntldr} description "Microsoft Windows XP"

The completed bcdedit file should resemble this:



-This will correctly add XP to your boot sequence, and even name it properly instead of "Earlier Version of Windows"
-the displayorder line also allows the entry to be visible under the advanced settings of your computer properties.



Vista is the default boot, if you wish to change this to XP it can be done by setting {current} to addlast, or under the computer

-> properties -> advanced settings.

If all done properly, XP and Vista will dual boot properly!

Regards,

Tarun.Reflex

jaiswal.tarun@gmail.com

SATA hard drives have become more and more appreciated tending to substitute the IDE drives due to the increasing speed they offer. Motherboard manufacturers started to implement the new standard years ago, when the technology was young and expensive. Now, as the SATA HDD prices have lowered to a level where anybody can afford to choose a SATA enabled HDD instead of an IDE one, a great migration has been observed among the common computer users.

They choose to install Windows and applications on SATA drives because they provide more speed which determines the system to run smoother. Thus, for those owning older mainboards with SATA support an extra step is required while attempting to install Windows XP. Windows XP does not provide drivers for all the SATA controllers, therefore, during the installation procedure, the user must insert a floppy with the drivers that came in the package along with the motherboard.

Not a big deal, not much effort, but the funny thing is that a great number of people passed on their floppy drives. Under these circumstances, no floppy means the impossibility to install Windows XP on SATA (on some mainboards). The result? The installation guide simply won’t detect the SATA HDD.

People that were happy they got rid of the old removable drive have now motives to worry. Some may reconsider buying new floppy drives for their computers. Even if I wrote in a precedent article about the utility of the floppy drive, I do not encourage spending your money buying back an obsolete piece of hardware. I will present you a method to avoid this inconvenient by doing a software trick.

Let’s take it slow. Where is the problem? We have a driver problem strictly because the SATA driver we need does not come embedded in the Windows XP installation package. What if we add the driver by ourselves before installing Windows?

What ingredients are involved in this operation? The original Windows XP Installation CD, a freeware application named NLite and a blank CD. Moreover, we need the drivers for the SATA controller provided by the manufacturer. In case you did not find any floppy inside the motherboard package or you cannot locate them on the mainboard installation CD, you can consult the manufacturer’s website to download the latest versions. To do the trick I have been talking about, it is assumed that you already have a Windows installed on an IDE drive. In case you don’t, pay a visit to a friend and ask him to let you use his computer. It won’t take too much time, I guarantee.

So, download the drivers and unzip them (in case they come archived) in a desired location. Then download and install the Nlite application. When you start the Nlite application, you will be asked to provide the location for the Windows installation package. Insert the genuine Windows Installation CD into the CD drive and, inside the application, select the CD drive letter.

To insert the SATA drivers within the installation package, you need to have it saved on the HDD. Hence, when the warning window appears click OK and select the destination folder for the files to be saved. Make sure that the destination partition / HDD has enough space to store the contents of the installation CD.

I tested a Windows XP Home Edition and it seems that it required about 566 MB. Immediately after you have chosen the destination folder, the application will start copying the Windows installation files. When finished, it will display some version information regarding the newly copied Windows Installation Package.

Now, click next twice until you get to a screen where you get options sorted in 4 categories: Integrate, Remove, Setup, Create. We are interested in the integration procedure, therefore select the Drivers button and click next. From the next menu window, click Import and select multiple drive folder option from the drop down menu. This option permits you to browse to the location where the downloaded drivers are found.

Select the containing directory and click next. You will get a list with the available drivers (in case there are more than one) or simply one driver. Select it (them) and click next. Now the application will ask for the permission to start the integration procedure. Choose Yes and wait for the drivers to be inserted into the installation package.

With problematic driver being included in the installation package you can install Windows XP on your SATA HDD…but…the installation package is on the HDD. You need a bootable CD in order to start an installation. Don’t worry, once the installation package has been adorned with additional user selected drivers it can be transformed into a bootable disk image and later burned on a CD. To encapsulate the installation into a ISO image use the same Nlite application.

Open it, make sure the HDD installation folder is selected and click next. Select “Last session” preset and click next again. Now from the options menu choose Bootable ISO and click next. In the following window, make sure that the mode is set to “Create Image” and click Make ISO. A destination folder is required where the resulting ISO image will be saved. Once the image saving process finished you have the freedom to burn it on a blank CD with whatever you favorite CD burner software may be.

The new CD will be the twin copy of the Windows Installation CD but with one difference, it includes the SATA driver.