booting straight to 3.1

[johnnycam]

Anybody know the trick in booting straight into 3.1 without having to type in "win" at the dos prompt?
The system is running fine...just would like to get 3.1 a little quicker!....thanks in advance!!,john

[kjanx]

boot to c:
type in
c:\edit autoexec.bat

below the last line, type in

c:\cd windows
win

in that order, just like i typed it

[Vernon Frazee]

Originally posted by kjanx
boot to c:
type in
c:\edit autoexec.bat

below the last line, type in

c:\cd windows
win

in that order, just like i typed it

Almost, but not quite. If they type those three commands exactly as you told them to, at least two will generate "Bad command or file name" error messages.



With a default setup of MS-DOS and Windows 3.x, the command to EDIT your C:\AUTOEXEC.BAT file would be:

• edit c:\autoexec.bat

Then add the following three lines to the end of the file:

• c:
  cd\windows
  win

Save your changes ([Alt-F][S]), exit ([Alt-F][X]), and reboot ([Ctrl-Alt-Del]).

[kjanx]

balony vernon.
i just set an old 3.1 yesterday using my commands.


i know i'm old, but the dirt pile hasn't come yet.

you need to quit interfering with other posts. post your info, leave me out of it.

i've never bothered your posts.

i don't need it.

[AlaricD]

Not to stir up the hornets' nest, but I have to side with Vernon on this. Not because he is a moderator, but because he is correct.

Originally posted by kjanx
boot to c:
type in
c:\edit autoexec.bat

below the last line, type in

c:\cd windows
win

in that order, just like i typed it

Your instruction to the johnnycam was to type in c:\edit autoexec.bat. Unless the file edit.com is actually in the root of C:, you will receive the message "Bad command or filename." Your instruction also assumes that this command is being issued with C:\ being the working directory, or else edit.com will attempt to create or modify autoexec.bat in the directory you are in. If you happen to be in the \windows directory, it will create a new autoexec.bat there.

In the second part of your instructions, you tell johnnycam to add the lines:

c:\cd windows
win

to autoexec.bat. cd is a DOS internal command, therefore, specifying a path to it will not work. This again will result in a "Bad command or filename".

Before you tell me that I'm wrong, refer to the Vernon Frazee's images he posted, showing what happens when he followed your explicit instructions. I could post similar screenshots, but the facts have already been presented.

[kjanx]

i didn't say vernon was wrong.
he said i was wrong.

again i say balony, i've been setting those 3.1 commands for many years, hundreds of them, those commands work, i just did one yesterday, works great!!!

end of converstion. you nutbrains have no respect for other people/posters, or expertise that can do things you can't.

adios

[Nix]

There maybe some confusion:

If edit autoexec.bat is typed at c:\>, it would look like c:\>edit autoexec.bat but you're only typing in the latter part and not the c:\> part.

Thus you get into edit and autoexec.bat is in c:\ so by default you open it if it's there.

Then even though the command c:\ cd windows will return an error, the path is probably already set up in your autoexec.bat somewhere eg SET PATH=C:\;C:\WINDOWS;C:\WINDOWS\COMMAND, so that when the Win command is executed it still boots despite the error which is non consequential.

Vernon has posted evidence to justify his arguments, you can either do the same or refrain from becoming abusive and inflammatory.

As for accusing Vernon of things he "can't" do - when it comes to DOS commands he is the guru - he's not an MS MVP for nothing.

[Nix]

And no I'm not a moderator coming to the defence of the other moderators.

I'm just a member like everyone else, trying to help others when and where I can.

Knowing where my limitations are and when to accepot advice gracefully and admit when I'm wrong.

[Nix]

And if you've got the @echo off command in the beginning of your autoexec.bat then you will never see the error message generated when the c:\ cd windows command is run so that's why you think it's all working ok.

[Vernon Frazee]

When you type:

• c:\any_command

you are instructing COMMAND.COM to:

1. ignore all of its internal commands
   
   and
   
2. only look in the root directory ("\") of drive "C:"

for your "any_command" program or batch file.

Therefore, if the following three files:

• c:\any_command.com
  c:\any_command.exe
  c:\any_command.bat

do not exist, COMMAND.COM will return the infamous "Bad command or file name" error message.

Avoiding this dilemma in simple. Unless you know for a fact that your
"any_command" program or batch file actually exists in "c:\", do not prepend your command with a "c:\".

Now COMMAND.COM will be free to check and see if:

1. your "any_command" is an internal command
   
2. the files "any_command.com", "any_command.exe" or "any_command.bat" exist in your current directory
   
3. the files "any_command.com", "any_command.exe" or "any_command.bat" exist in any directory in your PATH

[Vernon Frazee]

Originally posted by kjanx

you need to quit interfering with other posts. post your info, leave me out of it.

i've never bothered your posts.

i don't need it.

--

end of converstion. you nutbrains have no respect for other people/posters, or expertise that can do things you can't.

adios

As a Moderator it is my job to "interfere". Our Acceptable Use Policy (AUP) states, in part:

By using these Forums, you agree to the following:

• You will not post any material that is knowingly false, misleading, or inaccurate.
  
• You will not behave in an abusive and/or hateful manner, and will not harrass, threaten, nor attack anyone.
  
• You will, if asked by a representative of the Forums, cease posting any content ...

We reserve the right to delete any message and/or restrict posting rights in our Forums for any reason whatsoever. Should you continue to post messages that violate the rules of the Forums, your account may be terminated, your access to the Forums may be banned, and your service provider(s) may be contacted about your behavior.

Please do not post inaccurate information, (specifically invalid MS-DOS commands), nor attempt to attack, (degrade, belittle, disparage), anyone.

Thank You,