Bootup - Shutdown logger

PSRumbagh · Apr 16, 2008

I would like to produce a (text) file that shows when (date & time) bootup is
completed and when shutdown is initiated. The file needs to append itself
everytime bootup and shutdown occurs, i.e the file grows bigger with time.
For example, over a year period the file will probably have many hundreds of
entries in it. The program must NOT delete previous entries. Any
suggestions?

MEB · Apr 16, 2008

This was just discussed in *Elapsed time meter*

See Franc's second message [04-14-08] for autoexec.bat entries to create a
text file.

--
MEB http://peoplescounsel.orgfree.com
--
_________

"PSRumbagh" <PSRumbagh@discussions.microsoft.com> wrote in message
news:6509B7DE-669E-423D-BA68-0715655A5F5D@microsoft.com...
| I would like to produce a (text) file that shows when (date & time) bootup
is
| completed and when shutdown is initiated. The file needs to append itself
| everytime bootup and shutdown occurs, i.e the file grows bigger with time.
| For example, over a year period the file will probably have many hundreds
of
| entries in it. The program must NOT delete previous entries. Any
| suggestions?

MEB · Apr 16, 2008

Perhaps I should add, that there were times when someone would request an
actual program that would do this [with password protection] and I would
install Sentry or another boot protection program [something they could
understand].

--
MEB http://peoplescounsel.orgfree.com
--
_________

Gary S. Terhune · Apr 17, 2008

It's difficult to pin down when boot up is "finished", but a rough estimate
is provided by a script in the Startup folder. For shutdown, you use a
script to initiate shutdown. Both scripts write the date/time to a single,
mutual file.

How's that for an idea? I even have most of the code written. But you've
been given a lot of info already, with no seeming result. What's wrong with
the solutions already provided in this forum?

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"PSRumbagh" <PSRumbagh@discussions.microsoft.com> wrote in message
news:6509B7DE-669E-423D-BA68-0715655A5F5D@microsoft.com...
>I would like to produce a (text) file that shows when (date & time) bootup
>is
> completed and when shutdown is initiated. The file needs to append itself
> everytime bootup and shutdown occurs, i.e the file grows bigger with time.
> For example, over a year period the file will probably have many hundreds
> of
> entries in it. The program must NOT delete previous entries. Any
> suggestions?

PSRumbagh · Apr 17, 2008

Not being a computer whiz, I am a little reluctant to mess with the
autoexec.bat file. What happens if I make a typo error when modifying the
autoexec.bat file? Will my PC fail to boot? Then what?

"Gary S. Terhune" wrote:

> It's difficult to pin down when boot up is "finished", but a rough estimate
> is provided by a script in the Startup folder. For shutdown, you use a
> script to initiate shutdown. Both scripts write the date/time to a single,
> mutual file.
>
> How's that for an idea? I even have most of the code written. But you've
> been given a lot of info already, with no seeming result. What's wrong with
> the solutions already provided in this forum?
>
> --
> Gary S. Terhune
> MS-MVP Shell/User
> www.grystmill.com
>
> "PSRumbagh" <PSRumbagh@discussions.microsoft.com> wrote in message
> news:6509B7DE-669E-423D-BA68-0715655A5F5D@microsoft.com...
> >I would like to produce a (text) file that shows when (date & time) bootup
> >is
> > completed and when shutdown is initiated. The file needs to append itself
> > everytime bootup and shutdown occurs, i.e the file grows bigger with time.
> > For example, over a year period the file will probably have many hundreds
> > of
> > entries in it. The program must NOT delete previous entries. Any
> > suggestions?
>
>

PSRumbagh · Apr 17, 2008

Not being a computer whiz, I am a little reluctant to mess with the
autoexec.bat file. What happens if I make a typo error when modifying the
autoexec.bat file? Will my PC fail to boot? Then what?

"MEB" wrote:

> This was just discussed in *Elapsed time meter*
>
> See Franc's second message [04-14-08] for autoexec.bat entries to create a
> text file.
>
> --
> MEB http://peoplescounsel.orgfree.com
> --
> _________
>
> "PSRumbagh" <PSRumbagh@discussions.microsoft.com> wrote in message
> news:6509B7DE-669E-423D-BA68-0715655A5F5D@microsoft.com...
> | I would like to produce a (text) file that shows when (date & time) bootup
> is
> | completed and when shutdown is initiated. The file needs to append itself
> | everytime bootup and shutdown occurs, i.e the file grows bigger with time.
> | For example, over a year period the file will probably have many hundreds
> of
> | entries in it. The program must NOT delete previous entries. Any
> | suggestions?
>
>
>

MEB · Apr 18, 2008

Franc was careful enough: that seemed to be correct and intact when posted.
A cut and paste of the lines into a text editor, and saving the file as >
test.bat < would allow you to test without any difficulties. Just click on
the bat you created in Explorer, and look in the folder at the created text
file to see if it contains what you want [or use the RUN box or MSDOS
prompt]. If it suits your purposes, then add the lines into the autoexec.bat
by cutting and pasting there. NOTE: place them at the end of the Batch.

If you mess up the test.bat, then nothing untoward will occur while
testing.

--
MEB http://peoplescounsel.orgfree.com
--
_________

