Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!husc6!ut-sally!ut-ngp!ayac071
From: ayac071@ut-ngp.UUCP (William T. Douglass)
Newsgroups: comp.lang.pascal,comp.sys.ibm.pc
Subject: Re: "Documented" MS-DOS stuff
Message-ID: <5794@ut-ngp.UUCP>
Date: Mon, 3-Aug-87 21:06:54 EDT
Article-I.D.: ut-ngp.5794
Posted: Mon Aug  3 21:06:54 1987
Date-Received: Tue, 4-Aug-87 06:35:33 EDT
References: <151@ivory.SanDiego.NCR.COM> <1690@bellcore.bellcore.com> <1013@vi.ri.cmu.edu> <1080@bucsb.bu.edu.UUCP>
Reply-To: ayac071@ngp.UUCP (Bill Douglass)
Distribution: na
Organization: UTexas Computation Center, Austin, Texas
Lines: 20
Summary: FORMAT does depend on FCB's
Xref: mnetor comp.lang.pascal:236 comp.sys.ibm.pc:6313

>FORMAT will not work even with the space problem fixed.  Does anyone know
>what they did when they made FORMAT?  I'd be very, very interested in
>knowing.  I pass each program a perfect match for the command line and
>also a good FCB if possible.  My FCB building routines fail in some
>circumstances, but so do DOS's (although in a different manner) so I
>don't worry about it.  It gets a perfect environment, too.  Yet it
>gives me an "invalid parameter" error whenever I try to run FORMAT.


I would suspect the FCB's.  My working with EXEC and format indicated
that the FORMAT command does indeed pull its parameters from the FCB
that DOS sets up before executing the program.  If there is a bug in
your FCB routine, that could kill the program right there.

I set up my call to EXEC to parse the FCB with the relevent DOS call
(don't have the function # right now), but will be glad to e-mail the
whole program to you if interested.

Bill Douglass
ayac071@ngp.UUCP