It seems the Time & Date problem is resolved by a Reboot. Most changes in Config require a reboot. If Audrey cannot find the time server you have a problem with your internet connection. The time server I used is in /kojak/Datebook.sh for use with ntpdate and /config/Timeserver0 for use with setitime. It's still the same from FINAL update from 3COM.
</kojak/os2, this is a 353k app. I can not seem to find anything that uses this, can it be safely removed?>
I don't have the image running at this time, but you can remove this one, must be the remainder of a failed mount exercise.
< /nto/bin/pdksh, I am not sure what this is. Is this a flavor of ksh? It is worth 140k>
Be careful removing this one. I think you're right, it could be a flavor of ksh. You could change the name and see what happens. If nothing bad happens you could remove it, but it may have some adverse effect.
< I might remove picframe and go to a web based one. My server within the same network. Other than the three files in /nto/bin and the images
directory at /kojak/pics/ are there any other files for this? This is worth another 200k.>
Picframe is the executable and /kojak/pics is the directory I used for the example pics. Remove them.
< Since ntpdate is not working right, if I could figure out how to set the date and time manually, I might remove this for another 430k>
I disagree removing this one. If it doesn't work you have to Reboot after making changes with the Time & Date Cfg or you have a network problem. Again for rare occasions only when the timeserver is busy or under maintenance this feature should work at all times with a properly setup connection with the internet. However if you want to reclaim space you can reactivate Audrey's original Time & Date, I left it in on purpose. (setitime is only 7k)
Check /kojak/go, /config/rm-apps, /config/startup-main and /config/startup-warm and uncomment any line with setitime and it should work again at boot. You'll find it in 2 or three of these scripts, but I don't have this image up and running and cannot check myself at this time. If you have a problem reactivating setitime let me know and I will help you out.