Knowledge Base
Q#1:What is the difference between EVEREST Corporate Edition and EVEREST Ultimate Edition?
A#1:EVEREST Corporate Edition is for business use, targeting corporate, government and medical markets. EVEREST Ultimate Edition is for home use. EVEREST Corporate Edition includes unique features for network audit, remote control and SQL database connection. EVEREST Ultimate Edition includes unique features for benchmarking and overclocking.
Q#2:What report formats supported by EVEREST Corporate Edition and EVEREST Ultimate Edition?
A#2:EVEREST Corporate Edition supports standard text, HTML, MHTML (HTML with images), XML, CSV, MIF (for Microsoft SMS), INI reports and direct report insertion to SQL databases. EVEREST Ultimate Edition supports only standard text, HTML and MHTML report formats.
Q#3:Is it possible to create reports automatically using command-line options?
A#3:Only EVEREST Corporate Edition supports command-line options. List of them can be reviewed in main menu / Help / Command-line Options. Full list of command-line options with explanation is available in the EVEREST Manual. Using command-line options it is possible to create reports with custom layout in any of the supported report formats. Created reports can be saved to file, inserted to SQL database, sent in e-mail or uploaded to a FTP server.
Q#4:Is it possible to use EVEREST without an installation
procedure?
A#4:EVEREST is available in ZIP compressed package that can
be simply extracted to an empty folder. No installation procedure required at all.
Q#5:Is it necessary to install EVEREST on all workstations in
the network, in order to make a network audit of all networked
computers?
A#5:No distribution for EVEREST files is necessary, and also
it's not recommended at all. Instead, EVEREST files can be copied to a file server into a
shared folder that would provide access to EVEREST files to all network users. EVEREST
then can be launched from any computers using a shortcut like:
\\server\share\everestfolder\everest.exe
As a further step, the command-line could be extended with network audit options,
and then it could be added to the users logon script that would be executed at the
logon of each network user.
Example:
\\server\share\everestfolder\everest.exe /R
\\server\share\reportsfolder\$HOSTNAME /AUDIT /CSV /SAFE /SILENT
Full list of command-line options with explanation is available in the EVEREST
Manual.
Q#6:Is it possible to remove debug information from
reports?
A#6:The options to enable/disable debug information, report
header, report footer are available in main menu / File / Preferences /
Report.
Q#7:By using either the
main menu / Remote / Connect to Remote Computer,
main menu / Remote / Monitor Remote Computers or
main menu / Report / Remote Report Wizard
feature, EVEREST fails to connect to the remote computer(s) with
"Error 10061: Connection refused" error message. How to solve this?
A#7:It is not possible to connect to remote computer(s)
without running EVEREST on both the local and the remote computer(s). Installation
procedure is not mandatory, but at least EVEREST should be automatically launched from
the users logon script using a command-line like:
\\server\share\everestfolder\everest.exe /ACCEPTBG /SAFE /SILENT
The /ACCEPTBG command-line option automatically enables the main
menu / Remote / Accept Incoming Remote Connections feature that will enable the
connections from remote computers. Full list of command-line options with explanation
is available in the EVEREST Manual.
Q#8:EVEREST seems to lock up (or cause BSoD) on a couple of computers during the
network audit process. How to avoid the crash?
A#8:The /SAFE command-line option could be used to disable
several of EVEREST low-level features -- in most cases this could eliminate all
issues. Alternatively the /SAFEST command-line option could be used to completely
disable all EVEREST low-level features.
Q#9:Is it possible to change the delimiter character of CSV reports from comma to
another character?
A#9:It is not possible with EVEREST.
Q#10:Is it possible to use a single command-line to both create a report using
/R, /E or /FTPUPLOAD command-line option and to start EVEREST in remote connections
accept mode using /ACCEPTBG option?
A#10:That is possible only using 2 command-lines. In order
to use multiple command-lines in the same script or batch file, EVEREST.EXE should be
deleted and EVEREST.BIN should be renamed to EVEREST.EXE.
Q#11:Is it possible to copy EVEREST files to a single floppy disk?
A#11:EVEREST files are too large to fit into a single
floppy disk, and there is no way to squeeze it to make it smaller.
Q#12:Is it possible to launch EVEREST from a CD-ROM disk, DVD-ROM disk or
flash drive?
A#12:It is fully supported. EVEREST files can be simply extracted from the ZIP package and burnt to a CD/DVD disk, or copied to a DVD-RAM disk or flash drive.
Q#13:Is it possible to print the created HTML or MHTML reports with EVEREST?
A#13:After the report creation process, the Print and Print
Preview features are available in the report review window.
Q#14:Why is the information provided by the Computer / DMI page inaccurate?
A#14:The reliability and accuracy of DMI information
depends on the manufacturer of the motherboard or the computer (when a brand computer).
When vendors do not take the time to fill in the DMI tables properly, all applications
reading DMI will indicate the same wrong information. This is not the fault of
EVEREST.
Q#15:Is it possible to use EVEREST on 64-bit Windows systems like AMD Athlon 64, AMD Opteron, Intel Itanium, Intel Pentium 4 EM64T or Intel Xeon EM64T?
A#15:EVEREST has full support for 64-bit IA-64 Systems (Intel Itanium, Intel Itanium 2) and for 64-bit x64 Systems (AMD Athlon 64, AMD Opteron, Intel Pentium 4 EM64T, Intel Xeon EM64T).
Q#16:Does EVEREST support Windows Vista, Windows Server 2008, Windows 7 or Windows PE?
A#16:EVEREST has full support for all current 32- and 64-bit PC Windows systems including Windows 95, Windows 98, Windows Me, Windows NT 4.0, Windows 2000, Windows XP, Windows Server 2003, Windows XP 64-Bit Edition, Windows XP x64 Edition, Windows Vista, Windows Server 2008, Windows 7 and Windows PE.
Q#17:Does EVEREST support Windows 3.1/3.11, Windows NT 3.1/3.51, Windows CE or
Windows Pocket PC?
A#17:EVEREST does not support those systems.
Q#18:Is there an EVEREST version running under DOS, Mac OS, Linux or UNIX?
A#18:EVEREST supports Microsoft Windows systems only.
Q#19:Is it possible to find out the product key of Office 97 or Office 2000?
A#19:EVEREST license module is capable of detecting product key of Office XP, Office 2003 and Office 2007 only.
Q#20:During the network audit process, some computers fail to insert reports to
the SQL database. How to fix those computers up?
A#20:In most cases the generated .ADO file contains
information about the actual issue. In the case it is about improper MDAC version, the
MDAC (Microsoft Data Access Components) should be updated to the latest version. MDAC
2.80 is available for download at:
http://download.com.com/3000-2404-10040711.html
Q#21:Is it possible to detect temperatures, voltage values and fan status of
Dell computers?
A#21:Dell computers use a proprietary sensor chip that is
undocumented and so cannot be supported by EVEREST.
Q#22:With EVEREST is it possible to gather specific information stored in the
Windows Registry, a text file, an INI file or an environment variable?
A#22:Custom Variables feature is available to do that.
It can be configured in main menu / File / Preferences /
Summary, at the bottom of the page.
Q#23:On the Motherboard / Chipset page EVEREST warns about an improper setting of AGP Aperture Size. How to change AGP Aperture settings?
A#23:AGP Aperture Size can be configured in the BIOS Setup (also known as CMOS Setup).
Q#24:Is it possible to run EVEREST completely hidden?
A#24:The /SILENT command-line option can be used to hide EVEREST icon on the System Tray (also known as Notification Area) including the bubble shown on specific events under Windows 2000/XP/2003. The /ACCEPTBG command-line option can be used to launch EVEREST hidden in the background and make it stay in the memory and wait for incoming remote connections. Full list of command-line options with explanation is available in the EVEREST Manual.
Q#25:How to determine the firmware version of optical drives and hard disk drives?
A#25:Firmware version of optical drives and SCSI hard disk drives is displayed on the Storage / ASPI page. Firmware version of ATA and SATA hard disk drives is displayed on the Storage / ATA page.
Q#26:On the Motherboard / Chipset page, the AGP rate is lower than the maximum supported, or even the AGP seems to be completely disabled. How to fix this?
A#26:It can be because motherboard chipset drivers have not yet been installed, or the AGP video card in the system is incapable of AGP texturing (e.g. 3Dfx Voodoo Banshee or Voodoo3). Or it's simply a PCI video card. To solve the driver problem, it is recommended to first install the motherboard chipset driver, and after that to install the driver for the video card.
Driver for AMD chipset based motherboards:
Driver for ATI chipset based motherboards:
Driver for Intel chipset based motherboards:
Driver for nVIDIA chipset based motherboards:
Driver for SiS chipset based motherboards:
Driver for ULi / ALi chipset based motherboards:
Driver for VIA chipset based motherboards:
Q#27:What does the "Aux" temperature shown on the Computer / Sensor page mean?
A#27:There is no standard for sensor registers layout, so
the "Aux" temperature could show the temperature of the CPU or the motherboard, or
might be a non-connected wire of the sensor chip, and so it could show a bogus
value.
Q#28:What does the "CPU Diode" temperature shown on the Computer / Sensor page mean?
A#28:"CPU" temperature means the temperature measured around the CPU socket, whereas "CPU Diode" temperature means the temperature of the CPU core.
Q#29:The web links on the Computer / Summary and other pages do not work, clicking on them does not open my web browser. What's the problem here?
A#29:It means Windows default web browser is not selected.
Q#30:The temperature, voltage or fan rotation values on the Computer / Sensor page are inaccurate. For example, a bogus "Aux" temperature is displayed with a nonsense value; or the CPU and motherboard temperatures are reversed; or the -5V or -12V lines display a completely off positive value. How to make the sensor values more accurate?
A#30:Unfortunately there is no standard for sensor chip registers layout, hence in several cases the registers layout that EVEREST uses could fail to be accurate. In such cases please contact us through the
Lavalys Discussion Forum, under the "Hardware Monitoring" forum. When you open the new topic, please make sure to indicate the version number of EVEREST you're using, the model of your motherboard; and also copy-paste the full content of the
Computer / Sensor page into the new topic you open.
Q#31:When starting EVEREST it locks up the computer while it displays "Scanning PCI devices". How can this be avoided?
A#31:Create a new text file (e.g. using Notepad) in EVEREST folder, name it: "EVEREST.INI". Write the following 2 lines into the new file:
[Generic]
LowLevelPCI=0
Q#32:When starting EVEREST Ultimate Edition, right after the main window appears it suddenly locks up the computer. How can this be avoided?
A#32:Create a new text file in EVEREST folder, name it: "EVEREST.INI". Write the following 2 lines into the new file:Create a new text file in EVEREST folder, name it: "EVEREST.INI". Write the following 2 lines into the new file:
[Generic]
LowLevelSMBus=0
Q#33:Why is the CPU clock and CPU multiplier constantly fluctuate on the EVEREST CPUID Panel and the Overclock page?
A#33:It is because of the activity of the power management features of the processor, namely EIST (Enhanced Intel SpeedStep), C1E (Enhanced Halt State) and PowerNow. When the processor is idle those features automatically lower the CPU multiplier, CPU core clock and CPU core voltage in order to reduce the power consumption and operating temperature of the processor.
Q#34:Why is the "CPU" temperature considerably different from the core temperatures?
A#34:While the "CPU" and "Motherboard" temperatures are measured by the sensor chip mounted on the motherboard PCB; the core temperatures are measured by the CPU itself, using on-die temperature diodes. Due to the fundamental differences in the measurement solution, it's not recommended to compare those values against each other at all.
Q#35:Why are the core temperatures 10 or 15 Celsius lower or higher than what other hardware monitoring tools (e.g. CoreTemp, HWMonitor) measure?
A#35:EVEREST v5.00 and later versions follow the recent DTS (core temperature measurement) specification Intel published, so it should measure the core temperatures properly. Other software may or may not follow Intel's specifications.