Page 1 of 1
Virtual Magnifying Glass 3.3
Posted: Thu Oct 04, 2007 2:41 am
by moongirl
Virtual Magnifying Glass 3.3
For closeups put a moveable magnifying glass on your screen.
A free, open source, screen magnifier, for Windows, Linux and FreeBSD.
Virtual Magnifying Glass is designed for visually-impaired and others who need to magnify a part of the screen. Unlike most similar programs it does not open a separate window for the magnification but instead puts a movable magnifying glass on screen.
Operating System: 32-bit MS Windows (95/98 ), All 32-bit MS Windows (95/98/NT/2000/XP), OS Portable (Source code to work with many OS platforms), FreeBSD, Linux
License: GNU General Public License (GPL)
Category: Graphics, Other/Nonlisted Topic
http://magnifier.sourceforge.net/
Posted: Thu Oct 04, 2007 5:38 am
by battye
There is also lesser version of this program already built into Windows. To use the MS Magnifying Glass (in Windows XP) go to: Start -> All programs -> Accessories -> Accessibility -> Magnifyer
It will then appear at the top of the screen, magnifying the area where your mouse is placed.
Posted: Sat Oct 06, 2007 1:44 am
by moongirl
Posted: Thu Oct 11, 2007 3:58 am
by moongirl
Speaking of "elementary, my dear Watson"...
DrWtsn32.log is a diagnostic file created by a Microsoft program, DrWatson,
which appends to the file diagnostics when errors occur.
Interpreting the DrWtsn32.log File to Identify Program Crash Data
Dr. Watson for Windows NT is a program error debugger that detects and diagnoses program errors, and then logs the resulting diagnostic information. In the event of a program error, Dr. Watson starts automatically and, if configured appropriately, creates User.dmp and DrWtsn32.log files. These files are located in the %SystemRoot% folder. The DrWtsn32.log file is appended each time a program error occurs; the User.dmp file is overwritten.
This article describes how to review the DrWtsn32.log file to identify the program that crashed, when the crash occurred, the assembly instruction where the crash occurred, and a listing of functions involved in the crash.
http://support.microsoft.com/kb/246084
There is a comprehensive article at the above link.
