Re: Problem with MS Windows 3.1

Article View: comp.windows.ms

Article #14209

#14209

From: Gary
Date: Thu, 07 Dec 1995 00:00

2 lines
992 bytes

Could also be a dying battery on the motherboard losing CMOS settings. If the 
clock's been wrong lately, it might be worth popping for a new battery.

Technical Details

Message-ID: <4a7h3d$nnv@eccdb1.pms.ford.com>

Path: arc1-ca.pugleaf.net!unknown!not-for-mail

References: <xu.816800251@rintintin.Colorado.EDU>

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 1107e7,a8c1046d584b92cd
X-Google-Attributes: gid1107e7,public
X-Google-Thread: 1073ca,a8c1046d584b92cd
X-Google-Attributes: gid1073ca,public
X-Google-Thread: 1054ae,a8c1046d584b92cd
X-Google-Attributes: gid1054ae,public
X-Google-Thread: f49ec,a8c1046d584b92cd
X-Google-Attributes: gidf49ec,public
From: Gary <Gary-s@e-mail.com>
Subject: Re: Problem with MS Windows 3.1
Date: 1995/12/07
Message-ID: <4a7h3d$nnv@eccdb1.pms.ford.com>
X-Deja-AN: 121248873
references: <xu.816800251@rintintin.Colorado.EDU>
to: xu@rintintin.Colorado.EDU
content-type: text/plain; charset=us-ascii
organization: ECC at Ford Motor Company, Dearborn Michigan
mime-version: 1.0
newsgroups: comp.windows.ms,comp.misc,boulder.general,co.general
x-mailer: Mozilla 1.22 (Windows; I; 16bit)

Reply to Parent Message