How To Run Newer Programs On Windows Xp

Practice you accept elderly Windows or MS-DOS software that refuses to run under Windows XP? If then, there may nevertheless exist a way to get it working.

When Windows XP was outset released, it was already compatible with a wide range of hardware and software applications, largely because Microsoft and various 3rd-party developers had been working together to ensure the widest possible customer uptake of the OS. However, this compatibility mainly applied to the almost pop third-party products, including (naturally) Microsoft'south ain range, leaving a huge number of other software applications and hardware peripherals in limbo.

To be supported under whatever new operating system, hardware virtually always needs new drivers, so information technology's extremely of import to wait until these have been written earlier installing Windows XP. Many people upgraded their PCs to Windows XP immediately it was released and discovered the hard way that some peripherals (particularly soundcards, scanners, and printers) simply didn't work at all, and either returned to their previous version of Windows, or rushed out to purchase replacement hardware that did work.

Older applications stood a rather better chance of running under Windows XP than hardware, but it was however a bit of a lottery — some were found to work perfectly well, while others crashed, or even refused to run at all. However, Windows XP had another trick up its sleeve, in the shape of its Program Compatibility Mode, a function first seen in the Windows 2000 Service Pack 2, but rather more than versatile in its latest incarnation. This mode allows older applications to call back that they were running on a previous Windows version, which tin solve a lot of bug.

The Current Situation

Two years on, the vast majority of soundcards now have stable and efficient XP drivers, and well-nigh of the major music applications have been updated to new versions that incorporate XP compatibility, while other more contempo releases, such equally Steinberg's Cubase SX accept been written from the basis upward to adjust Windows XP. However, some musicians, while attracted to the new features of Windows XP, are still perfectly happy with the characteristic fix and performance of their existing software, and don't want to fork out for updated versions, especially if they include a lot of new and (for them) largely unwanted features. Others may have older music software that'south still vital to their studio, just whose developers have gone out of business, leaving no prospect of an XP update.

Then how can you find out whether any of your software might cause problems with XP? Firstly, Microsoft have a database of hardware and software that has been alleged compatible (www.microsoft.com/Windows/catalog), although it's by no means exhaustive, peculiarly in the case of music products. The soundcard department is nearly exclusively devoted to Creative products, for instance, while the Digital Video, Audio, and Animation section contains none of the virtually popular music software.

If you have a programme that causes you lot problems running under Windows XP, the Plan Compatibility Sorcerer provides a selection of modes that emulate various previous versions of Windows. Microsoft do likewise provide the Upgrade Advisor (a free 32Mb download). This tool will scan your hardware and software for possible conflicts, merely it isn't infallible — particularly, it seems, with scanners and software-based modems, often declaring them incompatible when in reality they're working well. The Upgrade Counselor is too supplied on the Windows XP CD-ROM, and runs automatically as part of the Setup routine if you determine to upgrade an existing version of Windows. It can too be run on demand: just click the 'Check System Compatibility' selection on the 'Welcome to Microsoft Windows' page that appears afterward you insert the XP CD-ROM into your drive or run its Setup.exe file.

What about applications not covered by Microsoft's list? Well, all Windows software released in the last couple of years volition almost certainly be XP-uniform. When information technology comes to software released before Summer 2001 and not subsequently updated, many helpful developers have posted a unproblematic assurance on their web site that all will be well if their software is run under XP, or offer specific instructions on the best mode to proceed, fifty-fifty if an update isn't likely. You may fifty-fifty be able to download a pocket-sized 'prepare' or 'patch' file that, once run, volition return the original application completely XP-uniform. An example is the patch supplied by Gary Gregson for his popular XGedit utility, which cures minor graphic corruption when running under Windows 2000 and XP. Yamaha accept a similar patch DLL file for their XGworks 2.0 application, to permit information technology run under Windows XP.

It may exist that no reassurances or instructions relating to your software of choice are visible, and in that location are no suitable updates. Or peradventure you're admittedly determined to stick with the current version of the awarding rather than indulge in a payable upgrade, even if there is i available. If so, you may be lucky: information technology'due south quite possible that you won't experience problems when installing and running the application in question under XP. Of the problems that tin occur, some may be immediately obvious, such as a Setup or Install routine that refuses to run (although sometimes such issues can exist cured in a PC with multiple user accounts past logging dorsum on as Administrator, or by logging off any other users except the account that volition install the plan).

