Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!think.com!snorkelwacker.mit.edu!linus!linus!mwunix.mitre.org!jcmorris From: jcmorris@mwunix.mitre.org (Joe Morris) Newsgroups: comp.sys.ibm.pc.misc Subject: Re: Looking for MS-DOS 5.0 Compatibility Tricks... Message-ID: Date: 20 Jun 91 20:59:39 GMT References: <1991Jun16.043650.7990@vpnet.chi.il.us> <1991Jun17.173153.17151@ugle.unit.no> <1991Jun20.121241.1190@sun1.ruf.uni-freiburg.de> Sender: news@linus.mitre.org (News Service) Organization: The MITRE Corporation, Bedford MA Lines: 19 Nntp-Posting-Host: mwunix.mitre.org hartnegg@sun1.ruf.uni-freiburg.de (Klaus Hartnegg) writes: >janeri@Lise.Unit.NO (Jan Eri) writes: >>Did you remember to reboot after issuing the SETVER command? >If this is really necessary (what I doubt) what shall I do if I have >one program that needs version 5 and another one that refuses >to work unless it is running on a specific dos version. >Do I have to boot every time I want to switch between these >two programs? Great! SETVER works on a program name basis: the fake version number it returns is a function of the name of the program which issued the return-version- number interrupt. Thus, you can have MSCDEX.EXE think it's running on DOS 4.00 while VDISK.SYS believe that we're still running DOS 3.3. Joe Morris