9 An error occurred while loading the file %1.\n\n
10 The file is damaged or is not a valid System Information log file.
11 An error occurred while loading one of the DLLs used by System Information Control. %1\n\nThe file %2 may be corrupted.
12 An error occurred while loading one of the DLLs used by System Information Control. %1\n\nThe file %2 could not be loaded. The file %3 may be corrupted.
13 You will not be able to load, save or print.
14 Not all system information will be collected.
15 Error information will be collected but not displayed.
16 Dr. Watson will not start.
17 System Information Control was unable to save the file %1.
18 Dr. Watson was unable to print the document.
19 The log path must be a fully-qualified path.
32 Saving results to log file directory...
33 (untitled)
34 %1%2 - Dr. Watson
35 Page %1!d!
62 %1 detected an error condition which was not handled by the application.
63 %1 used a system resource improperly.|%1 used an invalid or uninitialized "critical section".
64 %1 performed an invalid arithmetic operation.|%1 encountered an overflow during division.
65 %1 detected a programming error within itself.|%1 encountered a debugging single-step exception.
67 %1 detected a programming error within itself.|%1 encountered a hard-coded debugging breakpoint.
68 %1 performed an invalid arithmetic operation.|%1 detected an arithmetic overflow.
69 %1 performed an invalid memory access.|%1 attempted to access memory beyond that which it has allocated.
70 %1 attempted to execute an invalid instruction.
71 %1 performed an invalid arithmetic operation.|%1 attempted to use a nonexistent math coprocessor.
73 %1 performed an invalid memory access.|%1 instructed the math coprocessor to access invalid memory.
75 %1 performed an invalid memory access.|%1 attempted to access memory that has already been freed.
76 The application overflowed its temporary memory area.|The application overflowed its stack. This is typically caused by unrestricted recursion or an exception inside an exception handler.
77 %1 accessed memory improperly or encountered some nonspecific error.|%1 used an uninitialized variable, attempted to access memory or a DLL that has been freed, or encountered some other nonspecific error.
78 %1 attempted to access memory that does not exist.
80 %1 performed an invalid arithmetic operation.|%1 encountered an error in its use of the math coprocessor.
96 %1 used an uninitialized function pointer.
97 %1 or one of its DLLs corrupted the application's private memory.|%1 or one of its DLLs corrupted the application heap.
98 %1 attempted to use memory which has already been freed.|%1 attempted to use a freed heap block.
99 The application or one of its DLLs used a function pointer variable which was uninitialized or freed.
100 The application or one of its DLLs may have overflowed an internal temporary buffer.
101 The application or one of its DLLs used an uninitialized function pointer variable or attempted to use a DLL which has already been freed.
102 %1 performed an invalid memory access.|%1 attempted to use a null data pointer variable.
103 %1 performed an invalid memory access.|%1 attempted to write to memory that does not exist or is read-only. It may be using an uninitialized variable, or it may be attempting to access memory after having freed it.
104 %1 performed an invalid memory access.|%1 attempted to read from memory that does not exist. It may be using an uninitialized variable, or it may be attempting to access memory after having freed it.
105 The application overflowed its stack. Use the mkcompat program to give the application a larger stack.
112 Dr. Watson found nothing obviously unusual.
113 %1 has altered Windows system files.
114 If the Taskbar is behaving strangely, try exiting %1.
115 See http://www.microsoft.com/kb/peropsys/win95/q136475.htm for more information.
116 Dr. Watson recommends removing SMARTDRV.EXE from your Autoexec.bat to make more memory available to Windows.
117 The file mmsystem.dll is not listed in the [boot] section of system.ini. Multimedia services may be erratic.
118 %1 does not appear to be a Windows 95 Plug-and-Play compatible display driver.
119 Critical system memory memory appears to have been corrupted. Save your work and restart the computer.
128 Dr. Watson's Remarks:
129 User's Remarks:
144 Program
145 Type
146 Path
147 System module
148 Modified by
149 Hook type
150 Hooked by
151 Application
152 DLL path
153 Application path
154 Loaded from
155 Driver
156 Description
157 Name
158 Command
159 Likely path
160 Address
161 Date
162 Manufacturer
163 Part of
164 Version
165 System Information
166 There are no items to display in this category.
177 %1 %2 %3
184 Normal mode
185 Safe mode
186 Safe mode w/network
192 Clean install using
193 Upgrade using
195 network
196 CD
197 Floppy
198 Full Floppy
199 floppy
200 Select CD
201 OEM
202 OEM floppy
203 OEM CD
204 Microsoft Internal
205 Full CD
206 Web
207 MSDN CD
208 Full OEM CD
209 OEM Preinstall Kit
210 Analyzing collected information...
211 Collecting information about your system...
212 Building task list...
213 Loading startup groups...
214 Checking system files for modifications...
215 Collecting information about system hooks...
216 Collecting information about kernel-mode drivers...
217 Collecting information about user-mode drivers...
218 Collecting information about MS-DOS drivers...
219 Collecting information about 32-bit modules...
220 Collecting information about 16-bit modules...
225 Building trace file...
227 Tasks
229 Startup
230 Patches
231 Hooks
232 Kernel Drivers
233 User Drivers
234 MS-DOS Drivers
235 Modules
236 16-bit Modules
242 Summary/Overview
243 System Information
244 Task list
245 Startup Items
246 System Patches
247 System Hooks
248 Kernel Drivers
249 User-Mode Drivers
250 MS-DOS Drivers
251 32-bit Modules
252 16-bit Modules
257 Details
259 The following applications were running at the time the system snapshot was taken.
261 The following applications are registered to run when the system starts.
262 The following system modules have been modified ("patched") in memory.
263 The following modules have intercepted ("hooked") various aspects of the system.
264 The following Windows kernel-mode drivers are installed.
265 The following Windows user-mode drivers are installed.
266 The following MS-DOS drivers are installed.
267 The following 32-bit modules were in use by the application when it encountered an error.
268 The following 16-bit modules were in memory when the snapshot was taken. Note that this information may be duplicated elsewhere.
274 Message Filter
275 Journal Record
276 Journal Playback
277 Keyboard
278 GetMessage
279 Window Procedure
280 CBT
281 System MsgFilter
282 Mouse
283 Hardware
284 Debug
285 Shell
286 Foreground Idle
287 Window Procedure Result
290 Startup Group
291 Common Startup Group
292 Win.ini
293 Registry (Per-User Run)
294 Registry (Machine Run)
295 Registry (Per-User Service)
296 Registry (Machine Service)
306 Uptime: %1!d!:%2!02d!:%3!02d!:%4!02d!
307 %1!d!MB RAM
308 %1!d!%% system resources free
309 Virtual memory is disabled
310 Custom
311 Windows-managed
312 %1 swap file on drive %2!c! (%3!d!MB free)
313 Temporary files on drive %1!c! (%2!d!MB free)
314 On "%1" as "%2"
322 Device driver
323 TSR program
338 VMM |Virtual Machine Manager
339 VPOWERD |Advanced Power Management driver
340 ENABLE |Accessibility driver
341 VKD |Keyboard driver
342 VFLATD |Linear aperture video driver
343 BIOS |Plug and Play BIOS driver
344 VDD |Display driver
345 VMOUSE |Mouse driver
346 EBIOS |Extended BIOS driver
347 VSHARE |File sharing driver
348 VWIN32 |Win32 subsystem driver
349 VFBACKUP|Floppy backup helper driver
350 VCOMM |Communications port Plug and Play driver
