How To Run Newer Programs On Windows Xp

Do you have elderly Windows or MS-DOS software that refuses to run under Windows XP? If and then, at that place may still be a way to get information technology working.

When Windows XP was first released, it was already compatible with a broad range of hardware and software applications, largely because Microsoft and various third-party developers had been working together to ensure the widest possible client uptake of the OS. Nevertheless, this compatibility mainly practical to the most pop third-political party products, including (naturally) Microsoft's own range, leaving a huge number of other software applications and hardware peripherals in limbo.

To exist supported under whatever new operating organization, hardware most always needs new drivers, and so information technology's extremely important to wait until these have been written before installing Windows XP. Many people upgraded their PCs to Windows XP immediately it was released and discovered the difficult fashion 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 buy replacement hardware that did piece of work.

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

The Current State of affairs

Two years on, the vast majority of soundcards now have stable and efficient XP drivers, and most of the major music applications accept been updated to new versions that comprise XP compatibility, while other more recent releases, such as Steinberg's Cubase SX have been written from the ground upwardly to conform Windows XP. However, some musicians, while attracted to the new features of Windows XP, are even so perfectly happy with the feature set up 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 accept older music software that's still vital to their studio, but whose developers take gone out of business, leaving no prospect of an XP update.

So how can yous notice out whether any of your software might cause issues with XP? Firstly, Microsoft take a database of hardware and software that has been declared compatible (www.microsoft.com/Windows/catalog), although it's by no means exhaustive, peculiarly in the case of music products. The soundcard section is almost exclusively devoted to Artistic products, for instance, while the Digital Video, Audio, and Animation department contains none of the nigh pop music software.

If you take a program that causes you problems running nether Windows XP, the Program Compatibility Wizard provides a selection of modes that emulate diverse previous versions of Windows. Microsoft practise besides provide the Upgrade Advisor (a gratis 32Mb download). This tool will scan your hardware and software for possible conflicts, but it isn't infallible — specially, information technology seems, with scanners and software-based modems, oftentimes declaring them incompatible when in reality they're working well. The Upgrade Advisor is also supplied on the Windows XP CD-ROM, and runs automatically as role of the Setup routine if yous decide to upgrade an existing version of Windows. It can also be run on demand: just click the 'Cheque System Compatibility' pick on the 'Welcome to Microsoft Windows' page that appears afterward you lot insert the XP CD-ROM into your drive or run its Setup.exe file.

What about applications non covered past Microsoft's list? Well, all Windows software released in the terminal couple of years volition most certainly be XP-compatible. When it comes to software released earlier Summertime 2001 and not subsequently updated, many helpful developers have posted a simple assurance on their spider web site that all will exist well if their software is run nether XP, or offer specific instructions on the best way to go along, even if an update isn't likely. Y'all may fifty-fifty be able to download a small 'fix' or 'patch' file that, once run, will return the original application completely XP-compatible. An example is the patch supplied by Gary Gregson for his popular XGedit utility, which cures pocket-size graphic corruption when running nether Windows 2000 and XP. Yamaha accept a similar patch DLL file for their XGworks ii.0 application, to permit it 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 perhaps yous're absolutely determined to stick with the current version of the application rather than indulge in a payable upgrade, even if there is one bachelor. If so, y'all may exist lucky: it's quite possible that you lot won't experience problems when installing and running the application in question nether XP. Of the problems that can occur, some may be immediately obvious, such as a Setup or Install routine that refuses to run (although sometimes such problems tin be cured in a PC with multiple user accounts by logging back on as Administrator, or past logging off any other users except the account that volition install the program).

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

Hardware Incompatibility Problems

Program Compatibility modes can only deal with some software problems, and they don't attempt to resolve those relating to hardware. After all, this is the province of the hardware commuter, and therefore up to to the private hardware manufacturer. You should visit the web sites of all hardware expansion menu manufacturers to download the latest XP drivers for your devices, including soundcards, graphic cards, modems, network cards, and so on. Farther 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 audio drivers, yous may need an XP patch file to get the best results from USB two.0 sound peripherals.

Nevertheless, if one of your favourite hardware devices doesn't have an XP driver, don't bin it or abandon XP every bit an option simply yet, since in that location may be another way to get it to work. Try an Internet search using the device name and 'XP drivers' to see if there'due south any other information available, peculiarly from user groups. For instance, I'm all the same using an old Agfa Snapscan 1212P scanner, bought in 1999, with a parallel port connection. While Agfa claim that XP drivers will never be written for it, I discovered claims by users that the Windows 2000 Beta drivers volition piece of work under Windows XP, albeit with a few caveats. For the few times I use my scanner I'm happy to work effectually these, and it certainly beats throwing away a perfectly good slice of hardware!

