"Normal" view hangs in FP2002 after Office SP3

[JDempsey]

I'm using a new computer (IBM ThinkPad Windows XP Pro SP1) after a hard-drive crash on my old machine (Windows 2000, all SPs applied) and starting to work with my backup website files (mostly *.asp). I installed FP2002 from my original CD, then did the Office SP3 update

I primarily use FP as a fancy text editor for the HTML, but like to use Normal mode to get a basic idea what the page will look like. I never use FP to publish, always FTPing to my sites

Now, when I open any page in "Normal" mode, the CPU usage goes to 100% and the status bar flashes "Retrieving < a style file>" continuously. If I switch to HTML view, this stops and things work normally, but everything goes haywire if I switch back to Normal view. The HTML code that "retrieves" the file in question is

<LINK href="admin/jdstyle.htm" type=text/css rel=stylesheet

which is unchanged from before

My questions are

1) Is there some setting that I'm missing that accounts for this behavior? Or is it really a problem/bug of some sort
2) Is there any reasonable way to fix it, or do I just have to live with the reduced functionality

Thanks so much for your help

JDempse

 

[JDempsey]

Wow! I've resolved this and want to share for others who may have the same problem. Note that I no longer think this has anything to do with Office SP3

BACKGROUN
I've just had to change computers, and I copied all my website pages from my old computer (Windows 2000) to my new computer (Windows XP Pro). I reinstalled FP2002 from the original CD and also did all the updates for XP (SP1) and Office (SP3

PROBLE
When I opened my (unchanged) pages in FP Normal mode, CPU use would peg at 100% and the status bar would flash "Retrieving \\\C:...admin\jdstyle.htm" continuously. The style file was in the following HTML statement

<LINK href="admin/jdstyle.htm" type=text/css rel=stylesheet

Sometimes I could quickly click on HTML view, which would stop the CPU overload, but often I would have to use Task Manager to End the FP task

SOLUTIO
The solution is simple: open the jdstyle.htm page in FP, switch to HTML view, make a trivial change, then save. Alternatively, it seemed to work to have the jdstyle.htm page open when opening any other page that referred to it.

HYPOTHESIZED EXPLANATIO
Obviously, I don't really know what's going on, but it sure looks like FP didn't know where to find the jdstyle.htm page, even though the path was there and correct. My guess is that FP does its own versioning of every page it touches (this actually has been a problem for me in editing *.js files, so I use Notepad). When I copied the files from my old computer but then reinstalled FP on the new computer, I imagine that the new FP didn't recognize the old FP's versioning. To get it to work, I had to have the new FP create its own versioned version..

I hope this helps people, as it can't be that uncommon a problem. Also, if anyone has a better explanation or solution, I'd be very intereste

JDempse

----- JDempsey wrote: ----

I'm using a new computer (IBM ThinkPad Windows XP Pro SP1) after a hard-drive crash on my old machine (Windows 2000, all SPs applied) and starting to work with my backup website files (mostly *.asp). I installed FP2002 from my original CD, then did the Office SP3 update

I primarily use FP as a fancy text editor for the HTML, but like to use Normal mode to get a basic idea what the page will look like. I never use FP to publish, always FTPing to my sites

Now, when I open any page in "Normal" mode, the CPU usage goes to 100% and the status bar flashes "Retrieving < a style file>" continuously. If I switch to HTML view, this stops and things work normally, but everything goes haywire if I switch back to Normal view. The HTML code that "retrieves" the file in question is

<LINK href="admin/jdstyle.htm" type=text/css rel=stylesheet

which is unchanged from before

My questions are

1) Is there some setting that I'm missing that accounts for this behavior? Or is it really a problem/bug of some sort
2) Is there any reasonable way to fix it, or do I just have to live with the reduced functionality

Thanks so much for your help

JDempse