October 29, 2003
I have been using DMC++ since the Symantec days, and I have been struggling with Resource Studio. Being unwilling to bow to Lord Gates, I refused to use VC and its paltry resource editor. In desperation, I decided to look out on the web for a resource editor, hopeful that I would find something compatible with DMC++ that would give me access to visually edited resource files.

What I found out there came as a slight shock...apparently, you can download the Symantec version of Resource Studio, version 1.0, from a few places out there on the web. I decided to see if this would be helpful in solving my resource editor problem.

One location: http://personal5.iddeo.es/ret007ow/tools.html

I unzipped the file into \dm\bin where rs32 lives, and I let the unzip overwrite everything except the MFC DLLs.

This seems to be working fine, without major issues. The IDDE opens rs32 on demand, I can modify my resources, and I can get out, no fuss. Once in a great while rs32 will spawn over and over, so no matter how often I kill it, it returns from the dead. It happens so infrequently that it hasn't deterred me. So, after a small bit of effort, I am back up and running with a visual resource editor under DMC++'s IDDE. Granted, if anything has been fixed from 1.0 to 1.1, I do not have access to the fixes, but that didn't help when it crashed consistently before anyway.

Why this makes it go, I'm not sure. However, I'm not one to argue.

I hope this is of some help to one or more of you.

M@


October 29, 2003
From memory, I think originally it was a company called Whitewater group
that wrote one fine language called Actor.   They also wrote WRT - Whitewater
Resource Toolkit which was bundled with Borland BC2.0 and later Symantec
C++ 6.0.  The class editor for Actor is now in the IDDE and somehow a few
things in between.  I don't know whether it is SRT you mentioned.

The crashes I experienced with RS were:

1) Switching between Win-16 resources and Win-32 resource file format. 2) Network/Domain DLL conflict.

As I have posted before, running Win98 in safe mode allows me to run RS32 without problems.  Running in normal mode is luck dependant.

"Matt Morgan" <geckofood.ya-hoo@spammergotohell.com> wrote in message news:bnnbb3$1qie$1@digitaldaemon.com...
> I have been using DMC++ since the Symantec days, and I have been struggling with Resource Studio. Being unwilling to bow to Lord Gates, I refused to use VC and its paltry resource editor. In desperation, I decided to look out on the web for a resource editor, hopeful that I would find something compatible with DMC++ that would give me access to visually edited resource files.
>
> What I found out there came as a slight shock...apparently, you can download the Symantec version of Resource Studio, version 1.0, from a few places out there on the web. I decided to see if this would be helpful in solving my resource editor problem.
>
> One location: http://personal5.iddeo.es/ret007ow/tools.html
>
> I unzipped the file into \dm\bin where rs32 lives, and I let the unzip overwrite everything except the MFC DLLs.
>
> This seems to be working fine, without major issues. The IDDE opens rs32 on demand, I can modify my resources, and I can get out, no fuss. Once in a great while rs32 will spawn over and over, so no matter how often I kill it, it returns from the dead. It happens so infrequently that it hasn't deterred me. So, after a small bit of effort, I am back up and running with a visual resource editor under DMC++'s IDDE. Granted, if anything has been fixed from 1.0 to 1.1, I do not have access to the fixes, but that didn't help when it crashed consistently before anyway.
>
> Why this makes it go, I'm not sure. However, I'm not one to argue.
>
> I hope this is of some help to one or more of you.
>
> M@
>
>