Re: Year 2000 bug support ??
On 1 Oct 99, at 13:21, Luciano José Alves wrote: ELKS developers, I have a question. Does have ELKS support for Year 2000 bug ? -- Até mais... Luciano José Alves [EMAIL PROTECTED] [EMAIL PROTECTED] http://ilha.feesc.ufsc.br/~luciano Phones: (055)-048-234-1279 (FEESC) (055)-048-962-9306 (Celular) (055)-048-242-7394 (Casa) I think you mean if it can HANDLE the Y2K bug? AFAIK it does...
RE: Year 2000 bug support ??
Technically, it's not a bug, but rather a feature. It works the way that it was intended to, so it's not a bug. :) Elks should be y2k compliant, meaning that it can handle dates after the year 2000, IF the hardware that you're running on can handle them. Greg -Original Message- From: Zoiah [mailto:[EMAIL PROTECTED]] Sent: Saturday, October 02, 1999 7:29 AM To: [EMAIL PROTECTED] Subject: Re: Year 2000 bug support ?? On 1 Oct 99, at 13:21, Luciano José Alves wrote: ELKS developers, I have a question. Does have ELKS support for Year 2000 bug ? -- Até mais... Luciano José Alves [EMAIL PROTECTED] [EMAIL PROTECTED] http://ilha.feesc.ufsc.br/~luciano Phones: (055)-048-234-1279 (FEESC) (055)-048-962-9306 (Celular) (055)-048-242-7394 (Casa) I think you mean if it can HANDLE the Y2K bug? AFAIK it does...
Re: Year 2000 bug support ??
On Fri, 1 Oct 1999, Luciano [ISO-8859-1] José Alves wrote: I have a question. Does have ELKS support for Year 2000 bug ? How about a y2k statement? "Your computer will die before ELKS" sounds appropriately correct. Davey
RE: Anybody using this list?
hi I'm perfectly willing to put in the time to do this (expect it to take a while), and teach myself assembler at the same time, but I need some help going about it. A friend of mine loaned me his disassembler program, but it's designed to run under win95 and winnt. Can I (should I even try) to figure it out this way, or does it need to be on the t1200 to have it be acurate and useful? Thanks, Greg I not realy an expert in this, but I would only use the windows95/nt if it were capible of dissasembaling 16bit code (I am basing this thinking that a windows dissasember is designed to disasemble win code, maybe the prog you have does both?) I would use a dos based disasember, don't what one, supose turbo-debuger? I used to have a good prog that you put in exe's in one end and asm code poped out the other end. I will have a look (I downloaded it over a 2 years ago) What does anyone else think, I am not an expert. tom __ Get Your Private, Free Email at http://www.hotmail.com
