home *** CD-ROM | disk | FTP | other *** search
- From: Inbar Raz
- To: Itay Zandbank Date: 21 Mar 92 08:49:00
- Subj: PkLite extractor program, incl. source
- Conf: `PC Assembly Language'
- *******************************************************************************
- > You don't need a program for that. Run the PKLITEed program under a
- > debugger, and single-step past that load sequence. Then you'll have the
- > original program in memory just waiting to be saved to disk.
-
- That's exactly (well, almost) what my program does. I was searching for a 'MOV
- DI,AX' and replaces it with INT3. Before that instruction is executed, DI holds
- the filesize+100, so you even know what to put in Debug's CX. My new int3
- (reprogrammed by the program) simply writes the program to disk.
-
-
- The code, for COM's only:
-
-
- ======================== cut here ========================================
-
- [extracted to EXLITE.ASM]
-
- ======================= cut here ====================================
-
-
- See what I mean?
-
- Inbar Raz
- Co-SysOp,
- Alien's BBS
-
- -!-
- ! Origin: Inbar's Point, Yavne, ISRAEL. True ZMailH Point. (2:403/123.5)
-
- From: David Kirschbaum
- To: Inbar Raz Date: 25 Mar 92 11:15:58
- Subj: PkLite extractor program
- Conf: `PC Assembly Language'
-
- Hey, your EXLITE.ASM is just fine! Saves a lot of grunge work.
- I've taken the liberty of making a few tweaks (see attached).
-
- Do you object to your original message and the tweaked code
- being uploaded to the Internet's famous SIMTEL20 archive?
- You'll get full credits, of course. (I'm only the tweaker.)
-
- I'd like to add a "Released to the public domain" to it,
- if you don't mind, just to make it absolutely clear about
- copyrights, etc. Or if you *do* have any constraints on
- the code, could you let me know?
-
- David Kirschbaum
- Toad Hall
- === new EXLITE1.ASM follows ===
- [deleted]
-
- From: Inbar Raz
- To: David Kirschbaum Date: 31 Mar 92 14:16:00
- Subj: Pklite Extractor Program
- Conf: `PC Assembly Language'
-
- > Do you object to your original message and the tweaked code
- > being uploaded to the Internet's famous SIMTEL20 archive?
- > You'll get full credits, of course. (I'm only the tweaker.)
-
- I do not object at all. On the countrary. I have been interested in the process
- of making a software a PD so I could send a couple of other progs I wrote.
-
- > I'd like to add a "Released to the public domain" to it,
- > if you don't mind, just to make it absolutely clear about
- > copyrights, etc. Or if you *do* have any constraints on
- > the code, could you let me know?
-
- Be my guest. However, I am not familiar with the word 'constraints', and I am
- too lazy to dictionary it up. Please explain...
-
- > David Kirschbaum
- > Toad Hall
- > === new EXLITE1.ASM follows ===
-
- > ; ExLite, by Inbar Raz, Jan. 12th, 1992.
- > ; via FIDO's PC Assembly Language Echo
- > ;
- > ; Run: ExLite <filename>.
- > ;
- > ;v1.1 Toad Hall Tweak, 25 Mar 92
- > ; - Insured CS: overrides where required
- > ; - Significant tightening
- > ; David Kirschbaum
- > ; Toad Hall
- > ; kirsch@usasoc.soc.mil
- .
- .
- .
- mov ah,4Ch ; Terminate process
- int 21h
-
- > CSEG ENDS
- END ExLite ;v1.1
-
- Well, you are playing with a lot of M/TASM pseudo commands, which I am not
- familiar with them either. I am used to write a classic program. I should learn
- this sometime. I didn't understand a lot of your changes, if any...
-
- Inbar Raz
- Co-SysOp,
- Alien's BBS
-
- -!-
- ! Origin: Inbar's Point, Yavne, ISRAEL. True ZMailH Point. (2:403/123.5)
-
- From: David Kirschbaum
- To: Inbar Raz Date: 06 Apr 92 11:02:40
- Subj: PkLite extractor program
- Conf: `PC Assembly Language'
-
- DK> Do you object to your original message and the tweaked code
- DK> being uploaded to the Internet's famous SIMTEL20 archive?
- DK> You'll get full credits, of course. (I'm only the tweaker.)
-
- IR> I do not object at all. On the countrary. I have been interested in the
- IR> process of making a software a PD so I could send a couple of other
- IR> progs I wrote.
-
- Great! The process is easy: You just say "Released to the public domain"
- and do NOT say "Copyright". It then belongs to the world.
-
- DK> I'd like to add a "Released to the public domain" to it,
- DK> if you don't mind, just to make it absolutely clear about
- DK> copyrights, etc. Or if you *do* have any constraints on
- DK> the code, could you let me know?
-
- IR> Be my guest. However, I am not familiar with the word
- IR> 'constraints', and I am too lazy to dictionary it up. Please
- IR> explain...
-
- Some authors put constraints, limitations on how their code can
- be used, or who can use it. Some authors feel users must be
- "politically correct." I remember one example where the author
- forbade any US Department of Defense use. Others say their code
- can't be used in ANY commercial context.
-
- Some authors have been upset by their code being stolen and
- copyrighted by another person or company. It doesn't happen
- often, but it *does* happen. For this reason, whenever I
- produce anything significant that I wish to "give to the world",
- I usually copyright it ("Copyright (C) 1991 David P Kirschbaum"),
- but then add a release statement ("May be freely used for all
- purposes, public and private.") That keeps some feelthy
- multinational from claiming it as their own.
-
- Some authors like to add the line "May be freely distributed,
- so long as the original author [and copyright] is not removed."
-
- This insures their everlasting glory and fame, I suppose :-)
-
- > CSEG ENDS
- END ExLite ;v1.1
-
- IR> Well, you are playing with a lot of M/TASM pseudo commands, which I am not
- IR> familiar with them either. I am used to write a classic program. I should
- IR> learn this sometime. I didn't understand a lot of your changes, if any...
-
- Well, I don't use all the newfangled "simplistic" or "Ideal"
- options available in the latest version of TASM .. mainly
- because that makes it impossible for someone *without* TASM's
- manual to figure out! I stick with the old-fashioned segment
- declarations, and use LOTS of "ASSUME" statements just to insure
- the assembler (and reader) isn't confused about where DS and ES
- are pointing.
-
- Part of the CSEG and ASSUME stuff is to insure that the
- assembler correctly computes the program length (in paragraphs)
- for the TSR envocation. What I did works, and I'm *sure* it
- works, and I'm not sure any other "simplistic" or "Ideal" method
- would work.
-
- I'll double-check the EXLITE code, put in some nice public
- domain statement (if that's ok with you), and field it with some
- documentation (probably here since some others are asking for
- it), and via the Internet (SIMTEL20 and perhaps comp.sources.ibmpc
- via Usenet).
-
- That'll insure *your* everlasting fame :-)
-
- Until someone writes a better one.
-
- Regards
- David Kirschbaum
- Toad Hall
-
- ... Mail your ideas written on the back of a $20 bill to...
-