Well it is really a pain because I reset the date and time on the other 
computer.  Now when I try to set the date manually  (date 9808041156) 
NetBSD locks up.  Caps Lock wont even work.  And no, setting the date and 
time manually in BIOS will not work.  For some reason NetBSD now always 
boots to 1930 regardless of the initial system time.

Dead
Dead
Dead....

My i386 NetBSD 1.3.2 system seems to be forever set to 1930!

Any ideas as to a work around?

As my assistant Paul just said, who says time travel isn't possible!

jam

----------
From: 	Brian Buhrow[SMTP:buhrow@cats.ucsc.edu]
Sent: 	Tuesday, August 04, 1998 4:31 AM
To: 	johnam@kemper.org; 'netbsd-bugs'; 'netbsd-help'
Subject: 	Re: Before I offically call this a time bug can someone else try 
this?

	It turns out that the current time is stored in a 32-bit signed
integer.  This integer overflows into a negative number in 2038.  In 2060,
which is when your board thought it was, the NetBSD time value couldn't
cope.  So, yes it's a bug, but we have a few years to fix it. :)
-Brian

On Aug 4, 11:04am, "John A. Maier - MIS dept." wrote:
} Subject: Before I offically call this a time bug can someone else try 
this
} I pulled a old Pentium MB of the shelf and put my NetBSD drive in it.
}
} Everything booted fine.
}
} However I get a message initally that the file system time is much older
} than the system time.  I shruged this off figuring that the MB had lost
} time since it was last used (2 years ago) and that ntpdate in the rc
} startup would correct this.
}
} Well when the boot sequence hit the ntpdate to set the date, it informed 
me
} that the system time had been reset by 209,569,500 sec!!!
}
} After boot was finished I logged in and did a date and discovered that
} today is actually Thurs July 17 07:20:36 CDT 1930.
}
} Hmmmmm....that doesnt seem quite right.
}
} When when I rebooted I got into the (Award) BIOS and checked that date.
}  The CMOS reported that the date is actually Wed Jan 1 2060 0:0:2
}
} Just for grins I rebooted, same things happened and when I went into the
} BIOS the date was still Wed Jan 1 2060 and the time was back to 0:0
}
} This time I set the CMOS date and time to be correct and everything went
} okay.
}
} Just to make sure, I tried it on another computer and it to did the same
} thing.
}
} Now I think that the BIOS may be partially to blaim, because both 
machines
} have an Award BIOS and the BIOS only accepts years 1994 thru 2099.
}
} try it and tell me what happens!
}
} jam
>-- End of excerpt from "John A. Maier - MIS dept."