The GW-Info list is a discussion list, which can be very active with many messages per day. Any subscriber of the GW-Info list has the ability to post on-topic messages.

From:

 Chris Belle

Subject:

 RE: window-eyes ram usage with posible solution

Date:

 Mon, May 24, 2010 3:23:14 pm
Now where can we get the sm seesaw to control which processors we gets?


That sounds like just what I need.


At 01:38 PM 5/24/2010, Manny Gee wrote:
Aloha to all,
I have found a work around that helps me when window eyes stops talking
my first choice is to remove the sub connection to my wireless
headset, and viola window eyes starts talking using my external
speakers, then I just replug the sub and my wireless is talking again.
If that does not work, I use a hot key to shutdown all three window
eyes applications using a batch file and count to 10 and restart
window eyes and again
viola window eyes is up and running.
When I am about to run a program that I know will prevent window
eyes from talking because the program seems to take all of the
c-p-u, I run "sm seesaw pro and I isolate window eyes to one of my 4
processors, and then I run the other program, and I still can work
on the computer using window eyes still talking.
I am using Intel quad core q6600, with 8 gigs of ram memory
Somebody made the comment that window eyes seem to crash with
windows 7 more often than with other windows operating system, and I
agree. I also use windows vista and windows xp with all of the
service paks and window eyes seems to be more stable on these platforms.
Good luck,
Manny
If you need to contact me,
please email me at:
Maiman01@gmail.com

or skype me at Maiman01



