Re: email

2019-11-13 Thread peter Chin via Talk

Hello Rod,

Thanks so much for your instructions. will try it.



-Original Message- 
From: Rod Hutton via Talk

Sent: Wednesday, November 13, 2019 11:29 AM
To: Window-Eyes Discussion List
Cc: Rod Hutton
Subject: RE: email

Hi Peter,

Incidentally, what you actually pasted into your message to the list was the 
complete text of the app.

How you got it, makes me scratch my head in puzzlement.
What we would really need in order to help is the error report.
This report would be generated if you press the correct button in the dialog 
precisely when the error dialog appears.

You would then find the report in the Window-Eyes profile folder.
It could be most easily found if you sort the profile folder by date, since 
the report is a text file having the name of the app.
You find the profile folder by choosing the Explore profile folder in the 
File menu of the control panel.
You would then just open the file in Notepad, select its contents and paste 
it into a message to the list.


Hth,

Rod

Sent from Outlook for Windows

-Original Message-
From: Talk  On 
Behalf Of peter Chin via Talk

Sent: November 12, 2019 9:14 PM
To: David via Talk 
Cc: peter Chin 
Subject: Re: email

Hello Tom,

I guess you are right and in the end I will have to follow his advice. I did
include a copy of the error message in my last message. I pasted it below my
message after the row of dashes. The error message only occurs after I have
pressed Control+n for writing a new message, then  Alt+s to send it. It does
not occur if I reply to a message.

Thanks for trying to help.

-Original Message- 
From: Tom Kingston via Talk

Sent: Tuesday, November 12, 2019 9:03 AM
To: David via Talk
Cc: Tom Kingston
Subject: Re: email

Peter,

I would do as David says below. If nothing fixes it just copy and paste
the error message here. If nothing else we can just stick an error check
on the line and tell it to continue and ignore the message. But knowing
the error might allow us to fix it even though we're not using the
program and script.

Regards,
Tom


On 11/10/2019 9:38 PM, David via Talk wrote:

What exactly is the error message saying? It usually will tell us what
does not work, and which line in the scripting code that failed. That
is, which step in the processing of the script that caused the error.
Unless we know that, it all will be a matter of more or less wild
guessing.


Now, if you happen to have the WEPM file for the script, you might want
to reinstall the app. If you have not made any user settings in the app,
if it offers such capability, I generally suggest first uninstalling the
app altogether, prior to attempting any reinstallation. Should you not
have the WEPM file, let us see if we might be able to help you out.


Again, wild guessing. Since it worked for you up till recently, it might
be due to some stuff going on with your computer. Try any Anti-ware you
have, like AntiSpyware or AntiVirus. Run a full scan of the system. See
if anything gets better. Sometimes I have seen certain Antiware block
files from one of the WinEyes apps, so if that is the case,
reinstallation will not help, since it only will reinstall the file that
is being blocked. In such cases, checking the blocking list in your
anti-ware might be a good idea.


Don't use the software in question, so sorry for not being able to give
you any further assistance here. Next time the error pops on you, would
you mind try copy it and let the list know what it says?



David

On 11/11/2019 3:18 AM, peter Chin via Talk wrote:

Hello all,

I made some mistakes in my last message so I am sending it again.
--
Hello all,

I use WLM as my e-mail client on a Windows 8.1 machine and WE 9.5.4. I
had

no trouble with this client until just over a month ago. Since then, I
get a

script error message after sending out an e-mail message.I get four
choices:

ignore error, stop App, edit App or restart App. I have to choose the
last

option if I want to continue using WLM. However, WLM doesn't function

properly unless I either reload WE or get out of WLM and then go back in.


I hope someone can suggest a remedy for this problem. For those who

