Web Images Videos Maps News Shopping Gmail more »
Recently Visited Groups | Help | Sign in
Google Groups Home
Message from discussion Dreamweaver CS3 Crashes At Startup
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
David Powers  
View profile  
 More options Aug 25 2007, 10:26 am
Newsgroups: macromedia.dreamweaver
From: David Powers <da...@example.com>
Date: Sat, 25 Aug 2007 15:26:04 +0100
Local: Sat, Aug 25 2007 10:26 am
Subject: Re: Dreamweaver CS3 Crashes At Startup

marceloxx669 wrote:
> I did uninstalled before reinstalling to no avail. I ll try installing an older version, I didn`t pay for the Suite, the company did though.(dissapointed)

This is a long shot, but it might explain your problem.

While writing my latest book, I discovered that Dreamweaver crashed
every time that I changed a measurement in a particular stylesheet from
5px to 0. Not only that, it consistently crashed whenever I tried to
restart Dreamweaver, and the only way to solve the problem was to delete
the style sheet. Since the style sheet was installed by the Spry Tabbed
Panels Widget, I wondered if there was a bug with the widget, so I
contacted Adobe.

The answer revealed one of the most bizarre bugs ever. Dreamweaver CS3
crashes if you create a file that is exactly 8,192 bytes (or a multiple
thereof) in length. Try moving your sites (or the contents of the site
folders) temporarily to a different location, and see if Dreamweaver
launches. If it does, it's then a question of locating the file that's
causing the crash. I solved my problem by using 0px instead of 0. That
added 2 bytes to the file size, thereby avoiding the bug.

I understand that Adobe has identified the cause of the bug, and that it
will be eliminated in the next release (I'm hoping that means an
updater, but I don't have any information about that).

As I say, it's a long shot, but it's worth trying.

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


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.

Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google