Factbites
 Where results make sense
About us   |   Why use us?   |   Reviews   |   PR   |   Contact us  

Topic: 2038


Related Topics

In the News (Thu 21 Aug 08)

  
  Year 2038 problem - Wikipedia, the free encyclopedia
In computing, the year 2038 problem may cause some computer software to fail in or about the year 2038.
The move to these architectures is already underway and many expect it to be complete before 2038.
However, hundreds of millions of 32-bit systems are deployed as of 2006, many in embedded systems, and it is far from certain they will all be replaced by 2038.
en.wikipedia.org /wiki/Year_2038_problem   (389 words)

  
 2038
This is tied into the fact that 2038 uses minor companies, and as I discuss in my review these companies are even more powerful than usual (!), generating enormous cash flow in the short term followed by a large cash hand-out and an Asteroid League share in the long-term.
In 2038, you're restricted in share purchases from the get-go lest you be hammered.
While 2038 is long, I have always felt it maintains a solid interest level throughout.
homepage.mac.com /c_farrell/iblog/C2097221587/E279102424   (1024 words)

  
 [No title]
Standards Track [Page 2] RFC 2038 RTP Payload Format for MPEG1/MPEG2 Video October 1996 Much interest in the MPEG community is in the use of one of the MPEG System encodings, and hence, in Section 2 we propose encapsulations of MPEG1 System streams and MPEG2 Transport and Program Streams with RTP.
Standards Track [Page 5] RFC 2038 RTP Payload Format for MPEG1/MPEG2 Video October 1996 represented at the beginning of the stream) that the first Video_Sequence_Header (preceded by an end-of-stream indicator) be saved by the packetizer for periodic injection in to the network stream.
Standards Track [Page 9] RFC 2038 RTP Payload Format for MPEG1/MPEG2 Video October 1996 After scanning to the next Beginning-of-slice the Picture_Header is reconstructed from the P, TR, FBV, BFC, FFV and FFC contained in that packet, and from stream-dependent default values.
www.ietf.org /rfc/rfc2038.txt   (2973 words)

  
 The Year 2038 Problem
Year 2038 bugs, on the other hand, occur when a program reads in a date and carries it around from one part of itself to another.
They reason that, by the time 2038 rolls around, most programs will be running on 64-bit or even 128-bit computers.
And, perhaps worse, the parts of their software they had to fix for Year 2000 Compliance will be completely different from the parts of their programs that will fail on 19-Jan-2038, so fixing one problem will not fix the other.
home.netcom.com /~rogermw/Y2038.html   (1727 words)

  
 Howstuffworks "What is the Year 2038 problem?"
The Year 2000 problem is understood by most people these days because of the large amount of media attention it received.
This is possible because the library encapsulates the whole time activity with its own time types and functions (unlike most mainframe programs, which did not standardize their date formats or calculations).
So the Year 2038 problem should not be nearly as hard to fix as the Y2K problem was.
computer.howstuffworks.com /question75.htm   (448 words)

  
 digg - The Year 2038 problem.
I am sure there may be a few c programs still being used in 2038, but considering how many new technologies we have had over the last 15 years (java,.net, etc.) I doubt c programs will be anywhere near as prevelent as they are today.
Since I was employed during 2000 and dealt with fixing Y2K problems, I hope that by the time 2038 rolls around I'll be making big bucks fixing all that old code written in Perl 5 and PHP 4 from the early 2000's - after that I plan to retire to a desert island.
In any case, I'm hoping to be retired by the time 2038 rolls around, and unless the golf course is digital by then, I got no worries.
digg.com /programming/The_Year_2038_problem.   (1794 words)

  
 Y2K-like bug to hit Linux computers!   (Site not responding. Last check: 2007-09-06)
If you ask what this 2038 bug is, you will have to put up some technical argot.
The 2038 bug, on the other hand, affects the basic time-keeping function.
He, however, adds that the rate at which we are changing technology, most systems are unlikely to use 32-bit processing by the time we get to 2038.
us.rediff.com /money/2005/may/06linux.htm   (611 words)

  
 Labelaire 2038   (Site not responding. Last check: 2007-09-06)