understand script writing (which I don't), I include a copy of the script

which is supposed to be re-edited.



' For license information, see WindowsLiveMail License.txt which ships
with

this package.

Option Explicit


Dim myXMLFile : myXMLFile = ClientInformation.ScriptPath &

"\WindowsLiveMail.xml"

Dim myINIFile : myINIFile = ClientInformation.ScriptPath &

"\WindowsLiveMail.ini"

Dim myStrings : Set myStrings = Strings(myXMLFile)

Dim myScriptUpdateURL : myScriptUpdateURL =

"
http://www.gwmicro.com/scripts/windows_live_mail/xml
"

Dim checkedForUpdates : checkedForUpdates = False

Dim errorReportingEnabled : errorReportingEnabled = False

Dim SO_StandardHelpDialog : Set SO_StandardHelpDialog = Nothing

Dim

Re: email

2019-11-13 Thread Tom Kingston via Talk

Hi Peter,
Unfortunately Rod's suggestion to disable your braille display won't 
work. The function containing the conditional block that's throwing the 
error is run regardless because it's where it checks to see if you're 
using a braille display.
Fortunately all the conditional block is doing is seeing if you have a 
newer version of the GW toolkit, which you do. The change was made 
several versions back.
I believe the problem is due to a Windows security update that made type 
checking in VBScript more strict.
So I removed every instance of that conditional block along with the 
alternative code for the old version of the toolkit. I've built a new 
installer package: windowslivemail.wepm.

* First, close Windows Live Mail and uninstall the Windows Live Mail app!
Then activate the link below to download my new installer from my 
Dropbox. It should open a "Save as" dialog in your browser.

After downloading the file, focus it in explorer.
Press the Applications key to open the context menu.
Press R for properties.
Tab down to Unblock and press space to uncheck it.
Tab to the Apply button and press space.
Tab to the OK button and press space.
Now just press Enter on the wepm file to install it.
During the installation you should be prompted to accept the license 
agreement. I did this to let you and anyone else who uses it know that 
it's the new installer. I also changed the version from 1.3.2 to 1.3.3.


https://www.dropbox.com/s/32q204ix9ixmv2r/windowslivemail.wepm?dl=1

Let me know if you get any new errors. Now that I say this I should have 
changed the app so it would send error reports to me. Oh well. Too late 
now, which is to say, I'm lazy. Hahaahaaha!

Hth,
Tom


On 11/13/2019 5:30 AM, Rod Hutton via Talk wrote:

Hi Peter,

In the version of the Windows Live Mail app I have, which is 1.3.2, line 700 is 
working with braille.
Are you using a braille display?
If so, you can try disabling your braille display within Window-Eyes just for a 
bit in order to test if this could be causing the problem.

Hth,

Rod

Sent from Outlook for Windows

-Original Message-
From: Talk  On 
Behalf Of peter Chin via Talk
Sent: November 12, 2019 11:23 PM
To: peter Chin via Talk 
Cc: peter Chin 
Subject: Re: email

Hello David,

I hope the text given below the row of dashes what you were were asking for:
--
Windows Live Mail.VBS-Microsoft VB Script  runtime error
Line 700 column 2
Type mismatch 'sharedobject(...)'
<
0x800a000d





-Original Message-
From: David via Talk
Sent: Monday, November 11, 2019 10:38 AM
To: peter Chin via Talk
Cc: David
Subject: Re: email

What exactly is the error message saying? It usually will tell us what
does not work, and which line in the scripting code that failed. That
is, which step in the processing of the script that caused the error.
Unless we know that, it all will be a matter of more or less wild guessing.


Now, if you happen to have the WEPM file for the script, you might want
to reinstall the app. If you have not made any user settings in the app,
if it offers such capability, I generally suggest first uninstalling the
app altogether, prior to attempting any reinstallation. Should you not
have the WEPM file, let us see if we might be able to help you out.


Again, wild guessing. Since it worked for you up till recently, it might
be due to some stuff going on with your computer. Try any Anti-ware you
have, like AntiSpyware or AntiVirus. Run a full scan of the system. See
if anything gets better. Sometimes I have seen certain Antiware block
files from one of the WinEyes apps, so if that is the case,
reinstallation will not help, since it only will reinstall the file that
is being blocked. In such cases, checking the blocking list in your
anti-ware might be a good idea.


Don't use the software in question, so sorry for not being able to give
you any further assistance here. Next time the error pops on you, would
you mind try copy it and let the list know what it says?



David

On 11/11/2019 3:18 AM, peter Chin via Talk wrote:

Hello all,

I made some mistakes in my last message so I am sending it again.
--
Hello all,

I use WLM as my e-mail client on a Windows 8.1 machine and WE 9.5.4. I
had

no trouble with this client until just over a month ago. Since then, I
get a

script error message after sending out an e-mail message.I get four
choices:

ignore error, stop App, edit App or restart App. I have to choose the
last

option if I want to continue using WLM. However, WLM doesn't function

properly unless I either reload WE or get out of WLM and then go back in.


I hope someone can suggest a remedy for this problem. For those who

understand script writing (which I don't), I include a copy of the script

which is supposed to be re-edited.



' For license information, see WindowsLiveMail License.txt which ships
with

this pac

RE: I tone is very hard to use.

2019-11-13 Thread Darrell Bowles via Talk
If you are talking about an audio player, I suggest VLC medial player.


-Original Message-
From: Talk  On Behalf Of 
madl--- via Talk
Sent: Wednesday, November 13, 2019 9:44 AM
To: 'Window-Eyes Discussion List' 
Cc: m...@comcast.net
Subject: I tone is very hard to use. 

Hello all
As may you know, I-tone is not easy to use.  Does anyone can recommend player 
that is accessable and easy to use?  
Thanks for any help.
Moe 


 

___
Any views or opinions presented in this email are solely those of the author 
and do not necessarily represent those of Ai Squared.

For membership options, visit 
https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.window-eyes.com%2Foptions.cgi%2Ftalk-window-eyes.com%2Fdgbowles%2540msn.com&data=02%7C01%7C%7C71ea0d64c7f64965a36f08d76847e5e2%7C84df9e7fe9f640afb435%7C1%7C0%7C637092530310759666&sdata=EVrQRiubUl5Slq40ZRlVblSlw752HNBVf%2Fe7CxFaxDI%3D&reserved=0.
For subscription options, visit 
https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.window-eyes.com%2Flistinfo.cgi%2Ftalk-window-eyes.com&data=02%7C01%7C%7C71ea0d64c7f64965a36f08d76847e5e2%7C84df9e7fe9f640afb435%7C1%7C0%7C637092530310759666&sdata=10EnT4Yff%2BndInH96%2B2zoYq8O1vlSmsF7ucU1Fgu1Xs%3D&reserved=0
List archives can be found at 
https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.window-eyes.com%2Fprivate.cgi%2Ftalk-window-eyes.com&data=02%7C01%7C%7C71ea0d64c7f64965a36f08d76847e5e2%7C84df9e7fe9f640afb435%7C1%7C0%7C637092530310759666&sdata=xqZYZWwKOIM5mDxh1f8cq4bjO2N6KgyBxoSRYgTryYk%3D&reserved=0
___
Any views or opinions presented in this email are solely those of the author 
and do not necessarily represent those of Ai Squared.

For membership options, visit 
http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com.
For subscription options, visit 
http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com
List archives can be found at 
http://lists.window-eyes.com/private.cgi/talk-window-eyes.com


I tone is very hard to use.

2019-11-13 Thread madl--- via Talk
Hello all
As may you know, I-tone is not easy to use.  Does anyone can recommend player 
that is accessable and easy to use?  
Thanks for any help.
Moe 


 

___
Any views or opinions presented in this email are solely those of the author 
and do not necessarily represent those of Ai Squared.

For membership options, visit 
http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com.
For subscription options, visit 
http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com
List archives can be found at 
http://lists.window-eyes.com/private.cgi/talk-window-eyes.com


RE: email

2019-11-13 Thread Rod Hutton via Talk
Hi Peter,

In the version of the Windows Live Mail app I have, which is 1.3.2, line 700 is 
working with braille.
Are you using a braille display?
If so, you can try disabling your braille display within Window-Eyes just for a 
bit in order to test if this could be causing the problem.

Hth,

Rod

Sent from Outlook for Windows

-Original Message-
From: Talk  On 
Behalf Of peter Chin via Talk
Sent: November 12, 2019 11:23 PM
To: peter Chin via Talk 
Cc: peter Chin 
Subject: Re: email

Hello David,

I hope the text given below the row of dashes what you were were asking for:
--
Windows Live Mail.VBS-Microsoft VB Script  runtime error
Line 700 column 2
Type mismatch 'sharedobject(...)'
<
0x800a000d
>


-Original Message- 
From: David via Talk
Sent: Monday, November 11, 2019 10:38 AM
To: peter Chin via Talk
Cc: David
Subject: Re: email

What exactly is the error message saying? It usually will tell us what
does not work, and which line in the scripting code that failed. That
is, which step in the processing of the script that caused the error.
Unless we know that, it all will be a matter of more or less wild guessing.


Now, if you happen to have the WEPM file for the script, you might want
to reinstall the app. If you have not made any user settings in the app,
if it offers such capability, I generally suggest first uninstalling the
app altogether, prior to attempting any reinstallation. Should you not
have the WEPM file, let us see if we might be able to help you out.


Again, wild guessing. Since it worked for you up till recently, it might
be due to some stuff going on with your computer. Try any Anti-ware you
have, like AntiSpyware or AntiVirus. Run a full scan of the system. See
if anything gets better. Sometimes I have seen certain Antiware block
files from one of the WinEyes apps, so if that is the case,
reinstallation will not help, since it only will reinstall the file that
is being blocked. In such cases, checking the blocking list in your
anti-ware might be a good idea.


Don't use the software in question, so sorry for not being able to give
you any further assistance here. Next time the error pops on you, would
you mind try copy it and let the list know what it says?



David

On 11/11/2019 3:18 AM, peter Chin via Talk wrote:
> Hello all,
>
> I made some mistakes in my last message so I am sending it again.
> --
> Hello all,
>
> I use WLM as my e-mail client on a Windows 8.1 machine and WE 9.5.4. I
> had
>
> no trouble with this client until just over a month ago. Since then, I
> get a
>
> script error message after sending out an e-mail message.I get four
> choices:
>
> ignore error, stop App, edit App or restart App. I have to choose the
> last
>
> option if I want to continue using WLM. However, WLM doesn't function
>
> properly unless I either reload WE or get out of WLM and then go back in.
>
>
> I hope someone can suggest a remedy for this problem. For those who
>
> understand script writing (which I don't), I include a copy of the script
>
> which is supposed to be re-edited.
>
> 
>
> ' For license information, see WindowsLiveMail License.txt which ships
> with
>
> this package.
>
> Option Explicit
>
>
> Dim myXMLFile : myXMLFile = ClientInformation.ScriptPath &
>
> "\WindowsLiveMail.xml"
>
> Dim myINIFile : myINIFile = ClientInformation.ScriptPath &
>
> "\WindowsLiveMail.ini"
>
> Dim myStrings : Set myStrings = Strings(myXMLFile)
>
> Dim myScriptUpdateURL : myScriptUpdateURL =
>
> "
> http://www.gwmicro.com/scripts/windows_live_mail/xml
> "
>
> Dim checkedForUpdates : checkedForUpdates = False
>
> Dim errorReportingEnabled : errorReportingEnabled = False
>
> Dim SO_StandardHelpDialog : Set SO_StandardHelpDialog = Nothing
>
> Dim SO_CheckForUpdate : Set SO_CheckForUpdate = Nothing
>
> Dim SO_ErrorReporting : Set SO_ErrorReporting = Nothing
>
> Dim fsObj : Set fsObj = CreateObject("Scripting.FileSystemObject")
>
>
> Dim messageWindow : Set messageWindow = Nothing
>
> Dim setFileActiveEvent : setFileActiveEvent = 0
>
> Dim lastSpoken : lastSpoken = ""
>
> Dim blockedFocusEvent : Set blockedFocusEvent = Nothing
>
> Dim msaaFocusEvent : msaaFocusEvent = 0
>
> Dim myMSAAEventSource : Set myMSAAEventSource = Nothing
>
> Dim contactHwnd : contactHwnd = 0
>
> Dim fieldDataEvent : fieldDataEvent = 0
>
>
> Dim myMoveMessageHotkey : Set myMoveMessageHotkey = Nothing
>
> Dim myKeyDownEvent : myKeyDownEvent = 0
>
> Dim keyProcessedDownEventForBraille : keyProcessedDownEventForBraille = 0
>
> Dim myBrailleObj : Set myBrailleObj = Nothing
>
> Dim firstLetterNavStr : firstLetterNavStr = ""
>
> Dim keyPressTimer : keyPressTimer = 0
>
>
> Const TIMER_AUTOCOMPLETE = 1000
>
> Const GRAPHIC_PREFIX = "GRAPHIC_"
>
>
> Class MessageWindowClass
>
>Private toField
>
>Private autoCompleteSelected
>
>Private myMSAAEventSource
>
>Private autoCompleteEnt