"PSRumbagh" <PSRumbagh@discussions.microsoft.com> wrote in message
news:704CE063-2A48-449D-877D-E43FC254942F@microsoft.com...
| Not being a computer whiz, I am a little reluctant to mess with the
| autoexec.bat file. What happens if I make a typo error when modifying the
| autoexec.bat file? Will my PC fail to boot? Then what?
|
| "MEB" wrote:
|
| > This was just discussed in *Elapsed time meter*
| >
| > See Franc's second message [04-14-08] for autoexec.bat entries to
create a
| > text file.
| >
| > --
| > MEB http://peoplescounsel.orgfree.com
| > --
| > _________
| >
| > "PSRumbagh" <PSRumbagh@discussions.microsoft.com> wrote in message
| > news:6509B7DE-669E-423D-BA68-0715655A5F5D@microsoft.com...
| > | I would like to produce a (text) file that shows when (date & time)
bootup
| > is
| > | completed and when shutdown is initiated. The file needs to append
itself
| > | everytime bootup and shutdown occurs, i.e the file grows bigger with
time.
| > | For example, over a year period the file will probably have many
hundreds
| > of
| > | entries in it. The program must NOT delete previous entries. Any
| > | suggestions?
| >
| >
| >

Gary S. Terhune · Apr 18, 2008

Nothing you put in autoexec.bat is going to tell you when boot "finishes."

I'm lost. What was the recommended autoexec.bat command? Was it just to put
a timestamp in a log?

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"MEB" <meb@not here@hotmail.com> wrote in message
news:O62cIASoIHA.1740@TK2MSFTNGP05.phx.gbl...
> Franc was careful enough: that seemed to be correct and intact when
> posted.
> A cut and paste of the lines into a text editor, and saving the file as >
> test.bat < would allow you to test without any difficulties. Just click
> on
> the bat you created in Explorer, and look in the folder at the created
> text
> file to see if it contains what you want [or use the RUN box or MSDOS
> prompt]. If it suits your purposes, then add the lines into the
> autoexec.bat
> by cutting and pasting there. NOTE: place them at the end of the Batch.
>
> If you mess up the test.bat, then nothing untoward will occur while
> testing.
>
> --
> MEB http://peoplescounsel.orgfree.com
> --
> _________
>
>
> "PSRumbagh" <PSRumbagh@discussions.microsoft.com> wrote in message
> news:704CE063-2A48-449D-877D-E43FC254942F@microsoft.com...
> | Not being a computer whiz, I am a little reluctant to mess with the
> | autoexec.bat file. What happens if I make a typo error when modifying
> the
> | autoexec.bat file? Will my PC fail to boot? Then what?
> |
> | "MEB" wrote:
> |
> | > This was just discussed in *Elapsed time meter*
> | >
> | > See Franc's second message [04-14-08] for autoexec.bat entries to
> create a
> | > text file.
> | >
> | > --
> | > MEB http://peoplescounsel.orgfree.com
> | > --
> | > _________
> | >
> | > "PSRumbagh" <PSRumbagh@discussions.microsoft.com> wrote in message
> | > news:6509B7DE-669E-423D-BA68-0715655A5F5D@microsoft.com...
> | > | I would like to produce a (text) file that shows when (date & time)
> bootup
> | > is
> | > | completed and when shutdown is initiated. The file needs to append
> itself
> | > | everytime bootup and shutdown occurs, i.e the file grows bigger with
> time.
> | > | For example, over a year period the file will probably have many
> hundreds
> | > of
> | > | entries in it. The program must NOT delete previous entries. Any
> | > | suggestions?
> | >
> | >
> | >
>
>

Gary S. Terhune · Apr 18, 2008

Take our word for it, nothing that's been recommended will do anything to
hurt the system. At worst, the command won't do what you want it to do. But
as I'm discussing with MEB, I'm not clear that some command in autoexec.bat
can do what you want.

As stated, you want to log when bootup finishes and when shutdown commences.
Is this a secure system that you have to keep kids from messing with, for
instance?

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com
\
"PSRumbagh" <PSRumbagh@discussions.microsoft.com> wrote in message
news:B4A5F84B-1891-4B49-8AE1-22E3E76FA7E2@microsoft.com...
> Not being a computer whiz, I am a little reluctant to mess with the
> autoexec.bat file. What happens if I make a typo error when modifying the
> autoexec.bat file? Will my PC fail to boot? Then what?
>
> "Gary S. Terhune" wrote:
>
>> It's difficult to pin down when boot up is "finished", but a rough
>> estimate
>> is provided by a script in the Startup folder. For shutdown, you use a
>> script to initiate shutdown. Both scripts write the date/time to a
>> single,
>> mutual file.
>>
>> How's that for an idea? I even have most of the code written. But you've
>> been given a lot of info already, with no seeming result. What's wrong
>> with
>> the solutions already provided in this forum?
>>
>> --
>> Gary S. Terhune
>> MS-MVP Shell/User
>> www.grystmill.com
>>
>> "PSRumbagh" <PSRumbagh@discussions.microsoft.com> wrote in message
>> news:6509B7DE-669E-423D-BA68-0715655A5F5D@microsoft.com...
>> >I would like to produce a (text) file that shows when (date & time)
>> >bootup
>> >is
>> > completed and when shutdown is initiated. The file needs to append
>> > itself
>> > everytime bootup and shutdown occurs, i.e the file grows bigger with
>> > time.
>> > For example, over a year period the file will probably have many
>> > hundreds
>> > of
>> > entries in it. The program must NOT delete previous entries. Any
>> > suggestions?
>>
>>

Gary S. Terhune · Apr 18, 2008

Anyway, I just finished a whole set of scripts and shortcuts that will do
what you want. I can even put them into an installer so you don't have to
worry about mistakes. Or are you familiar enough with computers to, say, put
a couple of files into the C:\ folder, on into the Startup folder, etc.?

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"PSRumbagh" <PSRumbagh@discussions.microsoft.com> wrote in message
news:B4A5F84B-1891-4B49-8AE1-22E3E76FA7E2@microsoft.com...
> Not being a computer whiz, I am a little reluctant to mess with the
> autoexec.bat file. What happens if I make a typo error when modifying the
> autoexec.bat file? Will my PC fail to boot? Then what?
>
> "Gary S. Terhune" wrote:
>
>> It's difficult to pin down when boot up is "finished", but a rough
>> estimate
>> is provided by a script in the Startup folder. For shutdown, you use a
>> script to initiate shutdown. Both scripts write the date/time to a
>> single,
>> mutual file.
>>
>> How's that for an idea? I even have most of the code written. But you've
>> been given a lot of info already, with no seeming result. What's wrong
>> with
>> the solutions already provided in this forum?
>>
>> --
>> Gary S. Terhune
>> MS-MVP Shell/User
>> www.grystmill.com
>>
>> "PSRumbagh" <PSRumbagh@discussions.microsoft.com> wrote in message
>> news:6509B7DE-669E-423D-BA68-0715655A5F5D@microsoft.com...
>> >I would like to produce a (text) file that shows when (date & time)
>> >bootup
>> >is
>> > completed and when shutdown is initiated. The file needs to append
>> > itself
>> > everytime bootup and shutdown occurs, i.e the file grows bigger with
>> > time.
>> > For example, over a year period the file will probably have many
>> > hundreds
>> > of
>> > entries in it. The program must NOT delete previous entries. Any
>> > suggestions?
>>
>>

MEB · Apr 18, 2008

MEB · Apr 18, 2008

Its Franc's code, let him explain.

Like I said, I would install one of the available third party programs [for
those not wanting policies and other] to completely monitor access,
password protected and required for entry, encrypted, complete logged
activity if desired including hack attempts or failed logins, and several
other.

--
MEB http://peoplescounsel.orgfree.com
--
_________

"Gary S. Terhune" <none> wrote in message
news:%23yqjB$VoIHA.420@TK2MSFTNGP02.phx.gbl...
| Nothing you put in autoexec.bat is going to tell you when boot "finishes."
|
| I'm lost. What was the recommended autoexec.bat command? Was it just to
put
| a timestamp in a log?
|
| --
| Gary S. Terhune
| MS-MVP Shell/User
| www.grystmill.com
|
| "MEB" <meb@not here@hotmail.com> wrote in message
| news:O62cIASoIHA.1740@TK2MSFTNGP05.phx.gbl...
| > Franc was careful enough: that seemed to be correct and intact when
| > posted.
| > A cut and paste of the lines into a text editor, and saving the file as
>
| > test.bat < would allow you to test without any difficulties. Just click
| > on
| > the bat you created in Explorer, and look in the folder at the created
| > text
| > file to see if it contains what you want [or use the RUN box or MSDOS
| > prompt]. If it suits your purposes, then add the lines into the
| > autoexec.bat
| > by cutting and pasting there. NOTE: place them at the end of the Batch.
| >
| > If you mess up the test.bat, then nothing untoward will occur while
| > testing.
| >
| > --
| > MEB http://peoplescounsel.orgfree.com
| > --
| > _________
| >
| >
| > "PSRumbagh" <PSRumbagh@discussions.microsoft.com> wrote in message
| > news:704CE063-2A48-449D-877D-E43FC254942F@microsoft.com...
| > | Not being a computer whiz, I am a little reluctant to mess with the
| > | autoexec.bat file. What happens if I make a typo error when modifying
| > the
| > | autoexec.bat file? Will my PC fail to boot? Then what?
| > |
| > | "MEB" wrote:
| > |
| > | > This was just discussed in *Elapsed time meter*
| > | >
| > | > See Franc's second message [04-14-08] for autoexec.bat entries to
| > create a
| > | > text file.
| > | >
| > | > --
| > | > MEB http://peoplescounsel.orgfree.com
| > | > --
| > | > _________
| > | >
| > | > "PSRumbagh" <PSRumbagh@discussions.microsoft.com> wrote in message
| > | > news:6509B7DE-669E-423D-BA68-0715655A5F5D@microsoft.com...
| > | > | I would like to produce a (text) file that shows when (date &
time)
| > bootup
| > | > is
| > | > | completed and when shutdown is initiated. The file needs to
append
| > itself
| > | > | everytime bootup and shutdown occurs, i.e the file grows bigger
with
| > time.
| > | > | For example, over a year period the file will probably have many
| > hundreds
| > | > of
| > | > | entries in it. The program must NOT delete previous entries. Any
| > | > | suggestions?
| > | >
| > | >
| > | >
| >
| >
|

Gary S. Terhune · Apr 18, 2008

