PDF is based on a subset of Postscript, missing the control flow constructs that make Postscript into a full programming language, and making it better suited for displays.
PDF also has a royalty-free specification, allowing Apple to make its own DPS clone using a PDF model (Quartz), and DPS was apparently not cheap to license.
You don't need the metadata, you just need the allocation table (an array of block IDs on some OSes, a bitmap on others), and enough superblock information to verify the filesystem type and find the allocation table. I guess this would be harder on filesystems that don't use an array or bitmap. I think ext2/ext3 uses free block lists spread sparsely around the drive. Also, partitioning the flash drive might complicate things, since most flash drives aren't partitioned.
There's still "reasonable doubt" that the prosecution wasn't corrupt and faked the data, if you can't reproduce the recovery a second time. One time is good enough if you've lost important data, but not good enough for criminal evidence.
Actually the number of possible combinations are 2^(2048*8) bits. I'm just going to guess here that 2^16384 is more than the number of atoms in the galaxy, or even the universe.
Actually, this is no longer correct. SSDs (such as the one in this study) are quite capable of examining the filesystem stored on the drive, independently, and the concept of 'dutifully' and ignorantly maintaining deleted data goes out of the window as a result.
I think that would depend on which filesystem you used. I would be surprised if these days they didn't recognize FAT and FAT32, which have relatively simple allocation mapping, and are what almost always gets used on flash drives. And it should be reasonably possible to recognize HFS+, since it uses a simple bitmap to identify free blocks. NTFS may be possible, but the lack of a proper specification wouldn't help. In any case, a flash drive can't recognize any completely new filesystem that was invented after it was manufactured. Or even the lack of a filesystem, in the case of using it as a raw device for tar-style backups.
However, suppose you're using reiserfs and running a VM that also uses reiserfs on its virtual disk, which lives inside a file on your main filesystem. The recovery tools would see those structures, too, and merge them back into your directory structure. This is typically disastrous.
Sounds like it would be murder on your drive's directory structure.
Except that the Newton didn't happen until 1987, two years after this incident, and would probably have never happened at all.
And using Unix for low-power applications? That's a good one. That didn't happen until Linux became popular for embedded use. Even the iPod was around for years before Apple decided to port Darwin to it.
Also, obviously you are a Windows user. iTunes isn't nearly as bloated on Mac; it's that Carbon compatibility layer stuff and Quicktime that bloat it on Windows.
Actually, anyone who was Not Steve would have screwed it up. What Woz had in technical savvy, Jobs had in product savvy. Apple would have been long gone if NeXT hadn't bought them for negative 400 million dollars.
You talk like this is the first time that Google has done this. Remember a few months back when they came up with a programming language that was a common 2-letter word, and the name of an existing board game? I wonder what tweaking to their search algorithms they had to do to make it come up as high as #3 on that search, or even on the first page at all.
If you had bothered to go to the bottom of the linked page, you would have found an Apple Store link that shows all 5 standard SKUs with their prices, and buttons that take you to the Build To Order options. But no, you would rather bitch about it being a conspiracy or something. In any case, you would probably consider a low-end Dull with a supertwist LCD (or something that weighs 10+ pounds) to be "comparable" by looking at nothing but CPU speed and RAM and then whine about the "markup".
However, that means that you can't use an external monitor and a light peak device at the same time, unless you either deal with an ugly(almost certainly powered) breakout box, or buy an entirely new monitor that embeds the breakout box and/or a bunch of light peak-connected ports in itself(just like the ADC monitors of yore...).
Or unless the monitors that support that connector have a daisy-chain output, which they should. Or unless the adapter for older monitors has a daisy-chain output.
I think it's goofy to have a connector which can't make up its mind between video signals and a data signal be pushed as a data signal connector standard (so every cable has to have the video wires even when it's only being hooked to a hard drive?), but apparently you missed yesterday's article that said LP was daisy-chainable. I take this to mean that most devices (other than the main computer) will have two or three ports, just like most Firewire devices do now.
However, if you are like me, your skin oils or whatever will etch into the surface where your palms rest, and the silver color from the keys will have been eroded from your fingernails typing on the keys. I don't think I'm completely happy with the newer "chiclet" keys or the "hidden button" trackpad, but there were some big problems with the previous design (the current design is less than 4 years old), and I've had three since the PowerPC "aluminum" Powerbooks. (one 17" PPC, one 32-bit Intel, one 64-bit Intel), and I'm glad that Apple retired that case design. I got a Marware pad to protect that top surface, and while it is tattered where my palms rest, it at least kept the surface from eroding.
As someone else has said, the base 15" is $1799. The extra $400 gets you an extra 200MHz of CPU speed, an extra 250GB of hard drive, and video RAM is upgraded from 256M to 1G. If you don't plan on using your laptop for high-powered 3D gaming, you can probably live without all that. The 15" and 13" are for people who would rather have a smaller laptop than one with the kitchen sink.
(Though I do find the 13" 2.7GHz to be odd, since the larger ones only offer up to 2.3GHz as BTO. Maybe the Radeon somehow limits the maximum CPU speed.)
But that was even before the transistor was invented. It's one thing when everyone is manually turning knobs of the two clocks in the house, and pushing paper around. It's another thing when you have dozens of clocks around you, and computers constantly talking to each other. Plus, we now have dozens of clocks around us, many of which we don't notice because they know how to change to DST automatically.
It's not a default, it's the only way things have ever been done. Nobody uses a +2 summer time advance, and I don't think anyone ever has. "Default" implies that there's a number you can change. Currently everything uses a boolean "DST on" (+1 in summer) or "DST off" (+0 year-round). You can't wedge a third number into a boolean. (unless you're a regular on thedailywtf.com in which case booleans have a third value of FILE_NOT_FOUND).
If they just want to go CET, that's been tried before and it didn't last long before everyone wanted to go back.
Except that those changes only changed the date of the time change. This changes the shift from one hour to two, which has never been done before, ever.
Smarter DST code already is written around the possibility of the date changing, since it's happened before. But the result has always been "keep the standard time" or "add one hour to standard time".
The real problem is morons in government thinking that it has any effect on saving energy. The previous meddling by the US congress had no such effect. All it did was cause confusion.
Now if they want to permanently change their standard (winter) time from GMT to GMT+0100, they can go right ahead, though I suspect the tradition of Greenwich Mean Time will cause some pride-related troubles.
Way to pay attention, guy. These are taxes Texas wants to collect on stuff that Amazon imported from another state (mostly, anyhow), and sold in Texas to Texas residents.
So if they've already physically removed the connectors, what's the point in all that DRM BIOS bullshit? To keep some moron with a soldering iron from using the port? (which violates the warranty anyhow) And it's a problem with the chipset, not the CPU, so the chip is always soldered down and can't be re-used in another computer.
It's not like it affects any other part of the chip when it does go bad; it just kills the output that never had a connector until dickless over there decided to rig one up to it.
0/10 lame troll is lame... the division bug was a part of the chip that could be used in every computer that shipped with the chip. This bug only happens when you wire something up to specific pins. I don't see too many people doing the kind of SMT rework necessary to use these pins on motherboards that never had them hooked up in the first place.
Do you ever plan on changing your laptop's configuration? Add a harddrive? Where would you connect it?
This un-recall isn't for desktop motherboards with all SATA ports brought out to connectors. This is specifically and only for laptops and other situations where the four bad SATA ports never had a connector in the first place.
Slashdot Mirror
http://en.wikipedia.org/wiki/Portable_Document_Format#Technical_foundations
PDF is based on a subset of Postscript, missing the control flow constructs that make Postscript into a full programming language, and making it better suited for displays.
PDF also has a royalty-free specification, allowing Apple to make its own DPS clone using a PDF model (Quartz), and DPS was apparently not cheap to license.
So guruevi was both wrong and right.
You don't need the metadata, you just need the allocation table (an array of block IDs on some OSes, a bitmap on others), and enough superblock information to verify the filesystem type and find the allocation table. I guess this would be harder on filesystems that don't use an array or bitmap. I think ext2/ext3 uses free block lists spread sparsely around the drive. Also, partitioning the flash drive might complicate things, since most flash drives aren't partitioned.
There's still "reasonable doubt" that the prosecution wasn't corrupt and faked the data, if you can't reproduce the recovery a second time. One time is good enough if you've lost important data, but not good enough for criminal evidence.
Actually the number of possible combinations are 2^(2048*8) bits. I'm just going to guess here that 2^16384 is more than the number of atoms in the galaxy, or even the universe.
Actually, this is no longer correct. SSDs (such as the one in this study) are quite capable of examining the filesystem stored on the drive, independently, and the concept of 'dutifully' and ignorantly maintaining deleted data goes out of the window as a result.
I think that would depend on which filesystem you used. I would be surprised if these days they didn't recognize FAT and FAT32, which have relatively simple allocation mapping, and are what almost always gets used on flash drives. And it should be reasonably possible to recognize HFS+, since it uses a simple bitmap to identify free blocks. NTFS may be possible, but the lack of a proper specification wouldn't help. In any case, a flash drive can't recognize any completely new filesystem that was invented after it was manufactured. Or even the lack of a filesystem, in the case of using it as a raw device for tar-style backups.
However, suppose you're using reiserfs and running a VM that also uses reiserfs on its virtual disk, which lives inside a file on your main filesystem. The recovery tools would see those structures, too, and merge them back into your directory structure. This is typically disastrous.
Sounds like it would be murder on your drive's directory structure.
Except that the Newton didn't happen until 1987, two years after this incident, and would probably have never happened at all.
And using Unix for low-power applications? That's a good one. That didn't happen until Linux became popular for embedded use. Even the iPod was around for years before Apple decided to port Darwin to it.
Also, obviously you are a Windows user. iTunes isn't nearly as bloated on Mac; it's that Carbon compatibility layer stuff and Quicktime that bloat it on Windows.
But would a world without the Newton have been any different?
Actually, anyone who was Not Steve would have screwed it up. What Woz had in technical savvy, Jobs had in product savvy. Apple would have been long gone if NeXT hadn't bought them for negative 400 million dollars.
...and they would have been slow as molasses and died faster than the Zune.
Don't forget keeping sidewalks and roads from getting iced up in the winter!
You talk like this is the first time that Google has done this. Remember a few months back when they came up with a programming language that was a common 2-letter word, and the name of an existing board game? I wonder what tweaking to their search algorithms they had to do to make it come up as high as #3 on that search, or even on the first page at all.
If you had bothered to go to the bottom of the linked page, you would have found an Apple Store link that shows all 5 standard SKUs with their prices, and buttons that take you to the Build To Order options. But no, you would rather bitch about it being a conspiracy or something. In any case, you would probably consider a low-end Dull with a supertwist LCD (or something that weighs 10+ pounds) to be "comparable" by looking at nothing but CPU speed and RAM and then whine about the "markup".
However, that means that you can't use an external monitor and a light peak device at the same time, unless you either deal with an ugly(almost certainly powered) breakout box, or buy an entirely new monitor that embeds the breakout box and/or a bunch of light peak-connected ports in itself(just like the ADC monitors of yore...).
Or unless the monitors that support that connector have a daisy-chain output, which they should. Or unless the adapter for older monitors has a daisy-chain output.
I think it's goofy to have a connector which can't make up its mind between video signals and a data signal be pushed as a data signal connector standard (so every cable has to have the video wires even when it's only being hooked to a hard drive?), but apparently you missed yesterday's article that said LP was daisy-chainable. I take this to mean that most devices (other than the main computer) will have two or three ports, just like most Firewire devices do now.
However, if you are like me, your skin oils or whatever will etch into the surface where your palms rest, and the silver color from the keys will have been eroded from your fingernails typing on the keys. I don't think I'm completely happy with the newer "chiclet" keys or the "hidden button" trackpad, but there were some big problems with the previous design (the current design is less than 4 years old), and I've had three since the PowerPC "aluminum" Powerbooks. (one 17" PPC, one 32-bit Intel, one 64-bit Intel), and I'm glad that Apple retired that case design. I got a Marware pad to protect that top surface, and while it is tattered where my palms rest, it at least kept the surface from eroding.
As someone else has said, the base 15" is $1799. The extra $400 gets you an extra 200MHz of CPU speed, an extra 250GB of hard drive, and video RAM is upgraded from 256M to 1G. If you don't plan on using your laptop for high-powered 3D gaming, you can probably live without all that. The 15" and 13" are for people who would rather have a smaller laptop than one with the kitchen sink.
(Though I do find the 13" 2.7GHz to be odd, since the larger ones only offer up to 2.3GHz as BTO. Maybe the Radeon somehow limits the maximum CPU speed.)
But that was even before the transistor was invented. It's one thing when everyone is manually turning knobs of the two clocks in the house, and pushing paper around. It's another thing when you have dozens of clocks around you, and computers constantly talking to each other. Plus, we now have dozens of clocks around us, many of which we don't notice because they know how to change to DST automatically.
but with a default +1 advance.
It's not a default, it's the only way things have ever been done. Nobody uses a +2 summer time advance, and I don't think anyone ever has. "Default" implies that there's a number you can change. Currently everything uses a boolean "DST on" (+1 in summer) or "DST off" (+0 year-round). You can't wedge a third number into a boolean. (unless you're a regular on thedailywtf.com in which case booleans have a third value of FILE_NOT_FOUND).
If they just want to go CET, that's been tried before and it didn't last long before everyone wanted to go back.
Except that those changes only changed the date of the time change. This changes the shift from one hour to two, which has never been done before, ever.
Smarter DST code already is written around the possibility of the date changing, since it's happened before. But the result has always been "keep the standard time" or "add one hour to standard time".
The real problem is morons in government thinking that it has any effect on saving energy. The previous meddling by the US congress had no such effect. All it did was cause confusion.
Now if they want to permanently change their standard (winter) time from GMT to GMT+0100, they can go right ahead, though I suspect the tradition of Greenwich Mean Time will cause some pride-related troubles.
If Texas succeeds
I don't think that word means what you think it means.
Way to pay attention, guy. These are taxes Texas wants to collect on stuff that Amazon imported from another state (mostly, anyhow), and sold in Texas to Texas residents.
I agree that .nyc is stupid (I'm okay with .nyc.us), but .tx for Texas would be kind of cool, especially since they were once a sovereign nation.
So if they've already physically removed the connectors, what's the point in all that DRM BIOS bullshit? To keep some moron with a soldering iron from using the port? (which violates the warranty anyhow) And it's a problem with the chipset, not the CPU, so the chip is always soldered down and can't be re-used in another computer.
It's not like it affects any other part of the chip when it does go bad; it just kills the output that never had a connector until dickless over there decided to rig one up to it.
0/10 lame troll is lame... the division bug was a part of the chip that could be used in every computer that shipped with the chip. This bug only happens when you wire something up to specific pins. I don't see too many people doing the kind of SMT rework necessary to use these pins on motherboards that never had them hooked up in the first place.
Do you ever plan on changing your laptop's configuration? Add a harddrive? Where would you connect it?
This un-recall isn't for desktop motherboards with all SATA ports brought out to connectors. This is specifically and only for laptops and other situations where the four bad SATA ports never had a connector in the first place.