Updating xp to windows 7
You may well find yourself somewhere between these two extremes, though, and so the 'best' OS to use will be a more difficult decision. We've taken a test PC and laptop, installed XP, Vista and Windows 7 on them and applied a number of testing real-life benchmarks to see which will come out on top.
We're aware that speed isn't everything, though, so we've also explored the new features that each OS has introduced. Performance It's often said that recent versions of Windows have become bloated, and it's hardly unreasonable to expect each new OS to perform better than its previous iteration.
Figure 3-11: It's crazy but it's true: Windows XP and Windows 7 applications can now run side by side.
Secret: Windows Virtual PC is free for all Windows 7 users, but Windows XP Mode is a perk of the Professional, Enterprise, and Ultimate versions of the operating system. The next sections take a look at both of these new Windows 7 components.
Perhaps you should forget about Vista and Windows 7 altogether, opting for the mature XP instead? If you have old or extremely basic hardware, for instance, then XP will have a definite advantage: its relatively lightweight core means the operating system can theoretically run with only 64MB of RAM, so there'll be plenty of resources left over for your applications.
Recommended: To get the most current drivers for your Sound Card, download the driver installer below.
With a database of over 11 million drivers, you can quickly identify every Sound Card device made after 1994.
Windows starting at about Win2K SP3 (and all levels of XP, Vista, Win7, Win8) bundle and service varying numbers of VB6-related libraries as part of the OS. The only "safe" source of such libraries that I know of today is at and you'll have to extract them from their merge modules if you insist on using a legacy scripted installer like the PDW. For actual apps I release, I use Inno Setup though. Far more likely you have mismatched the versions of the various DLLs (such as those this one depends on, e.g. And in any case no version of Windows includes this DLL! I have no clue as to why those two files are different versions.
I have an app that was originally designed in XP Pro. Originally the problem was with ADO (original thread: Installer authroring tools use the standard merge modules Microsoft supplies for this. DLL) are changed in Win7 SP1 to match the ADO compatibility-break in that release. The solution may vary in details but the goal is to avoid using the "live" installed dev system version of these libraries. Everyone else has a shortcut on their desktop pointing to the Note that RDO is supposed to be broken similarly on Win7 SP1 as well! Yes I'll try to work towards not using the Monthview, but for now I just had to re-register an OCX file on the computers affected and it's working just fine. It comes up with the automation error as soon as that code I posted is activated, under the print button. And in any case no version of Windows includes this DLL! Version 188.8.131.52 is from VB6 SP6 (I just verified this by opening the SP6 merge module Microsoft provides).
However, if you have high-end requirements, such as using a powerful PC to run heavy-duty applications, Vista and Windows 7 come into their own.