What Compatibility Style Does

Windows NT, 2000 and XP Home and Professional person all run off a 32-bit kernel, which does abroad with the sixteen-fleck DOS layer used past 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 basic services for all other parts of the operating system. 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-bit applications designed for Windows 9x, NT, or 2000, plus 16-bit applications originally destined for operating systems as old as Windows 3.i or MS-DOS.

Although many such legacy applications will run perfectly well nether 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 it, or bank check for the being of specific system files that have long since been superseded, throwing up a cryptic fault message when they are not constitute.

So, but 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 comprehensive fashion to do the same thing for XP, without actually running any of the older code. Do note that utilities such as difficult bulldoze 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 style. You might scramble your bulldoze contents if yous do this.

The End Of DLL Hell

Vital arrangement files are stored by Windows XP in its system folder, but may also exist as duplicates in the WinSxS folder (encounter main text), and in private application folders, and then different versions can co-exist. As you can meet, the unlike instances may also vary considerably in size. Some problems with older applications tin can't exist solved merely past using Compatibility Mode, including those caused because an 'over the pinnacle' Windows XP install has left old versions of organization files in the shared system folder. In the past, Windows 98 suffered from quite a few issues caused past unlike versions of mutual DLL (Dynamic Link Library) files. Placing such commonly used system files into a single folder saved lots of drive space, merely installing an elderly application could upshot 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 cadre arrangement DLLs, while allowing individual applications to use their own individual versions of these files.

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

Many older applications, such as Cubase VST, rely on 16-bit DLL files which, under Windows 98/ME would probably be found in the Windows/System folder. If you're upgrading to XP it's of import that yous completely united nations-install such programs, and and then re-install them again after the changeover. These applications will then still think they are installing whatsoever system file versions they demand, but XP volition be managing the process and volition not permit them overwrite vital system files. Reinstalling should likewise ensure that information stored in the old Win.ini and Arrangement.ini files is correctly copied into the new Windows XP Registry. And so, when the applications are run, they can either utilise their own private versions of system files, safely stored within the awarding'southward own folder, or the required shared version from the Windows SxS folder, without interfering with the newer system files used past most XP applications.

How will y'all know if the applications you lot want to run utilise xvi-bit DLL files? Some developers will tell you on their web sites, but if you tin can't discover out, and in the case of large music apps, it might be wise to uninstall and reinstall as a matter of course, just to be sure.

How To Utilise Compatibility Mode

You can use XP's compatibility options with any application on your drive (with the above caveats). Information technology's also possible to choose an application on a CD-ROM or floppy disk to run in compatibility mode, which might be handy for a 1-off session, although the settings will exist forgotten equally soon as you leave the application.

The safest manner to proceed (peculiarly on the outset few occasions) is via the Program Compatibility Wizard, whose shortcut you should find in the Accessories department of your Beginning Menu. This will guide y'all carefully through the process, helping y'all make the nearly suitable decisions by testing them on the target awarding to notice 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 current deejay in the CD-ROM drive, or to locate the program manually past browsing through your bulldoze'southward folders.

Sometimes a problem awarding may give the game abroad with a bulletin similar this, making the pick of compatibility fashion easy, although in many cases you'll accept to do the detective work yourself. In one case you've chosen, clicking on the Next push button takes you to a screen where you tin choose the operating organization under which the application was originally designed to run. The choices volition exist Windows 95, Windows 98/ME, Windows NT 4.0 (Service Pack 5), or Windows 2000. The subsequent page provides various brandish settings where you lot can cull 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 volition only run properly in 640 x 480 x 256 mode. The lowest screen resolution offered past Windows XP is unremarkably 800 x 600 with 16-fleck colour, so Compatibility Mode is the only way to strength lower values to apply. You tin also 'Disable visual themes' on this page, a step that can overcome problems with some applications that insist on dealing wth graphics in a non-standard way.

Finally, yous get to test your compatibility settings. Bold you lot don't go an mistake message, the program yous've called to bank check volition be launched for y'all to try out. Every bit presently every bit yous've confirmed whether or not it works properly, you tin can exit it and render to the Compatibility Sorcerer, either to confirm the settings, try again with different ones, or abandon the attempt.

If you already know the about likely compatibility settings for a particular awarding, a rather quicker fashion to keep in XP is to correct-click either on the app'due south main EXE file (if you know in which folder this tin can be found) or (more than easily) right-click on its shortcut in the Start menu or the desktop and select the Properties option. The third tabbed folio of Properties is 'Compatibility', and here you lot'll find all the settings in i place — there's a tick-box for Compatibility Manner, and once this is ticked a farther driblet-down menu becomes bachelor, where you cull the operating organisation, and beneath this the display settings.

