Error - template LAYOUT-DATA-WRAPPER not found

A configuration error was detected in the CGI script; the LAYOUT-DATA-WRAPPER template could not be found.

Error - template STYLE-SHEET not found

A configuration error was detected in the CGI script; the STYLE-SHEET template could not be found.

Error - template SUB-TOP-BANNER not found

A configuration error was detected in the CGI script; the SUB-TOP-BANNER template could not be found.
Subject:
From:
Peter Shkabara <[log in to unmask]>
Reply To:
PCSOFT - Personal Computer software discussion list <[log in to unmask]>
Date:
Mon, 8 Oct 2001 08:22:03 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (34 lines)
The reason to go directly to C: is to speed the boot process. If the A: and
CD-ROM are included in the boot order first, then those devices are tested
if they are indeed set for boot before the boot process starts. Setting C:
as the first boot device will save you a few seconds each time that you
start your computer. Another reason is that if you inadvertently leave a
floppy or CD in your computer, the boot will still work without having to
stop and remove the floppy or CD. I realize that the CD boot often requires
operator intervention to ENABLE it so the only penalty is lost time in the
scan.

Peter

Peter Shkabara, P.E.
____________________________
Computer Science Instructor
Columbia College - Sonora, CA
209 588-5156
[log in to unmask]
http://gocolumbia.org/pesh

-----Original Message-----
A student brought up that almost always--now--software comes on cd
roms.  He showed everyone how to change the boot order to a:/cd rom/ c:.

Is there a reason someone would want to go directly to c: and if so, how
could
the user get into the computer again (if crashed) if a: isn't first?

Thanks,  Brenda

             PCSOFT maintains many useful files for download
                     visit our download web page at:
                  http://freepctech.com/downloads.shtml

ATOM RSS1 RSS2

LISTSERV.ICORS.ORG Secured by F-Secure Anti-Virus CataList Email List Search Powered by LISTSERV