Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!midway!valley From: valley@uchicago (Doug Dougherty) Newsgroups: comp.binaries.ibm.pc.d Subject: Re: DOS gcc (dj1bin) problems Message-ID: Date: 27 Feb 91 14:52:04 GMT References: <1991Feb21.195421.15820@cs.UAlberta.CA> <3282@sixhub.UUCP> <1026@iiasa.UUCP> Sender: news@midway.uchicago.edu (News Administrator) Organization: University of Chicago Lines: 23 wnp@iiasa.ac.at (Wolf PAUL ) writes: >In article <3282@sixhub.UUCP> davidsen@sixhub.UUCP (bill davidsen) writes: >>In article veit@du9ds3.uni-duisburg.de (Holger Veit) writes: >> >> Nope, the programmer's ref for v2.0 said either could be used, and >>that command.com by default would use / as a switch and \ as a path, but >>would use / for the path delimiter if any other character was chosen. I >>think that's still documented, and it's certainly still true. >Unfortunately it is no longer true, or if so, the way to tell >COMMAND.COM to use a different switch char has been changed. >None of the utilities (p.d. and i.e., MKS Toolkit) which used to fix >the switch character in DOS under 3.2 work in the newer versions of >DOS. They seem to work, in that after you do a "switch -" they will Which version(s) of DOS are you talking about? The only DOS that works with a version # greater than 3.2 is 3.3 (or 3.31) and I'm pretty sure the INT 21, fn 37 method works under 3.3. You aren't, by any chance, actually thinking of using a DOS (?) whose version # starts with a 4, are you?