I just have changed from Tasm to Masm.

Main-reasons for that action were the all nice INC's.
And of course Masm is totally for free!

Is it in all circumstances legal to publish & earn some
money with my own created Programs? I dont want to violate
any rights or laws.

Now to my questions:

1st


Is it true that RC.EXE (MASM) can not handle
Windowstyles-Strings like BRCC32.EXE (TASM)?

example:

LTEXT "BLABLA", -1, 141, 132, 80, 8 WS_DISABLED

--> gives error while compiling!

but this will compile fine

LTEXT "(c) 2002 Tricky Software", -1, 141, 132, 80, 8, 0x8000000
|
Hex-value of
WS_DISABLED

any idea? Perhaps someone has more experience with Masm's ResourceCompiler? Or should I change to a another freeware
ResourceComiler?


2nd

Why there are two DATA's ? I mean .DATA & .DATA?
(Yes, i know. For initialized DATA and unintialized DATA)
But where lays the advantage? After compiling it's one Section, right?

thanks for replies

CRYO
:confused:
Posted on 2002-04-10 13:57:32 by CRYO


LTEXT "BLABLA", -1, 141, 132, 80, 8[COLOR=red][b],[/b][/color] WS_DISABLED

--> gives error while compiling!

but this will compile fine

LTEXT "(c) 2002 Tricky Software", -1, 141, 132, 80, 8, 0x8000000
|
Hex-value of
WS_DISABLED


You forgot a comma (see the red text).


Why there are two DATA's ? I mean .DATA & .DATA?
(Yes, i know. For initialized DATA and unintialized DATA)
But where lays the advantage? After compiling it's one Section, right?


.data? (ununitialized) won't add size to your executable file...
Exemple, if you request 64 kb in .data, you will have it in your executable (it will grow of 64 kb), but in .data? the size won't increase.

.data is nice for arrays, like a static crc-32 computation table, strings, number, things like that
Posted on 2002-04-10 14:25:11 by JCP
thanks for your reply:alright:

Nope
I've tried that Comma already before I posted my question.
Now I'm tried it twice. Just to be sure.


compiling my resources still fails!


The error text returned by RC.EXE is:

undefined keyword or Keyname: WS_DISABLED
Posted on 2002-04-10 14:59:10 by CRYO
Hi CRYO

You need to include Resource.h

#include resource.h

KetilO
Posted on 2002-04-10 15:27:05 by KetilO
I had the same problem with menus in como. .rc files like:

MENUITEM "&Say Hello",IDM_HELLOG, GRAYED
MENUITEM "&Say Hello",IDM_HELLO

but I discoverd that is happ. when I use MENUEX instd. of MENU (this one let me set spec. styles).

Try to find similar changes...

Hope this help you...
Posted on 2002-04-11 05:58:00 by syntheticbyte
to KetilO

nope... I've included the Resource.h-Stuff in rsrc.rc itself.
Without the WS_DISABLED statement all compiles & works fine!

to syntheticbyte

I think RC.EXE seems to be poor in this case.

Working with HEX-Values to define some styles isn't what
I want at all.

trying some freeware-rccompiler like GORC.

I have looked in many MASM examples but never found Windowstyles in their rsrc.rc

Perhaps Tasm is the better choice


thanks

CRYO
Posted on 2002-04-11 06:44:01 by CRYO
GORC was a really good choice!
An excellent compiler if you ask me.

No more problems.:grin:

many thanks to it's creator!
Posted on 2002-04-11 07:41:08 by CRYO
I don't know what your problem is, I can use symbolic constants
just fine with rc.exe ... so it's probably you doing something wrong :]
Posted on 2002-04-11 07:53:20 by f0dder