voila, je cherche à savoir combien de temps mon ordinateur est en allumé par semaine. Je sais qu'il y a plein de log qui enregistre tout plein d'infos, mais par contre je ne sais pas les exploiter.
 
Es-ce que quelqu'un pourrait m'expliquer ?

Post à relancer, parce que ça peut intéresser des gens. Et puis ça ferait toujours avancer le science

je confirme, c'est utile ton topic.
 
as tu regarder du coté de www.telecharger.com ?

heu non, j'ai pas regarder.
c'est vrai que faudrai regarder dans la section utilitaire...

Comme dans Win98, tu peux connaître le "uptime" (cher aux utilisateurs de Nunux en affichant les infos systèmes avec l'outil du même nom.
Celà ne donne par contre que la durée écoulée depuis la mise en route du système et celà n'est à priori pas loggué pour un usage plus statistique.

ok, mais moi je suis sous 2000 et je souhaite connaître le temps cumulé depuis une semaine voir plus

voilà:
 

si c'est trop compliqué, tu fais la commande suivante dans n'importe quel programme IRC:
 
//say Windows $os $_ uptime: $DURATION($CALC($TICKS / 1000))

--Message édité par Latinus--

ceci n'est valable que si on pc reste allumé tout le temps...si tu veux mesurer l'uptime cumulée d'une semaine tu devras te servir d'un logiciel monitorant la chose...

L'utilitaire uptime de Microsoft permet de donner des statistiques précises sur les périodes d'activité du PC.
 
Voici son aide:
 
--8<----8<----8<----8<----8<----8<----8<----8<----8<--
 
UPTIME, Version 1.01
(C) Copyright 1999, Microsoft Corporation
 
Uptime [server] [/s ] [/a] [/d:mm/dd/yyyy | /p:n] [/heartbeat] [/? | /help]ss
 serverssName or IP address of remote server to process.
 /sssDisplay key system events and statistics.
 /assDisplay application failure events (assumes /s).
 /d:ssOnly calculate for events after mm/dd/yyyy.
 /p:ssOnly calculate for events in the previous n days.
 /heartbeat Turn on/off the system's heartbeat
 /?ssBasic usage.
 /helpssAdditional usage information.
 
Description:
UPTIME is a utility that processes the machine's event log to determine
system availability and current uptime. The target system can either be thess
local system or a remote system. No special privileges are required for basic
operation although it is most accurate to run the tool under an administrative
account. Many factors affect these calculations, and the results displayed
by this tool should be considered estimates.
 
Requirements:
ssssAvailability calculations require:
ssssWindows NT 4.0 Service Pack 4 or higher, including Windows 2000.
ssssAdditionally the system "heartbeat" must be active.
 
The system "heartbeat" is a date/time stamp that is written to the system
registry at a fixed interval. This heartbeat is available in Service Pack 4
or higher. It is enabled by default on Windows NT Server. Since thess
heartbeat causes the registry to be written to the disk at regularss
intervals, it can interfere with systems running various forms of powerss
management. It is not recommended to enable the heartbeat of laptop systems.
 
To enable the heartbeat use: UPTIME /heartbeat [\Machine]
 
If the heartbeat is disabled, or if you are not running Service Pack 4 orss
greater, UPTIME may report that the event logs do not contain sufficientss
information to calculate system availability. This is because UPTIME detectsss
an abnormal shutdown (for instance a bluescreen or power failure) but cannotss
determine how long the system was down during this abnormal outage.
 
It is best to run uptime as an administrator, since much more information
is available to calculate system uptime and availability. For instancess
the time zone of the system is important to many of the calculations, but
this information can only be reliably obtained by an administrator.ss
Additionally, when calculating the Current System Uptime, this tool attemptsss
to use the System Performance Counter for Uptime. However, if the user is notss
an administrator, this counter may be unavailable. In this case an estimatess
is made based on the last recorded boot noted in the event log.ss
 
Application Failures:
Application Failure event detection is dependent upon Dr Watson being enabled.
 
Bluescreens:
Bluescreen detection is dependent upon the system being configured to write an
event to the event log if the system stops unexpectedly.ss
To enable bluescreen event logging for Windows NT 4.0:
ss Go to the Control Panel and double click the System Icon.
ss Next select the startup/shutdown tab.
ss Finally check the "Write an event to the system log." check box.
 
To enable bluescreen event logging for Windows 2000 Systems do the following:ss
ss Go to the Control Panel and double click the System Icon.ss
ss Next select the "Advanced" tab.ss
ss From the "Advanced" property sheet select the "Startup and Recovery" button.
ss Finally check the "Write an event to the system log." check box.
 
Potential sources of error:ss
All calculations are based on the entries in the event log.ssIf thess
system time is altered significantly, this can have a dramatic affect on
the calculations made.ssAdditionally if the event logs have been cleared,
or have filled, such that additional events cannot be written, this will
also affect this tools ability to accurately estimate system availability.
 
The heartbeat is generally written every 5 minutes, so the amount of downtimess
calculated for abnormal outages is limited in accuracy to this window.
 
Systems that are a member of a cluster are currently unsupported by UPTIME.
If UPTIME detects that the target system may be a member of a cluster,ss
UPTIME will display a message stating that the results may be in error.
 
Where to go for more help:
For further information about this tool please see:
http://support.Microsoft.com/support and reference KB Article: Q232243
 
--8<----8<----8<----8<----8<----8<----8<----8<----8<--
 
L'utilitaire en question est disponible ici:
http://www.microsoft.com/ntserver/ [...] efault.asp

mille fois merci, c'est ce que je cherchais.
Faudra que j'essaye ce logiciel