> From: munawarb@gmail.com
> To: gw-info@gwmicro.com
> Subject: Re: window-eyes ram usage
> Date: Sun, 23 May 2010 15:56:15 -0400
>
> Hi,
> I'm not sure if programs in emulated 64 mode use the same amount of memory
> as true 64-bit programs, but I'd assume they don't because a 32-bit
> application that depends on datatype sizes can run under WOW-64
mode with no
> changes. As for W E, the main wineyes process is a 64-bit
process, but some
> of its dependencies are 32-bit. Otherwise the core is 64-bit. GW
still chose
> to install it to Program Files (x86) though, I'm assuming because
of all the
> 32-bit dependencies.
> Munawar A. Bijani
> blog: http://munawar0009.blogspot.com
> http://www.bpcprograms.com
> Follow on Twitter for blog updates: http://www.twitter.com/munawar0009
>
> --------------------------------------------------
> From: "Don H"
> Sent: Sunday, May 23, 2010 2:00 PM
> To: "'Munawar Bijani'"
> Subject: RE: window-eyes ram usage
>
> Does what you say about 64 bit apps still hold true when the app
is a 32 bit
> running on a 64 bit machine? WE is a 32 bit app.
>
> -----Original Message-----
> From: Munawar Bijani [mailto:munawarb@gmail.com]
> Sent: Sunday, May 23, 2010 9:14 AM
> To: gw-info@gwmicro.com
> Subject: Re: window-eyes ram usage
>
> Hi Everyone,
> If you are running W E on a 64-bit system, you will notice significantly
> increased memory usage. This is a result of the 64-bit processor, not W E
> itself. Typically, programs on 64-bit systems use double the memory than
> they do on 32-bit systems. This is because it costs more memory
to do things
> on 64-bit systems. For instance, for those of you who are programmers,
> pointers are doubled in size from 4 bytes to 8 bytes on 64-bit
systems. This
> means that the code void* s = null; will take up 8 bytes of RAM on a 64-bit
> system and 4 bytes on a 32-bit system. There are other memory differences
> like these between 32-bit and 64-bit systems which, for a large
program such
> as a screen reader, end up resulting in greater memory usage overall on the
> 64-bit platforms.
>
> The memory usage for W E is actually not bad compared to what it
used to be.
> In 7.0 and less, W E would usually start around 100 MB RAM on my system and
> start increasing with no limit. The maximum I remember W E taking
up was 500
> MB RAM, and this was on a 32-bit system! It was one of the reasons I
> reverted back to JAWS--that is, until the new version came out that fixed
> the memory leak.
>
> On 5/23/10, Chris Belle wrote:
> > Well, it's not always about how much ram your using, but mis-matched
> > software, or software that doesn't get along.
> > with other software.
> >
> >
> > I ask more of my systems than most folks do, running high end audio
> > with lots of vst plug-ins and my hardware is all the latest and
> > greatest stuff, i7 processor with 6 gigs of 1600 memory, nice upper
> > end gigabyte motherboard,
> >
> > etc.
> >
> > W7 64 is still pretty green, and all this stuff is just barely done,
> > so I imagine it'll get better in a year or so.
> >
> > But yeh, window-eyes will just quit talking in the middle of doing
> > stuff and I'll have to run narrator to shut it down, or worse yet,
> > just shut the system off.
> >
> > I should probably put nvda on the 64 bit machine, it's my favorite way
> > to un-snarl we on the xp machine.
> >
> > that's funny, using a lesser screen-reader to get the supposedly
> > better one out of trouble 'grin'.
> >
> > I find that very amusing.
> >
> > And I know it's not an eloquence issue either, because I tend to use
> > hardware speech a lot, it's just one of those annoying things, pc's
> > are annoying, they just don't do what they're supposed to all the
> > time, and we just have to put up with it and take the good with the
> > bad.
> >
> >
> > At 05:29 AM 5/23/2010, Keith Hinton wrote:
> >>As for crashes occuring more in Windows Seven than in XP, I thought
> >>that Windows seven was supposed to feature a lot of system stability?
> >>I run Window-Eyes here in demo form presently and have a 64-bit 4GB
> >>RAM machine that runs rather well. Window-Eyes performs just as well
> >>as it has under XP. I can't find any differences, rairly experience
> >>any crashes. The crashes I do get are because of outdated system drivers.
> >>Surely if you are using say a 1GB plus RAM system, then Window-Eyes
> >>shouldn't take up too much, does it?
> >>
> >>
> >>--------------------------------------------------
> >>From: "Chris Belle"
> >>Sent: Sunday, May 23, 2010 6:16 AM
> >>To: "Mohaned Sayegh" ;
> >>Subject: Re: window-eyes ram usage
> >>
> >>>Well, for the price they charge and for the amount of resources they
> >>>can marshall, they better do something good down there in Florida
> >>>'grin'.
> >>>
> >>>But if using a little extra memory will make we more stable, or help
> >>>it to not interfere with what I'm doing but just be my eyes for me,
> >>>then I don't mind.
> >>>
> >>>That's what we have these new hot-shot processors for and lots of
> >>>memory, and I don't really notice jaws being more responsive than we
> >>>now, it wasn't that way with the whole 7 series, there was a
> >>>noticeable lag, but I think we're back to our snappiness and much
> >>>better stability with 7.2
> >>>
> >>>It can still be improved on of course, but random crashes happen much
> >>>less often now.
> >>>
> >>>They happen more in windows 7 than in xp.
> >>>
> >>>Maybe we can get some comments from the giant brains as to what parts
> >>>of we are hogging the most memory and why.
> >>>
> >>>All these programs are big pigs these days, oink, oink, grunt grunt,
> >>>seems like everything I use has to be installed with 4 dvds or
> >>>several cds, and has to access multiple libraries which need 27
> >>>plug-ins, which need 50 updates, which need 77 patches, and they all
> >>>need a restart after installing 'grin'.
> >>>
> >>>As a friendly fellow commented to me off list privately, it's a
> >>>wonder any of this damned stuff works anyway.
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>At 12:26 AM 5/23/2010, Mohaned Sayegh wrote:
> >>>>JAWS shows about 37 mb of memory on average.
> >>>>Chris Belle wrote:
> >>>>>Just think of all a screen-reader has to do.
> >>>>>
> >>>>>Most folks don't realize the low level programming that goes in to
> >>>>>screen-reader functionallity.
> >>>>>
> >>>>>I'm not excusing piss poor programming, or laziness, but it's hard
> >>>>>to make a good screen-reader.
> >>>>>
> >>>>>Think of all the automatic functions we does, things like
> >>>>>hyperactive windows, reading tool-tips, the msaa stuff, the crazy
> >>>>>stuff that has to be done with video hacking even with mirror
> >>>>>drivers, everybody wants good sounding tts voices, so for quickest
> >>>>>access some of that is probably loaded in to memory.
> >>>>>
> >>>>>And never mind the scripting stuff.
> >>>>>
> >>>>>So it doesn't supprise me in this day of high level languages, and
> >>>>>let's just glue it all together and grab a module, that we is a bit
> >>>>>bloated like every other program on your system.
> >>>>>
> >>>>>But it has to do a lot more than most programs on your system.
> >>>>>
> >>>>>Watch your every keystroke, speak everything you mouse over or
> >>>>>interact with, and do it in some sort of logical and controled manner.
> >>>>>
> >>>>>I guess that's worth a hundred megs of my ram 'grin'.
> >>>>>
> >>>>>
> >>>>>At 08:41 PM 5/22/2010, Mohaned Sayegh wrote:
> >>>>>>Hello, I'm just wondering, how come Window-eyes takes up an
> >>>>>>ungodly amount of ram? When first loaded, with no scripts running,
> >>>>>>it takes up 106 MB of ram on a windows 7 home premium
> >>>>>>64 bit system right away.
> >>>>>>
> >>>>>>thanks
> >>>>>>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 gw-info@gwmicro.com 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.
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> WARNING!!!
> >>>>>
> >>>>>This email could contain innocent phrases which, if taken out of
> >>>>>context, or read from an existing inclination to be hostile, or an
> >>>>>overly politically correct world view could induce cursing, abusive
> >>>>>language, or other indications of less than desirable behavior in a
> >>>>>public venue.
> >>>>>No ill will is intended.
> >>>>>The sender takes no responsibility for mis-interpretation or
> >>>>>otherwise extrapolated extended meaning, intent, or purposes
> >>>>>implied or imagined from said phrases.
> >>>>>The receiver of any such email containing such phrases is solely
> >>>>>responsible for good interpretation and intelligent deployment of
> >>>>>subsequent responses to the above communication.
> >>>>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 gw-info@gwmicro.com 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.
> >>>
> >>>
> >>>
> >>>
> >>> WARNING!!!
> >>>
> >>>This email could contain innocent phrases which, if taken out of
> >>>context, or read from an existing inclination to be hostile, or an
> >>>overly politically correct world view could induce cursing, abusive
> >>>language, or other indications of less than desirable behavior in a
> >>>public venue.
> >>>No ill will is intended.
> >>>The sender takes no responsibility for mis-interpretation or
> >>>otherwise extrapolated extended meaning, intent, or purposes implied
> >>>or imagined from said phrases.
> >>>The receiver of any such email containing such phrases is solely
> >>>responsible for good interpretation and intelligent deployment of
> >>>subsequent responses to the above communication.
> >>>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 gw-info@gwmicro.com 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 gw-info@gwmicro.com 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.
> >
> >
> >
> >
> > WARNING!!!
> >
> > This email could contain innocent phrases which, if taken out of
> > context, or read from an existing inclination to be hostile, or an
> > overly politically correct world view could induce cursing, abusive
> > language, or other indications of less than desirable behavior in a
> > public venue.
> > No ill will is intended.
> > The sender takes no responsibility for mis-interpretation or otherwise
> > extrapolated extended meaning, intent, or purposes implied or imagined
> > from said phrases.
> > The receiver of any such email containing such phrases is solely
> > responsible for good interpretation and intelligent deployment of
> > subsequent responses to the above communication.
> > 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 gw-info@gwmicro.com 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.
> >
> >
>
>
> --
> Munawar A. Bijani
> Mailto:munawarb@gmail.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
> gw-info@gwmicro.com 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 gw-info@gwmicro.com 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.
>


----------
Hotmail has tools for the New Busy. Search, chat and e-mail from
your inbox.
Learn
more.

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 gw-info@gwmicro.com 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.




WARNING!!!

This email could contain innocent phrases which, if taken out of
context, or read from an existing inclination to be hostile, or an
overly politically correct world view could induce cursing, abusive
language, or other indications of less than desirable behavior in a
public venue.
No ill will is intended.
The sender takes no responsibility for mis-interpretation or
otherwise extrapolated extended meaning, intent, or purposes implied
or imagined from said phrases.
The receiver of any such email containing such phrases is solely
responsible for good
interpretation and intelligent deployment of subsequent responses to
the above communication.
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 gw-info@gwmicro.com 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.