Article View: alt.games.wing-commander
Article #17788Re: Directx 3 "upsets" existing DOS mode games
From: d... David L Webster
Date: Fri, 09 May 1997 00:00
Date: Fri, 09 May 1997 00:00
53 lines
2991 bytes
2991 bytes
On Thu, 8 May 97 09:02:00 +1100, ch...@vci.com.au (Chris Rogers) wrote: > >hmm..... I am sorry but my newsserver has not got the start of this >thread - hence I have missed the DirectX connection. >But as far as DOS 6.22 is concerned, I hate to be just as blunt, >but anyone who says that OLD DOS is NEVER needed just has no >clues at all either. > >$0.02 > >Chris > Well, continuing in the blunt vein, when I read about people who think they need to juggle different versions of DOS using bootdisks, dual boots etc, I wonder why they put themselves through all that hassle. When DOS 3.1 came out, I dumped 3.0, same thing for 3.3. When 5.0 was out, I certainly didn't keep 3.3 boot disks around for anything (note I didn't mention DOS 4, I did skip that one which was a real stinker). When 6.0 hit the streets, 5.0 was history. I dumped OLD DOS (6.22) in August '95 and have only used DOS 7 since then for everything. I use the same multi config options that I used in 6.22. No boot disks, no dual booting different versions of DOS. I have yet to find a DOS program I couldn't get to work. Besides a slightly larger footprint in conventional memory, it's the same old DOS. And for those few WIN 3.1 apps that won't work under 95? I run WFW3.11 from DOS 7, works great. No boot disks, no dual DOS, no hassle. Right now I'm doing contract computer work for a very large company (one of the largest Novell networks in the world). We are in the process of converting from DOS 6.2/Win3.1 to Win95. Now they have lots of custom apps, both DOS and Windows. During testing they found the DOS apps all work under DOS 7. Now they still have some Win 3.1 apps that don't quite work yet under 95, so until they get upgraded they still need Win 3.1 for some things. The MIS department decided on a DOS 7/Windows 4(95)/Win31 configuration. When they need Win3.1 they run it from DOS 7. Their thoughts were the same, why juggle two versions of DOS? It's just one more thing to deal with, more troubleshooting questions, two sets of boot disk for the MIS techs to carry around, etc. They certainly aren't supporting machines using DOS 1.0, 2.0, 2.1, 3.0, 3.1, 3.3, 4.0, 5.0, 6.0, 6.2, 6.21. One DOS is all you need, and certainly simplifies life, at least for me. Well, there's my .02. ----- Dave Webster d...@bridge.net
Technical Details
Message-ID:
<3372f076.23549939@news.bridge.net>Path:
mbox-mo1.pugleaf.net!unknown!not-for-mailReferences:
<01bc4912$3e2ff2e0$2568adce@crc3.concentric.net> <33524edf.990813@news.gabn.net> <01bc46e9$2e278f00$02551dcb@COMPUTER1> <33555055.5365121@news.bridge.net> <oMiczAPBBh107h@vci.com.au>Show Full Headers
Complete Article Headers
From: d...@bridge.net (David L Webster) Subject: Re: Directx 3 "upsets" existing DOS mode games Date: 1997/05/09 Message-ID: <3372f076.23549939@news.bridge.net> X-Deja-AN: 240444927 References: <01bc4912$3e2ff2e0$2568adce@crc3.concentric.net> <33524edf.990813@news.gabn.net> <01bc46e9$2e278f00$02551dcb@COMPUTER1> <33555055.5365121@news.bridge.net> <oMiczAPBBh107h@vci.com.au> Organization: BridgeNet LC, Miami Florida Newsgroups: alt.games.wing-commander,aus.games,comp.sys.ibm.pc.games.flight-sim MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit