"around the world in a ford GT" thread locked again


Status
Not open for further replies.

Silverbullitt

GT Owner
Mar 3, 2006
1,757
Lago Vista, TX
Sounds like FINGER IN THE WRONG HOLE problemo. Ha

Opie and Anthony call it the "Glory Hole"
 

Cobrar

GT Owner
Mark II Lifetime
Jun 24, 2006
4,018
Metro Detroit
The last time the thread got close it was immediately after the thread starter posted in it while I was driving a truck in the middle of Wyoming (which is why there are no entries for 3 days).

I'm thinkin' Dick Cheney, from an undisclosed location.
 

Empty Pockets

ex-GT Owner
Mark IV Lifetime
Le Mans 2010 Supporter
Oct 18, 2006
1,362
Washington State
I recommend this as a starting place.....

*******************************************************

Event Viewer
In Windows XP, an event is any significant occurrence in the system or in a program that requires users to be notified, or an entry added to a log. The Event Log Service records application, security, and system events in Event Viewer. With the event logs in Event Viewer, you can obtain information about your hardware, software, and system components, and monitor security events on a local or remote computer. Event logs can help you identify and diagnose the source of current system problems, or help you predict potential system problems.
Event Log Types
A Windows XP-based computer records events in the following three logs:

Application log

The application log contains events logged by programs. For example, a database program may record a file error in the application log. Events that are written to the application log are determined by the developers of the software program.
Security log

The security log records events such as valid and invalid logon attempts, as well as events related to resource use, such as the creating, opening, or deleting of files. For example, when logon auditing is enabled, an event is recorded in the security log each time a user attempts to log on to the computer. You must be logged on as Administrator or as a member of the Administrators group in order to turn on, use, and specify which events are recorded in the security log.
System log

The system log contains events logged by Windows XP system components. For example, if a driver fails to load during startup, an event is recorded in the system log. Windows XP predetermines the events that are logged by system components.

Back to the top
How to View Event Logs
To open Event Viewer, follow these steps:

Click Start, and then click Control Panel. Click Performance and Maintenance, then click Administrative Tools, and then double-click Computer Management. Or, open the MMC containing the Event Viewer snap-in.
In the console tree, click Event Viewer.

The Application, Security, and System logs are displayed in the Event Viewer window.

Back to the top
How to View Event Details
To view the details of an event, follow these steps:

Click Start, and then click Control Panel. Click Performance and Maintenance, then click Administrative Tools, and then double-click Computer Management. Or, open the MMC containing the Event Viewer snap-in.
In the console tree, expand Event Viewer, and then click the log that contains the event that you want to view.
In the details pane, double-click the event that you want to view.

The Event Properties dialog box containing header information and a description of the event is displayed.

To copy the details of the event, click the Copy button, then open a new document in the program in which you want to paste the event (for example, Microsoft Word), and then click Paste on the Edit menu.

To view the description of the previous or next event, click the UP ARROW or DOWN ARROW.

Back to the top
How to Interpret an Event
Each log entry is classified by type, and contains header information, and a description of the event.
Event Header
The event header contains the following information about the event:

Date

The date the event occurred.
Time

The time the event occurred.
User

The user name of the user that was logged on when the event occurred.
Computer

The name of the computer where the event occurred.
Event ID

An event number that identifies the event type. The Event ID can be used by product support representatives to help understand what occurred in the system.
Source

The source of the event. This can be the name of a program, a system component, or an individual component of a large program.
Type

The type of event. This can be one of the following five types: Error, Warning, Information, Success Audit, or Failure Audit.
Category

A classification of the event by the event source. This is primarily used in the security log.

Event Types
The description of each event that is logged depends on the type of event. Each event in a log can be classified into one of the following types:

Information

An event that describes the successful operation of a task, such as an application, driver, or service. For example, an Information event is logged when a network driver loads successfully.
Warning

An event that is not necessarily significant, however, may indicate the possible occurrence of a future problem. For example, a Warning message is logged when disk space starts to run low.
Error

An event that describes a significant problem, such as the failure of a critical task. Error events may involve data loss or loss of functionality. For example, an Error event is logged if a service fails to load during startup.
Success Audit (Security log)

An event that describes the successful completion of an audited security event. For example, a Success Audit event is logged when a user logs on to the computer.
Failure Audit (Security log)

An event that describes an audited security event that did not complete successfully. For example, a Failure Audit may be logged when a user cannot access a network drive.

Back to the top
How to Find Events in a Log
The default view of event logs is to list all its entries. If you want to find a specific event, or view a subset of events, you can either search the log, or you can apply a filter to the log data.
How to Search for a Specific Log Event
To search for a specific log event, follow these steps:

Click Start, and then click Control Panel. Click Performance and Maintenance, then click Administrative Tools, and then double-click Computer Management. Or, open the MMC containing the Event Viewer snap-in.
In the console tree, expand Event Viewer, and then click the log that contains the event that you want to view.
On the View menu, click Find.
Specify the options for the event that you want to view in the Find dialog box, and then click Find Next.

The event that matches your search criteria is highlighted in the details pane. Click Find Next to locate the next occurrence of an event as defined by your search criteria.
How to Filter Log Events
To filter log events, follow these steps:

