home *** CD-ROM | disk | FTP | other *** search
- ; 12/15/90
- A program which remains resident with 512 bytes after creating a
- file 'BTCHRLSE.COM' which when run releases 'BTCHROOM's resident
- code for use by COMMAND.COM for it's 'BATCH Information Block'.
- When COMMAND.COM executes a batch file it 1) opens the file,
- 2) reads a line, 3) closes the file after recording the file's name
- and location of the last line read and 4) then executes the line.
- This information is kept in RAM in what I will call a 'Batch File
- Information' block, part of the DOS memory chain which I will call
- a 'Batch File Information Block'.
- When running any batch file COMMAND.COM uses the 1st open memory
- block for it's 'Batch File Information Block' if there is no free room
- it puts this block at the top of free ram.
- When running a batch file which releases TSR's from memory using
- such programs as 'MARK/RELEASE', if this block is at the top of free
- ram the release program kills this 'information' block causing
- COMMAND.COM to hang when it can't find it's batch file information.
- Running 'BTCHROOM' in your AUTOEXEC.BAT file before the 1st release
- point leaves it resident with a size of 512 bytes and creates the file
- 'BTCHRLSE.COM'.
- After all the TSR's are loaded, run the new file 'BTCHRLSE', again
- from your AUTOEXEC.BAT, which will release 'BTCHROOM' leaving a 512K
- 'hole' for COMMAND.COM to use which will not be lost when a batch file
- using the 'RELEASE' portion of 'MARK/RELEASE' is run and will erase
- itself from the disk.
-