Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!brutus.cs.uiuc.edu!tut.cis.ohio-state.edu!att!cbnews!kww From: kww@cbnews.ATT.COM (Kevin W. Wall) Newsgroups: comp.sys.ibm.pc Subject: Problem setting YEAR in date cmd Keywords: date,time,AT&T6300PC Message-ID: <8567@cbnews.ATT.COM> Date: 25 Jul 89 01:19:31 GMT Distribution: na Organization: AT&T Bell Laboratories Lines: 36 A question for all of you AT&T PC6300 gurus out there: A friend of mine has a dual floppy AT&T PC6300 (i.e.. 8086) which he has converted to a single floppy / hard disk system. When he installed the hard disk, he had to upgrade the BIOS from revision 1.21 to 1.43 (I think 1.43 is the correct #, but I'm not absolutely sure). At the same time, he thought that he would install a DOS upgrade, so he purchased a vanilla DOS 3.2 from Microsoft (rather than buying the upgrade from AT&T). [He claims he got his 3.2 upgrade for $40, but that AT&T wanted about $120. Hmmm...] When he boots up his new version of DOS (3.2) with the new BIOS, he is unable to set the year correctly on the 'date' command. (He enters the date, but it apparently ends up stuffing random garbage in the 'year' portion of the date. butHowever, the 'month' and 'day' portions of the date are okay. Also, he has no trouble setting the time.) Also, he says that if he boots the OLD DOS (version 2.11, which came with the PC), he is able to set the date correctly. (Thus it isn't apparently a problem with weak batteries.) What my friend would like is a utility to CORRECTLY set ALL portions of the date under DOS 3.2 with BIOS rev. 1.43. (Or short of a utility, if someone could give him the addresses to 'tweak', or a small assembler script to do this.) Since my friend is not on the net and I do not often read this newsgroup, please E-mail replies DIRECTLY to me and I'll pass it on to him. If this posting generates sufficient interest (i.e., several people claim they would like to know how to do this as well), I'll summarize my findings to the net. Also, if it makes any difference, the PC is no longer under warranty, which he claims, makes the AT&T support hotline people reluctant to talk with him. Thanks in advance to all of you who offer help. -----