Once a plan has been installed, or if you've upgraded to XP 'over the pinnacle' , leaving existing applications in place, other obvious signs that something is incorrect are your PC locking upwards every time yous try to launch a particular application, or aborting immediately with an error message. The PC might work some of the time but still crash occasionally, or it might soldier on but with MIDI or audio timing issues. In all such cases information technology's well worth trying XP's Program Compatibility Mode. It isn't a cure for every Windows fault with older programs, but during my researches I discovered many problems that information technology can deal with.

Hardware Incompatibility Problems

Program Compatibility modes can only deal with some software problems, and they don't effort to resolve those relating to hardware. Afterwards all, this is the province of the hardware driver, and therefore up to to the private hardware manufacturer. You should visit the web sites of all hardware expansion card manufacturers to download the latest XP drivers for your devices, including soundcards, graphic cards, modems, network cards, and then on. Further drivers will exist required for any hardware devices that plug into the serial or parallel ports, such as MIDI interfaces, printers, scanners, and modems. Although XP does provide USB sound drivers, you may demand an XP patch file to get the best results from USB 2.0 sound peripherals.

Nevertheless, if one of your favourite hardware devices doesn't have an XP driver, don't bin information technology or abandon XP equally an option simply yet, since there may be another way to become it to work. Try an Internet search using the device proper noun and 'XP drivers' to see if at that place'southward any other data available, particularly from user groups. For instance, I'thou still using an old Agfa Snapscan 1212P scanner, bought in 1999, with a parallel port connection. While Agfa merits that XP drivers will never exist written for it, I discovered claims by users that the Windows 2000 Beta drivers volition work under Windows XP, albeit with a few caveats. For the few times I use my scanner I'm happy to work around these, and it certainly beats throwing abroad a perfectly expert piece of hardware!

What Compatibility Mode Does

Windows NT, 2000 and XP Abode and Professional all run off a 32-flake kernel, which does away with the 16-bit DOS layer used by Windows 95, 98, and ME. The kernel is the first part of the operating system to load into memory. It contains the core routines that provide the bones services for all other parts of the operating organization. Compatibility Mode is designed to help when running 'legacy' applications — those that were originally designed for a previous version of Windows. These can include 32-fleck applications designed for Windows 9x, NT, or 2000, plus 16-scrap applications originally destined for operating systems equally one-time as Windows 3.1 or MS-DOS.

Although many such legacy applications will run perfectly well under Windows XP without any tweaking at all, others check for the required version of Windows during their startup routines and abort if they don't find information technology, or check for the existence of specific system files that have long since been superseded, throwing upwards a cryptic error bulletin when they are not plant.

So, merely as Windows 98/ME had options to fool older programs into thinking that a version of MS-DOS was running, Windows XP'due south Compatibility Mode provides a more than comprehensive way to do the same matter for XP, without actually running any of the older code. Do note that utilities such as hard drive editors, defragmenters, some CD-called-for programs, virus-detection utilities, backup and other organization programs that crave low-level access to previous versions of Windows should not be used with Compatibility mode. Yous might scramble your bulldoze contents if you do this.

The End Of DLL Hell

Vital system files are stored by Windows XP in its organisation binder, but may also exist equally duplicates in the WinSxS folder (see main text), and in individual application folders, then different versions tin co-exist. As you lot can see, the different instances may also vary considerably in size. Some issues with older applications tin't be solved simply by using Compatibility Way, including those caused because an 'over the superlative' Windows XP install has left quondam versions of organisation files in the shared system binder. In the past, Windows 98 suffered from quite a few issues acquired by different versions of common DLL (Dynamic Link Library) files. Placing such commonly used system files into a single folder saved lots of drive space, but installing an elderly awarding could event in an older version of a shared system file overwriting the current one, causing other applications to fail or Windows itself to crash. Windows 2000 and ME both had Windows File Protection to prevent the modification of core system DLLs, while allowing individual applications to apply their own private versions of these files.

Windows XP goes further, past introducing 'shared assemblies' consisting of a grouping of resource, including DLLs, stored in the WinSxS (Windows Side by Side) binder, plus 'private assemblies' that are stored in the application's own binder. If an older application relies on an old DLL but a newer version already exists, Windows XP will spot this and divert calls to the older version, equally necessary, while leaving the newer version in place for other applications.

Many older applications, such as Cubase VST, rely on 16-chip DLL files which, under Windows 98/ME would probably be found in the Windows/System folder. If you're upgrading to XP it'due south of import that you lot completely united nations-install such programs, then re-install them again afterward the changeover. These applications will then nonetheless remember they are installing whatever system file versions they demand, but XP will be managing the process and will not allow them overwrite vital system files. Reinstalling should too ensure that information stored in the erstwhile Win.ini and System.ini files is correctly copied into the new Windows XP Registry. And then, when the applications are run, they can either use their own individual versions of system files, safely stored within the application's own folder, or the required shared version from the Windows SxS folder, without interfering with the newer organization files used by nearly XP applications.

