ADDS Mentor 2000 - Big success!

Dave Dunfield wrote: you have 512K system which is a fairly large system. you have 8 active ports. 9 processes, 1 / port, 1 for the print spooler process 768 PCB0 means you have 768 abs frames, which contain the system code. PCB's. Picks virtual architecture requres at any time a PCB, code to execute in any give ABS frame, and a monitor construct called a PIB. there is only one PIB / process, but there is a main PCB for the code to run in, and a special PCB for each process to run the debugger context in. the system file is laid down at 4485 and has 27 base frames (modulo = 1) a Maxfid of 74623 implies a 75mb disk if the frame sicze is 1024 and 35mb if it is 512. you have therefore got about 1/3 your space free. if you can dump a frame, say the first frame of the system frame we can infer from that dump what the frame size is. IIRC "DUMP 4485 (X" will give a hex dump. if it goes to 512, then we have 512 byte frames and the total system size id 74523 is multiplied by 512 to give the above estimate of 35mb, etc. Pick systems have been implemented with up to 4096 byte frames. more on the frames later. the reason for mentioning securing the console or port 0, is that the system always boots up on that. therefore there are never any spurious breaks to annoy you. once the system releases the other lines to run and accept logons, they dont get the spooler startup window, they all just get LOGON PLEASE, which does not have the hole (in theory) BTW, the behaviour of hanging your console with a break probably is due to the fact that you can do break while in the kernel. before the system goes "virtual" and runs the other lines and allows logins, all the async I/O is done by the kernal, and is frequently not designed by the kernel coders to be tolerant of breaks. just a fact of life with what pick systems did. the open sys2 accounts are inexcusible. that is just sloppy system administration. one of the things that pick did was to turn people who usually had adding machines next to their desks into system administrators, and as you will find programmers. This lead to some leaps in what you could expect in skills with the site that ran pick. It is worse than now because there was no way to point to examples of how things like these accounts could bite you so even if our documentaiton and training said to get rid of them, there was always some guy who figured if the acocunts were unknown, noone would log into them. it gets worse from there. I am thinking that maybe you need SYS1 privileges to create files. I suspect that DAVE got created with SYS0. on SYSPROG try the following: CT SYSTEM DAVE that will show us what the account can do. if there is a SYS0, we can try an edit of the dictionary, but that may be prevented. some pick systems tried to put in protections on editing the system dictionary as a reliability factor. I am not that familiar with ADDS and it may take a utility to modify the account. if you can do the following we can get some more info on the system utilities. If it isn't too long, do the following: on SYSPROG LIST BP LISTVERBS and publish that. It will give hints about the system utilites names. if that turns out to be to long, see where Jay can put it out of line so we don't have a huge junk message. I don't have a system to try this on, sorry. CREATE-FILE MYBP 1,1 17,1 need dictionay and data section sizes. I would never let SYSPROG be available on the net. I would rather have an R83 system online which could be restored than have a classic that could not. I guess at some time we should poke inside and see if the disk is a common one, and maybe you can do a swap and restore your backups. then we will have it made about keeping it running. I would never do a restore on the physical disk you have unless it forces you to. so the best approach will to be to try to find an identical one somewhere and put it in to try the restore on.