Yeah, so would I.

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"MEB" <meb@not here@hotmail.com> wrote in message
news:Ot913vXoIHA.5016@TK2MSFTNGP02.phx.gbl...
> Its Franc's code, let him explain.
>
> Like I said, I would install one of the available third party programs
> [for
> those not wanting policies and other] to completely monitor access,
> password protected and required for entry, encrypted, complete logged
> activity if desired including hack attempts or failed logins, and several
> other.
>
> --
> MEB http://peoplescounsel.orgfree.com
> --
> _________
>
> "Gary S. Terhune" <none> wrote in message
> news:%23yqjB$VoIHA.420@TK2MSFTNGP02.phx.gbl...
> | Nothing you put in autoexec.bat is going to tell you when boot
> "finishes."
> |
> | I'm lost. What was the recommended autoexec.bat command? Was it just to
> put
> | a timestamp in a log?
> |
> | --
> | Gary S. Terhune
> | MS-MVP Shell/User
> | www.grystmill.com
> |
> | "MEB" <meb@not here@hotmail.com> wrote in message
> | news:O62cIASoIHA.1740@TK2MSFTNGP05.phx.gbl...
> | > Franc was careful enough: that seemed to be correct and intact when
> | > posted.
> | > A cut and paste of the lines into a text editor, and saving the file
> as
>>
> | > test.bat < would allow you to test without any difficulties. Just
> click
> | > on
> | > the bat you created in Explorer, and look in the folder at the created
> | > text
> | > file to see if it contains what you want [or use the RUN box or MSDOS
> | > prompt]. If it suits your purposes, then add the lines into the
> | > autoexec.bat
> | > by cutting and pasting there. NOTE: place them at the end of the
> Batch.
> | >
> | > If you mess up the test.bat, then nothing untoward will occur while
> | > testing.
> | >
> | > --
> | > MEB http://peoplescounsel.orgfree.com
> | > --
> | > _________
> | >
> | >
> | > "PSRumbagh" <PSRumbagh@discussions.microsoft.com> wrote in message
> | > news:704CE063-2A48-449D-877D-E43FC254942F@microsoft.com...
> | > | Not being a computer whiz, I am a little reluctant to mess with the
> | > | autoexec.bat file. What happens if I make a typo error when
> modifying
> | > the
> | > | autoexec.bat file? Will my PC fail to boot? Then what?
> | > |
> | > | "MEB" wrote:
> | > |
> | > | > This was just discussed in *Elapsed time meter*
> | > | >
> | > | > See Franc's second message [04-14-08] for autoexec.bat entries to
> | > create a
> | > | > text file.
> | > | >
> | > | > --
> | > | > MEB http://peoplescounsel.orgfree.com
> | > | > --
> | > | > _________
> | > | >
> | > | > "PSRumbagh" <PSRumbagh@discussions.microsoft.com> wrote in message
> | > | > news:6509B7DE-669E-423D-BA68-0715655A5F5D@microsoft.com...
> | > | > | I would like to produce a (text) file that shows when (date &
> time)
> | > bootup
> | > | > is
> | > | > | completed and when shutdown is initiated. The file needs to
> append
> | > itself
> | > | > | everytime bootup and shutdown occurs, i.e the file grows bigger
> with
> | > time.
> | > | > | For example, over a year period the file will probably have many
> | > hundreds
> | > | > of
> | > | > | entries in it. The program must NOT delete previous entries.
> Any
> | > | > | suggestions?
> | > | >
> | > | >
> | > | >
> | >
> | >
> |
>
>

Gary S. Terhune · Apr 18, 2008

No, I'll post the code here, between lines of asterisks.

"StartTime.vbs"
****************************
Option Explicit
Dim fso, f
Set fso = CreateObject("Scripting.FileSystemObject")
Set f = fs

penTextFile("C:\uptime.txt", 8, True)
f.WriteLine "Start " & now
f.Close
WScript.Quit
******************************

"Shutdown.vbs"
*****************************
Option Explicit
Dim fso, f, wso
Set wso = WScript.CreateObject("WScript.Shell")
Set fso = CreateObject("Scripting.FileSystemObject")
Set f = fs

penTextFile("C:\uptime.txt", 8, True)
f.WriteLine now
f.Close
wso.run "C:\WINDOWS\RUNDLL32 SHELL32.DLL,SHExitWindowsEx 9"
********************************

""Restart.vbs"
*******************************
Option Explicit
Dim fso, f, wso
Set wso = WScript.CreateObject("WScript.Shell")
Set fso = CreateObject("Scripting.FileSystemObject")
Set f = fs

penTextFile("C:\uptime.txt", 8, True)
f.WriteLine now
f.Close
wso.run "C:\WINDOWS\RUNDLL32 SHELL32.DLL,SHExitWindowsEx 2"
********************************

"Logoff.vbs"
*******************************
Option Explicit
Dim fso, f, wso
Set wso = WScript.CreateObject("WScript.Shell")
Set fso = CreateObject("Scripting.FileSystemObject")
Set f = fs

penTextFile("C:\uptime.txt", 8, True)
f.WriteLine now
f.Close
wso.run "C:\WINDOWS\RUNDLL32 SHELL32.DLL,SHExitWindowsEx 0"
*********************************

Place StartTime.vbs into the Startup folder. Place the other three into the
C:\ root folder. "C:\Uptime.txt" is the log. I'd place shortcuts to the
shutdown scripts and the log onto the Desktop.

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"MEB" <meb@not here@hotmail.com> wrote in message
news:%23Dqa0vXoIHA.5016@TK2MSFTNGP02.phx.gbl...
> Okay, let me reply here. If you finished the scripts and other, is there a
> link for testing these [no installer yet please]?
>
>
> --
> MEB http://peoplescounsel.orgfree.com
> --
> _________
>
> "Gary S. Terhune" <none> wrote in message
> news:eZeTrhWoIHA.3652@TK2MSFTNGP03.phx.gbl...
> | Anyway, I just finished a whole set of scripts and shortcuts that will
> do
> | what you want. I can even put them into an installer so you don't have
> to
> | worry about mistakes. Or are you familiar enough with computers to, say,
> put
> | a couple of files into the C:\ folder, on into the Startup folder, etc.?
> |
> | --
> | Gary S. Terhune
> | MS-MVP Shell/User
> | www.grystmill.com
> |
> | "PSRumbagh" <PSRumbagh@discussions.microsoft.com> wrote in message
> | news:B4A5F84B-1891-4B49-8AE1-22E3E76FA7E2@microsoft.com...
> | > Not being a computer whiz, I am a little reluctant to mess with the
> | > autoexec.bat file. What happens if I make a typo error when modifying
> the
> | > autoexec.bat file? Will my PC fail to boot? Then what?
> | >
> | > "Gary S. Terhune" wrote:
> | >
> | >> It's difficult to pin down when boot up is "finished", but a rough
> | >> estimate
> | >> is provided by a script in the Startup folder. For shutdown, you use
> a
> | >> script to initiate shutdown. Both scripts write the date/time to a
> | >> single,
> | >> mutual file.
> | >>
> | >> How's that for an idea? I even have most of the code written. But
> you've
> | >> been given a lot of info already, with no seeming result. What's
> wrong
> | >> with
> | >> the solutions already provided in this forum?
> | >>
> | >> --
> | >> Gary S. Terhune
> | >> MS-MVP Shell/User
> | >> www.grystmill.com
> | >>
> | >> "PSRumbagh" <PSRumbagh@discussions.microsoft.com> wrote in message
> | >> news:6509B7DE-669E-423D-BA68-0715655A5F5D@microsoft.com...
> | >> >I would like to produce a (text) file that shows when (date & time)
> | >> >bootup
> | >> >is
> | >> > completed and when shutdown is initiated. The file needs to append
> | >> > itself
> | >> > everytime bootup and shutdown occurs, i.e the file grows bigger
> with
> | >> > time.
> | >> > For example, over a year period the file will probably have many
> | >> > hundreds
> | >> > of
> | >> > entries in it. The program must NOT delete previous entries. Any
> | >> > suggestions?
> | >>
> | >>
> |
>
>