The Model 2038 uses a stepper-driven rewind assembly which ensures long print-engine life improving your bottom line in the long run.
The 2038 can be easily modified to apply labels using tamp-on or tamp-blow labeling methods.
The 2038 comes equipped with standard error diagnostic routines, monitoring minimum product spacing and label presence on tamp pad, which ensure that the correct label gets on the proper package.
www.crownpack.com /html/identification/printers/labelaire/printandapply/2038   (190 words)

  
 2038 bug - Dev Shed
Note: The valid range of a timestamp is typically from Fri, 13 Dec 1901 20:45:54 GMT to Tue, 19 Jan 2038 03:14:07 GMT.
Beats me why your worryin about it, by the year 2038 you will probably be using a new version of PHP in your brain implant (like Johnie Neumonic or The Matrix)...
You could try finding 'algorithm 199: conversions between calendar date and Julian day number' from Communications of the ACM, which seems to be a way to fix the problem.
forums.devshed.com /php-development-5/2038-bug-31045.html   (496 words)

  
 Session :Bills : : flsenate.gov   (Site not responding. Last check: 2007-09-06)
ENROLLED 2004 Legislature CS for CS for SB 2038, 2nd Engrossed 1 the ceding insurer beneficiaries of the trust are domiciled.
For policies or contracts issued on or after 2 January 1, 1966, the tables of period 2 disablement rates and 3 the 1930 to 1950 termination rates of the 1952 disability 4 study of the Society of Actuaries, with due regard to the type 5 of benefit; 6 2.
At the option of the insurer, calculations for all 22 policies issued in a particular calendar year may be made on 23 the basis of a rate of interest not exceeding the 24 nonforfeiture interest rate, as defined in this subsection, 25 for policies issued in the immediately preceding calendar 26 year.
www.flsenate.gov /cgi-bin/view_page.pl?Tab=session&Submenu=1&FT=D&File=sb2038er.html&Directory=session/2004/Senate/bills/billtext/html   (7974 words)

  
 Time Travel Portal :: View topic - IBM 5100/5110, UNIX, Y2K & Year 2038 Bugs   (Site not responding. Last check: 2007-09-06)
In that language the clock is converted to a common C/C++ clock format and that one is causing the Year 2038 Bug.
The Year 2038 Bug is related to a 32-bit counter used in the Run-Time System of the programming languages C and C++.
GUI on the Year 2038 Bug (September 7, 1998) and More on the Y2.038K Bug (September 30, 1998).
timetravelportal.com /viewtopic.php?t=60   (952 words)

  
 Project 2038 FAQ
Unix and Unix-like operating systems do not calculate time in the Gregorian calendar, they simply count time in seconds since their arbitrary "birthday", GMT 00:00:00, Thursday, January 1, 1970 C.E. The industry-wide practice is to use a 32-bit variable for this number (32-bit signed time_t).
During their test, they advanced their real time clock to the year 2038, and suddenly, without warning, each of my log files started writing the year 2038 instead of 1999.
The 2038 problem may well cause more serious problems because it involves the basic system timekeeping functions from which most other time and date information is derived.
maul.deepsky.com /~merovech/2038.html   (2333 words)

  
 Y2K vs. Y2038
Yes, in the year 2038, another 'rollover' of sorts will occur.
Everybody can comprehend that the year 00 could be interpreted as 1900 instead of 2000.
However, on Monday January 18, 2038 at 9:14:08 P.M. a new computational anomaly will occur.
tiretracking.com /y2kvsy2038.htm   (722 words)

  
 Year 2038 Bug   (Site not responding. Last check: 2007-09-06)