How will yous know if the applications you desire to run apply 16-fleck DLL files? Some developers volition tell y'all on their web sites, merely if you can't find out, and in the case of large music apps, it might be wise to uninstall and reinstall as a matter of course, but to be certain.

How To Use Compatibility Mode

You tin can use XP's compatibility options with any application on your drive (with the above caveats). It'southward as well possible to choose an application on a CD-ROM or floppy deejay to run in compatibility mode, which might be handy for a ane-off session, although the settings will be forgotten every bit soon every bit you exit the application.

The safest mode to proceed (particularly on the kickoff few occasions) is via the Plan Compatibility Wizard, whose shortcut y'all should observe in the Accessories section of your Start Menu. This will guide you advisedly through the process, helping you make the near suitable decisions by testing them on the target awarding to detect out which emulation works best. Kickoff you decide whether to choose from a list of programs currently installed on your hard bulldoze, or one on the electric current deejay in the CD-ROM bulldoze, or to locate the programme manually by browsing through your drive's folders.

Sometimes a problem application may give the game away with a message like this, making the choice of compatibility mode easy, although in many cases you'll have to do the detective work yourself. One time you've chosen, clicking on the Adjacent button takes you lot to a screen where yous can choose the operating system nether which the application was originally designed to run. The choices will be Windows 95, Windows 98/ME, Windows NT 4.0 (Service Pack 5), or Windows 2000. The subsequent folio provides various display settings where yous tin choose to run your application in 256 colours or in 640 x 480-pixel screen resolution, both of which can be useful with some older games and educational programs that will just run properly in 640 10 480 x 256 mode. The lowest screen resolution offered by Windows XP is normally 800 ten 600 with 16-bit colour, then Compatibility Mode is the just mode to strength lower values to use. You tin can as well 'Disable visual themes' on this folio, a step that can overcome problems with some applications that insist on dealing wth graphics in a non-standard way.

Finally, you get to test your compatibility settings. Assuming y'all don't get an mistake bulletin, the program you've chosen to cheque will be launched for you lot to try out. As soon every bit you've confirmed whether or not it works properly, you tin get out it and return to the Compatibility Wizard, either to confirm the settings, attempt again with dissimilar ones, or abandon the attempt.

If you lot already know the most likely compatibility settings for a particular application, a rather quicker way to go on in XP is to right-click either on the app'due south chief EXE file (if you know in which folder this can be found) or (more than easily) right-click on its shortcut in the Kickoff menu or the desktop and select the Backdrop option. The third tabbed folio of Backdrop is 'Compatibility', and hither y'all'll find all the settings in 1 identify — in that location's a tick-box for Compatibility Way, and once this is ticked a further drop-down menu becomes available, where y'all cull the operating system, and below this the brandish settings.

Older Music Programs With Windows XP

In many cases, if an application is Windows 2000 compatible it will likewise work nether XP, although there are no guarantees. Elderly plug-ins and VST Instruments should also about always work fine; any problems relating to these are likely to exist due to the host application, or possibly the version of DirectX that you lot're using, in the example of DX plug-ins. The merely plug-in related software that does apparently cause issues is early on versions of Autotune.

I intended to post an extensive list here of older versions of music applications that would run under Windows XP, but plant information technology extremely difficult to get any definitive answers. Most developers automatically recommend that users update to the latest version of their applications, and whatever information on the compatibility of older versions tends to disappear from their spider web site once a newer version appears that directly supports XP. Moreover, Microsoft's Windows Catalogue only covers newer applications that fully support XP, and although there are hundreds of posts on music related forums, featuring user queries and anecdotal advice on getting ancient music software to run under XP, very few can unfortunately be substantiated, particularly when issues such as the tightness of MIDI or audio timing are involved.

My near successful observe was www.ntcompatible.com, which (despite its name) provides a user-supplied compatibility list for a huge range of hardware and software running under Windows NT 4.0, 2000, and XP, sometimes with explanatory notes (click on Evidence in the relevant Details cavalcade). Plenty of music software is covered, including elderly Cakewalk and Steinberg applications.

