That did the trick looks like a new user signed in with an extra Lon user name 17 characters and my idle screen says Her 7/6

Hmmm.....

UT-OH now my sysop user is not found asks if I want to create it??

Yeah sorry I could not help much on this one.. that whole thing blew up on you.  Even your backups were giving you errors, I am sure @bucko can help!

This is the loop error I got on the backups 

I am at a loss on this one.. I have seen the user #1 issue, it is because for some reason e.data record I think 31 got overwritten for some reason.. I had this issue at POC in Florida. I fixed it by rebuilding user 1 with the sysOp's info and just making the person who logged on and got user 1 log on new again.. Not sure what is causing it, it could very well be SCPU vice issue where when it is writing to the record it corrupts it. I can't figure it out for the life of me. As for the automaint issue, an illegal quantity error is when a number is more then 65535, in this case if you look at your date it is corrupt and automaint will NOT run because it is trying to reset the date to the current date. Make sure you are setting the clock via the CMD either HD or add a FD4000 disk as 9 or 10 and use that. Once you get the correct time and date automaint will run..

@bucko hmmm….I have been setting time off device 8 which is CMD HD ….why device 9 or 10 versus 8 ?

Posted by: @sutehk

@bucko hmmm….I have been setting time off device 8 which is CMD HD ….why device 9 or 10 versus 8 ?

It shouldn't matter. I use device 9 which is a FD4000 setup. BUT you can use 8.. Just make sure it see's the drive and sets the time. The pic you had attached in a post showed the clock was wacked, thus the reason for the errors..