The problem is that some "intelligent" person years ago used a long signed integer to store the date in the PC as being the number of seconds from midnight January 1st of 1970.
The problem is that those 31 bits (31 instead of 32 because of the sign bit) only last until 18 January 2038 at 19:14:07 (for all time zones).
My conclusion as to why everyone is still developing with this limitation are that 1) it would take quite an effort to start implementing a fix and 2) [probably the more correct reason] by not implementing a fix now, people can make more money.
www.dewtronics.com /y2038.html   (453 words)

  
 Y2K38 - Year 2038 Problem   (Site not responding. Last check: 2007-09-06)
The Y2K38 problem has been described as a non-problem, given that we are expected to be running 64-bit operating systems well before 2038.
However, it is possible that some machines going into service now may still be operating in 2038.
While 32-bit CPUs may be obsolete in desktop computers and servers by 2038, they may still exist in microcontrollers and embedded circuits.
vancouver-webpages.com /time/Y2K38.html   (365 words)

  
 The year 2038 bug
This means that when the second count reaches 2147483647, it will wrap to -2147483648.
The precise date of this occurrence is Tue Jan 19 03:14:07 2038.
At this time, a machine prone to this bug will show the time Fri Dec 13 20:45:52 1901, hence it is possible that the media will call this The Friday 13th Bug.
www.2038bug.com   (416 words)

  
 Google's cookie   (Site not responding. Last check: 2007-09-06)
The criticism focused largely on data Google collects through a commonly used Web-tracking technology known as the "cookie." Many sites drop cookies on visitors' hard drives and then check them on return visits to see what sites the people have gone to in the interim.
Although most such cookies expire within a relatively short time, Google's--which plants a unique ID on a visitor's hard drive that can be linked with the user's search queries--is set to continue functioning until the year 2038.
That information could theoretically be used to track information about Web usage on a particular computer, although Google's privacy policy states that the company "aggregates" the data, or gathers it into anonymous groupings.
www.mirabilis.ca /archives/000546.html   (168 words)

  
 Dr. GUI on the Year 2038 Bug
And now, as if the Y2K and Euro problems weren't bad enough, there's the year 2038 bug.
GUI got a letter from Mahmoud Saleh alerting him (reminding him, actually) of a similar problem that will face C and C++ programmers in coming years: we can call it the Y2.038K bug.
On most systems, long int is 32 bits, which means that we've got a range of 2^31-1 (2,147,483,647) seconds—until sometime on January 18, 2038.
www.dewtronics.com /msdn_090798a.html   (924 words)

  
 time to put that 2038 bug in the forward plan
I'm already running into problems due to the 2038 limit.
after 2038 and we have to make calculations for years 2039+.
This *bug* (as you put it) is based on 32 bit machines.
www.w00tlinux.com /bb/ftopic375.html   (1944 words)

  
 FedoraForum.org - 2038
I don't think kernel 2.4 or 2.6 is Unix Epoch "safe", but it would be trivial to recompile everything using a 64-bit integer for the time typedef's...
Right now it is a problem with 32 bit.
I bet all of Fedora Linux will be 64 bit well before 2038.
www.fedoraforum.org /forum/showthread.php?t=29082   (126 words)

  
 Calendar - Denmark - 2038
The year 2038 is a normal year, with 365 days in total (Gregorian calendar)
Phases of the moon are calculated using local time in Copenhagen
List of years that use the same calendar as 2038
www.timeanddate.com /calendar?year=2038&country=2   (308 words)

  
 FP2000: Invalid Page Fault Inserting Timestamp When System Date is 2038
When you insert a Time stamp on a page in FrontPage and your computer date is set to the year 2038, you may receive one of the following errors:
FrontPage does not recognize the year 2038 as part of the two-digit number system specified for the 21st century.
Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article.
support.microsoft.com /support/kb/articles/Q219/2/20.ASP   (227 words)

  
 [No title]
Is there a specific order to buying and selling on your turn: No (all but 2038), Yes(2038).
Yes(1830, 1856, 1870.*****), No, drops one per block of shares sold by a single player on his turn (1835, 2038).
No*(1829, 1835), Yes (1830, 1853, 1856, 2038, 1870).
www.gg.caltech.edu /~jeff/perl/18xx.html   (2075 words)

  
 Sony GDM 2038 Computer Monitor - Manual request   (Site not responding. Last check: 2007-09-06)
