|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
[ More Info ]
chkdsk /f on all drives in the system,
I started an image backup of a Windows Small Business Server (SBS) 2003 system
from a Norton Ghost 2003 boot CD. I was attempting to backup an internal
IDE drive to a double-layer DVD in the system's internal DVD writer.
When I attempted to backup drive C (the second partition to a double-layer DVD,
I got a "File Name ? (546)" error message. The backup aborted shortly after
it started with the current file being backed up listed as "0 $MFT".
When I hit enter for "OK", I then received the following error message:
Internal Error 36000
An internal inconsistency has been detected
If this problem persists, contact Symantec Technical Support
at http://service.symantec.com
[ OK ]
When I hit enter, I saw the following:
ABORT: 12020, Write to CD/DVD disc failed ABORT: 36000, A generalException occurred
ghost -fni instead, as suggested
by
How to troubleshoot the error: "Internal error 36000 . . . ".
I then proceeded with the backup of the second partition, excactly as before.
This time the backup completed succcessfully.
I found a script posted on TechRepublic at CPU Utilization Script1. I modified the script so that I could specify the time interval between CPU utilization checks through an argument to the script when it is run. The modified script is available at CPU_Use.vbs 2.
The script can be run with csript /nologo CPU_Use.vbs or
alternatively cscript /nologo CPU_Use num where "num" is the
number of seconds to wait between CPU checks, e.g. csript /nologo CPU_Use
300 to check every 5 minutes.
The output is placed in C:\Processor.log; the output location can
be changed by modifying the value of the strLogFile
variable in the script. Output will look similar to the following:
9/22/2007 09:43
9/22/2007 09:48 19
9/22/2007 09:53 17
9/22/2007 09:58 17
9/22/2007 10:03 35
9/22/2007 10:08 14
9/22/2007 10:13 15The first two columns list the date and time the script was run while the third lists the CPU utilization at the time the script was executed. There is no value for CPU utilization for the first entry in the log.
The script requires Windows XP or later. It will not run on Windows 2000.
If it is run on Windows 2000, you will see
CPU_Use.vbs(48, 1) Microsoft VBScript runtime error: ActiveX component
can't create object: 'WbemScripting.Swbemrefresher'
3, 4
Most of the systems I support are Windows XP systems, so the script will still be useful to me, but I can't check the system I wanted to check in this case, since that system is a Windows 2000 system.
References:
