When will they fix the scrolling problem in KB824145???????????????????????????

  • Thread starter Thread starter Mike Margolis
  • Start date Start date
Mike Margolis said:
This is getting frustrating! It's been over a month!
Click to expand...

My congratulations on the good fortune that allows you to consider this a
major problem. Believe me, it's way down on the priorities to be fixed.
 
Maybe this is the way the scroll is supposed to work.
Try using the keyboard. There is more ways to scroll
besides the scrollbar.
 
I do believe you. That's why I have switched to Firebird for the time
being. So far, I haven't found a single reason to use IE again, though I am
not yet prepared to say that there is none. I just haven't seen one yet.
 
Frank Saunders said:
My congratulations on the good fortune that allows you to consider this a
major problem. Believe me, it's way down on the priorities to be fixed.
Click to expand...

Well, congratulate me too: I also consider it a major problem, as it
reduces usability and decreases productivity. In addition, a failure to fix
problems like this will deter people from installing future security
updates, which will unnecessarily increase our vulnerability to security
problems: doesn't Microsoft WANT people to trust updates?
 
anonymous said:
Maybe this is the way the scroll is supposed to work.
Try using the keyboard. There is more ways to scroll
besides the scrollbar.
Click to expand...

Why should scroll for IE work differently than for every other Windows app?
 
Believe me, it's way down on the priorities to be fixed.
Click to expand...

No kidding! Seems to be way, way, way down on that
priority list. What would reduce user frustration would
be simple steps like these:

1) some direct public acknowledgement from Microsoft that
this is a problem (all we've had are second-hand
assurances that "Microsoft is aware of the problem")

2) a guesstimate as to when users can expect a fix. (Two
weeks? two more months? two more years? Yes, I know
software deadlines are often moving targets-- just give
us the best estimate you can.)

3) an answer to the question I've posted two or three
times, in both this discussion groups and one on Outlook,
as to whether Microsoft is aware of and planning to fix
the same problem in Outlook and Outlook Express.

4) Frank Saunders, MS-MVP, also posted this:
My congratulations on the good fortune that allows you
to consider this a major problem.
Click to expand...
In other words, "it's not a big problem for me,
therefore it's not a big problem for you"-- which I think
qualifies as a "user-hostile" attitude. Sure, this isn't
a big problem compared to losing your home to an
earthquake in Iran, or getting threatened by a death
squad in Colombia. But as software issues go, for me
personally (and clearly for others, given the amount of
traffic it's generated) this one is actually a
significant drag on my productivity in reading long e-
mails. I'd like some idea if we'll get the fix in a few
days, or in Fall of 2004-- and that doesn't seem like too
much to ask.
 
Peter said:
No kidding! Seems to be way, way, way down on that
priority list. What would reduce user frustration would
be simple steps like these:

1) some direct public acknowledgement from Microsoft that
this is a problem (all we've had are second-hand
assurances that "Microsoft is aware of the problem")

2) a guesstimate as to when users can expect a fix. (Two
weeks? two more months? two more years? Yes, I know
software deadlines are often moving targets-- just give
us the best estimate you can.)

3) an answer to the question I've posted two or three
times, in both this discussion groups and one on Outlook,
as to whether Microsoft is aware of and planning to fix
the same problem in Outlook and Outlook Express.

4) Frank Saunders, MS-MVP, also posted this:
In other words, "it's not a big problem for me,
therefore it's not a big problem for you"-- which I think
qualifies as a "user-hostile" attitude. Sure, this isn't
a big problem compared to losing your home to an
earthquake in Iran, or getting threatened by a death
squad in Colombia. But as software issues go, for me
personally (and clearly for others, given the amount of
traffic it's generated) this one is actually a
significant drag on my productivity in reading long e-
mails. I'd like some idea if we'll get the fix in a few
days, or in Fall of 2004-- and that doesn't seem like too
much to ask.
Click to expand...

I'm using NAV 2002 and Sygate Personal Firewall so I just took the security
risk and uninstalled the update. My scrolling works beautifully now and
I'll just wait until they fix it.
 
Back
Top