Sony GDM 2038 Computer Monitor - Manual request
I have a problem with my monitor...I was using it a week ago....Switched it off to go home...and next morning when i turn on the monitor i am hearing a squarel noise on the G Board...
I hope you have some service skills and you know precautions you should apply in this case.
www.edaboard.com /ftopic70327.html   (200 words)

  
 Google's Cookie
The CIA had to stop using a comparatively innocent log-analysis cookie that expired in 10 years, and their document search site isn't even used by many people.
A cult of geeky blogging Google pundits joins in, and ridicules the notion that you'll be using the same computer in 2038.
When we noticed this in year 2000 (it was the first time we had ever seen such a long-lived cookie), the idea of Google Watch was born.
www.google-watch.org /cgi-bin/cookie.htm   (976 words)

  
 The Year 2038 Bug
Which means that 32-bit UNIX systems won't be able to process time beyond 19 Jan 2038 at 3:14:07 AM One of the common solutions will be to switch to 64-bit architecture systems that can store a maximium of
31 years, 6 months, and 16 days until 19 Jan 2038.
To give an indication if a Unix machine is 2038 Compliant, one can run this perl script to see if the time is incremented correctly.
gsp.com /2038   (247 words)

  
 Date Set to Year Later Than 2038 Can Cause Problems
This error can occur if the date on your computer is set to a year later than 2038.
Set the date on your computer to the year 2038 or earlier.
If Internet Explorer has stopped responding, you can close it by pressing CTRL+ALT+DELETE to open the Close Program dialog box, clicking Microsoft Internet Explorer in the list of programs, and then clicking End Task.
support.microsoft.com /support/kb/articles/q142/5/76.asp   (225 words)

  
 US CODE: Title 26,2038. Revocable transfers   (Site not responding. Last check: 2007-09-06)
TITLE 26 > Subtitle B > CHAPTER 11 > Subchapter A > PART III > § 2038
The value of the gross estate shall include the value of all property—
LII has no control over and does not endorse any external Internet site that contains links to or references LII.
www.law.cornell.edu /uscode/html/uscode26/usc_sec_26_00002038----000-.html   (90 words)

  
 RFC 2038 (rfc2038) - RTP Payload Format for MPEG1/MPEG2 Video
RFC 2038 (rfc2038) - RTP Payload Format for MPEG1/MPEG2 Video
RFC 2038 - RTP Payload Format for MPEG1/MPEG2 Video
Next: RFC 2039 - Applicability of Standards Track MIBs to Management of World Wide Web Servers
www.faqs.org /rfcs/rfc2038.html   (2880 words)

  
 Amazon.com: Fuji Industrial Spray Equipment 2038 Plastic Diaphragms (3): Tools & Hardware   (Site not responding. Last check: 2007-09-06)
Join Amazon Prime and ship Two-Day for free and Overnight for $3.99.
Fuji Industrial Spray Equipment 2038 Plastic Diaphragms (3)
Prevents paint entering the spraygun through the pressure tube.
www.amazon.com /exec/obidos/tg/detail/-/B0000UJJIO?v=glance   (426 words)

  
 Amazon.com: Michelin Rome Mini-Spiral Atlas No. 2038 (Michelin Maps & Atlases): Books: Michelin Travel Publications   (Site not responding. Last check: 2007-09-06)
Amazon.com: Michelin Rome Mini-Spiral Atlas No. 2038 (Michelin Maps & Atlases): Books: Michelin Travel Publications
This item is not eligible for Amazon Prime, but over a million other items are.
Michelin Rome Mini-Spiral Atlas No. 2038 (Michelin Maps & Atlases) (Spiral-bound)
www.amazon.com /exec/obidos/tg/detail/-/2062038003?v=glance   (783 words)

Try your search on: Qwika (all wikis)

Factbites
  About us   |   Why use us?   |   Reviews   |   Press   |   Contact us  
Copyright © 2005-2007 www.factbites.com Usage implies agreement with terms.