🚀 go-pugleaf

In article <4a4v4j$1n8p@tako.info.ucla.edu>,
Steve Andres <steven@ucla.edu> wrote:
>Does anyone have a command line FDISK substitue?  I'm trying to write a 
>workstation rebuild utility for a computer lab and it needs to run a batch file 
>that will delete and recreate the partition, format it, and unzip a file.
Just a thought. Create a file with all of the necessary keystrokes,
for example, to view information under DOS 5.0 fdisk you need to hit
4 and then the enter key.  When you are done viewing the information,
you need to hit ESC twice.  Create a file KEYS and put '4<CR><ESC><ESC>'
without the quotes into it.  Then redirect the file to FDISK like:

fdisk <keys

good luck,

don
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Don and Sue Jones       |   If debugging is the process of removing errors,
djones@max.tiac.net     |   Then programming is the process of putting them in.

In <4a57ik$ho5@sundog.tiac.net> djones@tiac.net (Don Jones) writes:

>In article <4a4v4j$1n8p@tako.info.ucla.edu>,
>Steve Andres <steven@ucla.edu> wrote:
>>Does anyone have a command line FDISK substitue?  I'm trying to write a 
>>workstation rebuild utility for a computer lab and it needs to run a batch file 
>>that will delete and recreate the partition, format it, and unzip a file.

>Just a thought. Create a file with all of the necessary keystrokes,
>for example, to view information under DOS 5.0 fdisk you need to hit
>4 and then the enter key.  When you are done viewing the information,
>you need to hit ESC twice.  Create a file KEYS and put '4<CR><ESC><ESC>'
>without the quotes into it.  Then redirect the file to FDISK like:
>
>fdisk <keys
>
>good luck,

He'll need a lot of good luck because FDISK (the DOS flavour) doesn't
look like an application getting its input from stdin :-)

Dan
--
Dan Pop
CERN, CN Division
Email: danpop@mail.cern.ch 
Mail:  CERN - PPE, Bat. 31 R-004, CH-1211 Geneve 23, Switzerland

In article <4a4v4j$1n8p@tako.info.ucla.edu>, steven@ucla.edu says...
>
>Does anyone have a command line FDISK substitue?  I'm trying to write a 
>workstation rebuild utility for a computer lab and it needs to run a batch 
file 
>that will delete and recreate the partition, format it, and unzip a file.
>
>The formatting and unzipping I can take care of, but since FDISK requires 
user 
>input, that part can't be automated.  Thus, the user (usually ignorant to 
the 
>intricacies of FDISK) must delte and recreate the partition.
>
   This is totally off-topic for comp.lang.C++.
   But .... Couple of years ago 
I had exactly the same problem. My solution was: throw away FDISK, but make 
a program which write phisical boot sector (using BIOS level), replace
autoexec.bat and reboot. After reboot - rut format e.t.c.



>Any information would be appreciated either posted here or sent to 
>steven@ucla.edu.  Thanks.
>
>

-- 
---------------------------------------------------------------
Michael Furman,                       (603)893-1109
Geophysical Survey Systems, Inc.  fax:(603)889-3984
13 Klein Drive - P.O. Box 97          engr@gssi.mv.com 
North Salem, NH 03073-0097            71543.1334@compuserve.com
---------------------------------------------------------------

steven@ucla.edu (Steve Andres) wrote:
>Does anyone have a command line FDISK substitue?  I'm trying to write a 
>workstation rebuild utility for a computer lab and it needs to run a batch file 
>that will delete and recreate the partition, format it, and unzip a file.
>
>The formatting and unzipping I can take care of, but since FDISK requires user 
>input, that part can't be automated.  Thus, the user (usually ignorant to the 
>intricacies of FDISK) must delte and recreate the partition.

Keep in mind, also, that batch file lines are read as they are executed, so make 
sure your batch file isn't on the partition being deleted. :)

-- 
John Ayo
Engineering LAN Admin., Laitram Corp.

steven@ucla.edu (Steve Andres) wrote:

>Does anyone have a command line FDISK substitue?  I'm trying to write a 
>workstation rebuild utility for a computer lab and it needs to run a batch file 
>that will delete and recreate the partition, format it, and unzip a file.

>The formatting and unzipping I can take care of, but since FDISK requires user 
>input, that part can't be automated.  Thus, the user (usually ignorant to the 
>intricacies of FDISK) must delte and recreate the partition.

If fdisk will be taking the same commands each time you run it then
you could probably get round your problem like this:

1.  Create a text file (commands.txt) and put into it all the commands
that you would have to type into fdisk by hand exactly as you would
type them, for example

3
1
etc

Don't forget to include all the return characters and escape
characters that you need.

2.  Run call fdisk from your command prompt using:

	fdisk < commands.txt

to run fdisk but take input to the program from the file called
commands.txt

That should do it for you.

Hope I was of some help.

Andrew Castles