Instant Dreamweaver Killer??

I hope I do not have to keep deleting this file each time DW crashes.

Is this a one off or just a daylight savings problem?

This issue seems to have reared its head again this week. Surely a year would have been long enough to fix it? If I left my clients waiting a year for a bug fixes I'd be bankrupt.

On Fri, 9 Nov 2007 12:31:58 -0500, "Murray *ACE*"
<forums@HAHAgreat-web-sights.com> wrote:

>Could be. I do have it turned off....

Me too. That's what made me think of it.

Win
--
Win Day, Wild Rose Websites
http://www.wildrosewebsites.com
winday@NOSPAMwildrosewebsites.com
Skype winifredday

Could be. I do have it turned off....

--
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
==================


"Win Day" <winday@NOSPAMwildrosewebsites.com> wrote in message
news:fa29j3lqj7j53jo8f66vntb3cqnvnkqb42@4ax.com...
> On Fri, 09 Nov 2007 16:12:07 +0000, David Powers <david@example.com>
> wrote:
>
>>Murray *ACE* wrote:
>>> Certainly agree with that. It's curious indeed that this issue didn't
>>> arise with the US time change, however....
>>
>>It did. The problem is that it doesn't appear to have affected everyone.
>>David Alcala at Adobe has been investigating this issue since it was
>>first reported. He has managed to reproduce it with PHP, but not with
>>ASP or ColdFusion. However, quite a lot of ASP and ColdFusion users have
>>reported suffering from it. But in all cases that I have heard of,
>>deleting WinFileCache-********.dat fixes the problem.
>>
>>I've heard of at least one person who was still working in Dreamweaver
>>at the time of the clock change, and who has suffered no crashes. I know
>>that, in the past, you have left Dreamweaver running for days without
>>switching off. If your computer was running with Dreamweaver open at the
>>time of the clock change, that might explain why you escaped.
>
>
> Is it at all possible that those who were not affected are those who
> in Vista have UAC turned off, or in XP installed as the administrator
> (rather than using another account with admin privileges)?
>
> Unlike Murray, I don't keep DW running for days. Like Murray, I
> turned UAC off in Vista before installing (and continue to keep it
> turned off). Also like Murray, I didn't experience a crash.
>
> My thinking is this has something to do with Windows and permissions.
>
> Win
> --
> Win Day, Wild Rose Websites
> http://www.wildrosewebsites.com
> winday@NOSPAMwildrosewebsites.com
> Skype winifredday

I don't think it was open at the time of the clock change.

--
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
==================


"David Powers" <david@example.com> wrote in message
news:fh20ua$4qi$1@forums.macromedia.com...
> Murray *ACE* wrote:
>> Certainly agree with that. It's curious indeed that this issue didn't
>> arise with the US time change, however....
>
> It did. The problem is that it doesn't appear to have affected everyone.
> David Alcala at Adobe has been investigating this issue since it was first
> reported. He has managed to reproduce it with PHP, but not with ASP or
> ColdFusion. However, quite a lot of ASP and ColdFusion users have reported
> suffering from it. But in all cases that I have heard of, deleting
> WinFileCache-********.dat fixes the problem.
>
> I've heard of at least one person who was still working in Dreamweaver at
> the time of the clock change, and who has suffered no crashes. I know
> that, in the past, you have left Dreamweaver running for days without
> switching off. If your computer was running with Dreamweaver open at the
> time of the clock change, that might explain why you escaped.
>
> --
> David Powers, Adobe Community Expert
> Author, "The Essential Guide to Dreamweaver CS3" (friends of ED)
> Author, "PHP Solutions" (friends of ED)
> http://foundationphp.com/

On Fri, 09 Nov 2007 16:12:07 +0000, David Powers <david@example.com>
wrote:

>Murray *ACE* wrote:
>> Certainly agree with that. It's curious indeed that this issue didn't
>> arise with the US time change, however....
>
>It did. The problem is that it doesn't appear to have affected everyone.
>David Alcala at Adobe has been investigating this issue since it was
>first reported. He has managed to reproduce it with PHP, but not with
>ASP or ColdFusion. However, quite a lot of ASP and ColdFusion users have
>reported suffering from it. But in all cases that I have heard of,
>deleting WinFileCache-********.dat fixes the problem.
>
>I've heard of at least one person who was still working in Dreamweaver
>at the time of the clock change, and who has suffered no crashes. I know
>that, in the past, you have left Dreamweaver running for days without
>switching off. If your computer was running with Dreamweaver open at the
>time of the clock change, that might explain why you escaped.


