Rohit wrote:
>
> [EMAIL PROTECTED] wrote:
> > on dos prompt, giving -
> > c:\> command
> > brings a child shell and does nothing.
>
that's what its supposed to do.
> Right. Wonder why it does not call autoexec.bat?
It's not supposed to call autoexec.bat each time command.com is run.
only when the machine is booted is autoexec.bat called.
>
> > giving -
> > c:\>command c:\autoexec.bat
> > gives message: "specified COMMAND search directory bad" and does
> > nothing.
>
your path is invalid ?
> What does that mean? That you probably wish to execute command.com from
> c:\autoexec.bat which is a nonexistent directory. Probably it is taking
> the second argument as directory. What is your conclusion?
C:\>command /?
Starts a new instance of the MS-DOS command interpreter.
COMMAND [[drive:]path] [device] [/E:nnnnn] [/P] [/C string] [/MSG]
[drive:]path Specifies the directory containing COMMAND.COM file.
device Specifies the device to use for command input and
output.
/E:nnnnn Sets the initial environment size to nnnnn bytes.
/P Makes the new command interpreter permanent (can't
exit).
/C string Carries out the command specified by string, and then
stops.
/MSG Specifies that all error messages be stored in memory.
You
need to specify /P with this switch.
>
> > the PROMPT string also disappeared in this new child, giving prompt as:
> > c>
>
> Right. echo prompt to find out that the value is not set.
>
> > on giving -
> > c> set
> > PATH=
> > single env variable PATH appears which itself is empty.
>
> Because you are SETTING IT. If it did not appear empty that way, I would
> consider this a bug in DOS 6.22, my favourite O/S before I installed
> Linux on my PC.
>
> If you want to see your path echoed on DOS prompt, do
>
> prompt=$p$g$s
>
> to get
>
> c:\windows> [one space]
>
> > > [Autoexec is invoked the first time the shell is launched]
> > meaning command.com does invoke it.
>
> You seem to be hell bent upon linking invoking of autoexec.bat by
> command.com and nothing else. Who knows, you might even be right
> but try and look for the answer in a logical fashion. The DOS kernel
> is actually made up of three files. MSDOS.SYS, IO.SYS and COMMAND.COM.
> As of I know, command.com is the last one to be loaded and it may
> even be needed by the executions in autoexec.bat but why do you
> abhor the idea that command.com is loaded at bootup and that
> autoexec.bat
> is called at bootup, may have been all doings of some other file?
> Like MSDOS.SYS? Or some environment variable would be set at bootup?
>
> Let us admit that we do not know for sure, alright? Or explain why
> each command.com does not fire execution of autoexec.bat? Or what
> calls the autoexec.bat at startup - probably some file which is loaded
> only once in memory at startup..l msdos.sys? io.sys? Or something else?
>
> You tell me.
msdos.sys in windows is a txt file. msdos.sys in dos was a real file. I
guess it's msdos.sys job to load command.com and execute autoexec.bat.
Cheerio
Robin
>
> Rohit
> >
> > regards
> > -vulcan
> >
> > -----------------------------------------------------------------------
> > For more information on the LIH mailing list see:
> > http://lists.linux-india.org/lists/LIH
>
> -----------------------------------------------------------------------
> For information on this and other Linux India mailing lists check out
> http://lists.linux-india.org/
--
_END_
Robin S Chatterjee Yahoo pager ID -Robinchatterjee
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
FAX 1-(815)550-6171
Robin's Poetry Pages
http://www.geocities.com/singerosongs
Robin's Perl Pages
http://www.geocities.com/robinchatterjee
-----------------------------------------------------------------------
Check out the 'What to do before posting to the list' site
for a list of things to try before posting. The site is
at http://botsie.tripod.com/beforeposting/
