Security certificate issues

[glatt]

Yea! Problem solved!

[tw]

Originally Posted by binky

Thanks so much UT and SD. I reset the time and date after the power outage but neglected to notice that it was set to 2003! Problem resolved.

Problem not yet solved. A power outage must never cause that date time clock to change. It implies a battery failure or some other problem exists. A problem easily identified quickly if you don't try to fix it by just swapping parts. Power outage will not change the date on a functional machine.

[glatt]

Originally Posted by tw

Problem not yet solved. A power outage must never cause that date time clock to change. It implies a battery failure or some other problem exists. A problem easily identified quickly if you don't try to fix it by just swapping parts. Power outage will not change the date on a functional machine.

It's a trade off though. isn't it? She can spend a lot of time and aggravation and money to fix a possible battery problem, or she can spend 30 seconds changing the date back the next time the power goes out. I know what I would choose.

[binky]

thanks tw, I know this PC is obsolete (5 yrs old), but will have to do until I get a new one next year, unless you have any other suggestions do-able by a computer idiot like me.

[Undertoad]

It is surely a battery failure which may or may not be user-solvable. Some other settings may have also changed but if the system seems to run, you can limp along in that state until you have the money to send it to me to fix.

[binky]

I think that is the way to go glatt, I don't want to spend anytime or money to fix a 5 yr old, $500 dell PC

[tw]

Originally Posted by binky

I think that is the way to go glatt, I don't want to spend anytime or money to fix a 5 yr old, $500 dell PC

The time would have taken 30 seconds. Far more complex with the simple knowledge and tool to eliminate the problem.

However we do not fix things to save time and money. We fix things to learn. A changing date time is a precursor to other and future problems - such as a disk drive that cannot be accessed. Some simply solve these problems by purchasing a new machine. A solution to avoid labor of learning.

[binky]

Thanks btw UT, but fixing this thing would be like putting lipstick on a pig

[Shawnee123]

I had my computer worked on once, and after I got it back there was a certain type of game I couldn't save. The save option came up, but it wouldn't do anything. (I was downloading free rpg type games like Final Fallacy.) It wasn't until I had a problem with another type of game that said something cryptic that made me look at my clock and I saw the year was set to 8002. I don't know how or why, but fixing it fixed the problem. It really is time for a new computer, though.

[tw]

Originally Posted by Shawnee123

It wasn't until I had a problem with another type of game that said something cryptic that made me look at my clock and I saw the year was set to 8002. I don't know how or why,

More interesting, the clock has no way to store 8002. Data time clocks measure by counting seconds from a fixed date - typically a day in 1981. No date time clock has the ability to count seconds up to 8002.

BTW, that knowledge also says why the millennium fears were total nonsense in 2000. Why would a count that changes from 596937607 to 596937608 cause a computer crash? Because too many _new_ without first learning the facts. Fear due to technical ignorance was a primary reason for panic and predictions.

Curious because a date time clock cannot store the number of seconds for the year 8002. Implies a problem elsewhere - ie somebody wrote software with a defect - that used signed rather than unsigned integers. IOW the defect date also identified another problem with that computer.

[Shawnee123]

Originally Posted by tw

More interesting, the clock has no way to store 8002. Data time clocks measure by counting seconds from a fixed date - typically a day in 1981. No date time clock has the ability to count seconds up to 8002.

BTW, that knowledge also says why the millennium fears were total nonsense in 2000. Why would a count that changes from 596937607 to 596937608 cause a computer crash? Because too many _new_ without first learning the facts. Fear due to technical ignorance was a primary reason for panic and predictions.

Curious because a date time clock cannot store the number of seconds for the year 8002. Implies a problem elsewhere - ie somebody wrote software with a defect - that used signed rather than unsigned integers. IOW the defect date also identified another problem with that computer.

I'm not sure what you just said...but I think it means I need a new computer. That is for sure! Mine has seen better days.

Any suggestions from those in the know? I like my Dell, it's served me well. (I know I'm a poet.)

[xoxoxoBruce]

I think he was saying the PC couldn't have come up with 8002 by itself, but you already said you'd had it worked on, so obviously that person set it wrong.

[dar512]

Originally Posted by xoxoxoBruce

I think he was saying the PC couldn't have come up with 8002 by itself, but you already said you'd had it worked on, so obviously that person set it wrong.

No, in this case, TW is correct. Remember the year 2000 issue for mainframes? PCs have a similar limitation for the year 2038.

Your computer has no way to store a date beyond 2038, so there must be something going on if you've seen the date 8002. Are you sure you weren't being dyslexic (for 2008)?

[binky]

LOL @ 8002. Something that futuristic should have worked really well!

[Shawnee123]

You'd think!