MEB · Apr 18, 2008

penTextFile("C:\uptime.txt", 8, True)
| f.WriteLine now
| f.Close
| wso.run "C:\WINDOWS\RUNDLL32 SHELL32.DLL,SHExitWindowsEx 0"
| *********************************
|
| Place StartTime.vbs into the Startup folder. Place the other three into
the
| C:\ root folder. "C:\Uptime.txt" is the log. I'd place shortcuts to the
| shutdown scripts and the log onto the Desktop.
|
| --
| Gary S. Terhune
| MS-MVP Shell/User
| www.grystmill.com
|

Okay, tested shutdown and startup vbs. Not sure if this is accurate, but
apparently the desire is to monitor ALL log times [like in a networked
server/work station environment or multi-user environment {tracking kids
usage}].
How do you intend to ensure that a user MUST use these to logoff or
shutdown, hence creating an accurate and complete log for usage tracking
purposes, and ensure that the Startup vbs is not removed from Startup?

The poster also wished TOTAL runtime output logged [as in other apparent
users apparently for comparison to cumulative logged activity]. The
suggestion was to compare SMART values [hard drive runtime hours].

--
MEB http://peoplescounsel.orgfree.com
--
_________

|
| "MEB" <meb@not here@hotmail.com> wrote in message
| news:%23Dqa0vXoIHA.5016@TK2MSFTNGP02.phx.gbl...
| > Okay, let me reply here. If you finished the scripts and other, is there
a
| > link for testing these [no installer yet please]?
| >
| >
| > --
| > MEB http://peoplescounsel.orgfree.com
| > --
| > _________
| >
| > "Gary S. Terhune" <none> wrote in message
| > news:eZeTrhWoIHA.3652@TK2MSFTNGP03.phx.gbl...
| > | Anyway, I just finished a whole set of scripts and shortcuts that will
| > do
| > | what you want. I can even put them into an installer so you don't have
| > to
| > | worry about mistakes. Or are you familiar enough with computers to,
say,
| > put
| > | a couple of files into the C:\ folder, on into the Startup folder,
etc.?
| > |
| > | --
| > | Gary S. Terhune
| > | MS-MVP Shell/User
| > | www.grystmill.com
| > |
| > | "PSRumbagh" <PSRumbagh@discussions.microsoft.com> wrote in message
| > | news:B4A5F84B-1891-4B49-8AE1-22E3E76FA7E2@microsoft.com...
| > | > Not being a computer whiz, I am a little reluctant to mess with the
| > | > autoexec.bat file. What happens if I make a typo error when
modifying
| > the
| > | > autoexec.bat file? Will my PC fail to boot? Then what?
| > | >
| > | > "Gary S. Terhune" wrote:
| > | >
| > | >> It's difficult to pin down when boot up is "finished", but a rough
| > | >> estimate
| > | >> is provided by a script in the Startup folder. For shutdown, you
use
| > a
| > | >> script to initiate shutdown. Both scripts write the date/time to a
| > | >> single,
| > | >> mutual file.
| > | >>
| > | >> How's that for an idea? I even have most of the code written. But
| > you've
| > | >> been given a lot of info already, with no seeming result. What's
| > wrong
| > | >> with
| > | >> the solutions already provided in this forum?
| > | >>
| > | >> --
| > | >> Gary S. Terhune
| > | >> MS-MVP Shell/User
| > | >> www.grystmill.com
| > | >>
| > | >> "PSRumbagh" <PSRumbagh@discussions.microsoft.com> wrote in message
| > | >> news:6509B7DE-669E-423D-BA68-0715655A5F5D@microsoft.com...
| > | >> >I would like to produce a (text) file that shows when (date &
time)
| > | >> >bootup
| > | >> >is
| > | >> > completed and when shutdown is initiated. The file needs to
append
| > | >> > itself
| > | >> > everytime bootup and shutdown occurs, i.e the file grows bigger
| > with
| > | >> > time.
| > | >> > For example, over a year period the file will probably have many
| > | >> > hundreds
| > | >> > of
| > | >> > entries in it. The program must NOT delete previous entries.
Any
| > | >> > suggestions?
| > | >>
| > | >>
| > |
| >
| >
|

Gary S. Terhune · Apr 19, 2008

I've proved the concept, just not actually written all the code, that would
provide individual and cumulative uptime notations added to the log at
shutdown, but I think it might be better to leave the log alone and run a
script on it whenever a report is desired. Depends on end use. You mention
various scenarios. Perhaps the OP could help us pin down the target
environment. Or, perhaps OP has used that code of Franc's and it works just
fine and he just hasn't bothered to report back.

Locking down Windows 98 using Doug Knox's methods would be the only way I
know to prevent meddling with the tracking system. Locking down would be
required NO MATTER what tracking method was used if trust of the user(s) is
not complete. Perhaps a combination of POLEDIT and Doug's scripts.
http://www.dougknox.com/security/index.htm, which would be necessary under
those conditions, anyway.

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"MEB" <meb@not here@hotmail.com> wrote in message
news:ujCQpyeoIHA.4760@TK2MSFTNGP06.phx.gbl...
>
> "Gary S. Terhune" <none> wrote in message
> news:ueoHUCaoIHA.4760@TK2MSFTNGP06.phx.gbl...
> | No, I'll post the code here, between lines of asterisks.
> |
> | "StartTime.vbs"
> | ****************************
> | Option Explicit
> | Dim fso, f
> | Set fso = CreateObject("Scripting.FileSystemObject")
> | Set f = fs

