The standard pressure of 1 atm (atmosphere) equals 101325 Pascal (=N/m^2). Since 10E5 Pascal is indeed inconvenient, we have the bar. 1 bar equals 10E5 Pascal. Doesn't get easier than that, no?
Dadaism (ceci n'est pas une pipe) was born for exactly that reason. After the abstract art was discovered, people were just calling more and more things art that actually weren't. Some artist riduculed this by creating similar, but original pieces.
The bottom side is just a mm of transparant plastic. It is quite resistant to scratches, since the laser beam's diameter is wide upon entry of this plastic and then diverges (due to diffraction in the plastic) to a point on the data layer. Scratching the label side will destroy the data layer, which is immediately below the label. You can see this with an old CD-R when you break it: the label paint will have a reflective coating underneath. This is the actual data layer.
Actually, on a lot of my CD-Rs, I packed files in RAR archives with recovery records enabled. This allows similar corruption detection/correction. Although QuickPar seems to be a better tool (allowing more redundant data). Thanks for the link.
My first CD-Rs (over 10 years old) also still work perfectly. Some simple rules I follow are:
- Buy CD-Rs withouth printed label (the printing process causes material stress)
- Burn them at low speed (the lowest my current burner allows with my SW is 8x)
- Verify the data after writing (very important!)
- Always be careful with the label side (e.g. don't put that side on the table, dirt could cause scratches)
- Prevent hot temperatures and direct sunlight
I later found some advisory text that basically said the same thing.
If you have 1GB of RAM, as I do, you can just disable the swap file. I'm running XP for a few months like that now, seems to work fine. Or at least set the minimum and maximum swap sizes to 100MB, to reduce that rediculous 1.5GB swap file (although XP can still resize it then if it runs out of RAM).
'Looks exactly like' is maybe a bit strong. Granted, it is very similar in design. When comparing it with the transparant eyepiece of the Laser Vision system, the EyeTap seems to obstruct the real world image much more. Looking sideways may be impossible with the EyeTap (although I'm not sure of this, since I never got to wear one).
while we may all be fine and happy with drivers that work using vendor supplied binary-only bits of firmware inside an otherwise open driver, those vendors are not guaranteed to continue supplying that firmware or keep it free forever
While I can understand the fuss about binary-only drivers, I think embedding firmware code should be allowed. It should be seen as data needed to initialize the device in a workable state. I think there's no difference between only a few bytes written to some registers, or a whole firmware download. Including that firmware in the GPL code will allow others to use it in their modified drivers. The manufacturer could have put the firmware in an onboard ROM, but chose not to, so the firmware could be easily upgraded in case of bugs. Once the firmware code is stable, it will probably not change anymore anyway.
Only forming/melting ice (i.e. a water-ice mixture) is at 0C. Once ice is completely formed/melted, the temperature will fall/rise further. Maybe you were thinking about snow, which can act like an insulating blanket, because it traps air.
With all these buffer overflows, I wonder why they don't use array bounds checking in critical program parts. It's a bit slower, but it would be worth it (running a worm or virus slows your computer down even more). C/C++ doesn't have bounds checking, but I'm sure i've heard of compiler extensions that do it. Or they could use a language like Pascal (yes, I know, not my favorite either, but still a useful and bounds safe language) for security critical parts.
If this is the future of advertising, then in the future you won't be able to look in any direction without seeing some kind of commercial (in some places that's already true). You could close your eyes of course, but then they would probably invent some technique to induce these images directly in your visual cortex...
In windows, the uptime is derived from the Tick Count. The tick count is incremented by the kernel, based on a hardware timer source. This source is usually an Intel 8253 Programmable Interval Timer (or compatible device). Some implementations of this timer have been known to be buggy (actually the first one was meant to tick every 20ms instead of the now common 18.2ms). Probably in these Dell laptops, the timer got initialized with the wrong value somehow.
Slashdot Mirror
The standard pressure of 1 atm (atmosphere) equals 101325 Pascal (=N/m^2). Since 10E5 Pascal is indeed inconvenient, we have the bar. 1 bar equals 10E5 Pascal. Doesn't get easier than that, no?
Qute looks fine for me... Download the last version here.
WxWindows is called WxWidgets nowadays. wx4j is a binding of WxWidgets for Java, and is similar to SWT. Still in first stages of development, though.
Dadaism (ceci n'est pas une pipe) was born for exactly that reason. After the abstract art was discovered, people were just calling more and more things art that actually weren't. Some artist riduculed this by creating similar, but original pieces.
The 40" reference is in the update part of the post...
This was already mentioned here
Smelly cat, smelly cat, ...
If you run Windows on a 1000-node supercomputer, do you need a volume license? Also, MS will probably ask for a per-user license for running Office...
Since the S stands for Stimulated, that would become Ztimulated
Try removing the core memory modules. Works for me every time...
The bottom side is just a mm of transparant plastic. It is quite resistant to scratches, since the laser beam's diameter is wide upon entry of this plastic and then diverges (due to diffraction in the plastic) to a point on the data layer. Scratching the label side will destroy the data layer, which is immediately below the label. You can see this with an old CD-R when you break it: the label paint will have a reflective coating underneath. This is the actual data layer.
Actually, on a lot of my CD-Rs, I packed files in RAR archives with recovery records enabled. This allows similar corruption detection/correction. Although QuickPar seems to be a better tool (allowing more redundant data). Thanks for the link.
I later found some advisory text that basically said the same thing.
/. before) here
I googled a bit and found that text again (was in
My first CD-Rs (over 10 years old) also still work perfectly. Some simple rules I follow are:
- Buy CD-Rs withouth printed label (the printing process causes material stress)
- Burn them at low speed (the lowest my current burner allows with my SW is 8x)
- Verify the data after writing (very important!)
- Always be careful with the label side (e.g. don't put that side on the table, dirt could cause scratches)
- Prevent hot temperatures and direct sunlight
I later found some advisory text that basically said the same thing.
If you have 1GB of RAM, as I do, you can just disable the swap file. I'm running XP for a few months like that now, seems to work fine. Or at least set the minimum and maximum swap sizes to 100MB, to reduce that rediculous 1.5GB swap file (although XP can still resize it then if it runs out of RAM).
'Looks exactly like' is maybe a bit strong. Granted, it is very similar in design. When comparing it with the transparant eyepiece of the Laser Vision system, the EyeTap seems to obstruct the real world image much more. Looking sideways may be impossible with the EyeTap (although I'm not sure of this, since I never got to wear one).
Wood chips, eh. I have a big pile of paper here that needs to be processed. Might as well do something useful with it...
while we may all be fine and happy with drivers that work using vendor supplied binary-only bits of firmware inside an otherwise open driver, those vendors are not guaranteed to continue supplying that firmware or keep it free forever
While I can understand the fuss about binary-only drivers, I think embedding firmware code should be allowed. It should be seen as data needed to initialize the device in a workable state. I think there's no difference between only a few bytes written to some registers, or a whole firmware download. Including that firmware in the GPL code will allow others to use it in their modified drivers. The manufacturer could have put the firmware in an onboard ROM, but chose not to, so the firmware could be easily upgraded in case of bugs. Once the firmware code is stable, it will probably not change anymore anyway.
Don't worry. In a while they will add some new extensions and call it D++.
Only forming/melting ice (i.e. a water-ice mixture) is at 0C. Once ice is completely formed/melted, the temperature will fall/rise further. Maybe you were thinking about snow, which can act like an insulating blanket, because it traps air.
With all these buffer overflows, I wonder why they don't use array bounds checking in critical program parts. It's a bit slower, but it would be worth it (running a worm or virus slows your computer down even more). C/C++ doesn't have bounds checking, but I'm sure i've heard of compiler extensions that do it. Or they could use a language like Pascal (yes, I know, not my favorite either, but still a useful and bounds safe language) for security critical parts.
How long before someone finds a workaround for these security features? Until now, no DRM has been left standing.
Splut! What's that sound? Damn! Ran over another penguin crossing the road :(
If this is the future of advertising, then in the future you won't be able to look in any direction without seeing some kind of commercial (in some places that's already true). You could close your eyes of course, but then they would probably invent some technique to induce these images directly in your visual cortex...
In windows, the uptime is derived from the Tick Count. The tick count is incremented by the kernel, based on a hardware timer source. This source is usually an Intel 8253 Programmable Interval Timer (or compatible device). Some implementations of this timer have been known to be buggy (actually the first one was meant to tick every 20ms instead of the now common 18.2ms). Probably in these Dell laptops, the timer got initialized with the wrong value somehow.