Jay Garcia wrote: > > JTK wrote: > > > "Phillip M. Jones, C.E.T." wrote: > > > > > > [snip] > > > > > >>Has he tried: Edit > Preferences > Advanced > Cache. Setting to Page in > >>cache compared to one on network: > >> > >>Everytime ?? That way N6/Moz / Communicator never relies on the page in > >>the cache. > >> > > > > Uh, well, yeah, I would sure hope that disabling the cache would fix > > it! Then again, this *is* Mozilla we're talking here. That's not the > > point though. If the cache is broken, and it clearly is, it either > > needs to be fixed it or removed. > > > > No, YOUR cache is busted, not ours for whatever reason. >
No, *I* don't have a cache. Mozilla does. I had nothing to do with the development of it. In fact on my installation, I didn't even do anything whatsoever to change the settings from their defaults. It simply don't work right, right out of the box. > Since /cache/ contains "files" written to specific areas of the HD maybe > a scan-disk and defrag may help and even a "complete sector check" may > provide relief .. who knows at this point, maybe worth a try. > Neither are likely to do much on an NTFS disk. > Do you have another computer 'at hand' to attempt to dupe the problem ?? > I do, but I have neither the time nor the patience. Several people besides me have reported this defect, at great risk to themselves being called liars and heathen and Lord knows what else. The cache is broken, I've personally provided the screenshots to prove it. I can tell you "yep, it's broke here too" 'til doomsday and that still won't get it fixed, will it? And if I tell you, "well, it works here and not there", the defect gets blown off as *my* problem and still doesn't get fixed, doesn't it? You forget that I know all too well how this operation works; or rather doesn't. For some strange reason, I suspect that AOL has plenty of computers to devote to Mozilla testing, even after buying Time Warner. And plenty of people paid to track down the source of such aggregious defects. They can do what they will, or won't, with the fact that Mozilla's cache is broken, as proven for them by myself and others. Gratis. And BTW, the very notion that "you're the only one seeing this" is an outrageous lie even if several others hadn't reported the same problem: I use Mozilla's web browser virtually not at all. Perhaps twice a day max: once to download the latest nightly to see what still hasn't been fixed yet, and once to see week-old CNN. That's it. So either I'm a "heavy Mozilla user" (wouldn't surprise me), or a lot of AOL people are in severe denial as to the defectiveness of their software.
