kdq@demott.COM (Kevin D. Quitt) (06/30/90)
Ok, I've got msker301.pch, I rename it to mskermit.pch, I start
kermit and issue the patch command. Nothing happens. When I exit, the
file's the same. How do I save the patches? Do I have to have the patch
command in mskermit.ini from now on? Why doesn't the patch work? Anybody
care to tell me how I'm making an ass of myself? Thanks in advance.
--
_
Kevin D. Quitt demott!kdq kdq@demott.com
DeMott Electronics Co. 14707 Keswick St. Van Nuys, CA 91405-1266
VOICE (818) 988-4975 FAX (818) 997-1190 MODEM (818) 997-4496 PEP last
96.37% of all statistics are made up.altman@sbstaff2.cs.sunysb.edu (Jeff Altman) (07/01/90)
Just leave the mskermit.pch file in the same directory as the kermit.exe and place the 'patch' command at the beginning of the mskermit.ini file. No changes are made to the executable on the disk. The patch is made at run-time. - Jeff (jaltman@ccmail.sunysb.edu)
LC.YRS@forsythe.stanford.edu (Richard Stanton) (07/02/90)
In article <346@demott.COM>, kdq@demott.COM (Kevin D. Quitt) writes: > > Ok, I've got msker301.pch, I rename it to mskermit.pch, I start >kermit and issue the patch command. Nothing happens. When I exit, the >file's the same. How do I save the patches? Do I have to have the patch >command in mskermit.ini from now on? Why doesn't the patch work? Anybody >care to tell me how I'm making an ass of myself? Thanks in advance. > It only patches the in RAM copy of the program, not the permanent version stored on disk. Put the command "PATCH" as the first line in your MSKERMIT.INI file. Richard Stanton
kdq@demott.COM (Kevin D. Quitt) (07/02/90)
In article <10276@lindy.Stanford.EDU> LC.YRS@forsythe.stanford.edu (Richard Stanton) writes: >In article <346@demott.COM>, >kdq@demott.COM (Kevin D. Quitt) writes: >> >> Ok, I've got msker301.pch, I rename it to mskermit.pch, I start >>kermit and issue the patch command. Nothing happens. When I exit, the >>file's the same. How do I save the patches? Do I have to have the patch >>command in mskermit.ini from now on? Why doesn't the patch work? Anybody >>care to tell me how I'm making an ass of myself? Thanks in advance. >> >It only patches the in RAM copy of the program, not the permanent >version stored on disk. Put the command "PATCH" as the first line in >your MSKERMIT.INI file. > I tried this, but the patches don't work. For example, the cwd command still echoes. -- _ Kevin D. Quitt demott!kdq kdq@demott.com DeMott Electronics Co. 14707 Keswick St. Van Nuys, CA 91405-1266 VOICE (818) 988-4975 FAX (818) 997-1190 MODEM (818) 997-4496 PEP last 96.37% of all statistics are made up.
LC.YRS@forsythe.stanford.edu (Richard Stanton) (07/03/90)
In article <348@demott.COM>, kdq@demott.COM (Kevin D. Quitt) writes: >In article <10276@lindy.Stanford.EDU> LC.YRS@forsythe.stanford.edu (Richard Stanton) writes: >>It only patches the in RAM copy of the program, not the permanent >>version stored on disk. Put the command "PATCH" as the first line in >>your MSKERMIT.INI file. > > I tried this, but the patches don't work. For example, the cwd command >still echoes. > I remember this happening to me. A patch for 3.00 cured this problem, and 3.01 was supposed to contain fixes for all the known problems in 3.00, but something went wrong. 3.01 with its first patch file still echoed CD commands. Later versions of the patch file cured the problem. You can get patch files from WATSUN.CC.COLUMBIA.EDU via anonymous FTP. Richard Stanton