Older Music Programs With Windows XP

In many cases, if an application is Windows 2000 compatible information technology will also work nether XP, although there are no guarantees. Elderly plug-ins and VST Instruments should too nearly always piece of work fine; any problems relating to these are likely to be due to the host application, or perhaps the version of DirectX that you're using, in the case of DX plug-ins. The only plug-in related software that does apparently cause problems is early on versions of Autotune.

I intended to post an all-encompassing list here of older versions of music applications that would run nether Windows XP, but found it extremely difficult to get whatsoever 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 web site once a newer version appears that directly supports XP. Moreover, Microsoft'south 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 aboriginal music software to run under XP, very few tin can unfortunately exist substantiated, particularly when problems such every bit the tightness of MIDI or sound timing are involved.

My most successful find was world wide web.ntcompatible.com, which (despite its name) provides a user-supplied compatibility list for a huge range of hardware and software running nether Windows NT four.0, 2000, and XP, sometimes with explanatory notes (click on Evidence in the relevant Details column). Plenty of music software is covered, including elderly Breeze and Steinberg applications.

In the case of Steinberg applications, Cubase SX was written with XP specifically in mind (so, conversely, there are no guarantees of its performance if you lot install it nether Windows 98SE). Nonetheless, version 5.1r1 is the only version of Cubase VST that officially runs nether Windows XP. (Similarly, Wavelab 4.0 is the first version of Wavelab to officially run under XP.) While earlier versions of Cubase VST, such as V3.seven, will run successfully under Windows 2000, and may install under XP, you will probably experience audio and MIDI skipping, timing issues, or other issues, whatsoever compatibility modes you try.

Cakewalk started their PC music software range very early on on, with Cakewalk Professional person one.0 through 4.0 for DOS, before moving on to Windows versions, and then followed information technology with their Pro Audio range for Windows. They seem to accept chop-chop embraced each new version of Windows every bit it appeared. Pro Audio 9.0 was launched with back up for Windows NT 4.0 as well as 95, 98, and 98SE, simply apparently likewise runs well under XP. Pro Audio 8.0 is also claimed to be compatible with Windows 2000 on ntcompatible.com, so it'south possible that it might run under XP every bit well. Sonar 1.0 was optimised to run nether Windows 98SE, ME, and 2000, despite few soundcards supporting the last at the time, but it will also run under XP, forth with all newer versions.

Emagic'southward range presents a tricky situation, since farther development for the PC platform stopped at Logic version 5.five.one, while the current Mac version is now at half dozen.3.i. However, all version 5 releases of Logic Audio are compatible with XP, and I also came across references to version four.viii working on XP equally long as you use the Windows 2000 installer CD.

MS-DOS Programs Under XP

The Windows 9x family included a 'real fashion', or 16-scrap MS-DOS surroundings, as an option, which you lot could admission by choosing the 'restart in MS-DOS mode' option in the Shut Down Windows dialogue. This mode allowed Windows to be completely bypassed, for performing tasks such equally fault-finding. However, Windows XP can only run MS-DOS programs while Windows itself is still running, since XP is non based on the MS-DOS kernel.

Despite this, you can still run well-nigh MS-DOS programs under Windows XP in largely the aforementioned way as nether other versions of Windows. They can either appear in a window of their own aslope other Windows applications, or in total-screen manner as they would have originally appeared running from DOS. Toggle this display mode when the program is running past using the Alt-Enter key combination.

To alter any other attribute of operation you just right-click over the title-bar of the running programme and select Properties, where you lot tin can change such things as font size (which determines the overall size of the window). These settings are saved in a PIF (Plan Data File), which is substantially a shortcut file that sets up a uniform environs in which that particular MS-DOS program can be run. Any DOS programs without a specific file will utilize the default settings, which are saved in the _default.pif file.

Right-clicking on the DOS file, or its shortcut, and selecting Properties allows further customisation. In add-on to the Compatibility page, you'll find several other options, including one that may prove handy for musicians. It can be accessed via the Advanced push on the Programme page, where the tick-box labeled 'Compatible timer hardware emulation' may help solve some timing problems with DOS programs. Another potentially useful option is 'Fast ROM emulation' on the Screen folio, which may solve screen corruption issues. On the Misc(ellaneous) page, un-ticking the 'Ever suspend' box volition permit the DOS program carry on running when you've switched to another Windows application.

