04-22-2001
The reason is your computer forgets its CMOS settings. During the boot-up process or POST (Power-On Self Test) a checksum is generated by the BIOS from the CMOS and compared to the one saved the last time the CMOS Setup was run or the BIOS defaults were loaded. If the two numbers don't agree it is an indication that the data in the CMOS has been corrupted. and a checksum error is issued by the BIOS.
Reason:
A bad battery.
A battery that has become discharged (the computer has been off a very long time).
A disconnected battery.
Static electricity.
Grounding the CMOS circuitry.
A bad motherboard.
A bad real-time clock.
A simple solution you can try:
change the CMOS battery.
Write down all of the settings from the various setup menus.
Power off your PC.
Open the case and locate the battery on the motherboard.
Obtain a replacement battery from a local or online computer parts dealer.
Remove the old battery and replace it with the new one.
Replace the case and power on the PC.
Enter your PC's setup mode.
Reenter the settings you have written down from the various setup menus.
HTH
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Let me explain my problem, I have a file in the following format
9602622 - User ID
01 -2 - Question number & Grade
02 - 3
03 - 7
04 - 12
05 - 9
06 - 0
9601664 - User ID
01 -2
02 - 3
03 - 7
04 - 12
05 - 9
06 - 0
I need to change the file so it looks like this
9601664 54 -... (1 Reply)
Discussion started by: Captain Woods
1 Replies
2. Windows & DOS: Issues & Discussions
I have a UNIX server w/an Adaptec aha-2740 card and i keep getting this error during post: EISA CMOS checksum error. It then tries to boot from the floppy. Upon researching this problem i found that it could be one of two things. Either it is the battery on the m/b (which i have all but ruled out),... (3 Replies)
Discussion started by: dlee35
3 Replies
3. UNIX for Dummies Questions & Answers
I wish to seach a Dir for a specific file, once the file is found i will perform additional logic. If the file is not found within two hours, i would like to exit.
Logically, I'm looking for the best way to approach this
Thanks for any assistance in advance.
Note: I'm using a C shell and... (2 Replies)
Discussion started by: mmarsh
2 Replies
4. Solaris
Hello Guys,
and good day to everybody.
I am battling to redirect console on this V20Z 'beast', and would really like to know if it's possible to 'see' CMOS settings from Solaris10 point of view.
Machine is remote and I can't easily go and reboot the box and press F2 etc...
So is there a... (3 Replies)
Discussion started by: mponjevic
3 Replies
5. UNIX for Advanced & Expert Users
Advance Thanks.
(1) I would like to know any unix/Linux command to check EOF char in a file.
(2) Or Any way I can check a file has been reached completely at machine B from machine A. Note that machine A ftp/scp the file to machine B at unknown time. (5 Replies)
Discussion started by: alexalex1
5 Replies
6. Shell Programming and Scripting
Hello everyone,
I am looking to basically creating md5sum files for all iso files in a directory and archive the resulting md5 files into a single archive in that very same directory.
I worked out a clumsy solution such as:
#find files for which md5sum are to be created and store the... (1 Reply)
Discussion started by: SurfTranquille
1 Replies
7. Shell Programming and Scripting
Hi Experts,
I am checking how to get day in Perl.
If it is “Monday” I need to process…below is the pseudo code.
Can you please prove the code for below condition.
if (today=="Monday" )
{
while (current_time LESS THAN 9:01 AM)
... (1 Reply)
Discussion started by: ajaypatil_am
1 Replies
8. UNIX for Dummies Questions & Answers
I'm looking for a script that sums the contents of a folder,
When you give a parameter to the script , i want to know the size of the directory, the number of files, number of folders,
These are commands that I have already found
du -s
find . -type f | wc -l
find . -type d | wc -ly
... (19 Replies)
Discussion started by: Roggy
19 Replies
9. UNIX for Dummies Questions & Answers
Hi Experts,
Please help with the following.
I have 3 columns in File 1 , variables with values nested within groups.
File 1
gr1 var1 a
gr1 var2 b
gr1 var3 a
gr1 var4 c
gr2 var1 a
gr2 var2 a
gr2 var4 c
gr3 var1 b
gr3 var3 b
gr3 var4 a
gr3 var5 a (3 Replies)
Discussion started by: ritakadm
3 Replies
LEARN ABOUT OPENDARWIN
queuedefs
queuedefs(4) File Formats queuedefs(4)
NAME
queuedefs - queue description file for at, batch, and cron
SYNOPSIS
/etc/cron.d/queuedefs
DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue.
The format of the lines are as follows:
q.[njobj][nicen][nwaitw]
The fields in this line are:
q The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs started by batch (see
at(1)); c is the default queue for jobs run from a crontab(1) file.
njob The maximum number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first
njob jobs will be run, and the others will be run as jobs that are currently running terminate. The default value is 100.
nice The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user. The default value is 2.
nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that job's
queue, or because the system-wide limit of jobs executing has been reached. The default value is 60.
Lines beginning with # are comments, and are ignored.
EXAMPLES
Example 1: A sample file.
#
#
a.4j1n
b.2j2n90w
This file specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value
of 1. As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying
again to run it.
The b queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2. If a job
cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All other queues can
have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs
are running cron will wait 60 seconds before trying again to run it.
FILES
/etc/cron.d/queuedefs queue description file for at, batch, and cron.
SEE ALSO
at(1), crontab(1), nice(1), cron(1M)
SunOS 5.10 1 Mar 1994 queuedefs(4)