After installing all the software from the DigitalMars CD, and after initial
teething problems with the IDDE not remembering my preferred settings (which
turned out to be due to the fact that all the files on the CD are read-only,
and stay that way when copied to the hard drive, so the user settings can't
be updated !), all was well. ......Except that  I've never been able to use
Resource Studio.
If I try to open an existing resource file (one of those in the examples
supplied on the CD) from within the IDDE, an error box pops up (with no
program title on its menu bar) saying "abnormal program termination".
If I run Resource Studio in stand-alone mode (by running RS32.EXE) and do
the same thing,  the same error box pops up, and on the status line of the
Resource Studio window it says "File winres.h line 736".
(I was trying to open dm\SAMPLES\MFC32\CONTROLS\BUTTON\button.rc at the
time, but have had the same problem with other resource files).
Does anyone have any idea what the problem is please ?
The only thing I can think of is that perhaps some DLLs need to be copied to
the windows system directory (as in the recent posting about SCT3D32.DLL) -
and if that is the case, then which ones ?

Regards to all,

Jurek.

On Thu, 8 Nov 2001 14:32:59 -0000, "Jurek Wozniak" <jurek_uk01@yahoo.co.uk> wrote:

>After installing all the software from the DigitalMars CD, and after initial
>teething problems with the IDDE not remembering my preferred settings (which
>turned out to be due to the fact that all the files on the CD are read-only,
>and stay that way when copied to the hard drive, so the user settings can't
>be updated !), all was well. ......Except that  I've never been able to use
>Resource Studio.
>If I try to open an existing resource file (one of those in the examples
>supplied on the CD) from within the IDDE, an error box pops up (with no
>program title on its menu bar) saying "abnormal program termination".
>If I run Resource Studio in stand-alone mode (by running RS32.EXE) and do
>the same thing,  the same error box pops up, and on the status line of the
>Resource Studio window it says "File winres.h line 736".
>(I was trying to open dm\SAMPLES\MFC32\CONTROLS\BUTTON\button.rc at the
>time, but have had the same problem with other resource files).
>Does anyone have any idea what the problem is please ?
>The only thing I can think of is that perhaps some DLLs need to be copied to
>the windows system directory (as in the recent posting about SCT3D32.DLL) -
>and if that is the case, then which ones ?
>
>Regards to all,
>
>Jurek.
>
>
>

Jurek,

It wasn't that trivial for me, I ended up copying the resource studio over from SC++ 7.5. Jan's looking into it, but has asked to be reminded to come up with an answer ;-) so please do.

Chris

Thanks Chris.
Unfortunately I don't have a copy of Symantec C++, so it looks as if I'm out
of luck !
I hope you're reading this Jan ...... please can you help ???!!!!   :-)

Yes, I am reading this. I actually follow all the threads in the news groups.

Jan



Jurek Wozniak wrote:

> Thanks Chris.
> Unfortunately I don't have a copy of Symantec C++, so it looks as if I'm out
> of luck !
> I hope you're reading this Jan ...... please can you help ???!!!!   :-)

I'm also having problems with Resource Studio, but only under 32-bit IDDE (abnormal program termination, I didn't try 16bit version, and I'm not going to!).  If I start RS32.EXE from CMD.EXE (Win2000SP2), it works fine.  Is there also a DLL version of RS32, like the compiler being available as EXE for cmdline, and DLL for IDDE?

Maybe you're right about read-only files, maybe this is crashing it.  AFAIK, RS32 and IDDE are somehow inherited from Symantec C++... did they ever work together?  Anyway, crashes are usually easy to debug, so, if Jan will find time for that... :)

Laurentiu

"Jurek Wozniak" <jurek_uk01@yahoo.co.uk> wrote in message news:9se59p$2jca$1@digitaldaemon.com...
> After installing all the software from the DigitalMars CD, and after
initial
> teething problems with the IDDE not remembering my preferred settings
(which
> turned out to be due to the fact that all the files on the CD are
read-only,
> and stay that way when copied to the hard drive, so the user settings
can't
> be updated !), all was well. ......Except that  I've never been able to
use
> Resource Studio.
> If I try to open an existing resource file (one of those in the examples
> supplied on the CD) from within the IDDE, an error box pops up (with no
> program title on its menu bar) saying "abnormal program termination".
> If I run Resource Studio in stand-alone mode (by running RS32.EXE) and do
> the same thing,  the same error box pops up, and on the status line of the
> Resource Studio window it says "File winres.h line 736".
> (I was trying to open dm\SAMPLES\MFC32\CONTROLS\BUTTON\button.rc at the
> time, but have had the same problem with other resource files).
> Does anyone have any idea what the problem is please ?
> The only thing I can think of is that perhaps some DLLs need to be copied
to
> the windows system directory (as in the recent posting about
SCT3D32.DLL) -
> and if that is the case, then which ones ?
>
> Regards to all,
>
> Jurek.
>
>
>
>

Laurentiu Pancescu wrote:

> I'm also having problems with Resource Studio, but only under 32-bit IDDE (abnormal program termination, I didn't try 16bit version, and I'm not going to!).  If I start RS32.EXE from CMD.EXE (Win2000SP2), it works fine.

