Possible regressions running Dreamweaver MX? [Solved]

[Evil]

I finally got around to looking further into this today.  It turns out 
the culprit wasn't actually a regression at all.

When the settings were moved out of the config file to the registry, I 
didn't realize that I lost all the DLL override settings.  Failure to 
use the native msvcrt.dll was what stopped it on the splash screen.

After adding the override back via winecfg (and overriding comctl32 + 
commctl, to fix dialog problems), it appears to work as well as ever.

Cheers,
J



Evil wrote:

> Robert Shearman wrote:
>
>> Evil wrote:
>>
>>> After pulling the CVS changes yesterday, My Dreamweaver MX no longer 
>>> starts (hangs on splash).  I'm pretty sure I ran it against CVS on 
>>> Thursday, so this must be a recent change.
>>>
>>> I turned on a couple of debug channels and it seems to be looping on 
>>> a NtWaitForMultipleObjects whose signal never fires.
>>>
>>> Anyone else seeing this, or just me?
>>
>>
>>
>>
>> There were a number of major changes made on Thursday to the 
>> configuration options. I would make sure all of your configuration 
>> settings are moved over to the new registry location first. Then if 
>> that doesn't work, you can start a binary search for regression using 
>> CVS.
>>
> I deleted the .wine directory and re-installed DreamWeaver 
> (successfully), and it's hanging in the same place (splash, 
> NtWaitForMultipleObjects)... so it probably is a regression issue.  
> I'll attempt to figure it out mid-week, if someone doesn't beat me to 
> it (crossing fingers <g>).
>
> -J
>