penTextFile("C:\uptime.txt", 8, True)
> | f.WriteLine now
> | f.Close
> | wso.run "C:\WINDOWS\RUNDLL32 SHELL32.DLL,SHExitWindowsEx 0"
> | *********************************
> |
> | Place StartTime.vbs into the Startup folder. Place the other three into
> the
> | C:\ root folder. "C:\Uptime.txt" is the log. I'd place shortcuts to the
> | shutdown scripts and the log onto the Desktop.
> |
> | --
> | Gary S. Terhune
> | MS-MVP Shell/User
> | www.grystmill.com
> |
>
>
>
> Okay, tested shutdown and startup vbs. Not sure if this is accurate, but
> apparently the desire is to monitor ALL log times [like in a networked
> server/work station environment or multi-user environment {tracking kids
> usage}].
> How do you intend to ensure that a user MUST use these to logoff or
> shutdown, hence creating an accurate and complete log for usage tracking
> purposes, and ensure that the Startup vbs is not removed from Startup?
>
> The poster also wished TOTAL runtime output logged [as in other apparent
> users apparently for comparison to cumulative logged activity]. The
> suggestion was to compare SMART values [hard drive runtime hours].
>
> --
> MEB http://peoplescounsel.orgfree.com
> --
> _________
>
>
> |
> | "MEB" <meb@not here@hotmail.com> wrote in message
> | news:%23Dqa0vXoIHA.5016@TK2MSFTNGP02.phx.gbl...
> | > Okay, let me reply here. If you finished the scripts and other, is
> there
> a
> | > link for testing these [no installer yet please]?
> | >
> | >
> | > --
> | > MEB http://peoplescounsel.orgfree.com
> | > --
> | > _________
> | >
> | > "Gary S. Terhune" <none> wrote in message
> | > news:eZeTrhWoIHA.3652@TK2MSFTNGP03.phx.gbl...
> | > | Anyway, I just finished a whole set of scripts and shortcuts that
> will
> | > do
> | > | what you want. I can even put them into an installer so you don't
> have
> | > to
> | > | worry about mistakes. Or are you familiar enough with computers to,
> say,
> | > put
> | > | a couple of files into the C:\ folder, on into the Startup folder,
> etc.?
> | > |
> | > | --
> | > | Gary S. Terhune
> | > | MS-MVP Shell/User
> | > | www.grystmill.com
> | > |
> | > | "PSRumbagh" <PSRumbagh@discussions.microsoft.com> wrote in message
> | > | news:B4A5F84B-1891-4B49-8AE1-22E3E76FA7E2@microsoft.com...
> | > | > Not being a computer whiz, I am a little reluctant to mess with
> the
> | > | > autoexec.bat file. What happens if I make a typo error when
> modifying
> | > the
> | > | > autoexec.bat file? Will my PC fail to boot? Then what?
> | > | >
> | > | > "Gary S. Terhune" wrote:
> | > | >
> | > | >> It's difficult to pin down when boot up is "finished", but a
> rough
> | > | >> estimate
> | > | >> is provided by a script in the Startup folder. For shutdown, you
> use
> | > a
> | > | >> script to initiate shutdown. Both scripts write the date/time to
> a
> | > | >> single,
> | > | >> mutual file.
> | > | >>
> | > | >> How's that for an idea? I even have most of the code written. But
> | > you've
> | > | >> been given a lot of info already, with no seeming result. What's
> | > wrong
> | > | >> with
> | > | >> the solutions already provided in this forum?
> | > | >>
> | > | >> --
> | > | >> Gary S. Terhune
> | > | >> MS-MVP Shell/User
> | > | >> www.grystmill.com
> | > | >>
> | > | >> "PSRumbagh" <PSRumbagh@discussions.microsoft.com> wrote in
> message
> | > | >> news:6509B7DE-669E-423D-BA68-0715655A5F5D@microsoft.com...
> | > | >> >I would like to produce a (text) file that shows when (date &
> time)
> | > | >> >bootup
> | > | >> >is
> | > | >> > completed and when shutdown is initiated. The file needs to
> append
> | > | >> > itself
> | > | >> > everytime bootup and shutdown occurs, i.e the file grows bigger
> | > with
> | > | >> > time.
> | > | >> > For example, over a year period the file will probably have
> many
> | > | >> > hundreds
> | > | >> > of
> | > | >> > entries in it. The program must NOT delete previous entries.
> Any
> | > | >> > suggestions?
> | > | >>
> | > | >>
> | > |
> | >
> | >
> |
>
>

MEB · Apr 19, 2008

Okay, let's see if PSRumbagh can verify exactly what the target for
security is or if that is necessary, and whether either presented technique
provides what they need..

--
MEB http://peoplescounsel.orgfree.com
--
_________

