From 7421e70053b25a8609f2414dc595692afcd6b525 Mon Sep 17 00:00:00 2001 From: "B. Watson" Date: Fri, 24 May 2024 15:38:55 -0400 Subject: unprotbas: tweak doc. --- unprotbas.1 | 4 ++++ unprotbas.rst | 4 ++++ 2 files changed, 8 insertions(+) diff --git a/unprotbas.1 b/unprotbas.1 index 6c82dc0..0f7f37c 100644 --- a/unprotbas.1 +++ b/unprotbas.1 @@ -176,6 +176,8 @@ table might be smaller. The program \fBPROTECT.BAS\fP, found on Disk 2 of the Holmes Archive, creates protected BASIC programs that only use variable name scrambling. +.sp +\fBunprotbas \-pv\fP also does variable name scrambling. .TP .B Bad next\-line pointer Every line of tokenized BASIC contains a line length byte, which @@ -209,6 +211,8 @@ information is lost by doing this. The program \fBUNPROTEC\fP, from the \fIPirate\(aqs Treasure Chest\fP, can fix bad pointers in protected programs, though it doesn\(aqt do anything about variable name scrambling. +.sp +\fBunprotbas \-pc\fP also does this type of protection. .UNINDENT .sp One more thing \fBunprotbas\fP can do is remove extra data from the end diff --git a/unprotbas.rst b/unprotbas.rst index 13c16a6..f6e733d 100644 --- a/unprotbas.rst +++ b/unprotbas.rst @@ -151,6 +151,8 @@ Variable name table scrambling creates protected BASIC programs that only use variable name scrambling. + **unprotbas -pv** also does variable name scrambling. + Bad next-line pointer Every line of tokenized BASIC contains a line length byte, which BASIC uses as a pointer to the next line of code. Before printing @@ -184,6 +186,8 @@ Bad next-line pointer fix bad pointers in protected programs, though it doesn't do anything about variable name scrambling. + **unprotbas -pc** also does this type of protection. + One more thing **unprotbas** can do is remove extra data from the end of the file. It's possible for BASIC files to contain extra data that occurs after the end of the program. Some programs use this as a way -- cgit v1.2.3