pk@wet.UUCP (Philip King) (03/31/91)
I've been having problems with Atime. Every time I try to execute the TimeServ from my startup-sequence, it locks up the s-s. If I do it from a shell I open after the startup is finished, no problem! I first suspected it was because the initial CLI was not a shell- so I put a line to open a shell from the s-s, which remained on the screen after boot. Still doesn't work! Then I thought, maybe that shell was inheriting some path, assign, or stack from the initial CLI that conflicted with Atime/ TimeServ. No go. I checked everything, changed directories...still couldn't get TimeServ to do anything but lock up the shell if I ran it from the s-s or a shell launched from the initial CLI. What's going on? Also, no matter what I do, PC Color always opens up with part of the PC screen obscured. Even though I save the parameters including Full Size Screen (I run the BB on a non-WB screen), I have to either select Full Size from the menu when the screen starts, or double-click on it twice- in order to see all the lines. (I run a slightly over-scanned screen) Does anyone know a fix for this? Thanks in advance for any hints. Philip pk@wet.uucp {ucsfcca,claris,hoptoad}!wet!pk