Security certificate issues

[tw]

Originally Posted by Undertoad

Which Dell is it? Perhaps we can fix from afar.

Solution is provided here:
http://tinyurl.com/5hr96r

[tw]

Originally Posted by binky

I'll look into it. I have no idea what model it is

For Dells, you don't look at the silly names such as Inspiron or Vostos. Find the Service Tag number. Enter that (seven alpha) number in Dell. It shows you everything unique to your machine AND all relevant updates awaiting your curiosity. Date time clock functions would be listed under BIOS.

However I would not bother. Fixing things - especially BIOS - without first identifying a problem is the classic recipe for disaster.

[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.

[Shawnee123]

Heh...he probably had some whiskeys while he worked on it.

[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)?

[Shawnee123]

Well, like I said, an error in one game led me to look at the calendar and after I changed the date to 2008 I was able to save my free download rpgs again.

I'm no techie, but the date said 8002. I'm pretty sure. I think. I'm almost positive. Now I'm doubting myself.