Next to Action computer. They were both in the buildings south of St. John's and north of 24 Hour Fitness. Now Action moved into the same complex as St. John's I think.
Thanks to the other poster for the T-Zone thing, that sounds right, I just don't feel like posting twice.
I forgot, there is one thing RawCHS nowadays. That is that there is no proper spec for how to know if a partition in an MBR (fdisk) partition table is a valid partition. So there are heuristics that are applied to the entries to guess if they are real or to be ignored as empty. One of the heuristics that some software uses is to ignore all partition entries that don't begin on a cylinder boundary. To be on a cylinder boundary, the partition has to start on a sector number that is a multiple of the number of sectors (S in CHS) in order to be valid. And since all drives 8GB or greater present an S of 63, that is why the first partition on an MBR disk has always started at sector 63, which makes it unaligned when the internal sector size is 4K (8 internal sectors).
Windows before 2000 checks the CHS alignment of MBR entries and ignores any partition entries that don't start on a multiple of S. So all disks out there are misaligned. With Windows 2000 or later, you can start the partition on any boundary you want.
Western Digital has a jumper you can put on the drive that adds 1 to all access requests, making all those misaligned first partitions aligned. But it'll also make any aligned partitions misaligned. So the real answer is just to layout your disk different. I would recommend using GUID disk partitioning instead of MBR anyway, because MBR doesn't work for >2TB drives. And GUID doesn't have any weird alignment requirements (and doesn't have any knowledge of CHS).
RawCHS hasn't meant anything in a decade. The largest drive you can describe with CHS is 8GB.
Track size hasn't meant anything in even longer than that. When drives went to zone bit recording (ZBR), the number of sectors per track became variable. This happened in about 1989.
The sector size does mean something, but it is the actual sector size, not the sector "grouping" size. If the drive reported a sector size of 4K, then it would expect that the host understand that sectors are actually 4K in size, not 512B in size. But really no major OS supports this, they all expect 512B sectors. That's why these drives internally use one sector size and show another size to the host. And there is no way in the ATA specification for devices to indicate their internal sector size when they are presenting a different external sector size.
So this won't be fixed with a firmware update, unless Vista, 7 and every other major OS is fixed to actually support large sectors presented to the host. Then the drive could be firmware updated to report the large sector size to the host. And the drive would then be completely unusable under any earlier OS or with any USB or Fireware adapter.
It was in where the Grainger is now. Fry's was where Sports Basement is. But Weird Stuff was on that side of the road before Fry's, I think. Fry's used to be one street east, on Lakeside Drive. Maybe you can still see the "Fry's parking only" stencil on the parking spots just on the other side of the row of trees forming the east side of the parking lot St. John's is in.
What was the name of the computer/electronics store that moved in after Weird Stuff? It was an import from another country. They sure jumped into a battle, with NCA and Fry's already running huge component sales, they were eaten alive quickly.
atapi.sys isn't the file that is patched, it's the file with the rootkit in it.
You're saying MS should have checked atapi.sys before replacing another file? How many files does it need to check before changing a system file? This rootkit is calling into other DLLs in a way that is designed to bypass safety measures, is it a wonder MS' safety measures don't prevent it?
If you learn one thing, learn this. MS doesn't patch files with their updates. They only replace them. So this can't be a case of a patch (offset or context) going awry.
MS does put a lot into their anti-malware activities. It's just it isn't in their 8 year old OS. When you redesign a system, sometimes you can't backpatch it into older stuff. If you ran the newest OS, you would have been protected from this particular malware.
As you may have read elsewhere, MS doesn't use context or offset diffs. They just replace files. So the case you speak of is unlikely.
The most likely case is that people who are having the problem have a foreign DLL in their system that calls directly into an offset into this DLL without version checking it. This DLL does so because it's a rootkit, and it wants to fly under the radar. When you change this DLL that other DLL is now calling into invalid code.
But the problem here is this other DLL is bad. It isn't a problem in MS' DLL at all. And how is MS to prevent this, are they to somehow figure out every other DLL in your system that could try to call into this DLL using surreptitious means?
MS didn't know this rootkit existed, or if they knew, they didn't test with it. That's about as far as I can blame them without any more info.
I totally agree. This is another reason that we cannot trust the US anymore. Their only interest is their own interest, and everything else they do and say is hypocrisy. They sold out on all of their values. And I mean the US government, including the whole political system, but not all people living there. US business is a very bad factor in the world as well (think of banks), but the US state makes this possible.
Everyone puts their own interests first. The EU is likely reject this treaty because doing so is in their own interests.
Of course it doesn't stay in those wells, that's how it was found in the other well too. And it's surely in other wells even further away, just at lower concentrations.
That's why they're looking for the source of the leak by drilling more wells. Once they find the leak they can fix it.
Some say they should shut down the plant while they find the leak. Which is an interesting concept. Do you know how they find leaks in underground pipes? They put in radioactive tracers and then detect for it.
So, as long as the levels of radiation at wells outside the plant are low enough it's safe to keep running the plant while the leak is found.
Also, radiation doesn't build up in your body. There is a model for body damage from radiation that counts cumulative exposure over a long period. But that isn't because the radiation stays in your body the whole time, it's because the damage from the radiation takes a long time to repair so it's useful mathematically to sum it up over time.
Either way, the radiation levels have not increased 37x. The danger has not increased 37x. There's not even information (at this time) that the leak has grown at all, they're just measuring at a new spot. This would be like jumping in a pool at the shallow end and saying it's 3 feet deep, then walking to the deep end and saying the pool got deeper. It was 6 feet deep at that end before, you just didn't measure it in that spot before.
The article says the levels in the well from before doubled and are still below the federal level. Levels at another existing well dropped. And a new well was drilled to try to find the leak and it has a much higher concentration of tritium.
Unless you're drinking from the new well (and no one is, it's a test well), this doesn't really affect you at all. It's not like you're getting 37x as much radiation now (at least as far as the data we have says). And it's part of the process of finding the leak and fixing it.
But you really should watch them both since the 2nd one which is easier to listen to since it flows better and has less bad grammar and typos leaves out things like Leno being sad and Conan being happy about the shift (the original shift, not the shift back).
I think this video really works well. I think there's a market for this stuff.
The car had a push button ignition, you had to hold the button 3.3 seconds to turn off the car while it is in motion. As this was a loaner car, he didn't know this. He should have, but he didn't.
Still, even without knowing that, he could have put the car into neutral and he failed to do that also.
Also, this Lexus isn't part of the pedal recall, it is only part of the floormat recall. Toyota doesn't think they have pedal problems with Japanese-built vehicles, and this (like all that I know of) Lexus is Japanese-built.
There were several ways Toyota could improve the car to overcome what happened in this case. First is, on many throttle-by-wire cars (like the Lexus ES 350 in this case), if you depress the brake, it cancels the gas. So if the gas is stuck, you brake normally and you're done. Audi has had this feature for 10 years. Another is that if you push the ignition button while moving, the car can put a message up saying "press and hold (or whatever) to turn off" instead of doing nothing. Also in a GM car for example, if you press the ignition button while moving twice within 5 seconds, the vehicle turns off. So in a panic case, you likely would press the button more than once and it would turn off.
So yeah, I believe this man could have saved his own life and failed to do so. He and the 3 others could be alive today. But Toyota has some steps they must take also to make the car more "fail-safe".
When you hear something ridiculous about California... true or not... does it really surprise you?
When I hear something stupid about California, like that warning tags have the name of some California lawsuit on them, or that California has a $21B deficit on them, it doesn't surprise me at all. Why not? Because haters abound. See, neither of these two things are true. I've been alive for 40 years and in California for almost 20 and I've never need a name of a lawsuit from any state on a warning tag. And I doubt you have either. Even when it's a Prop 65 warning (useless as they are), that's still not the name of a lawsuit, it's the name of a law.
And California's deficit? Every state is running a deficit right now because times are tough. California's deficit as passed is about $8B (depending on how you measure some of the BS measures that just change accounting instead of fixing things). Texas, whom everyone points out knows how to run a state right, is predicting larger deficits over the next 2 years (Texas uses a two-year budget) per capita and per-GDP than California is.
So it never surprises me to see someone talking trash about California, ever. Now if I could understand why people do so, I'd be a large step ahead.
I'm sure the new auction starting price is the current "value" of the art piece. So it will never sell for less than it has before, it just won't sell. So it can get stuck at one museum forever, but it won't actually be sold for less than before.
I'm sure a portion of the 15% paid is used by the artist to defray the eBay auction fees.
I don't give a crap about how unhappy the people who still think Xvid and AVI are the way to go are.
It's time to move forward, and you don't do that by standing still.
If you want to produce Xvid, there are still programs to do it. Go get one.
I'm not saying programs shouldn't play back Xvid, they definitely should. But it's time to stop producing new files in an old format that produces noticeably inferior results for the same size file.
I do wish the H.264 guys didn't make the same mistake other formats did with having multiple profiles. It's really annoying when you have a device that "plays H.264" and yet won't play a lot of files. But now we seem to be pretty much past that. Use profile 3.1 and you'll play on any reasonable HD device.
Also, if a.m2ts file plays on the PC, you don't need more codecs to play the corresponding.mkv file of it, all you need is something that understands the.mkv container format. Because the payload is the same, just the container is different.
I'm sure a good streaming program can remux.mkvs to.m2ts on the fly, even high bitrate HD video, because my PC can convert a 3GB.mkv to.m2ts in about 90 seconds. However, I can't find a streaming (DLNA) program that I like that does it.
Look, the Handbrake guys are saying Xvid is the past, H.264 is the present. Quoting what an OS that is 7 years old can do is just reinforcing what the Handbrake folks say.
mkv is a great format, but it isn't supported by Windows 7, Mac OS X (Quicktime), 360 or PS3.
I can however play an H.264/AC-3.m2ts file on Windows 7 and PS3. Maybe Mac OS X too, I'm not sure (my Mac is too slow for HD video anyway).
Because of this I end up converting virtually all my.mkvs to.2mts files (using TSMuxer) and throwing the.mkvs away. I can stream them to my PS3 for viewing on my TV or watch them in VLC on my Mac or VLC or Windows Media Player on my Windows PC..m2ts is a very capable format, I wish more people would use it.
And on the main topic, I'm so over AVI. Only with extensions can it support files large enough for HD movies, and then the playback compatibility drops through the floor anyway. And H.264 is so good it almost baffles me.
XVid was key when we were watching SD content on hacked (original) Xboxes. That was a long time ago now. It's time to move on.
Perhaps you need to stop using a 7 year old OS as your reference of what "Windows does".
Re:never can get enough of the theme song.
on
M.U.L.E. Is Back
·
· Score: 1
That sounds great too, it might even be better from some objective level. But it's just not what I'm used to so it sounds funny to me. I always wanted an Atari 800, but you can't always get what you want.
The trills in the final segment sound discordant to me.
And to the other poster: I knew the game came from the 800, the 800 was the only machine which had 4 joystick play (on the C64 two players had to use the keyboard during trading). But the C64 version is what's familiar to me.
never can get enough of the theme song.
on
M.U.L.E. Is Back
·
· Score: 4, Informative
Some of the best home computer music of the time. This song is the number 1 reason I fire up SIDplay (followed closely by many things by David Whittaker).
They offer IPv6. It's tunneled as far as I can tell, but it's tunneled within their own network so it works well.
sonic.net is the best, you just can't get fast service from them in most places. Lucky for you one of the places you can get it is downtown San Francisco.
Slashdot Mirror
Next to Action computer. They were both in the buildings south of St. John's and north of 24 Hour Fitness. Now Action moved into the same complex as St. John's I think.
Thanks to the other poster for the T-Zone thing, that sounds right, I just don't feel like posting twice.
I forgot, there is one thing RawCHS nowadays. That is that there is no proper spec for how to know if a partition in an MBR (fdisk) partition table is a valid partition. So there are heuristics that are applied to the entries to guess if they are real or to be ignored as empty. One of the heuristics that some software uses is to ignore all partition entries that don't begin on a cylinder boundary. To be on a cylinder boundary, the partition has to start on a sector number that is a multiple of the number of sectors (S in CHS) in order to be valid. And since all drives 8GB or greater present an S of 63, that is why the first partition on an MBR disk has always started at sector 63, which makes it unaligned when the internal sector size is 4K (8 internal sectors).
Windows before 2000 checks the CHS alignment of MBR entries and ignores any partition entries that don't start on a multiple of S. So all disks out there are misaligned. With Windows 2000 or later, you can start the partition on any boundary you want.
Western Digital has a jumper you can put on the drive that adds 1 to all access requests, making all those misaligned first partitions aligned. But it'll also make any aligned partitions misaligned. So the real answer is just to layout your disk different. I would recommend using GUID disk partitioning instead of MBR anyway, because MBR doesn't work for >2TB drives. And GUID doesn't have any weird alignment requirements (and doesn't have any knowledge of CHS).
I'll get to why in a second, but first:
RawCHS hasn't meant anything in a decade. The largest drive you can describe with CHS is 8GB.
Track size hasn't meant anything in even longer than that. When drives went to zone bit recording (ZBR), the number of sectors per track became variable. This happened in about 1989.
The sector size does mean something, but it is the actual sector size, not the sector "grouping" size. If the drive reported a sector size of 4K, then it would expect that the host understand that sectors are actually 4K in size, not 512B in size. But really no major OS supports this, they all expect 512B sectors. That's why these drives internally use one sector size and show another size to the host. And there is no way in the ATA specification for devices to indicate their internal sector size when they are presenting a different external sector size.
So this won't be fixed with a firmware update, unless Vista, 7 and every other major OS is fixed to actually support large sectors presented to the host. Then the drive could be firmware updated to report the large sector size to the host. And the drive would then be completely unusable under any earlier OS or with any USB or Fireware adapter.
That pic is from 2007.
Have you seen him lately?
http://cache-03.gawkerassets.com/assets/images/1/2008/11/Rogen_Kevin_Fat_Guys.flv.jpg
It was in where the Grainger is now. Fry's was where Sports Basement is. But Weird Stuff was on that side of the road before Fry's, I think. Fry's used to be one street east, on Lakeside Drive. Maybe you can still see the "Fry's parking only" stencil on the parking spots just on the other side of the row of trees forming the east side of the parking lot St. John's is in.
What was the name of the computer/electronics store that moved in after Weird Stuff? It was an import from another country. They sure jumped into a battle, with NCA and Fry's already running huge component sales, they were eaten alive quickly.
When you bitch about people having nicknames for MS, you sound like a tool.
atapi.sys isn't the file that is patched, it's the file with the rootkit in it.
You're saying MS should have checked atapi.sys before replacing another file? How many files does it need to check before changing a system file? This rootkit is calling into other DLLs in a way that is designed to bypass safety measures, is it a wonder MS' safety measures don't prevent it?
If you learn one thing, learn this. MS doesn't patch files with their updates. They only replace them. So this can't be a case of a patch (offset or context) going awry.
MS does put a lot into their anti-malware activities. It's just it isn't in their 8 year old OS. When you redesign a system, sometimes you can't backpatch it into older stuff. If you ran the newest OS, you would have been protected from this particular malware.
His own trusted baby at MS told him to install Vista two years ago and Windows 7 this year and he did. Because of this he didn't have the problem.
It's weird to me to see people so nonchalantly talk about running an OS that's so far out of date. You wouldn't run Ubuntu 5.04, would you?
As you may have read elsewhere, MS doesn't use context or offset diffs. They just replace files. So the case you speak of is unlikely.
The most likely case is that people who are having the problem have a foreign DLL in their system that calls directly into an offset into this DLL without version checking it. This DLL does so because it's a rootkit, and it wants to fly under the radar. When you change this DLL that other DLL is now calling into invalid code.
But the problem here is this other DLL is bad. It isn't a problem in MS' DLL at all. And how is MS to prevent this, are they to somehow figure out every other DLL in your system that could try to call into this DLL using surreptitious means?
MS didn't know this rootkit existed, or if they knew, they didn't test with it. That's about as far as I can blame them without any more info.
I totally agree. This is another reason that we cannot trust the US anymore. Their only interest is their own interest, and everything else they do and say is hypocrisy. They sold out on all of their values. And I mean the US government, including the whole political system, but not all people living there. US business is a very bad factor in the world as well (think of banks), but the US state makes this possible.
Everyone puts their own interests first. The EU is likely reject this treaty because doing so is in their own interests.
Of course it doesn't stay in those wells, that's how it was found in the other well too. And it's surely in other wells even further away, just at lower concentrations.
That's why they're looking for the source of the leak by drilling more wells. Once they find the leak they can fix it.
Some say they should shut down the plant while they find the leak. Which is an interesting concept. Do you know how they find leaks in underground pipes? They put in radioactive tracers and then detect for it.
http://www.darvill.clara.net/nucrad/uses.htm
So, as long as the levels of radiation at wells outside the plant are low enough it's safe to keep running the plant while the leak is found.
Also, radiation doesn't build up in your body. There is a model for body damage from radiation that counts cumulative exposure over a long period. But that isn't because the radiation stays in your body the whole time, it's because the damage from the radiation takes a long time to repair so it's useful mathematically to sum it up over time.
Either way, the radiation levels have not increased 37x. The danger has not increased 37x. There's not even information (at this time) that the leak has grown at all, they're just measuring at a new spot. This would be like jumping in a pool at the shallow end and saying it's 3 feet deep, then walking to the deep end and saying the pool got deeper. It was 6 feet deep at that end before, you just didn't measure it in that spot before.
I hope they get this problem fixed soon.
The article says the levels in the well from before doubled and are still below the federal level. Levels at another existing well dropped. And a new well was drilled to try to find the leak and it has a much higher concentration of tritium.
Unless you're drinking from the new well (and no one is, it's a test well), this doesn't really affect you at all. It's not like you're getting 37x as much radiation now (at least as far as the data we have says). And it's part of the process of finding the leak and fixing it.
There's a slightly better translation here.
http://www.youtube.com/watch?v=-Yrj35SHhZM&feature=related
But you really should watch them both since the 2nd one which is easier to listen to since it flows better and has less bad grammar and typos leaves out things like Leno being sad and Conan being happy about the shift (the original shift, not the shift back).
I think this video really works well. I think there's a market for this stuff.
The car had a push button ignition, you had to hold the button 3.3 seconds to turn off the car while it is in motion. As this was a loaner car, he didn't know this. He should have, but he didn't.
Still, even without knowing that, he could have put the car into neutral and he failed to do that also.
Also, this Lexus isn't part of the pedal recall, it is only part of the floormat recall. Toyota doesn't think they have pedal problems with Japanese-built vehicles, and this (like all that I know of) Lexus is Japanese-built.
There were several ways Toyota could improve the car to overcome what happened in this case. First is, on many throttle-by-wire cars (like the Lexus ES 350 in this case), if you depress the brake, it cancels the gas. So if the gas is stuck, you brake normally and you're done. Audi has had this feature for 10 years. Another is that if you push the ignition button while moving, the car can put a message up saying "press and hold (or whatever) to turn off" instead of doing nothing. Also in a GM car for example, if you press the ignition button while moving twice within 5 seconds, the vehicle turns off. So in a panic case, you likely would press the button more than once and it would turn off.
So yeah, I believe this man could have saved his own life and failed to do so. He and the 3 others could be alive today. But Toyota has some steps they must take also to make the car more "fail-safe".
When you hear something ridiculous about California... true or not... does it really surprise you?
When I hear something stupid about California, like that warning tags have the name of some California lawsuit on them, or that California has a $21B deficit on them, it doesn't surprise me at all. Why not? Because haters abound. See, neither of these two things are true. I've been alive for 40 years and in California for almost 20 and I've never need a name of a lawsuit from any state on a warning tag. And I doubt you have either. Even when it's a Prop 65 warning (useless as they are), that's still not the name of a lawsuit, it's the name of a law.
And California's deficit? Every state is running a deficit right now because times are tough. California's deficit as passed is about $8B (depending on how you measure some of the BS measures that just change accounting instead of fixing things). Texas, whom everyone points out knows how to run a state right, is predicting larger deficits over the next 2 years (Texas uses a two-year budget) per capita and per-GDP than California is.
So it never surprises me to see someone talking trash about California, ever. Now if I could understand why people do so, I'd be a large step ahead.
I'm sure the new auction starting price is the current "value" of the art piece. So it will never sell for less than it has before, it just won't sell. So it can get stuck at one museum forever, but it won't actually be sold for less than before.
I'm sure a portion of the 15% paid is used by the artist to defray the eBay auction fees.
It has been since it debuted in an XP service pack.
So if you "disable" DEP to make some apps work, it still isn't disabled for IE8, because IE8 opts-in for it.
Seriously, and I don't mean this as an insult.
I don't give a crap about how unhappy the people who still think Xvid and AVI are the way to go are.
It's time to move forward, and you don't do that by standing still.
If you want to produce Xvid, there are still programs to do it. Go get one.
I'm not saying programs shouldn't play back Xvid, they definitely should. But it's time to stop producing new files in an old format that produces noticeably inferior results for the same size file.
I do wish the H.264 guys didn't make the same mistake other formats did with having multiple profiles. It's really annoying when you have a device that "plays H.264" and yet won't play a lot of files. But now we seem to be pretty much past that. Use profile 3.1 and you'll play on any reasonable HD device.
And you can't add codecs to the PS3.
Also, if a .m2ts file plays on the PC, you don't need more codecs to play the corresponding .mkv file of it, all you need is something that understands the .mkv container format. Because the payload is the same, just the container is different.
I'm sure a good streaming program can remux .mkvs to .m2ts on the fly, even high bitrate HD video, because my PC can convert a 3GB .mkv to .m2ts in about 90 seconds. However, I can't find a streaming (DLNA) program that I like that does it.
Look, the Handbrake guys are saying Xvid is the past, H.264 is the present. Quoting what an OS that is 7 years old can do is just reinforcing what the Handbrake folks say.
mkv is a great format, but it isn't supported by Windows 7, Mac OS X (Quicktime), 360 or PS3.
I can however play an H.264/AC-3 .m2ts file on Windows 7 and PS3. Maybe Mac OS X too, I'm not sure (my Mac is too slow for HD video anyway).
Because of this I end up converting virtually all my .mkvs to .2mts files (using TSMuxer) and throwing the .mkvs away. I can stream them to my PS3 for viewing on my TV or watch them in VLC on my Mac or VLC or Windows Media Player on my Windows PC. .m2ts is a very capable format, I wish more people would use it.
And on the main topic, I'm so over AVI. Only with extensions can it support files large enough for HD movies, and then the playback compatibility drops through the floor anyway.
And H.264 is so good it almost baffles me.
XVid was key when we were watching SD content on hacked (original) Xboxes. That was a long time ago now. It's time to move on.
Perhaps you need to stop using a 7 year old OS as your reference of what "Windows does".
That sounds great too, it might even be better from some objective level. But it's just not what I'm used to so it sounds funny to me. I always wanted an Atari 800, but you can't always get what you want.
The trills in the final segment sound discordant to me.
And to the other poster:
I knew the game came from the 800, the 800 was the only machine which had 4 joystick play (on the C64 two players had to use the keyboard during trading). But the C64 version is what's familiar to me.
http://www.youtube.com/watch?v=p6L6MhSgpgo
Some of the best home computer music of the time. This song is the number 1 reason I fire up SIDplay (followed closely by many things by David Whittaker).
They offer IPv6. It's tunneled as far as I can tell, but it's tunneled within their own network so it works well.
sonic.net is the best, you just can't get fast service from them in most places. Lucky for you one of the places you can get it is downtown San Francisco.
http://sonic.net/features/ipv6/
It'd be better if they supported native IPv6, but then again my home router doesn't support native IPv6 either (but it does support tunneling).