From: utzoo!decvax!ucbvax!info-vax Newsgroups: fa.info-vax Title: vms 1983 bugs Article-I.D.: ucbvax.1002 Posted: Mon Feb 28 22:46:48 1983 Received: Tue Mar 1 08:10:31 1983 >From GEOFF@SRI-CSL Mon Feb 28 22:45:22 1983 Received: by UCBVAX.ARPA (3.314/3.5) id AA11589; 28 Feb 83 22:46:32 PST (Mon) To: info-vax@sri-csl Remailed-Date: 28 Feb 1983 1632-PST Remailed-From: the tty of Geoffrey S. GoodfellowRemailed-To: Info-VAX@SRI-CSL.ARPA: ; I spoke with TSC a few weeks ago about a problem we just noticed with BACKUP/RECORD (stand-alone) marking with the wrong date and they told me the following: 1) Stand-alone Backup, when used with the /RECORD switch, marks all files as having been backed up in 1982 (the day and month will be correct.) They have not determined a workaround yet. It apparently has something to do with the fact that STABACKIT makes a new SYS.EXE for the backup kit and uses DEFAULT and some default date says 1982! (For those of you who did not see my warning about stand-alone backup with /RECORD trashing large files some months ago, you should not use /RECORD stand-alone unless you have the ECO 17 patch from DEC which will come with VMS 3.2) 2) There is a related problem in the AUTOGEN procedure that shows up in 1983. Apparently, somewhere (in SYS.EXE? in AUTOGEN.PAR?) the date gets saved without the year and the default year is 1982, so if you do an AUTOGEN REBOOT and don't set the time yourself, the system time will be a year off. So if you use AUTOGEN, make sure to check the system time when you re-boot. We are using VMS 3.1. I am not certain if these problems occur in VMS 3.0 also. (We upgraded to 3.1 on Jan 8.) ** MORE NEWS 03-Feb-83** DEC has come up with some workaround or patch - TSC told me today that I would receive it next week. When I receive details, I will let you all know. -- Gail Rubin GRubin @ bbn-unix (I have been trying to send this msg for some time - what ever happened to sri-csl?)