From owner-freebsd-emulation Wed Apr 12 5:58:18 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from wireless.net (wireless.net [207.137.156.159]) by hub.freebsd.org (Postfix) with ESMTP id 04AB537BB49 for ; Wed, 12 Apr 2000 05:58:16 -0700 (PDT) (envelope-from dbutter@wireless.net) Received: from db.wireless.net (db.wireless.net [209.75.70.101]) by wireless.net (8.9.3/8.9.3) with ESMTP id CAA15266; Wed, 12 Apr 2000 02:59:19 -0700 (PDT) Received: from wireless.net (dbm.wireless.net [192.168.0.2]) by db.wireless.net (8.9.3/8.9.3) with ESMTP id CAA24524; Wed, 12 Apr 2000 02:47:00 -0700 (PDT) (envelope-from dbutter@wireless.net) Message-ID: <38F4471E.20901@wireless.net> Date: Wed, 12 Apr 2000 02:51:26 -0700 From: Devin Butterfield User-Agent: Mozilla/5.0 (X11; N; Linux 2.2.12 i386; en-US; m14) Netscape6/6.0b1 X-Accept-Language: en MIME-Version: 1.0 To: Dag-Erling Smorgrav Cc: emulation@FreeBSD.ORG Subject: Re: Clock drift in VMWare References: <200004112006.WAA97397@peedub.muc.de> <38F3FB20.4B233222@wireless.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dag-Erling Smorgrav wrote: > > Devin Butterfield writes: > > Gary Jennejohn wrote: > > > Have you tried the /dev/rtc port to see if it helps ? Don't know > > > whether it only works for Windoze or not. > > I think this is a good suggestion. I have not tried it so I too would be > > interested in the results. I recall that VMWare complains about the host > > not having the /dev/rtc device upon startup and it says that windows > > will not keep time correctly as a result. So I think this is the right > > thing to try. > > Yes, I am using /dev/rtc; no, it does not help; and NO, I AM NOT > RUNNING WINDOWS for crying out loud. Where'd'ya guys learn to read? > Sheesh. Simple clarification is sufficient. Chill out. Your gonna get high blood pressure. ;) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message