🚀 go-pugleaf

( text about breaking up a large RC file and using copy /b to make final RC)

>This is a bogus thing to do in general. In Win 2 this may have worked but
>in Win3 the result is a bogus exe file.  The suggested method is to
>
>#include "foo.rc"
>
>in your main rc file. Then the 3.0 rc will generate one big res file.
>
>Win 2 rc had some size limitations which were removed in Win 3.
>
>
>
>--Dave






Well Dave...

The limitations may have been up'ed but not removed.  I hoped that that was
the case when I ported our product to win30.  We were a part of the beta
program.  I tried to use a single RC file with each upgrade of the beta disks.
Each time it failed with a memory message.  Each time I used multiple .res
files copied after each other to a final .res file which was then put into
the .exe file with rc.exe.  It still works, the product works, no problems.
We took all strings out of the code and put them into string tables.  Using
the rcinclude does not help if your tables just get to large.  rc.exe will
still have to choke down the tmp file that has the full tables and whatever
else.  What do you mean by bogus .exe file?  Does that mean that it won't run?
Does it mean that exehdr.exe won't report on it?  Our product runs, and
exehdr.exe reports correctly.  That seems to me that the .exe is not bogus
dosen't it?  Try again Microsoft.  RC.EXE still has limitations.





------------------------------------------------------------------------------
"tired and shagged out from a prolonged squawk" - mpfc the parrot sketch