PDA

View Full Version : XP SP2 and Its Impacts on FrontPage 2002


Jim K
August 27th 04, 08:09 AM
I downloaded and installed XP SP2 without incident. This system is running
McAfee Personal Firewall (enabled), and McAfee AV (enabled), as well as
Windows firewall (enabled). Actually, the system is happier than I am at the
moment.

Prior to upgrading (actually, since 1998) this system has run a version of
FrontPage without any difficulties whatsoever. I've used FP to publish my web
site updates to a Web Presence Provider for over 6 years, but that's
impossible now. The application will not even open to the point that
Publishing is an option in the File menu or the Icon bar. FrontPage was
running about an hour prior to the download began...no problems or
indications that there was anything amiss.

After the SP2 install, FP2002 will not open any pages on my web site for
editing. Attempts to open any file result in a gray screen similar to that
displayed with a web is first opened. No data files are ever opened; or, if
they are (but not displayed), there is no indication in FP that Normal, HTML
or Preview windows are available.

Remedial efforts included:
- Waiting for over an hour to get into a Tech Support chat with a fellow
from India who was with MS Tech Support. He assured me SP2 did nothing to
damage my ability to access other applications; but, since he knew nothing
about FP, he referred the issue to a different group, which I may (or may
not) hear from in 2 business days. (Uhhhh, it's nearly Friday here, and if I
have to wait through the weekend I will not be pleasant to work with when/if
they do get back to me...)
- Detect & Repair of FrontPage, which ran to completion without incident.
Prior to running D&R, the system acted as though registration status of
FP2002 had been lost. Restarting system, and running D&R, I have not been
confronted with the need to re-register the product.
- Re-establishing the association between .htm files and FP2002. Files
initially opened in IE. After correcting that issue, files now open with FP.

All other Office applications running well...just FP, the one I really need
to get into, is failing.

The only thing I can think of to recover from this is to fall back to a
pre-SP2 restore point. But, this means the entire dl and install gets
repeated (someday). Does anyone have other suggestions? Any help would be
greatly appreciated.

August 27th 04, 09:35 AM
if you were to drop back to pre SP2 which I don't think is possible, just
like the SP1 install, it could not be un-installed.

you can then stop automatic updates,

To control or disable automatic updating, open the System icon in Control
Panel (or right-click My Computer and select Properties), and choose the
Automatic Updates tab.
there you can chose what method you want.

Jason



"Jim K" <Jim > wrote in message
...
> I downloaded and installed XP SP2 without incident. This system is running
> McAfee Personal Firewall (enabled), and McAfee AV (enabled), as well as
> Windows firewall (enabled). Actually, the system is happier than I am at
the
> moment.
>
> Prior to upgrading (actually, since 1998) this system has run a version of
> FrontPage without any difficulties whatsoever. I've used FP to publish my
web
> site updates to a Web Presence Provider for over 6 years, but that's
> impossible now. The application will not even open to the point that
> Publishing is an option in the File menu or the Icon bar. FrontPage was
> running about an hour prior to the download began...no problems or
> indications that there was anything amiss.
>
> After the SP2 install, FP2002 will not open any pages on my web site for
> editing. Attempts to open any file result in a gray screen similar to that
> displayed with a web is first opened. No data files are ever opened; or,
if
> they are (but not displayed), there is no indication in FP that Normal,
HTML
> or Preview windows are available.
>
> Remedial efforts included:
> - Waiting for over an hour to get into a Tech Support chat with a fellow
> from India who was with MS Tech Support. He assured me SP2 did nothing to
> damage my ability to access other applications; but, since he knew nothing
> about FP, he referred the issue to a different group, which I may (or may
> not) hear from in 2 business days. (Uhhhh, it's nearly Friday here, and if
I
> have to wait through the weekend I will not be pleasant to work with
when/if
> they do get back to me...)
> - Detect & Repair of FrontPage, which ran to completion without incident.
> Prior to running D&R, the system acted as though registration status of
> FP2002 had been lost. Restarting system, and running D&R, I have not been
> confronted with the need to re-register the product.
> - Re-establishing the association between .htm files and FP2002. Files
> initially opened in IE. After correcting that issue, files now open with
FP.
>
> All other Office applications running well...just FP, the one I really
need
> to get into, is failing.
>
> The only thing I can think of to recover from this is to fall back to a
> pre-SP2 restore point. But, this means the entire dl and install gets
> repeated (someday). Does anyone have other suggestions? Any help would be
> greatly appreciated.

johnf
August 27th 04, 10:01 AM
Definitely possible. It's simply a matter of rolling back to the previous
Restore Point (providing Jim hasn't deleted the "$NtServicePackUninstall$"
folder in Windows).

--

johnf

> if you were to drop back to pre SP2 which I don't think is possible,
> just like the SP1 install, it could not be un-installed.
>
> you can then stop automatic updates,
>
> To control or disable automatic updating, open the System icon in
> Control Panel (or right-click My Computer and select Properties), and
> choose the Automatic Updates tab.
> there you can chose what method you want.
>
> Jason
>
>
>
> "Jim K" <Jim > wrote in message
> ...
>> I downloaded and installed XP SP2 without incident. This system is
>> running McAfee Personal Firewall (enabled), and McAfee AV (enabled),
>> as well as Windows firewall (enabled). Actually, the system is happier
>> than I am at the moment.
>>
>> Prior to upgrading (actually, since 1998) this system has run a
>> version of FrontPage without any difficulties whatsoever. I've used FP
>> to publish my web site updates to a Web Presence Provider for over 6
>> years, but that's impossible now. The application will not even open
>> to the point that Publishing is an option in the File menu or the Icon
>> bar. FrontPage was running about an hour prior to the download
>> began...no problems or indications that there was anything amiss.
>>
>> After the SP2 install, FP2002 will not open any pages on my web site
>> for editing. Attempts to open any file result in a gray screen similar
>> to that displayed with a web is first opened. No data files are ever
>> opened; or, if they are (but not displayed), there is no indication in
>> FP that Normal, HTML or Preview windows are available.
>>
>> Remedial efforts included:
>> - Waiting for over an hour to get into a Tech Support chat with a
>> fellow from India who was with MS Tech Support. He assured me SP2 did
>> nothing to damage my ability to access other applications; but, since
>> he knew nothing about FP, he referred the issue to a different group,
>> which I may (or may not) hear from in 2 business days. (Uhhhh, it's
>> nearly Friday here, and if I have to wait through the weekend I will
>> not be pleasant to work with when/if they do get back to me...)
>> - Detect & Repair of FrontPage, which ran to completion without
>> incident. Prior to running D&R, the system acted as though
>> registration status of FP2002 had been lost. Restarting system, and
>> running D&R, I have not been confronted with the need to re-register
>> the product. - Re-establishing the association between .htm files and
>> FP2002. Files initially opened in IE. After correcting that issue,
>> files now open with FP.
>>
>> All other Office applications running well...just FP, the one I really
>> need to get into, is failing.
>>
>> The only thing I can think of to recover from this is to fall back to a
>> pre-SP2 restore point. But, this means the entire dl and install gets
>> repeated (someday). Does anyone have other suggestions? Any help would
>> be greatly appreciated.

Google