On Sat, Oct 17, 2020 at 07:20:32PM +0200, Eric Auer wrote:
> It basically says there are many ways in which hardware or
> software could fail to handle the year, but you do not say
> WHICH of them affect YOU. In particular, you could give it
> a try and change that "19" to "20" in your CMOS
On 10/17/2020 9:33 AM, ZB wrote:
Does there exist any DIY to fix "millennium bug" in old BIOS (no update
available, unfortunately)? I mean "real fix, not workaround" - finding the
proper cells in BIOS, modifying contents accordingly, burning... done
Well, short answer: No.
There are literally
On Sat, Oct 17, 2020 at 08:47:35PM +, Mercury Thirteen via Freedos-user
wrote:
> There's Y2KPatch which did the job on the dozen-or-so computers I had access
> to at the time. Be warned, however, that I make absolutely no guarantees as
> to how it will work on your system... I was a very
There's Y2KPatch which did the job on the dozen-or-so computers I had access to
at the time. Be warned, however, that I make absolutely no guarantees as to how
it will work on your system... I was a very young coder circa 1999, and I
haven't revised it since.
You can find it here in the QBASIC
On Sat, Oct 17, 2020 at 07:31:02PM +0200, userbeit...@abwesend.de wrote:
> Wow! Thanks for the link to Y2kure! This is the fix I absolutely prefer
> for most of my older systems, since I deem any meddling with the BIOS
> too dangerous... I just don't have the know-how to repair a possible
>
On Sun, Oct 18, 2020 at 01:39:41AM +0800, TK Chia wrote:
> I guess it cannot hurt to ask a few questions:
>
> 1) What does the PC say that the "current date" is, at startup?
It properly keeps hour:minutes, month and day - just changes the "year"
always to "2094".
I came up with workaround -
Hello ZB, hello Eric,
I found some basic information here: https://www.daqarta.com/y2kure.htm
(I mean "BACKGROUND" paragraph), but when possible I'd like simply to modify
BIOS and resolve the problem "once for always"
It basically says there are many ways in which hardware or
software could
ZB wrote on 17th of October 2020:
I found some basic information here: https://www.daqarta.com/y2kure.htm
(I mean "BACKGROUND" paragraph), but when possible I'd like simply to modify
BIOS and resolve the problem "once for always"
Wow! Thanks for the link to Y2kure! This is the fix I absolutely
> I found some basic information here: https://www.daqarta.com/y2kure.htm
> (I mean "BACKGROUND" paragraph), but when possible I'd like simply to modify
> BIOS and resolve the problem "once for always"
It basically says there are many ways in which hardware or
software could fail to handle the
On Sat, Oct 17, 2020 at 06:44:20PM +0200, Eric Auer wrote:
> Hi! In which sense do you suffer from which bug exactly?
>
> Does int 1a function 4 return the wrong century? Wrong
> year? Wrong other date fields and function 5 fails to
> let you fix it? A simple TSR could override those calls.
>
>
Hi! In which sense do you suffer from which bug exactly?
Does int 1a function 4 return the wrong century? Wrong
year? Wrong other date fields and function 5 fails to
let you fix it? A simple TSR could override those calls.
I fail to remember any other BIOS function handle years
and
Does there exist any DIY to fix "millennium bug" in old BIOS (no update
available, unfortunately)? I mean "real fix, not workaround" - finding the
proper cells in BIOS, modifying contents accordingly, burning... done
--
regards,
Zbigniew
___
12 matches
Mail list logo
