QUOTE (celtish @ May 31 2008, 06:05 PM)

My son is pressing me to install WinXP in place of Win98SE. Well, actually the XP is already installed on his machine which he is proposing to sell me in place of my Win98SE machine. The idea has until now been simply to switch my hard disks into the newer machine. (see another thread about this matter)
One of the big concerns I have is to do with "true" DOS which seems to have been discontinued after Win98SE. Would it be feasible to install true DOS onto XP??? If so, how would I do it?
(see another thread about this matter)Somehow missed that thread. Link? Thought this was where you were working that out.
Would it be feasible to install true DOS onto XP???Afraid not. However there are ways to make DOS and Windows 16-bit apps work just fine. Here is my checklist order of precedence ...
(1) WinXP CMD :: aka Command Prompt aka DOS Prompt. This is where you wind up when you open a Command Prompt. CMD.EXE is the actual program in use here whereas Win9x used COMMAND.COM. It is enhanced and configureable. Apps run here using the default DOS environment found in the registry (in two keys I believe). If you double-click a DOS app without a shortcut it effectively runs here.
(2) WinXP Shortcut :: for DOS apps creates a PIF file like in Win9x. If you change nothing in the properties the app runs using the default environment located in CONFIG.NT and AUTOEXEC.NT in the SYSTEM32 folder. NOTE: many of the other Win9x DOS PIF properties are still present here in WinXP. However, if you use Properties|Program|Advanced, instead of creating an MS-DOS Mode *reboot* environment like in Win9x, you get to pick custom-made AUTOEXEC.NT and CONFIG.NT which the app will see as its environment when run from that shortcut (there is no reboot). For a Windows app the LNK file offers some extra options in Properties|Compatibility such as 'Run ths program in Compatibility Mode for Windows 95' etc.
(3) 3rd party DOS Command Boxes :: best known has to be
DOSBox which has a large community to draw support from including a front-end called
Turbo Dos Box. Another one is
eConsole. Expect this to become a growth industry since the trend in Windows has been to get away from the command line. Did I mention these are free?
One problem has carried over of course, and that is DOS/WIN16 games that
expect specific IRQ and DMA channels for sound output and are too stubborn to let you change them within the program or in some INI file. I try to edit the 'DOS' environment variables for that specific app and hope it looks there for guidance. If not, I don't use that game on WinXP. However there are many Creative and other sound card command line emulation utilities that alter resources visible to a DOS program. They get installed with the drivers (but ask an expert for more details).
'True' DOS apps really are being killed by a thousand cuts independent of WinXP. The technology itself regardless of Windows version has incrementally excluded entire categories of DOS apps (those expecting direct disk access, direct video access, memory, DMA, IRQs ... ). Things started to get really risky with LFN in Win95. If you hope to fire up true DOS heavyweights like SoftICE it ain't gonna happen because you can't really load something underneath Windows anymore. Heck the older .386 dirvers for 'legitimate' programs like scanners won't load either.
Anything that is OpenGL or Direct-X based of course runs and that seems to be enough to satisfy 99% of the planet. But in reality most old DOS apps by thoughtful authors who allowed for hardware changes can be managed in their native form on WinXP: Wolf3D, Doom etc. More importantly, many people are busy porting old classics into Win32 apps: Doom95 (an early example by MS),
Shadow Warrior, Duke/Blood/Redneck (
Build Engine) Rise Of The Triad ( I just recently heard about
ROTT and will definitely be grabbing that! For a while I thought I was the only one that bought that game). Also there is a slew of emulators and ports of those really ancient ROM cartridge games from Commodore, Atari, Amiga.
...pressing me to install WinXP in place of Win98SEThere is something to be said for WinXP as an end-user operating system. If you think life is too darn short to be micro-managing OS details you should be on WinXP. If your head is always under the hood of your car you're probably suited to stay on Win9x. If you'd rather just drive the car, definitely get WinXP.
Is there some reason you cannot keep two computers, Win9x and WinXP? It's simple enough to shuffle files between them on a flashdrive. I find redundancy to be a good thing especially when there is a problem on one system. If the WinXP system got a virus you'd be wishing the Win9x was there as a backup! I'd suggest buying his computer and keeping the Win9x system also. If the Win9x system collects dust in the corner then WinXP was the right choice. If you find yourself constantly firing up the old beast, ah well it's ok. Just make sure the XP system is set up right, with 1 GB RAM and some of the basic tweaks (Disk Indexing off) you can find all over this forum.
Let us know how it turns out!