When I got my Dell, it had an outlook add-in installed as part of a software
package Dell had pre-installed. It made my outlook crash regularly.
That add-in was called cyberlink and was part of Dell's "Media Direct"
package, but other add-ins are known to crash outlook. Have a look at this
page which documents some of the known issues:
http://www.slipstick.com/outlook/ol2007/known_issues.htm
hth,
Chip
-----Original Message-----
From: Heidi [mailto:[email protected]]
Sent: Saturday, May 01, 2010 1:30 PM
To: 'Barry Toner'; [email protected]
Subject: RE: WE goes silent in Outlook
I have experienced this, outlook 07 crashes a lot with WE 7.1 To the point
where outlook automatically asked to do diagnostics. One place I had found
it in the past was when selecting through. If I went to open a contact
outlook would crash. Now I bring up the call box from the menus and the
numbers I am looking for are easily retrievable.
I guess what I am saying is that I use outlook a great deal both at work and
home and I crash a great deal at work. At home for a while I was using
VISTA crashed as well. I have upgraded to windows 7 64 bit and it does seem
like WE is working better.
-----Original Message-----
From: Barry Toner [mailto:[email protected]]
Sent: Saturday, May 01, 2010 12:31 PM
To: [email protected]
Subject: WE goes silent in Outlook
Hi all,
I've noticed in Outlook 2K7 with the Beta that if I maxamise the screen, or
add a mail to the Junk folder or a few other things WE goes silent. As a
workaround I go to the desktop and get speech back. I can tehn alt tab back
to outlook where it's speaking again.
Anyone else?
Barry Toner
BCS Belfast Branch
YPG Representative & Disability Group
http://www.bcs.org/server.php?show=nav.10444
Contact me @
Professional: [email protected]
Personal Email: [email protected]
MSN/Live: [email protected]
AIM/FB: [email protected]
TWITTER: dj_paddy
Skype: djpaddy
Mobile: (UK) +44 (0) 7921 611 253
__________ Information from ESET Smart Security, version of virus signature
database 5077 (20100501) __________
The message was checked by ESET Smart Security.
http://www.eset.com
If you reply to this message it will be delivered to the original sender
only. If your reply would benefit others on the list and your message is
related to GW Micro, then please consider sending your message to
[email protected] so the entire list will receive it.
GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can
manage your list subscription at http://www.gwmicro.com/listserv.
If you reply to this message it will be delivered to the original sender
only. If your reply would benefit others on the list and your message is
related to GW Micro, then please consider sending your message to
[email protected] so the entire list will receive it.
GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can
manage your list subscription at http://www.gwmicro.com/listserv.
If you reply to this message it will be delivered to the original sender only.
If your reply would benefit others on the list and your message is related to
GW Micro, then please consider sending your message to [email protected] so
the entire list will receive it.
GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage
your list subscription at http://www.gwmicro.com/listserv.
Thanks Alan, I received it, and was able eventually to cause an error by
continuing to move around in that document.
However, I'm using a different version of window eyes than you are, and in
my version, the error (or the error handler), caused a complete crash, so I
wasn't able to tell what feature of Word is causing this.
I'll fix it by just handling any error that happens, and ignoring the error,
but I sure would have liked to know what was going on.
I have a hunch, since this document was full of pictures, I managed to move
the cursor into a picture, where paragraphs and text and so on technically
don't exist, and so my script trying to look for all those, ended up causing
an error. however, it's only a hunch.
thanks again, and I'll let you know when the next version is up.
Chip
_____
From: Alan R. Downing [mailto:[email protected]]
Sent: Sunday, January 24, 2010 2:44 PM
To: 'Allison and Chip Orange'
Subject: RE: [Error Report] MS Word.vbs 1.40
I just sent you the data that I was attempting to read when the error
occurred.
Alan R. Downing
Phoenix, AZ
From: Allison and Chip Orange [mailto:[email protected]]
Sent: Sunday, January 24, 2010 12:26 PM
To: 'Alan R. Downing'
Subject: RE: [Error Report] MS Word.vbs 1.40
ok, thanks. if you could forward it to me (the message and it's
attachment), since it doesn't appear to be personal, it would be a big help.
thanks.
Chip
_____
From: Alan R. Downing [mailto:[email protected]]
Sent: Sunday, January 24, 2010 2:06 PM
To: 'Allison and Chip Orange'
Subject: RE: [Error Report] MS Word.vbs 1.40
Hi Chip,
The only thing that I really know is that it was supposed to be data on a
UPS unit from Dell. It appeared to be in Word format, but I'm not
completely sure about that. I don't think that it was any kind of form
though.
Alan R. Downing
Phoenix, AZ
From: Allison and Chip Orange [mailto:[email protected]]
Sent: Sunday, January 24, 2010 11:26 AM
To: [email protected]
Subject: RE: [Error Report] MS Word.vbs 1.40
thanks for sending me your comments with the error.
it's not one I have seen before; could it be the attachment you were trying
to read was a Word "form" (where you can only fill-in data in fields, and
you're locked out of the rest of the document?).
thanks.
Chip
_____
From: [email protected] [mailto:[email protected]]
Sent: Sunday, January 24, 2010 1:17 PM
To: [email protected]
Subject: [Error Report] MS Word.vbs 1.40
User Comments: I was just attempting to read an email attachment when this
error occurred.
An error occurred in script MS Word.vbs at 11:16:03 AM on Sunday, January
24, 2010.
Name: MS Word.vbs
Version: 1.40
Source: Microsoft Word
Description: This method or property is not available because typing is not
currently allowed for reading.
Column: 1
Line: 670
Path: C:\Users\Alan\AppData\Roaming\GW Micro\Window-Eyes\Users\Default
Error Code: 800A11FD
Script Context: if not sel.paragraphFormat.spaceAfterAuto then
Active Window Overlap Class: OpusApp
Active Window Title: UPS Units (2) [Compatibility Mode] - Microsoft Word
non-commercial use
Active Window Module: WWLIB
Active Window Class: OpusApp
Active Window Original Class: OpusApp
Active Window Type: 1
Active Window Original Type: 1
Active Window Is Valid: True
Active Window Set File: word.000
Focused Window Overlap Class: _WwG
Focused Window Module: WWLIB
Focused Window Class: _WwG
Focused Window Original Class: _WwG
Focused Window Type: 11
Focused Window Original Type: 11
Focused Window Is Valid: True
Window-Eyes Application Path: C:\Program Files\GW Micro\Window-Eyes
Window-Eyes User Profile Path: C:\Users\Alan\AppData\Roaming\GW
Micro\Window-Eyes\Users\Default\
Window-Eyes Version: 7.11
Window-Eyes Language: 0
Active Synthesizer: TripleTalk USB (USB)
Active Braille Display: None
Run in System Tray: False
Run at Login Screen: True
OS Version: 6.0 (6002) SP: 2.0
WSH Version: VBScript 5.8.18702
Internet Explorer: 8.0.6001.18882
GW Toolkit: 8.1.1
XML Language: 1033
System Start Time: 1/24/2010 6:12:10 AM
Total Disk Space: 309.28GB
Free Disk Space: 225.25GB
Total Memory: 2.14GB
Available Memory: 774.16MB
Resolution: 1680x1050 (32bit)
Process Information:
System Idle Process ID:0, CPU Time:34312.79, MEM:0MB, VM:0MB
System ID:4, CPU Time:272.8, MEM:50.6MB, VM:0MB
smss.exe ID:468, CPU Time:0.05, MEM:0.5MB, VM:0MB
csrss.exe ID:600, CPU Time:2.43, MEM:3.9MB, VM:0MB
wininit.exe ID:656, CPU Time:0.16, MEM:3MB, VM:0MB
csrss.exe ID:664, CPU Time:7.75, MEM:16.2MB, VM:0MB
services.exe ID:704, CPU Time:17.66, MEM:5.7MB, VM:0MB
lsass.exe ID:716, CPU Time:5.83, MEM:2.7MB, VM:0MB
lsm.exe ID:724, CPU Time:0.17, MEM:3.2MB, VM:0MB
svchost.exe ID:876, CPU Time:197.65, MEM:6.2MB, VM:0MB
svchost.exe ID:992, CPU Time:3.04, MEM:6.5MB, VM:0MB
winlogon.exe ID:1092, CPU Time:0.37, MEM:4.5MB, VM:0MB
svchost.exe ID:1140, CPU Time:7.02, MEM:10MB, VM:0MB
svchost.exe ID:1180, CPU Time:84.15, MEM:74MB, VM:0.1MB
svchost.exe ID:1208, CPU Time:14.71, MEM:18.4MB, VM:0MB
audiodg.exe ID:1300, CPU Time:24.59, MEM:12.2MB, VM:0MB
svchost.exe ID:1328, CPU Time:0.28, MEM:5MB, VM:0MB
SLsvc.exe ID:1380, CPU Time:1.15, MEM:3MB, VM:0MB
svchost.exe ID:1412, CPU Time:1.64, MEM:10.9MB, VM:0MB
LBTSERV.EXE ID:1712, CPU Time:0.05, MEM:2.9MB, VM:0MB
svchost.exe ID:1844, CPU Time:11.03, MEM:12.1MB, VM:0MB
spoolsv.exe ID:392, CPU Time:2.92, MEM:10MB, VM:0MB
taskeng.exe ID:384, CPU Time:0.14, MEM:4.7MB, VM:0MB
taskeng.exe ID:452, CPU Time:0.47, MEM:9.5MB, VM:0MB
svchost.exe ID:864, CPU Time:3.28, MEM:9.7MB, VM:0MB
ASTSRV.EXE ID:2196, CPU Time:0.02, MEM:2.1MB, VM:0MB
BcmSqlStartupSvc.exe ID:2224, CPU Time:0.2, MEM:5.8MB, VM:0MB
svchost.exe ID:2252, CPU Time:0.05, MEM:3.2MB, VM:0MB
dlcxcoms.exe ID:2276, CPU Time:0.2, MEM:4.4MB, VM:0MB
dlsdbnt.exe ID:2316, CPU Time:0.05, MEM:2.2MB, VM:0MB
DQLWinService.exe ID:2356, CPU Time:0.02, MEM:2.6MB, VM:0MB
IAANTmon.exe ID:2392, CPU Time:0.02, MEM:2.1MB, VM:0MB
McSACore.exe ID:2448, CPU Time:2.39, MEM:4.5MB, VM:0MB
McProxy.exe ID:2532, CPU Time:0.39, MEM:0.6MB, VM:0MB
rundll32.exe ID:2564, CPU Time:0.03, MEM:3.5MB, VM:0MB
Mcshield.exe ID:2604, CPU Time:96.74, MEM:52.5MB, VM:0.1MB
MpfSrv.exe ID:2748, CPU Time:4.18, MEM:5MB, VM:0MB
msksrver.exe ID:2780, CPU Time:6.58, MEM:11.7MB, VM:0MB
svchost.exe ID:2808, CPU Time:0.11, MEM:3.7MB, VM:0MB
dwm.exe ID:3052, CPU Time:0.59, MEM:3.6MB, VM:0MB
explorer.exe ID:3084, CPU Time:71.71, MEM:40.3MB, VM:0MB
SeaPort.exe ID:3548, CPU Time:0.17, MEM:5.6MB, VM:0MB
sprtsvc.exe ID:3612, CPU Time:0.22, MEM:1.1MB, VM:0MB
sqlbrowser.exe ID:3632, CPU Time:0.06, MEM:2.8MB, VM:0MB
sqlwriter.exe ID:3648, CPU Time:0.03, MEM:4.1MB, VM:0MB
stacsv.exe ID:3676, CPU Time:6.57, MEM:4.4MB, VM:0MB
svchost.exe ID:3744, CPU Time:0.19, MEM:5.1MB, VM:0MB
svchost.exe ID:3784, CPU Time:0, MEM:1.6MB, VM:0MB
weserv.exe ID:3852, CPU Time:0.17, MEM:3.9MB, VM:0MB
WLIDSVC.EXE ID:3988, CPU Time:2.9, MEM:7.4MB, VM:0MB
SearchIndexer.exe ID:4028, CPU Time:29, MEM:42.2MB, VM:0.1MB
WUDFHost.exe ID:2132, CPU Time:0.45, MEM:4.4MB, VM:0MB
LBTWiz.exe ID:2796, CPU Time:0.09, MEM:4.2MB, VM:0MB
IAAnotif.exe ID:2960, CPU Time:0.53, MEM:5.7MB, VM:0MB
issch.exe ID:2968, CPU Time:0.02, MEM:2.9MB, VM:0MB
CCU_TrayIcon.exe ID:2948, CPU Time:0.08, MEM:4.7MB, VM:0MB
IntelHCTAgent.exe ID:1604, CPU Time:3.14, MEM:8.6MB, VM:0MB
XAudio.exe ID:2904, CPU Time:0.14, MEM:2MB, VM:0MB
dlpwdnt.exe ID:3048, CPU Time:0.08, MEM:3.2MB, VM:0MB
dlcxmon.exe ID:3036, CPU Time:0.16, MEM:5.1MB, VM:0MB
memcard.exe ID:2144, CPU Time:12.89, MEM:5.2MB, VM:0MB
WLIDSVCM.EXE ID:3768, CPU Time:0.03, MEM:2.2MB, VM:0MB
DMXLauncher.exe ID:3172, CPU Time:0.05, MEM:4.8MB, VM:0MB
Acrotray.exe ID:3196, CPU Time:0.98, MEM:5.8MB, VM:0MB
mcagent.exe ID:4120, CPU Time:0.58, MEM:0.4MB, VM:0MB
mcmscsvc.exe ID:4176, CPU Time:7.55, MEM:5.7MB, VM:0MB
rundll32.exe ID:4436, CPU Time:0.09, MEM:4.4MB, VM:0MB
mobsync.exe ID:4460, CPU Time:4.82, MEM:7.7MB, VM:0MB
sttray.exe ID:4468, CPU Time:0.11, MEM:5.7MB, VM:0MB
dlupdr.exe ID:4496, CPU Time:0.08, MEM:3.7MB, VM:0MB
ehtray.exe ID:4540, CPU Time:0.05, MEM:2.5MB, VM:0MB
msnmsgr.exe ID:4572, CPU Time:6.1, MEM:26.6MB, VM:0MB
wineyes.exe ID:4588, CPU Time:352.44, MEM:86.3MB, VM:0.2MB
DSAgnt.exe ID:4696, CPU Time:6.71, MEM:10.3MB, VM:0MB
BTTray.exe ID:4732, CPU Time:3, MEM:8.7MB, VM:0MB
SetPoint.exe ID:4764, CPU Time:1.25, MEM:9.6MB, VM:0MB
ehmsas.exe ID:5496, CPU Time:0.42, MEM:4.1MB, VM:0MB
wmpnscfg.exe ID:5624, CPU Time:0.06, MEM:4.9MB, VM:0MB
wmpnetwk.exe ID:5736, CPU Time:1.31, MEM:12.5MB, VM:0MB
rundll32.exe ID:5744, CPU Time:0.06, MEM:5.6MB, VM:0MB
weli.exe ID:5800, CPU Time:0.02, MEM:0.9MB, VM:0MB
bdisplay.exe ID:4744, CPU Time:0.03, MEM:3.4MB, VM:0MB
wecom.exe ID:6124, CPU Time:0.03, MEM:4.6MB, VM:0MB
KHALMNPR.exe ID:2976, CPU Time:0.33, MEM:6.1MB, VM:0MB
BTStackServer.exe ID:1820, CPU Time:0.44, MEM:8.4MB, VM:0MB
CCU_Engine.exe ID:6040, CPU Time:0.23, MEM:5.7MB, VM:0MB
FNPLicensingService.exe ID:3972, CPU Time:0.42, MEM:2.5MB, VM:0MB
wlcomm.exe ID:3200, CPU Time:0.75, MEM:12.1MB, VM:0MB
AlertService.exe ID:1908, CPU Time:0.08, MEM:4.7MB, VM:0MB
mcsysmon.exe ID:4172, CPU Time:1.28, MEM:4MB, VM:0MB
McNASvc.exe ID:7180, CPU Time:7.8, MEM:7.9MB, VM:0MB
svchost.exe ID:6212, CPU Time:118.61, MEM:5.6MB, VM:0MB
weproxea.exe ID:5560, CPU Time:0.03, MEM:3.1MB, VM:0MB
iexplore.exe ID:2192, CPU Time:2.37, MEM:17.7MB, VM:0MB
iexplore.exe ID:5972, CPU Time:11.12, MEM:48.8MB, VM:0MB
FlashUtil10d.exe ID:8076, CPU Time:0.27, MEM:5.7MB, VM:0MB
OUTLOOK.EXE ID:4036, CPU Time:12.78, MEM:115.4MB, VM:0.1MB
SearchFilterHost.exe ID:7380, CPU Time:0.17, MEM:6.8MB, VM:0MB
WINWORD.EXE ID:6188, CPU Time:8.6, MEM:70.4MB, VM:0MB
OfficeLiveSignIn.exe ID:520, CPU Time:0.05, MEM:5.5MB, VM:0MB
SearchProtocolHost.exe ID:7888, CPU Time:0.19, MEM:3.5MB, VM:0MB
WmiPrvSE.exe ID:5556, CPU Time:0.06, MEM:5.4MB, VM:0MB
WmiPrvSE.exe ID:2496, CPU Time:0.11, MEM:8.1MB, VM:0MB
Appended Details:
