boot up screen has c: c:
Stu Wilson
As my computer boots up I see this
c:
c:
at one point. I assume that it does'nt need to be there. Is there a
way to get rid of it?
--
Stu Wilson
Liverpool NY
My homepage:
http://home.att.net/~stuwilson/
Bob B.
>From: Stu Wilson stuw...@worldnet.att.net
Edit both config.sys and autoexec.bat. If they are empty hold the shift key
down, then press the END key. Keep holding the shift key and press and hold the
arrow down key. Wherever it stops hit the del key.
If they are not empty, place your cursor directly under the last line and do
the same thing as above. Often simple carriage returns, (can't see 'em), will
give you are series of C:'s.
>Here is a trivial question.
>As my computer boots up I see this
>c:
>c:
>at one point. I assume that it does'nt need to be there. Is there a
>way to get rid of it?
>
>--
>Stu Wilson
Bob
Please reply to the newsgroup.
croak
lines in your autoexec.bat file.
have a nice day
croak
"Stu Wilson" <stuw...@worldnet.att.net> wrote in message
news:38413153...@worldnet.att.net...
> Here is a trivial question.
> As my computer boots up I see this
> c:
> c:
> at one point. I assume that it does'nt need to be there. Is there a
> way to get rid of it?
>
> --
> Stu Wilson
Ken Blake
news:38413153...@worldnet.att.net...
> Here is a trivial question.
> As my computer boots up I see this
> c:
> c:
> at one point. I assume that it does'nt need to be there.
Is there a
> way to get rid of it?
There is probably a blank line in autoexec.bat. Delete it.
--
Ken Blake
Stu Wilson
There are no blank lines. There are three lines that start with @.
There are no blank lines at the end.
Plato
>
> Here is a trivial question.
> As my computer boots up I see this
> c:
> c:
> at one point. I assume that it does'nt need to be there. Is there a
> way to get rid of it?
try adding the line
@echo off
at the beginning of your autoexec.bat file in c:\_
Stu Wilson
@echo off is my third line. Should I move it to first in line?
AFTech
to turn the autoexec.bat output off after it has already output. :)
--
The Klingon Approach to Programming:
"What is this talk of 'release'? Klingons do not make software
'releases'. Our software 'escapes' leaving a bloody trail of designers and
quality assurance people in its wake."
--|AFTech|-- AFTec...@leading.net (cut -IT- out to e-mail)
Stu Wilson <stuw...@worldnet.att.net> wrote in message
news:3841AEF2...@worldnet.att.net...
Plato
>
> @echo off is my third line. Should I move it to first in line?
it should always be the first line really ...
Art
at the beginning of any
line in your autoexec.bat means "echo off" for that line only. The command
"echo off" means the same for any following commands. "echo off" simply
means that the commands won't be printed, or "echoed" to the screen
while they're being performed. Sometimes, however, this is good info to
see. Thats up to you. You can put
@echo off any place you want, or not at all.
The placement of "@echo off" shouldn't effect your original problem though.
You probably have an
extra CR LF (carriage return, line-feed), at the end of your autoexec.bat
file. This won't show up in the
editor window. It also doesn't hurt anything. If you want to get rid of it
though, try going into "sysedit" from the
START>RUN menu. Just place your cursor at the end of the last line and hit
"Delete" several times. That
should clear it up.
Art.
PCForrest
batch file - it's very rare that you'd want to see each command
being echoed to the screen.
The @ at the beginning of a line implies that command echoing be
turned off for that line only, so you can remove all others that follow
an @ECHO OFF. The reason it has an @ is so it doesn't echo itself
before turning off command echoing.
Command output will still be seen, however, which in most cases is
a good thing. However, you can disable command output for individual
lines by tagging " > nul" (no quotes) to the end of a line.
For more information on disabling command echoing and output:
http://www.pcforrest.co.uk/@echo_off.htm
--
Peter C Forrest
www.PCForrest.co.uk
"Stu Wilson" <stuw...@worldnet.att.net> wrote in message news:3841AEF2...@worldnet.att.net...
> Plato wrote:
>
> > Stu Wilson wrote:
> > >
> > > Here is a trivial question.
> > > As my computer boots up I see this
> > > c:
> > > c:
> > > at one point. I assume that it does'nt need to be there. Is there a
> > > way to get rid of it?
> >
> > try adding the line
> > @echo off
> > at the beginning of your autoexec.bat file in c:\_
>
> @echo off is my third line. Should I move it to first in line?
>
>
PCForrest
"Trent" <trent...@hotmail.com> wrote in message news:384d02e8...@news.corecomm.net...
> When the commands get processed in the autoexec.bat file, the success
> or failure is presented on the screen by default. If you don't want
> to see the results, placing "echo off" as a line in the autoexec will
> prevents all subsequent lines from displaying on the screen.
Rubbish! This only blocks command echoing, not command output.
Ken Blake
news:81stig$kb6$1...@news7.svr.pol.co.uk...
> @ECHO OFF should always be the first command in any
> batch file - it's very rare that you'd want to see each
command
> being echoed to the screen.
>
> The @ at the beginning of a line implies that command
echoing be
> turned off for that line only, so you can remove all
others that follow
> an @ECHO OFF. The reason it has an @ is so it doesn't echo
itself
> before turning off command echoing.
>
> Command output will still be seen, however, which in most
cases is
> a good thing. However, you can disable command output for
individual
> lines by tagging " > nul" (no quotes) to the end of a
line.
With some trepidation, let me add the following, primarily
for the sake of completeness:
You can turn off all command output (all output of any
kind), not just for individual lines, but for all subsequent
lines in a batch file by using the CTTY command, such as
CTTY NUL
You then need to turn it on again at the end of the batch
file with
CTTY CON
I say "with some trepidation" because this command shouldn't
be used by the faint of heart. Failure to issue the CTTY CON
command presents the need to reboot to get any display back
on the monitor.
PCForrest
"Trent" <trent...@hotmail.com> wrote in message news:38436f9...@news.corecomm.net...
>
> Would the paging blocks still be 4k if I have 16k clusters?
Yes.
PCForrest
"Trent" <trent...@hotmail.com> wrote in message news:38426ee...@news.corecomm.net...
> On Mon, 29 Nov 1999 10:03:46 -0000, "PCForrest" <nob...@home.co.uk>
> wrote:
>
> >
> >"Trent" <trent...@hotmail.com> wrote in message news:384d02e8...@news.corecomm.net...
> >> When the commands get processed in the autoexec.bat file, the success
> >> or failure is presented on the screen by default. If you don't want
> >> to see the results, placing "echo off" as a line in the autoexec will
> >> prevents all subsequent lines from displaying on the screen.
> >
> >Rubbish! This only blocks command echoing, not command output.
>
>
> How did I get out of your kill file?
>
You didn't.
Ken Blake
> On Mon, 29 Nov 1999 09:15:44 -0700, "Ken Blake"
<nob...@home.com>
> wrote:
>
> >With some trepidation, let me add the following,
primarily
> >for the sake of completeness:
> >
> >You can turn off all command output (all output of any
> >kind), not just for individual lines, but for all
subsequent
> >lines in a batch file by using the CTTY command, such as
> >
> > CTTY NUL
> >
> >You then need to turn it on again at the end of the batch
> >file with
> >
> > CTTY CON
> >
> >I say "with some trepidation" because this command
shouldn't
> >be used by the faint of heart. Failure to issue the CTTY
CON
> >command presents the need to reboot to get any display
back
> >on the monitor.
>
> Have you ever used this command in an autoexec batch file?
Yes, but years ago.
> I've never used it...but the syntax doesn't list NUL as
one of the
> valid devices.
Yes, I see that now myself. I *think* it doesn't matter what
you redirect the output to, but maybe I'm wrong and didn't
use NUL. Possibly I sent it someplace like COM1, which would
effectively throw it away.
> How does this work?...since the command also changes the
INPUT device.
> Would the monitor go completely blank?
I can't remember whether it blanks the monitor or just
caused any following lines not to display. I *think* the
latter, but I'm not sure.
It's probably close to ten years since I've done this, so my
memory is hazy on the details.
Again, I don't really recommend that anyone do this. I
mentioned it more as a matter of academic interest than
anything else.
If you want to play with the idea, the safest way to do it
is probably to make a boot floppy with an autoexec.bat
containing these commands.