No local graphics displayed

  • Thread starter Thread starter Tom
  • Start date Start date
T

Tom

This problem started while I was editing a website in FrontPage. The
graphics will display in normal (composing) mode, but when I try to preview
the page, none of the graphics are displayed. Saving the page and opening it
in IE6 does not display the graphics. Opening the same page with Netscape
4.6 shows the graphics as normal. If I upload the pages to the website, IE6
will now show the graphics. None of my pages use hard urls. Everything uses
relevant paths.

This issue occurs for all locally stored web pages which have worked for
years. What's more, I could go to Google for example, save the page (with
all it's associated files) but now IE will no longer display the graphics as
it used to do. Nothing was altered to make this problem crop up.

I have checked and toggled the relevant graphic settings in IE to no avail.
Against my better judgment, I have even deleted TIF and cookies and even
uninstalled and reinstalled IE several times, also to no avail.

Has anyone ever seen this issue before and know how to fix it?

(Using IE6 in Windows 98)
 
My cache has been set at 95 megs since 1998 but OK, I resized to 60 and
dropped to real mode to delete TIF. Unfortunately, that did not fix the
problem. I did discover there were something like 20k files orphaned in TIF
so it wasn't a total loss to trash TIF.

Does anyone have any ideas not involving rudimentary fixes? This problem
just began while I was editing pages. I edited several pages and viewed them
just fine until suddenly IE stopped working. Weird. I really dread the
thought of reloading the HD from scratch just to get IE working again.

Tom
 
Tom said:
My cache has been set at 95 megs since 1998 but OK, I resized to 60 and
dropped to real mode to delete TIF. Unfortunately, that did not fix the
problem. I did discover there were something like 20k files orphaned in TIF
so it wasn't a total loss to trash TIF.

Does anyone have any ideas not involving rudimentary fixes? This problem
just began while I was editing pages. I edited several pages and viewed them
just fine until suddenly IE stopped working. Weird. I really dread the
thought of reloading the HD from scratch just to get IE working again.

Tom

Looks like this is a new problem nobody has seen or can resolve. Perhaps
someone knows how FrontPage and IE6 interact. I tried reinstalling FP but
that did not fix the problem either. Tried running scandisk too, to see if
any files became corrupt. Tried checking for naughty spyware too.

Anyone have an idea what could possibly fix this problem?

Tom
 
Tom said:
Looks like this is a new problem nobody has seen or can resolve. Perhaps
someone knows how FrontPage and IE6 interact. I tried reinstalling FP but
that did not fix the problem either. Tried running scandisk too, to see if
any files became corrupt. Tried checking for naughty spyware too.

Anyone have an idea what could possibly fix this problem?

Tom

Tap, tap, tap... Hellooo... Is anyone out there?

Perhaps there is some bit of information I'm not including that might help
identify the problem except I don't know what that something is exactly.
Let's try again with this...

From my analysis, the properties of local files always have "file://"
prefixed. i.e., if the file is on a local hard drive, I get
"file:///c:/etc." and if its on a remote drive on my LAN, it reads
"file://computername/etc.", thus still considered local. In both of these
cases none of the graphics are visible/displayed. Meanwhile, the same
unmodified files work fine on the website. The only difference is the
properties of the graphics display "http://domainname/etc." and this is what
leads me to believe there is a separate but parallel library performing the
rendering.

So, does anyone know if IE6 uses a different library to display graphics
stored locally opposed to on a website?

With Windows 98 nearing non-supported operating system status, and since IE
is an integral part of the OS, this issue seems analogous to a physical
product acting up while nearing it's warranty expiration. Not fully
defective to warrant mfg concern, but not fully functional as when it was
spanking new which raises individual concern.

Tom
 
Back
Top