invocation of dw/s4 crashes after super suite install

We ran DW/CS4 (10.0 build b4117) from both our Duo2Core iMac and our Mac Mini (both running 10.5.8). I installed (with Adobe Extension Manager) all of the WebAssist Super Suite extensions (purchased September 27, 2007 and recently updated for this first-time install) and then installed:

Cookies Toolkit 3.1.1
DataAssist 1.3.1
Database Search 1.4.1
Digital File Pro 1.1.3
Dynamic Dropdowns 2.7.3
Dynamic Flash Charts 1.9.2
eCart 4.5.0
Eric Meyer's CSS Sculptor 1.1.5
Site Import 1.1.5
SiteAssist 3.2.3
Universal Email 3.0.6
Validation Toolkit 2.3.5
WebAssist.com PhotoAssist 1.1.0
WebAssist.com Validation Toolkit Recipes 1.2.0

I rebooted the Mac Mini system and invoked.
DW crashes every time upon invocation.
I tried it on the iMac as well with the same problem.
Please advise....

I can avail the traceback "dump" for you for either or both systems.
Here is the Mac Mini's "system configuration" info:

Model: Macmini3,1, BootROM MM31.0081.B06, 2 processors, Intel Core 2 Duo, 2 GHz, 2 GB
Graphics: kHW_NVidiaGeForce9400Item, NVIDIA GeForce 9400, sppci_pci_device, 256 MB
Memory Module: global_name
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x90), Broadcom BCM43xx 1.0 (5.10.91.19)
Bluetooth: Version 2.1.9f10, 2 service, 1 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Serial ATA Device: FUJITSU MHZ2120BH G1, 111.79 GB
Serial ATA Device: OPTIARC DVD RW AD-5670S
USB Device: USB to Serial-ATA bridge, (null) mA
USB Device: USB2.0 Hub, (null) mA
USB Device: Back-UPS CS 500 FW:806.q8.D USB FW:q8, (null) mA
USB Device: EPSON Scanner 010F, (null) mA
USB Device: Inkjet color printer, (null) mA
USB Device: Iomega HDD USB 2.0 Drive, (null) mA
USB Device: IR Receiver, (null) mA
USB Device: PTZ-431W, (null) mA
USB Device: Hub in Macally ICEKEY keyboard, (null) mA
USB Device: Apple Optical USB Mouse, (null) mA
USB Device: Macally ICEKey keyboard, (null) mA
USB Device: BRCM2046 Hub, (null) mA
USB Device: Bluetooth USB Host Controller, (null) mA

Thanks,
Chris Gray
(925) 682-8733
Pleasant Hill, CA

Have you cleared the cache?

Solving problems with Dreamweaver
146/

Thanks for the quick reply.

Sometimes just a reboot will clear away buffer errors, however, I am unsure when it comes to cache. Since the caches (not seen via any MacOSX utility of which I am aware) all appear to be application-based, and if that's the problem-area, anything from a user logoff or a reboot may not be automated unless by another maintenance application.

To force a cleaning of some cache, I used MacTuneUp 3.6.0, which is not specific about which non-Apple application caches it clears, and I dio not know if it even does clear anything besides Apple caches, nonetheless, I am using it:

MacTuneUp --> Maintenance --> Clean Up --> Clean Application Caches:

[x] All standard caches
[ ] Mail
[ ] Address Book
[ ] iPhoto
[ ] iChat
[ ] iCal
[ ] Java

I performed this, and it still cannot be invoked, so any DW-specific ability to clear cache is unreachable to me from what I currently know.

Is this the cache you meant?
Other caches or clearing methods?

If this clears cache as the culprit, then perhaps there is some sort of integration bug w/r/t 1+ of the extensions and DW, an extension load bug (which the traceback might reveal), or merely a DW Preferences conflict resulting from a corrupted installation process?

I await further suggestions or already written-up procedures for resolution.
Remember, I do have the traceback from both systems, which will reveal exactly what crashed and in which order.... Would removal of all fix the problem? If so, I could install one extension at a time to see which breaks it?

Thanks,
Christopher Gray
rasputin@teleport.com

Wrong cache.

Please see step 1:
Solving problems with Dreamweaver
146/

Thanks.
After renaming MacFileCache-A58CCE96.dat to MacFileCache-A58CCE96.original-dat via instructions in Step 1, the DW/CS4 (Mac) invocation still crashed, so I moved on to Step 2.

DW/CS4 now invokes, and all previous Site Manager connectivity is unscathed. Whew! I manage ten (10) web sites via my DW/CS4 and BBEdit tools.

I will remove all extensions. I had pulled them all down from the WebAssist server far after CS4 was released.

Did you notice an out-of-date extension version, listed in my first post? If my version list matches the "latest-and-greatest" listed on the download page, then I am going to install one extension at a time, with DW/CS4 invocation checks after each. I do not want to go through this full install/uninstall again, but may have to if one extension conflict that conflicts with the Adobe-Apple bug is used to corrupt the whole configuration.

I do very much appreciate your assistance while Adobe and Apple whine about doing the customer-oriented, legal, and ethical thing: fixing the problem. Rather, they pass the problem down to treated-as "lowly" partners and users while instead, they spend that time, marketed ever so well as "quality first", counting their dollars. Grrrr!

I will keep you posted if I do not get an specific extension version from you that may have been the one that was out-of-date. because, then, I will presumably have to start all over or leave that extension out if it indeed 'is' up-to-date but problematic.

Thanks again,
Chris gray

You're welcome.

What I do is check to make sure I have the most up-to-date version every time I use an extension that I haven't used in awhile. Then I check the forum for stickies on Known Issues.

The new layout for the Downloads page makes it very easy to check all versions by opening up Extension Manger next to the list of extensions. If I find that one of mine is out-of-date, I delete it from Extension Manager and download the new version. This prevents me from accidentally trying to install a new version over the old one and corrupting my cache.

After I have all the new versions downloaded and the old ones removed, I start installing them one at a time deleting the cache after installing. This method has allowed me to avoid the common problems with DW.