Is it at all possible that those who were not affected are those who
in Vista have UAC turned off, or in XP installed as the administrator
(rather than using another account with admin privileges)?

Unlike Murray, I don't keep DW running for days. Like Murray, I
turned UAC off in Vista before installing (and continue to keep it
turned off). Also like Murray, I didn't experience a crash.

My thinking is this has something to do with Windows and permissions.

Win
--
Win Day, Wild Rose Websites
http://www.wildrosewebsites.com
winday@NOSPAMwildrosewebsites.com
Skype winifredday

Murray *ACE* wrote:
> Certainly agree with that. It's curious indeed that this issue didn't
> arise with the US time change, however....

It did. The problem is that it doesn't appear to have affected everyone.
David Alcala at Adobe has been investigating this issue since it was
first reported. He has managed to reproduce it with PHP, but not with
ASP or ColdFusion. However, quite a lot of ASP and ColdFusion users have
reported suffering from it. But in all cases that I have heard of,
deleting WinFileCache-********.dat fixes the problem.

I've heard of at least one person who was still working in Dreamweaver
at the time of the clock change, and who has suffered no crashes. I know
that, in the past, you have left Dreamweaver running for days without
switching off. If your computer was running with Dreamweaver open at the
time of the clock change, that might explain why you escaped.

--
David Powers, Adobe Community Expert
Author, "The Essential Guide to Dreamweaver CS3" (friends of ED)
Author, "PHP Solutions" (friends of ED)
http://foundationphp.com/

>There does need to be a better system for propagating information about
>this sort of problem.

Certainly agree with that. It's curious indeed that this issue didn't arise
with the US time change, however....

--
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
==================


"David Powers" <david@example.com> wrote in message
news:fh1t1m$svc$1@forums.macromedia.com...
> Murray *ACE* wrote:
>> I believe that there was a potential fix posted within 24 hours of the
>> issue being raised.
>
> I'm afraid you're mistaken, Murray. I raised the issue internally with
> Adobe at 11.40 GMT on 28 October. The potential fix (which turned out to
> be the real solution) was confirmed at 18.01 GMT on 29 October and
> subsequently posted here. That's a gap of more than 30 hours, which is why
> I said "within 36 hours". However, there's little point quibbling about
> exactly how long it took. Considering the time difference between
> California and Europe, and that it was first raised on a Sunday, it was
> fixed very quickly.
>
> The real problem is that, in spite of many people's efforts, getting the
> message to everyone affected has been difficult. As Steve (Dooza) notes,
> it's not listed anywhere on the Dreamweaver support page as a "Hot issue".
> There does need to be a better system for propagating information about
> this sort of problem.
>
> --
> David Powers, Adobe Community Expert
> Author, "The Essential Guide to Dreamweaver CS3" (friends of ED)
> Author, "PHP Solutions" (friends of ED)
> http://foundationphp.com/

Murray *ACE* wrote:
> I believe that there was a potential fix posted within 24 hours of the
> issue being raised.

I'm afraid you're mistaken, Murray. I raised the issue internally with
Adobe at 11.40 GMT on 28 October. The potential fix (which turned out to
be the real solution) was confirmed at 18.01 GMT on 29 October and
subsequently posted here. That's a gap of more than 30 hours, which is
why I said "within 36 hours". However, there's little point quibbling
about exactly how long it took. Considering the time difference between
California and Europe, and that it was first raised on a Sunday, it was
fixed very quickly.

The real problem is that, in spite of many people's efforts, getting the
message to everyone affected has been difficult. As Steve (Dooza) notes,
it's not listed anywhere on the Dreamweaver support page as a "Hot
issue". There does need to be a better system for propagating
information about this sort of problem.

--
David Powers, Adobe Community Expert
Author, "The Essential Guide to Dreamweaver CS3" (friends of ED)
Author, "PHP Solutions" (friends of ED)
http://foundationphp.com/

Murray *ACE* wrote:
> I believe that there was a potential fix posted within 24 hours of the
> issue being raised.
>

From watching the forum over the last couple of weeks it would appear
that the fix wasn't that easy to find. I have just looked at the Support
site, and think that whilst having the "Hot Issues" on the support home
page is great, maybe they should do the same with the Dreamweaver
support page. It does have Top Issues listed, but the latest is 19 Apr
07. What it needs is a new box with issues like the one we have just
experienced.

What is weird is that I have not experienced this issue and I am based
in the UK. I have worked on dynamic select lists without any problems.

Steve