I didn't feel that this belonged in Main, the Heap, or holy Wars....

Why is it that Masm takes up so much room? The assembler and
linker aren't so bad, but if you try and add kernel32.lib,inc and
windows.inc it doesn't fit onto a disk anymore!

(windows.inc of course could be cut, but not by an amateur)

Tasm on the other hand.. I can get assembler, linker on the same
disk. And then I can add a program that makes .libs from .dlls
(VERY nice ;) ) that I can't find a masm equivilent of. Although
I do remember somthing about one. That eliminates the need
for huge libraries. And the windows.inc tasm uses is much smaller
too. But again, that hardly counts.

To sum it, why is the kernel32.lib so big!? Is 'Lib.exe' a masm
version of IMPLIB.exe.. Is there a small version of windows.inc,
messages and some styles only.. I know the normal one is
everything you could find in it.

Hutch--! You have to help me get masm on 1 disk, and avoid tasm! :grin:
Posted on 2002-02-22 23:27:25 by matthew
Zip it up or Rar it up. :)


check these functions to do it dynamically:

LoadLibrary
FreeLibrary
GetProcAddress
Posted on 2002-02-22 23:36:05 by stryker
BTW, my current disk-masm package:

L2INCA.EXE ;lib to include
L2INCU.EXE ;unicode
LINK.EXE
ML.EXE
NMAKE.EXE
ML.ERR
NMAKE.ERR
BUILD.BAT
HEXIWIN.CNT ;nice, small, basic hexeditor
HEXIWIN.EXE
HEXIWIN.GID
HEXIWIN.HLP

I'd like to get LIB.EXE working so I can include it as a usefull
tool. I'm going to finish an editor and add it. And I'd like to know
DGBWIN.exe works... i'll gonna go look into the readmes with
the masm package and hutch's site.
Posted on 2002-02-22 23:40:42 by matthew
You also forgot the necessary dll's. I suggest you unzip these files under another folder and go to the command line, try assembling an asm file for testing and see if it assembles correctly. :( I already forgot the necessary dll's :( .
Posted on 2002-02-22 23:46:52 by stryker
matthew,

It has a bit to do with what you want to write, more than half of windows.inc is dedicated to NT/w2k type data but editing it out would take a long time.

To get some file sizes down, get a copy of UPX 1.20 from the sourceforge site and try compressing any of the EXE files using the -9 option. This will get some size down. Use the utility HCOMPACT.EXE in the include directory on a copy of windows.inc to remove excess formatting space and se if you end up with enough room to put a few libraries on the disk.

Regards,

hutch@movsd.com
Posted on 2002-02-23 03:14:05 by hutch--
Hutch--, i must offer my sincere gratitude....

The compression on UPX is INSANE!!!!

:grin: :alright: :cool: :tongue:
Posted on 2002-02-23 16:10:29 by matthew
Get yourself a CD writer!

My current "AsmWin" directory is 27 meg. That includes all the .LIB and .INC files, various .HLP files, WINDBG, etc.

I can't imagine giving up any of them!

:)
Posted on 2002-02-23 20:41:08 by S/390

Get yourself a CD writer!
I totally agree. There is nothing like searching a large body of source code and tutorial texts to reduce the road blocks in a project.
Posted on 2002-02-23 20:46:03 by bitRAKE