In the instance of Steinberg applications, Cubase SX was written with XP specifically in mind (and so, conversely, at that place are no guarantees of its performance if you install it under Windows 98SE). Withal, version 5.1r1 is the simply version of Cubase VST that officially runs under Windows XP. (Similarly, Wavelab 4.0 is the first version of Wavelab to officially run under XP.) While before versions of Cubase VST, such every bit V3.7, will run successfully nether Windows 2000, and may install nether XP, you will probably experience audio and MIDI skipping, timing problems, or other issues, whatever compatibility modes you try.

Breeze started their PC music software range very early on on, with Cakewalk Professional 1.0 through 4.0 for DOS, earlier moving on to Windows versions, and then followed it with their Pro Audio range for Windows. They seem to have rapidly embraced each new version of Windows as it appeared. Pro Audio 9.0 was launched with back up for Windows NT four.0 besides as 95, 98, and 98SE, but apparently besides runs well under XP. Pro Audio 8.0 is too claimed to be compatible with Windows 2000 on ntcompatible.com, and then it'southward possible that it might run under XP as well. Sonar 1.0 was optimised to run under Windows 98SE, ME, and 2000, despite few soundcards supporting the last at the time, but it will too run under XP, along with all newer versions.

Emagic's range presents a tricky state of affairs, since further development for the PC platform stopped at Logic version 5.v.1, while the current Mac version is now at 6.3.1. However, all version 5 releases of Logic Audio are compatible with XP, and I likewise came across references to version 4.8 working on XP as long as you lot use the Windows 2000 installer CD.

MS-DOS Programs Under XP

The Windows 9x family included a 'real way', or 16-bit MS-DOS environment, as an pick, which you lot could access by choosing the 'restart in MS-DOS mode' option in the Shut Downwardly Windows dialogue. This mode allowed Windows to exist completely bypassed, for performing tasks such as fault-finding. Still, Windows XP tin can only run MS-DOS programs while Windows itself is still running, since XP is not based on the MS-DOS kernel.

Despite this, you lot can still run almost MS-DOS programs under Windows XP in largely the same way equally under other versions of Windows. They can either appear in a window of their own alongside other Windows applications, or in total-screen mode as they would accept originally appeared running from DOS. Toggle this display mode when the program is running by using the Alt-Enter fundamental combination.

To alter whatsoever other attribute of operation you simply correct-click over the title-bar of the running program and select Properties, where y'all tin can change such things every bit font size (which determines the overall size of the window). These settings are saved in a PIF (Program Data File), which is essentially a shortcut file that sets up a uniform environment in which that item MS-DOS programme can exist run. Any DOS programs without a specific file will use the default settings, which are saved in the _default.pif file.

Correct-clicking on the DOS file, or its shortcut, and selecting Properties allows further customisation. In improver to the Compatibility page, y'all'll find several other options, including 1 that may testify handy for musicians. It can be accessed via the Advanced button on the Programme page, where the tick-box labeled 'Compatible timer hardware emulation' may help solve some timing issues with DOS programs. Another potentially useful option is 'Fast ROM emulation' on the Screen folio, which may solve screen abuse problems. On the Misc(ellaneous) page, united nations-ticking the 'Always suspend' box will let the DOS program carry on running when you've switched to another Windows awarding.

I've been using Phillip Nickell'southward DOS-based FED (File Editor) for years to examine the contents of files, and it still runs perfectly well under Windows XP, in a window, with plenty of user options accessed from its Properties dialogue. Many older DOS-based games, and applications such every bit early MIDI sequencers (Breeze's Professional series, for example), were originally booted upwards with the PC in DOS mode, long before Windows e'er got a look in, and completely took the PC over, configuring the RAM and hardware such every bit the graphics menu and soundcard to its own requirements. Indeed, these programs would often cause extra lines to appear in the Autoexec.bat and Config.sys files, both of which are largely unused under Windows XP. This made such games extremely efficient, since they had total control over the PC, but very inflexible when new graphics cards or soundcards came forth.

XP stores environment variables from both the higher up-mentioned files directly into its Registry when yous install the programs in question. If yous've performed an 'over the top' upgrade from Windows 98 or ME to Windows XP, to avert having to reinstall all your applications, some may be relying on lines in these Autoexec.bat and Config.sys files to load special driver files or alter system variables. As a quick cheque, but open the Autoexec.bat and Config.sys files in a simple text editor, such as Notepad, and run into if there are any lines in them relating to graphics or sound devices.

Since XP ignores the Autoexec.bat and Config.sys files, if y'all attempt to run the application it will probably abort with an error complaining of 'missing device drivers', or even reboot Windows. This may also happen with some scanners and their drivers. One solution is to uninstall the quondam DOS program (or old Windows 98 hardware drivers if nosotros're talking about scanners, for example) and then run Install again. This might cure the problem, but if not, install again using Compatibility Fashion. You lot might have to choose Windows 2000 or NT four.0 mode to forcefulness unlike drivers to be installed, but and then the extra lines of educational activity won't be needed.