"Gary S. Terhune" <none> wrote in message
news:eaMssDjoIHA.5016@TK2MSFTNGP02.phx.gbl...
| I've proved the concept, just not actually written all the code, that
would
| provide individual and cumulative uptime notations added to the log at
| shutdown, but I think it might be better to leave the log alone and run a
| script on it whenever a report is desired. Depends on end use. You mention
| various scenarios. Perhaps the OP could help us pin down the target
| environment. Or, perhaps OP has used that code of Franc's and it works
just
| fine and he just hasn't bothered to report back.
|
| Locking down Windows 98 using Doug Knox's methods would be the only way I
| know to prevent meddling with the tracking system. Locking down would be
| required NO MATTER what tracking method was used if trust of the user(s)
is
| not complete. Perhaps a combination of POLEDIT and Doug's scripts.
| http://www.dougknox.com/security/index.htm, which would be necessary under
| those conditions, anyway.
|
| --
| Gary S. Terhune
| MS-MVP Shell/User
| www.grystmill.com
|
| "MEB" <meb@not here@hotmail.com> wrote in message
| news:ujCQpyeoIHA.4760@TK2MSFTNGP06.phx.gbl...
| >
| > "Gary S. Terhune" <none> wrote in message
| > news:ueoHUCaoIHA.4760@TK2MSFTNGP06.phx.gbl...
| > | No, I'll post the code here, between lines of asterisks.
| > |
| > | "StartTime.vbs"
| > | ****************************
| > | Option Explicit
| > | Dim fso, f
| > | Set fso = CreateObject("Scripting.FileSystemObject")
| > | Set f = fs

penTextFile("C:\uptime.txt", 8, True)
| > | f.WriteLine "Start " & now
| > | f.Close
| > | WScript.Quit
| > | ******************************
| > |
| > | "Shutdown.vbs"
| > | *****************************
| > | Option Explicit
| > | Dim fso, f, wso
| > | Set wso = WScript.CreateObject("WScript.Shell")
| > | Set fso = CreateObject("Scripting.FileSystemObject")
| > | Set f = fs

penTextFile("C:\uptime.txt", 8, True)
| > | f.WriteLine now
| > | f.Close
| > | wso.run "C:\WINDOWS\RUNDLL32 SHELL32.DLL,SHExitWindowsEx 9"
| > | ********************************
| > |
| > | ""Restart.vbs"
| > | *******************************
| > | Option Explicit
| > | Dim fso, f, wso
| > | Set wso = WScript.CreateObject("WScript.Shell")
| > | Set fso = CreateObject("Scripting.FileSystemObject")
| > | Set f = fs

penTextFile("C:\uptime.txt", 8, True)
| > | f.WriteLine now
| > | f.Close
| > | wso.run "C:\WINDOWS\RUNDLL32 SHELL32.DLL,SHExitWindowsEx 2"
| > | ********************************
| > |
| > | "Logoff.vbs"
| > | *******************************
| > | Option Explicit
| > | Dim fso, f, wso
| > | Set wso = WScript.CreateObject("WScript.Shell")
| > | Set fso = CreateObject("Scripting.FileSystemObject")
| > | Set f = fs

penTextFile("C:\uptime.txt", 8, True)
| > | f.WriteLine now
| > | f.Close
| > | wso.run "C:\WINDOWS\RUNDLL32 SHELL32.DLL,SHExitWindowsEx 0"
| > | *********************************
| > |
| > | Place StartTime.vbs into the Startup folder. Place the other three
into
| > the
| > | C:\ root folder. "C:\Uptime.txt" is the log. I'd place shortcuts to
the
| > | shutdown scripts and the log onto the Desktop.
| > |
| > | --
| > | Gary S. Terhune
| > | MS-MVP Shell/User
| > | www.grystmill.com
| > |
| >
| >
| >
| > Okay, tested shutdown and startup vbs. Not sure if this is accurate, but
| > apparently the desire is to monitor ALL log times [like in a networked
| > server/work station environment or multi-user environment {tracking
kids
| > usage}].
| > How do you intend to ensure that a user MUST use these to logoff or
| > shutdown, hence creating an accurate and complete log for usage tracking
| > purposes, and ensure that the Startup vbs is not removed from Startup?
| >
| > The poster also wished TOTAL runtime output logged [as in other apparent
| > users apparently for comparison to cumulative logged activity]. The
| > suggestion was to compare SMART values [hard drive runtime hours].
| >
| > --
| > MEB http://peoplescounsel.orgfree.com
| > --
| > _________
| >
| >
| > |
| > | "MEB" <meb@not here@hotmail.com> wrote in message
| > | news:%23Dqa0vXoIHA.5016@TK2MSFTNGP02.phx.gbl...
| > | > Okay, let me reply here. If you finished the scripts and other, is
| > there
| > a
| > | > link for testing these [no installer yet please]?
| > | >
| > | >
| > | > --
| > | > MEB http://peoplescounsel.orgfree.com
| > | > --
| > | > _________
| > | >
| > | > "Gary S. Terhune" <none> wrote in message
| > | > news:eZeTrhWoIHA.3652@TK2MSFTNGP03.phx.gbl...
| > | > | Anyway, I just finished a whole set of scripts and shortcuts that
| > will
| > | > do
| > | > | what you want. I can even put them into an installer so you don't
| > have
| > | > to
| > | > | worry about mistakes. Or are you familiar enough with computers
to,
| > say,
| > | > put
| > | > | a couple of files into the C:\ folder, on into the Startup folder,
| > etc.?
| > | > |
| > | > | --
| > | > | Gary S. Terhune
| > | > | MS-MVP Shell/User
| > | > | www.grystmill.com
| > | > |
| > | > | "PSRumbagh" <PSRumbagh@discussions.microsoft.com> wrote in message
| > | > | news:B4A5F84B-1891-4B49-8AE1-22E3E76FA7E2@microsoft.com...
| > | > | > Not being a computer whiz, I am a little reluctant to mess with
| > the
| > | > | > autoexec.bat file. What happens if I make a typo error when
| > modifying
| > | > the
| > | > | > autoexec.bat file? Will my PC fail to boot? Then what?
| > | > | >
| > | > | > "Gary S. Terhune" wrote:
| > | > | >
| > | > | >> It's difficult to pin down when boot up is "finished", but a
| > rough
| > | > | >> estimate
| > | > | >> is provided by a script in the Startup folder. For shutdown,
you
| > use
| > | > a
| > | > | >> script to initiate shutdown. Both scripts write the date/time
to
| > a
| > | > | >> single,
| > | > | >> mutual file.
| > | > | >>
| > | > | >> How's that for an idea? I even have most of the code written.
But
| > | > you've
| > | > | >> been given a lot of info already, with no seeming result.
What's
| > | > wrong
| > | > | >> with
| > | > | >> the solutions already provided in this forum?
| > | > | >>
| > | > | >> --
| > | > | >> Gary S. Terhune
| > | > | >> MS-MVP Shell/User
| > | > | >> www.grystmill.com
| > | > | >>
| > | > | >> "PSRumbagh" <PSRumbagh@discussions.microsoft.com> wrote in
| > message
| > | > | >> news:6509B7DE-669E-423D-BA68-0715655A5F5D@microsoft.com...
| > | > | >> >I would like to produce a (text) file that shows when (date &
| > time)
| > | > | >> >bootup
| > | > | >> >is
| > | > | >> > completed and when shutdown is initiated. The file needs to
| > append
| > | > | >> > itself
| > | > | >> > everytime bootup and shutdown occurs, i.e the file grows
bigger
| > | > with
| > | > | >> > time.
| > | > | >> > For example, over a year period the file will probably have
| > many
| > | > | >> > hundreds
| > | > | >> > of
| > | > | >> > entries in it. The program must NOT delete previous entries.
| > Any
| > | > | >> > suggestions?
| > | > | >>
| > | > | >>
| > | > |
| > | >
| > | >
| > |
| >
| >
|