Bad enough... That's how it has been tested before it was put in CD-ROM...

>  Is
> there also a DLL version of RS32, like the compiler being available as EXE
> for cmdline, and DLL for IDDE?

Not, not as far as I know.

> Maybe you're right about read-only files, maybe this is crashing it.  AFAIK, RS32 and IDDE are somehow inherited from Symantec C++...

Correct.

> did they ever work together?

Yes, in the Symantec C++ V7.5 suite...
However.... *THAT* version is not available....

> Anyway, crashes are usually easy to debug, so, if Jan will find time for that... :)

Hopefully somewhere in the next two weeks.
Do you need a replacement for now?!

Jan

"Jan Knepper" <jan@smartsoft.cc> wrote in message news:<3C0251B5.4C8AB7FA@smartsoft.cc>...
> Laurentiu Pancescu wrote:
>
> > Anyway, crashes are usually easy to debug, so, if Jan will find time for that... :)
>
> Hopefully somewhere in the next two weeks.
> Do you need a replacement for now?!

No, it was actually the first time I used IDDE (I used only command line and makefiles until now, since I started IDDE once, some while ago, and was disappointed by the lack of access to Walter's latest developments in compiler: not even PentiumPro support, I can only select Pentium :).

I was curious how different is DMC's approach to MFC, compared with MSVC's: I like IDDE much more, it's much more powerful!!  BTW, I think the CD contains MFC 3.0, and help files for MFC 4.x; is it possible to plug in MFC 4.2 code from DMC site (if it compiles now), and use everything from IDDE.

A suggestion for web site: could you automatically generate some description with the date of last modifications, and the list of fixes, for those automatically generated tar-gz files?  I know they're generated every night, but this doesn't mean that something has really changed from one day to the other.  So, it's a little harder to decide when it's worth downloading...


Thanks,
  Laurentiu

Laurentiu Pancescu wrote:

> "Jan Knepper" <jan@smartsoft.cc> wrote in message news:<3C0251B5.4C8AB7FA@smartsoft.cc>...
> > Laurentiu Pancescu wrote:
> >
> > > Anyway, crashes are usually easy to debug, so, if Jan will find time for that... :)
> >
> > Hopefully somewhere in the next two weeks.
> > Do you need a replacement for now?!
>
> No, it was actually the first time I used IDDE (I used only command line and makefiles until now, since I started IDDE once, some while ago, and was disappointed by the lack of access to Walter's latest developments in compiler: not even PentiumPro support, I can only select Pentium :).

Sorry, that indeed is one of the things that is going to change as soon as the whole package can be properly compiled and build. (Actually, the changes already have been made.)

> I was curious how different is DMC's approach to MFC, compared with MSVC's: I like IDDE much more, it's much more powerful!!  BTW, I think the CD contains MFC 3.0, and help files for MFC 4.x; is it possible to plug in MFC 4.2 code from DMC site (if it compiles now), and use everything from IDDE.

The CD also should contain MFC 4.2, for the 32 bits platform that is...

> A suggestion for web site: could you automatically generate some description with the date of last modifications, and the list of fixes, for those automatically generated tar-gz files?

Some time in the future...

>  I know they're generated every night,
> but this doesn't mean that something has really changed from one day to the
> other.  So, it's a little harder to decide when it's worth downloading...

No, MFC 4.21 in the .tar.gz files hardly ever changes. Basically only if problems appear after a compiler update. This because I do not think it is a very good idea to deviate to much from the original MFC incase people want to compile their projects with more than one compiler...

Jan

Jan Knepper wrote:
> 
> Laurentiu Pancescu wrote:
> 
> > I'm also having problems with Resource Studio, but only under 32-bit IDDE (abnormal program termination, I didn't try 16bit version, and I'm not going to!).  If I start RS32.EXE from CMD.EXE (Win2000SP2), it works fine.
> 
> Bad enough... That's how it has been tested before it was put in CD-ROM...
> 

Just testing my understanding: the above observations mean you folks were able to start and _load_ a resource file?

"Jan Knepper" <jan@smartsoft.cc> wrote in message news:3C02BEC8.130C9F63@smartsoft.cc...
> The CD also should contain MFC 4.2, for the 32 bits platform that is...

I saw it in the README last night, *after* posting... :(  What confused me is that I didn't find TBSTYLE_FLAT defined anywhere (it's there in MSVC's MFC 4.2, and Win32 headers, since it's a COMCTL32 feature).  The compiler also complained about CToolBar not having a LoadToolbar method, which I already used with MSVC, and MFC help files that come with DMC say it's there.  Does the target have any impact over MFC version?  I saw 16-bit gets it to 2.53, but how about 32-bit targets (Win32s, WinNT, Win95)?  I think Win95 marks the EXE as being 4.0.  BTW, I wasn't getting tooltips because _MFC_VER doesn't get properly defined during resource compiling, and it's checked for by the generated application.  I thought "rcc -32" defines _WIN32, which triggers afx.h to go into 32BIT version of MFC (4.2).


Laurentiu