Windows NT and 2000 both prevent any program talking directly to the hardware, which tends to make them a lot more stable than Windows 95, 98 and ME, just also less compatible with older software requiring Soundblaster support or lower-resolution graphics, which especially affected DOS-based games. Windows XP likewise prevents straight access, but this time information technology has Soundblaster emulation congenital into its NTDVM (NT DOS Virtual Auto) system. The NTDVM is used to run each MS-DOS application equally a separate process, to protect them from each other, and from the balance of the operating system. And then you lot may find that really old DOS games and music programs with bones Soundblaster support run under XP when they refused to do so under Windows NT or 2000.

Choppy audio (timing problems) and graphic updates when running older applications nether XP may exist the most difficult problems to solve, since 16-bit applications use co-operative multitasking, which means that they become their CPU time when another application has finished using it. The 32-bit applications of Windows XP employ pre-emptive multi-tasking, where priorities are used to determine process interruptions. Problems with graphics may exist resolved by updating your graphic drivers and installing the latest version of DirectX, although the latter may cause problems with a few music applications, and so practise a lilliputian checking on the forums first earlier taking the plunge. If timing problems persist afterwards reinstalling, at that place's probably little you can practice about them.

Conclusions

You're always likely to get the most stable Windows XP installation past starting with a freshly formatted partition, and many of the musicians who performed an install 'over the top' of their existing Windows partition and had problems would do well to retrieve this before condemning XP out of mitt. However, if you've done an 'over the peak' install and are notwithstanding having problems with one or two applications, attempt uninstalling them and reinstalling from scratch. This will give XP a much better chance of dealing with references to old system files and previous entries in the Win.ini and System.ini files, and will reduce the possibility of other applications being afflicted by old files even so floating about in the system. First past installing them just like any other XP application. If you lot get any install problems, start again while running the near appropriate Program Compatibility Mode, since this may let you complete the install. One time the installation is complete, if you get whatsoever problems while running the awarding, such as obvious error messages or obscure crashes, try again under Compatibility Mode to meet if this cures the problem.

In the case of DOS programs, at that place are enough of system tweaks, as mentioned earlier, that can aid to go them working satisfactorily. Nonetheless, the chances are that fifty-fifty if such programs crusade not-resolvable problems while running nether XP you might still be able to get them going on a fast modern PC when information technology'southward truly running DOS, either by booting your PC from a Windows 98SE startup floppy disk, or in the absence of a floppy bulldoze, from a bootable CD-ROM with a DOS option, such as PowerQuest's Partition Magic. The DOS command-line surround might seem primitive by comparison with Windows, but if (for example) it lets you retrieve some synth banks in a proprietary format and transport them to a hardware synth via SysEx, and then reboot your PC into Windows and retrieve and store the sounds using a more modern awarding, it's well worth the effort. Skillful luck!

Compatibility Mode Problems

If you get whatever strange issues from an XP application with your mouse or keyboard, check that Compatibility Mode hasn't been accidentally engaged. Because of the way information technology works, Programme Compatibility style may cause problems when used with some applications. Symptoms to scout out for include a frozen mouse pointer, unresponsive PC keyboard, various USB errors, and complete software lockups. Information technology's also been known for similar bug to occur with applications that are perfectly capable of beingness run on Windows XP, but which have been accidentally fix to compatibility manner. To bank check for this, just right-click on the application'due south shortcut in the Starting time Menu and cull Backdrop. Then navigate to the Compatibility page and bank check that the 'Run this programme in compatibility mode' tick box is inactive.

By the way, if you lot enter Safe Mode (using the advisable menu option after pressing the Ctrl central during a Windows 98/ME boot, or F8 during a Windows 2000/XP kick), you'll see, nether the Performance tab of Device Manager, that 'Some drives are using MS-DOS compatibility'. This is nothing to do with the main topic under give-and-take here, and is perfectly normal in Safe Mode, since Windows reverts to using a basic set of drivers. However, if you lot ever meet this message when running Windows normally, information technology probably means that your hard drive controller or drive device driver has a problem. Your best bet in this situation is to reinstall the appropriate drivers.

Source: https://www.soundonsound.com/techniques/running-legacy-software-under-windows-xp

Posted by: hancockhandep84.blogspot.com

Share this post