jim@syteke.UUCP (Jim Sanchez) (06/03/89)
I know this has been hashed over before but I just started reading
this newsgroup a couple of weeks ago when I got this old PC/XT. I
installed a 720K drive(3.5 inch) with DOS 3.3 and thought I would
tell the OS about this disk via the drivparm operation in config.sys.
Well to make a long story short, I cannot get drivparm to work at
all. I just get invalid command in config.sys. The line in
config.sys that I use is: drivparm=/d:1/f:2 which I think should
tell the OS that I have a 3.5 inch 720K drive for drive b: If
there is something I am doing wrong I would appreciate any pointers.
Thanks
--
Jim Sanchez {sun,hplabs}!sun!sytek!syteke!jim OR
Hughes LAN Systems, Brussels mcvax!prlb2!sunbim!syteke!jimcur022@zodiac.ukc.ac.uk (Bob Eager) (06/04/89)
In article <241@syteke.UUCP>, jim@syteke.UUCP (Jim Sanchez) writes: > I know this has been hashed over before but I just started reading > this newsgroup a couple of weeks ago when I got this old PC/XT. I > installed a 720K drive(3.5 inch) with DOS 3.3 and thought I would > tell the OS about this disk via the drivparm operation in config.sys. > Well to make a long story short, I cannot get drivparm to work at > all. I just get invalid command in config.sys. The line in > config.sys that I use is: drivparm=/d:1/f:2 which I think should > tell the OS that I have a 3.5 inch 720K drive for drive b: If > there is something I am doing wrong I would appreciate any pointers. Use the command: DRIVPARM=^A^A^A/D:1/F:2 where each ^A is the Control-A character (ASCII 1).
psfales@cbnewsc.ATT.COM (Peter Fales) (06/05/89)
In article <241@syteke.UUCP>, jim@syteke.UUCP (Jim Sanchez) writes: > I know this has been hashed over before but I just started reading > this newsgroup a couple of weeks ago when I got this old PC/XT. I > installed a 720K drive(3.5 inch) with DOS 3.3 and thought I would > tell the OS about this disk via the drivparm operation in config.sys. I have (re)posted this several times before, but it is short, simple, and useful enough that I am going to post it again: --------------------- begin repost --------------------------------- From ttrdc!att!rutgers!apple!bbn!csd4.milw.wisc.edu!bionet!agate!ucbvax!decwrl!sun!pitstop!sundc!seismo!uunet!mcvax!ukc!harrier.ukc.ac.uk!rde Mon Feb 27 04:25:16 1989 Path: ttrde!ttrdc!att!rutgers!apple!bbn!csd4.milw.wisc.edu!bionet!agate!ucbvax!decwrl!sun!pitstop!sundc!seismo!uunet!mcvax!ukc!harrier.ukc.ac.uk!rde From: rde@ukc.ac.uk (R.D.Eager) Newsgroups: comp.sys.ibm.pc Subject: Re: DRIVPARM config.sys variable - how do I access it? Keywords: PC-DOS 3.30,DRIVPARM,config.sys Message-ID: <238@harrier.ukc.ac.uk> Date: 27 Feb 89 10:25:16 GMT References: <606@infovax.lan.informatik.tu-muenchen.dbp.de> Reply-To: rde@ukc.ac.uk (R.D.Eager) Organization: Computing Lab, University of Kent at Canterbury, UK. Lines: 18 I did post this before, but I fear it got lost.... There is a simple way of making DRIVPARM work, at least on PC-DOS 3.3 (I have tried it and it works). It is *extremely* baroque, but who cares? Place three control-A characters (yes, the ASCII value 1) into the line after the DRIVPARM= bit, before the parameters. If we represent CONTROL-A as ^A, the line might look like this: DRIVPARM=^A^A^A/D:n /F:n ... etc I don't know why it works, but it sure does! -- Bob Eager rde@ukc.UUCP ...!mcvax!ukc!rde Phone: +44 227 764000 ext 7589 -- Peter Fales AT&T, Room 5B-420 2000 N. Naperville Rd. UUCP: ...att!ihlpb!psfales Naperville, IL 60566 Domain: psfales@ihlpb.att.com work: (312) 979-8031