From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_0312_01C76544.4BC79120
Content-Type: text/plain;
        charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

   I bet your system scheduler events to which you refer are at jobs or =
tasks scheduled in local time and not adjust for time zone changes.  =
Outlook appts and the like do vary by time zone as you would expect.  =
That you don't get notification unless Outlook is running is specific to =
your configuration.  I do on my phone.

   I don't care that you don't find your schedule important.  What I =
think is wrong of you is to complain about issues you encountered = because
you didn't care enough to do anything even though you knew that = you
should.

Rich

  "Geo."  wrote in message =
news:45f679e1$1{at}w3.nls.net...
  I'm not sure what you mean, I have scheduled events in the system =
scheduler,=20
  these outlook events are not shown there they are shown only in =
Outlook.=20
  Scheduled events in the system scheduler were fine, these are Outlook =
events=20
  and I don't receive notifications of them unless Outlook is running? =
If it's=20
  a system scheduler why do I not get notification unless Outlook is =
running?=20
  Is there some other software that will give me notifications and allow =
me to=20
  change the outlook events besides Outlook?

  As to preparation, it's simple, this is a non-critical function for =
me.=20
  Unlike most MS'ers I don't live and die by a computer scheduler. They =
are=20
  about as important to me as the local temperature/weather gadget. Does =
that=20
  bother you?

  Geo.


  "Rich"  wrote in message news:45f61647$1{at}w3.nls.net...
    No "function of Outlook" needed to be fixed.  What you are updating =
is
  your scheduled events.  This only applies to events you scheduled =
before you
  updated Windows with the knowledge of the change in DST.  A =
consequence of
  that is the events you scheduled have the wrong time because you =
changed the
  meaning of that time.  Despite your trying to attribute blame for =
something
  you apparently do not understand, Outlook still requires no update.  =
This is
  why you can update the same scheduled events against the Exchange =
store.
  The issue is with the scheduled events not the code that uses them.

     As for your last paragraph, I can't guess what you are blabbering =
on
  about.  You are not making any sense.  My question was simple, why did =
you
  not attempt any preperation by checking the support site when you were =
well
  aware and discussed in advance that the government's DST change had
  consequences to software.  It seems you answered this partly which is =
that
  you didn't care to prepare in which case you deserve what you get.

  Rich

    "Geo."  wrote in message =
news:45f6106b$1{at}w3.nls.net...
    "Rich"  wrote in message news:45f5e849{at}w3.nls.net...

    >>   You are not patching Outlook.  You are updating your existing
  calendar
    >> items which if you were using Exchange you could have done by =
running a
    >> tool against the Exchange store.<<

    Call it what you like, it is a function of outlook that needed =
fixed, that
    function is not available to me via anything but outlook.

    >>   It's still something to do.  Had you looked at the DST Help and
  Support
    >> Center on microsoft.com (http://support.microsoft.com/gp/cp_dst) =
you
    >> would see this clearly spelled out.  Why did you never look?<<

    Because it never occurred to me that in the dll hell world of MS =
where the
    rule is system integration and code reuse even at the cost of =
extreme
    bloating, that they would be so inconsistent as to recode what =
already
    exists. Well no wait, that did occur to me, it just wasn't important
  enough
    to worry about.

    Geo.

------=_NextPart_000_0312_01C76544.4BC79120
Content-Type: text/html;
        charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable








   I bet your system =
scheduler events to=20
which you refer are at jobs or tasks scheduled in local time and not = adjust for=20
time zone changes.  Outlook appts and the like do vary by time
zone = as you=20
would expect.  That you don't get notification unless Outlook is =
running is=20
specific to your configuration.  I do on my phone.
 
   I don't
care that you =
don't find your=20
schedule important.  What I think is wrong of you is to complain = about=20
issues you encountered because you didn't care enough to do anything = even though=20
you knew that you should.
 
Rich
 

  "Geo." <georger{at}nls.net>">mailto:georger{at}nls.net">georger{at}nls.net>
wrote=20
  in message news:45f679e1$1{at}w3.nls.net...I'm=20
  not sure what you mean, I have scheduled events in the system =
scheduler,=20
  these outlook events are not shown there they are shown only in =
Outlook.=20
  Scheduled events in the system scheduler were fine, these are =
Outlook=20
  events and I don't receive notifications of them unless Outlook is =

  running? If it's a system scheduler why do I not get notification =
unless=20
  Outlook is running? Is there some other software that will give me =

  notifications and allow me to change the outlook events besides=20
  Outlook?As to preparation, it's simple, this is a
non-critical =

  function for me. Unlike most MS'ers I don't live and die by a =
computer=20
  scheduler. They are about as important to me as the local=20
  temperature/weather gadget. Does that bother=20
 
you?Geo."Rich"
<{at}> wrote in message news:45f61647$1{at}w3.nls.net...=
 =20
  No "function of Outlook" needed to be fixed.  What you are =
updating=20
  isyour scheduled events.  This only applies to events you =
scheduled=20
  before youupdated Windows with the knowledge of the change in =
DST.  A=20
  consequence ofthat is the events you scheduled have the wrong time =
because=20
  you changed themeaning of that time.  Despite your trying to=20
  attribute blame for somethingyou apparently do not understand, =
Outlook=20
  still requires no update.  This iswhy you can update the same =

  scheduled events against the Exchange store.The issue is with the=20
  scheduled events not the code that uses
them.   As =
for your=20
  last paragraph, I can't guess what you are blabbering =
onabout.  You=20
  are not making any sense.  My question was simple, why did =
younot=20
  attempt any preperation by checking the support site when you were=20
  wellaware and discussed in advance that the government's DST =
change=20
  hadconsequences to software.  It seems you answered this =
partly which=20
  is thatyou didn't care to prepare in which case you deserve what =
you=20
  get.Rich 
"Geo." <georger{at}nls.net>">mailto:georger{at}nls.net">georger{at}nls.net>
wrote in =
message news:45f6106b$1{at}w3.nls.net...=
 =20
  "Rich" <{at}> wrote in message news:45f5e849{at}w3.nls.net...=
 =20
  >>   You are not patching
Outlook.  You are =
updating your=20
  existingcalendar  >> items
which if you were using =
Exchange=20
  you could have done by running a  >>
tool against the =
Exchange=20
  store.<<  Call it what you
like, it is a function =
of=20
  outlook that needed fixed, that  function is not available to =
me via=20
  anything but outlook. 
>>   It's still =
something=20
  to do.  Had you looked at the DST Help
andSupport  =
>>=20
  Center on microsoft.com (http://support.microsoft" target="new">http://support.microsoft.=">http://support.microsoft.com/gp/cp_dst">http://support.microsoft.=
com/gp/cp_dst)=20
  you  >> would see this clearly spelled
out.  Why =
did you=20
  never look?<<  Because it
never occurred to me that =
in the=20
  dll hell world of MS where the  rule is system integration =
and code=20
  reuse even at the cost of extreme  bloating, that they would =
be so=20
  inconsistent as to recode what already  exists. Well no wait, =
that=20
  did occur to me, it just wasn't
importantenough  to worry =

  about. 
Geo.

------=_NextPart_000_0312_01C76544.4BC79120--

--- BBBS/NT v4.01 Flag-5