I've been using Phillip Nickell's DOS-based FED (File Editor) for years to examine the contents of files, and it however 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 equally early MIDI sequencers (Cakewalk's Professional person serial, for example), were originally booted up with the PC in DOS mode, long before Windows ever got a look in, and completely took the PC over, configuring the RAM and hardware such as the graphics carte and soundcard to its own requirements. Indeed, these programs would frequently cause actress lines to announced 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, only very inflexible when new graphics cards or soundcards came forth.

XP stores environs variables from both the above-mentioned files straight into its Registry when you install the programs in question. If you've performed an 'over the top' upgrade from Windows 98 or ME to Windows XP, to avoid 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 modify system variables. As a quick check, just open up the Autoexec.bat and Config.sys files in a simple text editor, such as Notepad, and meet if there are any lines in them relating to graphics or audio devices.

Since XP ignores the Autoexec.bat and Config.sys files, if you lot attempt to run the application information technology will probably abort with an mistake lament of 'missing device drivers', or even reboot Windows. This may also happen with some scanners and their drivers. I solution is to uninstall the old DOS programme (or old Windows 98 hardware drivers if we're talking about scanners, for example) and then run Install again. This might cure the problem, but if not, install once again using Compatibility Mode. You might have to choose Windows 2000 or NT four.0 mode to force different drivers to exist installed, but then the extra lines of instruction won't be needed.

Windows NT and 2000 both foreclose any plan talking direct to the hardware, which tends to brand them a lot more stable than Windows 95, 98 and ME, merely also less compatible with older software requiring Soundblaster support or lower-resolution graphics, which particularly affected DOS-based games. Windows XP also prevents directly access, but this time information technology has Soundblaster emulation built into its NTDVM (NT DOS Virtual Machine) system. The NTDVM is used to run each MS-DOS application as a separate process, to protect them from each other, and from the rest of the operating system. So yous may find that really one-time DOS games and music programs with basic Soundblaster support run under XP when they refused to do and so nether Windows NT or 2000.

Choppy audio (timing problems) and graphic updates when running older applications nether XP may exist the most difficult bug to solve, since 16-bit applications use branch multitasking, which means that they become their CPU fourth dimension when another awarding 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 be resolved past updating your graphic drivers and installing the latest version of DirectX, although the latter may cause problems with a few music applications, and so do a piffling checking on the forums first before taking the plunge. If timing bug persist after reinstalling, in that location'south probably niggling you tin can exercise nearly them.

Conclusions

You're always likely to get the near 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 division and had issues would practice well to call up this earlier condemning XP out of hand. However, if you've done an 'over the top' install and are still having issues with one or ii applications, endeavour uninstalling them and reinstalling from scratch. This volition give XP a much better chance of dealing with references to old organization files and previous entries in the Win.ini and System.ini files, and will reduce the possibility of other applications existence afflicted by old files withal floating nigh in the organization. Start by installing them just similar whatever other XP application. If you get any install problems, start again while running the most appropriate Program Compatibility Style, since this may let you complete the install. Once the installation is complete, if you lot become whatever problems while running the application, 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 plenty of system tweaks, as mentioned before, that tin can assistance to go them working satisfactorily. However, the chances are that fifty-fifty if such programs cause non-resolvable problems while running under XP you might even so be able to get them going on a fast modern PC when it's truly running DOS, either by booting your PC from a Windows 98SE startup floppy deejay, or in the absence of a floppy drive, from a bootable CD-ROM with a DOS option, such every bit PowerQuest'southward Sectionalisation Magic. The DOS command-line surround might seem primitive by comparing with Windows, simply if (for example) it lets you think some synth banks in a proprietary format and send them to a hardware synth via SysEx, and then reboot your PC into Windows and recall and store the sounds using a more modern awarding, it's well worth the endeavour. Good luck!

Compatibility Mode Bug

If you get any foreign problems from an XP application with your mouse or keyboard, cheque that Compatibility Manner hasn't been accidentally engaged. Because of the way information technology works, Program Compatibility way may cause bug when used with some applications. Symptoms to watch out for include a frozen mouse pointer, unresponsive PC keyboard, various USB errors, and consummate software lockups. It's also been known for similar problems to occur with applications that are perfectly capable of beingness run on Windows XP, simply which take been accidentally ready to compatibility mode. To cheque for this, just right-click on the application'due south shortcut in the Kickoff Menu and choose Backdrop. Then navigate to the Compatibility folio and check that the 'Run this program in compatibility way' tick box is inactive.

By the style, if you enter Rubber Fashion (using the advisable menu option afterward pressing the Ctrl fundamental during a Windows 98/ME boot, or F8 during a Windows 2000/XP kick), yous'll see, nether the Performance tab of Device Managing director, that 'Some drives are using MS-DOS compatibility'. This is cypher to do with the main topic under discussion hither, and is perfectly normal in Condom Mode, since Windows reverts to using a basic fix of drivers. However, if you ever see this message when running Windows normally, it probably means that your difficult drive controller or drive device commuter 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: martintagazier1947.blogspot.com

Share this post