Category: CSS / HTML

I use Adobe Creative Suite 3 (CS3) Web Premium every day, Flash, Fireworks, Photoshop, but most of all Dreamweaver. I consider Dreamweaver CS3 to be the best HTML/CSS visual editor available and a it’s a very handy FTP client as well. It also serves as a nice text editor with syntax highlighting for PHP (although PDT for Eclipse is MUCH better). My problem is that it crashes on me almost every day with this really annoying error: Runtime Error! This application has requested the Runtime to terminate it in an unusual way. Here’s what it looks like:

This error makes my blood boil! I’ve done everything to try it including, but not limited to:

Delete the configuration Files

This seems to give me the most success. Dreamweaver stores a file cache and some non-site related settings in C:\Users\[your username]\AppData\Roaming\Adobe\Dreamweaver 9\Configuration. If you delete or rename this directory then Dreamweaver will recreate it when it starts up.

Delete the Dreamweaver Windows Prefetch file

When a program starts up, Windows trys to optimize the startup process by creating a “cache” type file in C:\windows\Prefetch. Next time the program opens it uses this file to speed up the process. You can safely delete everything in the Prefetch folder. Doing this helped me get Dreamweaver working yesterday.

Get rid of Logitech SetPoint

Someone on an Adobe forum said this worked for them – I haven’t had much success

Restart computer with only essential processes enabled

Also from Adobe, this seems to have no impact on my computer – it still crashes.

Maybe it’s the 8KB file bug???

According to many people on Adobe’s forum, if you a working on a file that is exactly 8,192 bytes (8KB) Dreamweaver will crash. Well, my files are taking up 8,192K because the block size on my disk pushes 7+K files up to 8,192 (look at “size on disk”), but I put a huge HTML comment at the end of the file to push it past 10K and it didn’t help.

Doing the exact same thing every time will make Dreamweaver crash every time

Here’s my most effective solution as of this morning: once Dreamweaver crashes, you can’t do the exact same thing when you reopen it or it will just keep crashing. I was trying to add a 4×3 table to a document and everytime I did Insert->Table->OK it immediately crashed (I did this 10+ times while changing other Windows stuff). Then I went to show my business partner and instead of adding a table, I went to a different Site and changed some code around, then when back to the original site and BAM! it works fine now! What the HECK is going on here?

Final thoughts

You know, I’ve been working with Linux and open source software for over 10 years, and I finally break down and by a $2,000+ software package – I expect it to work! If it doesn’t work I expect that I can get support to make it work (and not that “please restart your computer then uninstall/reinstall” BS)! Come on Adobe!!! If I charge my clients >$100/hr and I have to fight with Dreamweaver for 1 hr per day, where’s my $36,500 from Adobe for the last year?

P.S. I think the problem is related to MS Visual Studio 2005’s runtime update and Vista or something.

Have you ever seen the annoying gray box around Flash content on websites? If you have, you must have done the unthinkable and used Windows Update [:O]. To make a long story short, a company called Eolas Technologies got in a yelling match with Microsoft and the two companies have since tried to make life more difficult for each other. Microsoft decided to require Internet Explorer users to click once on EVERY ActiveX control (actually anything in an EMBED or OBJECT tag) as a safety precaution. You can read more about that battle here: Microsoft tweaks browser to avoid liability | CNET The solution to this problem is to embed the object in the page dynamically – after the page is loaded. This is exactly what SWFObject by deconcept does – and it does it well! SWFObject is also capable of Flash Player version detection in Javascript and has been used on some big name sites like YouTube.

Everytime I want to use SWFObject I am annoyed that I don’t remember the syntax, so I wrote a nice little script that will convert the <object>…</object>┬ácode that you get when you publish in Flash into SWFObject friendly code! The script is located here:

As an example, it will convert this HTML code:

<object classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000"
/,0,0,0" width="100" height="50" id="flashtab"

<param name="allowScriptAccess" value="sameDomain" />
<param name="movie" value="flashtab.swf" />
<param name="quality" value="high" />
<param name="wmode" value="transparent" />
<param name="bgcolor" value="#ffffff" />
<embed src="flashtab.swf" quality="high" wmode="transparent"
bgcolor="#ffffff" width="100" height="50" name="flashtab"
align="middle" allowscriptaccess="sameDomain"
pluginspage="" />

To this SWFObject code:

<div id="swfdiv_flashtab">  
This text is replaced by the Flash movie.  
<script type="text/javascript">  
  var so = new SWFObject("flashtab.swf", "flashtab", "100", "50",
"8.0.0", "#ffffff");  
  so.addParam("allowscriptaccess", "samedomain");  
  so.addParam("quality", "high");  
  so.addParam("wmode", "transparent");  

I just ran across a problem where I needed to ignore/disable <br> tags. Here’s the situation – I use CSS to spice up my <code> tags in this blog, but when I add new entries it adds a <br /> after every line feed; this normally wouldn’t be a problem but I use ‘white-space: pre’ to keep my code indents. ‘white-space: pre’ is like using a <pre> tag for your element, so both line feeds and <br /> tags are converted to new lines. After searching on the net for a bit I realized that people are over complicating the answer – just change the line-height to 0px:

code br{
    line-height: 0px;