Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!rpi!crdgw1!sixhub!davidsen
From: davidsen@sixhub.UUCP (Wm E. Davidsen Jr)
Newsgroups: comp.unix.msdos
Subject: Re: VP/ix date is wrong under Xenix!
Message-ID: <2399@sixhub.UUCP>
Date: 26 Nov 90 02:29:25 GMT
References: <1158@teslab.lab.OZ> <1990Nov22.052246.11841@maverick.ksu.ksu.edu> <16130@brahms.udel.edu>
Reply-To: davidsen@sixhub.UUCP (bill davidsen)
Organization: *IX Public Access UNIX, Schenectady NY
Lines: 23

In article <16130@brahms.udel.edu> weave@brahms.udel.edu (Ken Weaverling) writes:

| If your DOS window is non-active for a weekend, then I theorize that VP/ix
| puts it to sleep and therefore, no code can be executed after midnight by
| DOS to manually update the clock. The next Monday, when you hit the
| keyboard, DOS notices the midnight flag, dutifully updates the date by
| ONE day, and your date is now screwed up.

  Ken has described this exactly correctly. And it's not a bug, in that
real MS-DOS works just this way, loses two days every weekend, and if
VP/ix didn't work that way some twit would say the emulation was bad.

  If you have some TSR hanging on the clock tick this doesn't happen,
but that probably will drive the CPU offscale. I haven't tried it, nor
do I feel the need to, but I have such a TSR around somewhere from DOS
days at work, when we chased just this problem and found it easier to
give the user a TSR to run than explain that our applications weren't
causing it.
-- 
bill davidsen - davidsen@sixhub.uucp (uunet!crdgw1!sixhub!davidsen)
    sysop *IX BBS and Public Access UNIX
    moderator of comp.binaries.ibm.pc and 80386 mailing list
"Stupidity, like virtue, is its own reward" -me