Franc Zabkar · Apr 19, 2008

On Fri, 18 Apr 2008 15:06:16 -0700, "Gary S. Terhune" <none> put
finger to keyboard and composed:

>No, I'll post the code here, between lines of asterisks.
>
>"StartTime.vbs"
>****************************
>Option Explicit
>Dim fso, f
>Set fso = CreateObject("Scripting.FileSystemObject")
>Set f = fs

penTextFile("C:\uptime.txt", 8, True)
>f.WriteLine "Start " & now
>f.Close
>WScript.Quit
>******************************
>
>"Shutdown.vbs"
>*****************************
>Option Explicit
>Dim fso, f, wso
>Set wso = WScript.CreateObject("WScript.Shell")
>Set fso = CreateObject("Scripting.FileSystemObject")
>Set f = fs

penTextFile("C:\uptime.txt", 8, True)
>f.WriteLine "Shutdown" & now
^^^^^^^^^^^^

>f.Close
>wso.run "C:\WINDOWS\RUNDLL32 SHELL32.DLL,SHExitWindowsEx 9"
>********************************

I'm no programmer, but have you forgotten to add explanatory notes (eg
Shutdown, Restart, Logoff) to the date/time stamps in the respective
scripts?

BTW, I get a VBScript runtime error in line 3 of StartTime.vbs:

ActiveX component can't create object 'Scripting.FileSystemObject'
Code: 800A01AD

Does this mean that I am missing some component or that my permissions
are set incorrectly?

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

Franc Zabkar · Apr 19, 2008

On Sat, 19 Apr 2008 08:18:37 -0700, "Gary S. Terhune" <none> put
finger to keyboard and composed:

>I've proved the concept, just not actually written all the code, that would
>provide individual and cumulative uptime notations added to the log at
>shutdown, but I think it might be better to leave the log alone and run a
>script on it whenever a report is desired. Depends on end use. You mention
>various scenarios. Perhaps the OP could help us pin down the target
>environment. Or, perhaps OP has used that code of Franc's and it works just
>fine and he just hasn't bothered to report back.

My simplistic shutdown code does not log restarts, so from that point
of view your approach is better.

I primarily use my method because I have a lot of automatic
housekeeping tasks that execute just prior to shutdown, eg check for
changes in critical files and sectors, display new Run components in
registry, display HD SMART parameters (reallocated sectors), etc.
Aside from the fact that I don't know how to achieve the same end
within the GUI, the added benefit from doing this at the DOS command
line is that malware may not remain memory resident once one exits the
GUI.

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

PCR · Apr 19, 2008

penTextFile("C:\uptime.txt", 8, True)
|>f.WriteLine "Shutdown" & now
| ^^^^^^^^^^^^
|
|>f.Close
|>wso.run "C:\WINDOWS\RUNDLL32 SHELL32.DLL,SHExitWindowsEx 9"
|>********************************
|
| I'm no programmer, but have you forgotten to add explanatory notes (eg
| Shutdown, Restart, Logoff) to the date/time stamps in the respective
| scripts?
|
| BTW, I get a VBScript runtime error in line 3 of StartTime.vbs:

It worked for me & produced "Start 4/19/08 11:39:16 PM" in UpTime.txt.

| ActiveX component can't create object 'Scripting.FileSystemObject'
| Code: 800A01AD
|
| Does this mean that I am missing some component or that my permissions
| are set incorrectly?

Can it be you need to update your scripting engine?

(But I have failed to remember or discover how to do that. All I have
are these three URLs...
http://msdn2.microsoft.com/en-us/library/t0aew7h6.aspx
VBScript User Manual
http://msdn2.microsoft.com/en-us/library/9bbdkx3k.aspx
More VBScript User Manual
http://www.billsway.com/vbspage/
Windows VBScript Tools
)

| - Franc Zabkar
| --
| Please remove one 'i' from my address when replying by email.

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR
pcrrcp@netzero.net

Bootup - Shutdown logger

PSRumbagh

MEB

MEB

Gary S. Terhune

PSRumbagh

PSRumbagh

MEB

Gary S. Terhune

Gary S. Terhune

Gary S. Terhune

MEB

MEB

Gary S. Terhune

Gary S. Terhune

MEB

Gary S. Terhune

MEB

Franc Zabkar

Franc Zabkar

PCR

Similar threads