Click Start, and then click Control Panel. Click Performance and Maintenance, then click Administrative Tools, and then double-click Computer Management. Or, open the MMC containing the Event Viewer snap-in.
In the console tree, expand Event Viewer, and then click the log that contains the event that you want to view.
On the View menu, click Filter.
Click the Filter tab (if it is not already selected).
Specify the filter options that you want, and then click OK.

Only events that match your filter criteria are displayed in the details pane.

To return the view to display all log entries, click Filter on the View menu, and then click Restore Defaults.
Back to the top
How to Manage Log Contents
By default, the initial maximum of size of a log is set to 512 KB, and when this size is reached, new events overwrite older events as needed. Depending on your requirements, you can change these settings, or clear a log of its contents.
How to Set Log Size and Overwrite Options
To specify log size and overwrite options, follow these steps:

Click Start, and then click Control Panel. Click Performance and Maintenance, then click Administrative Tools, and then double-click Computer Management. Or, open the MMC containing the Event Viewer snap-in.
In the console tree, expand Event Viewer, and then right-click the log in which you want to set size and overwrite options.
Under Log size, type the size that you want in the Maximum log size box.
Under When maximum log size is reached, click the overwrite option that you want.
If you want to clear the log contents, click Clear Log.
Click OK.

How to Archive a Log
If you want to save your log data, you can archive event logs in any of the following formats:

Log-file format (.evt)
Text-file format (.txt)
Comma-delimited text-file format (.csv)

To archive a log, follow these steps:

Click Start, and then click Control Panel. Click Performance and Maintenance, then click Administrative Tools, and then double-click Computer Management. Or, open the MMC containing the Event Viewer snap-in.
In the console tree, expand Event Viewer, and then right-click the log in which you want to archive, and then click Save Log File As.
Specify a file name and location where you want to save the file. In the Save as type box, click the format that you want, and then click Save.

The log file is saved in the format that you specified.

*******************************************************

Wouldn't it be a lot quicker and easier for someone to just have wunna their 4 or 5-yr-old grandkids come over and 'splain it via show 'n' tell? 'Tis fer me...
 

GTdrummer

GT Owner
Mark II Lifetime
Le Mans 2010 Supporter
Mar 13, 2010
2,104
Richmond Virginia
My IT guy here at work says although little known, if a thread contains a certain number of thumbs up inserts it can automatically lock.
 

red gt 1442

GT Owner
Mark IV Lifetime
Dec 23, 2005
754
NY Metro Area
Sounds like FINGER IN THE WRONG HOLE problemo. Ha

I have to agree with you.....:lol.........Tomi, was sorry not to see you and Sue...:shrug..... You missed a really great one....:driving:....And we missed you two.....:bow....Hope everything is good...:thumbsup.....will look forward to the next one with both of you.:banana


Gino and Linda
 

THamonGT

GT
Mark IV Lifetime
Le Mans 2010 Supporter
After finally getting home, I hope you found things OK with no problems. Who would ever think that storm would do so much damage on the East Coast. We only have those on the Gulf Coast and we're past due here with the heat and warm water. Sorry we had to back our on the Rally at the last minute. We'll be there next year for sure. Thanks Gino for the kind words. Tomy & Sue
 

Nardo GT

Well-known member
Jul 15, 2006
2,300
Texas
My IT guy here at work says although little known, if a thread contains a certain number of thumbs up inserts it can automatically lock.

"Thumbsup" where and "automatically lock" what?? Settin' u guys up here.......
 

daytrayd

GT Owner
Mark II Lifetime
Apr 23, 2010
557
Austin, TX
What are the chances someone else has Joeys login info and closed it using his account?? Im calling it.
 

Nardo GT

Well-known member
Jul 15, 2006
2,300
Texas
What are the chances someone else has Joeys login info and closed it using his account?? Im calling it.

But why???
 

dbk

The Favor Factory™
Staff member
Le Mans 2010 Supporter
Jul 30, 2005
15,189
Metro Detroit
But why???

Maybe to draw more attention to the original thread.

Anyways, I'm locking THIS thread.
 

dbk

The Favor Factory™
Staff member
Le Mans 2010 Supporter
Jul 30, 2005
15,189
Metro Detroit
By the way, according to the vBulletin support staff:

Wayne Luke said:
Unless you allow people to close the random threads of other users in the Usergroup or Forum Permissions, the only other person who could have closed it would be the thread starter. If it is happening randomly, tell the user to stop double-clicking on the thread's status icon as that will toggle the open or close status.

and

1) If a Moderator closed the thread (and is NOT the thread owner) then it would show in the Moderator log.
2) If you have the thread/open close option checked for regular users, for their own threads, then it can only be the thread owner opening or closing the thread.

These are the only way that threads can be opened and closed. In the case of the thread owner opening and locking their thread, then it is not logged in the Moderator or Admin control logs. Therefore, if you have a thread that is being closed and it wasn't done by a moderator (doesn't show in the moderator log) then the logical answer is that the thread owner is doing it.

Wayne Luke said:
Without the use of addons, only the following people can be given permission to open/close threads.

Adminstrators
Super Moderators
Moderators
Thread Owner

The first three will be logged and show when you edit the page or view the logs. The last one won't be. If the thread is being closed, it is someone on that user's account. If it is happening randomly then ask the user if they double click the status icons ever. This toggles to open/close state.
 
Status
Not open for further replies.