Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Computer Learning -- Ignore unavailable to you. Want to Upgrade?

To: dpl who wrote (1646)	1/22/1999 7:14:00 PM
From: Phil(bullrider)	Respond to of 110652

David, Tonight before midnight, simply change the date on your 'puter to 12/31/99 and see what happens in the morning. You might wish to have all of your really important files backed up first. Seriously, I don't know what will happen, but if you are brave enough to try it, let us know. Have fun, Phil

To: dpl who wrote (1646)	1/22/1999 7:20:00 PM
From: mr.mark	Respond to of 110652

microsoft.com also suggest you search yahoo for windows 3.1. under operating systems, select win3.1, then usenet, then windows.apps.utilities.win3x. there's a bunch of posts there that kinda' walk you through it. good luck, mark

To: dpl who wrote (1646)	1/22/1999 7:28:00 PM
From: Ed Boudinot	Read Replies (1) \| Respond to of 110652

dpl There is another quick way. I have widows 95. Go control panel, Date and time. Set the date to 12/31/99 and the time to 1158 PM. punch OK then sit back and watch it tick off- Mine jumped back to Jan 1 1980 so I know I am not Y2K compliant. My solution will be to get a new puter this summer as this old baby is a refurbished 486 and ready for the junk heap anyway. Try it. it's fun, and the 2 or 3 minutes did nothing to any of my files.

To: dpl who wrote (1646)	1/23/1999 11:00:00 AM
From: PMS Witch	Respond to of 110652

"Is there a way for me to test if my PC is Y2K ready?" There's stuff you can download that test your system. It seems there are different levels of Y2K compliance: totally messed up; totally OK; easy work-arounds; and hard work-arounds. A typical easy work-around is having to enter the date and time manually ONCE after the new year. Harder is entering the correct date and time on every boot. A quick test: set clock to 11:59 1999-12-31 and wait a couple of minutes and check to see if it rolls over correctly. This checks the clock which the system uses while it's running. Next, set clock to 11:59 1999-12-31, SHUT THE SYSTEM OFF, and wait a couple of minutes. Power up and check to see if it had rolled over correctly. This checks the clock which stores date and time the system uses while it's shut off. So much for hardware. Now software ... Microsoft has web pages telling consumers which Microsoft products comply and for the products which don't comply, where they don't and suggested work-arounds. You'll need to contact the other suppliers of your software to see what support they offer. Example: I use Lotus-123 and @Date(99,12,31) becomes @Date(100,1,1). A little messy, but I'll survive. Hope this helps. PW.

To: dpl who wrote (1646)	1/23/1999 3:37:00 PM
From: Doug Coughlan	Read Replies (1) \| Respond to of 110652

This came from a publication that I can't recall. I saved it to a folder and hope it will help you out. Don't ask me any questions because some of it is Greek to me.:-) Q: What should I do to my computer hardware to prepare for Y2K? A: "Y2K" is what computer nerds call the Year 2000 computer problem -- the bug that makes some machines unable to recognize dates in the next century. The first thing to remember in dealing with it is: Don't flip out. You may very well have no problem at all. If you do, there is more than enough time to fix it. Finding out about hardware compliance is easy. You can download one of several programs floating around the Internet that take a look at your machine to see if it is Y2K-compliant. They include Yes2K version 1.0 and Y2K Test Windows version 1.03. You can find them by typing in their names at Web search engines. If you do have a problem, it may be in your BIOS, the chip that stores basic information about your computer and has an electronic calendar. One possible remedy is to get something called a TSR (terminate and stay resident) program that corrects a BIOS deficiency. An example is the Millennium Bug Toolkit ($83) from Computer Experts. One obvious shortcoming of this approach, however, is that this file could get erased or damaged, leaving you with the Y2K bug. A better solution is to physically replace the BIOS. You can buy a new, Y2K-compliant one at superstores or by mail order. If prying off your BIOS is not your idea of a good time, you might want to consider one of the ISA (industry standard architecture) cards that plug in and act as an adjunct to your BIOS. American Megatrends (www.megaraid.com) and Award's Unicore division (www.unicore.com) have these cards available. These steps should take care of hardware problems. You'll also want to check your software manuals to see if crucial software that uses dates is compliant.