apn@nonvon.UUCP (root) (05/25/87)
since I have had a few requests for this I am posting
some patches for IBM DOS 3.2 (NOTE, this is not
meant to work on MS-DOS)
4/26/86
DOS32.PAT
PATCHES FOR DOS 3.2
This file follows contains a number of the patches from DOS31A.PAT,
with addresses changed to reflect the DOS 3.2 locations. There are
also several new patches. You should refer to that file for
supplementary information, which you may find useful.
***********************************
The following patches are to be applied to the system file, IBMBIO.COM.
Since this is file has a hidden-system-read-only attribute and since it
must reside on the first sectors of a disk, special care is required
when patching it. There are other methods than the one given below, but
the one given is easy to follow and reliable if followed exactly, and
allows these instructions to be written with fewer words.
1) Format /S a disk with 3.2. Copy DOS 3.2 SYS.COM to it.
2) Use CHMOD or other utility to set the file attibute for IBMBIO.COM
to NORMAL (00h). Use the disk only for applying these patches.
Above all, DO NOT erase anything from the disk!
3) After the IBMBIO.COM patches have been made, reset the file
attibute to hidden-system-read-only (27h), using CHMOD, Norton's
NU, etc.
4) Put the disk in Drive A: and boot from it. To copy it to an HD,
type: SYS C:
PATCH #1:
Purpose:
To quiet and improve performance of Tandon 360k drives:
DEBUG IBMBIO.COM
-e 2A95
xxxx:2A95 0F.00 <cr> (Settle time)
-e 2A9B <cr>
xxxx:2A9B DF.EF <cr> (Step rate)
-w
-q
PATCH #2:
Purpose:
This patch is for HD users only. Use it if you have a 19mb or
smaller HD that was set-up under 3.1 for 2k cluster sizes, AND,
with which you are experiencing difficulty reading, after you've
installed 3.2. (Remember, you are to make this patch on the floppy
outlined above!)
Contributor: Mark Lautenschlager, Micro-Systems Software
DEBUG IBMBIO.COM
-e 2F4E <cr>
xxxx:2F4E 75.72 02.EC EB.90 08.90 <cr>
-e 2F58 <cr>
xxxx:2F58 75.77 <cr>
-w
-q
End of IBMBIO.COM patches.
*****************************
PATCH #3:
Purpose:
To make ECHO OFF the default for .BAT files, including AUTOEXEC's.
DEBUG COMMAND.COM
-e 115E <cr>
xxxx:115E 03.02 <cr>
-e 1B2C <cr>
xxxx:1B2C 01.00 <cr>
-w
-q
****************************
PATCH #4:
Purpose:
To enable the ECHO command followed by 2 spaces to generate a
blank line.
DEBUG COMMAND.COM
-e3A88 <cr>
xxxx:3A88 E8.83 20.F9 00.02 74.02 <cr>
-w
-q
****************************
Note: The CLS problem in DOS 3.1, COMMAND.COM which caused 26 lines
to be cleared instead of 25, has been fixed in 3.2.
****************************
PATCH #5:
Purpose:
To permit up to 50 mismatches in COMP.COM instead of 10.
DEBUG COMP.COM
-E 0AF3<cr>
xxxx:0AF3 0A.32<cr>
-E 0E09<cr>
xxxx:0E09 31.35<cr>
-W<cr>
-Q<cr>
****************************
More patches will be added as we figure them out.
Many thanks to Ted Eyrick for his work with DOS 3.1, which made
the above work much easier.davidsen@steinmetz.steinmetz.UUCP (William E. Davidsen Jr) (05/27/87)
I have said this before, but I'll mention it again.
_______________________________________________________
| |
| You don't need patches to get blank echo lines in DOS |
|_______________________________________________________|
in a batch file an ECHO command followed by exactly on dot will product
a blank line. Example: "ECHO."
This has been in every version of DOS since 2.0!! A patch for this
"problem" is not needed, and encourages writing batch files which are
not portable.
PS: in DOS3.3 you can put "@ECHO OFF" at the start of a batch file and
it will not be echoed. Microsoft listened on this one.
--
bill davidsen sixhub \ ARPA: wedu@ge-crd.arpa
ihnp4!seismo!rochester!steinmetz -> crdos1!davidsen
chinet /
"Stupidity, like virtue, is its own reward"