Dave Dunfield wrote:
> My 0.02USD:
>
>
>
try doing a "POVF" and reporting what is there. Also type
"WHAT"
pick free space is called overflow, because when you create a database file
in pick, you create a base block sized to have a number of hash buckets,
and once these fill up the system adds in "overflow" to contain more data.
this makes for a double edged sword. If you guess and size the file
right, you end up with the first frame being read in and having your
data. if you goof, the ssytem will search down the chains of frames
till it finds it. as time goes on the files get worse and worse.
restoreing
from a backup is the only choice then.
If you have a DC600, you may have 45mb or 60mb of data / tape.
if you get the what info, we can figure out if you have written enough
tapes to equal your disk size.
another command to use is "WHERE" which will tell you about
all the users logged on. Unless the adds is set up for modem control,
you can just move your terminal from port to port and log in.
I can give you some basic program stuff to try once you get a user
account created to play on. Use CREATE-ACCOUNT if there
is no indication of a menu with such utilities in it. Pick had no
consistent menus to assist in these administrative tasks, but
vendors such as Adds added them, and enhanced them.
LISTU will show who is supposed to be logged on, whereas
where is like a unix PS command.
as another warning, there is a 3 or 4 stroke kill the system
permanently at the ! sign, depending on your bad luck. when
you get the ! you are getting a frame number before the period,
and an offset in the frame after it. So 6.123 shows that the
program pointer was in frame 6 (TERMIO) and at offset
123. If you happen to type a . then a valid hex number, it
may store that directly into frame 6 at 123, yeilding a bad
user experence. That is why I want you to get to a sys1
or sys0 Dave account asap. That little feature is disabled.
I'm glad you broke into it, it would have been difficult but
not impossible (danger of above) to break into the system
otherwise.
The system really is not that insecure, as there was and is the
issue of how secure a software system can be without the
encryption that is integrated into laptops today, if you have
physical access to the machine. And the only place the
exploit you pulled can happen is on the console, so if you
secured the console and the connection and the machine,
you were okay. and it was not feasible to be more secure
as in encyrpting everything back then.
when you get a Dave account ttry the following Hello
world program
CREATE-FILE MYBP
ED MYBP HELLO
(prompt is a .)
I<cr> (insert)
001 PRINT "HELLO WORLD"
002 END
003 <cr>
(numbers supplied by editor)
.FI<cr> (file it)
BASIC MYBP HELLO
****
[nnn] PROGRAM MYBP COMPILED
(os some sort of rendition of the above)
RUN MYBP HELLO
HELLO WORLD
if the above works, you are cooking.
of course the > is the TCL prompt. I used MYBP because frequently one
shared a BP (basic program) file with several accounts, and used subroutines
from it on a local account.
I am glad all of you seem to be okay with this, I was offering to shut up
if not. Sounds like we need to get a pick machine up somewhere for all
to play on :-)
Jim