From: <cpt.kirk@1tree.net>
To: speakup@braille.uwo.ca
Subject: Re: vmware
Date: Thu, 30 Mar 2000 09:39:48 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.10.10003300935290.1423-100000@rocky> (raw)
In-Reply-To: <036701bf9a5b$9fffb4e0$b58cb683@hq.nasa.gov>
You can specify a script. In fact here is how it works (if memory serves
correct). If there is no script given on the commend line then setup looks
in the current directory for msbatch.inf. If that is found it uses it. If
it is not found, then it will proceed with default. If an inf file is
specified but not found then you will get an error and you must restart
setup. It is not capable of recovering that.
I don't wish to spend all my time answering Windows questions, but I can
(And will) assist with the occasional problem. I just wish I knew as much
in Linux as I do in Windows.
Kirk Wood
Cpt.Kirk@1tree.net
------------------
Your fly might be open (but don't check it just now).
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
vmware Scott Howell
` vmware Geoff Shang
` vmware Scott Howell
` vmware Kerry Hoath
` vmware scott howell
` vmware Bart Bunting
` vmware John Covici
` vmware Kris Van Hees
` vmware cpt.kirk
` vmware Scott Howell
` cpt.kirk [this message]
` vmware Count Zero
` vmware Victor Tsaran
` vmware Scott Howell
` vmware Bart Bunting
` vmware John Covici
` vmware scott howell
` vmware John Covici
` vmware scott howell
vmware Sergey Fleytin
vmware Dawes, Stephen
VmWare Zachary Kline
` VmWare Gregory Nowak
` VmWare Alex Snow
` VmWare Zachary Kline
` VmWare Gregory Nowak
` VmWare Tyler Spivey
` VmWare Zachary Kline
` VmWare Brent Harding
` VmWare Zachary Kline
` VmWare Alex Snow
` VmWare Doug Smith
` VmWare Christopher Moore
` VmWare Alex Snow
` VmWare Doug Smith
` VmWare Jeremy
` VmWare Alex Snow
` VmWare Brent Harding
` VmWare Ricky Enger
` VmWare Zachary Kline
` VmWare Brent Harding
` VmWare Alex Snow
` VmWare Gregory Nowak
` VmWare Alex Snow
` VmWare Jeremy
` VmWare Brent Harding
VmWare Jeremy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.10.10003300935290.1423-100000@rocky \
--to=cpt.kirk@1tree.net \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).