From the article, it's not just that it fails to work in O2007, it's stated that it's not vulnerable. I'm pretty sure that the current file won't work on Office 2004 for Mac, but that's still listed as vulnerable. If they're consistent, the codepath is really fixed/changed in the new version.
Anyway, I'm surprised to see Access in the list of "possibly vulnerable". I guess it might be some part of the VBA parsing, since, except for that, lots of the file logic is different (the databases are not compound OLE documents).
Yeah, cause we know that pyramid schemes and MLM require each and every recipient to join the game. If only 50 % of the population used Office, but each infected machine sent out two copies (and each was opened), we would have a steady state of fresh infections. Logic like yours might have worked when the primary vector was the actual work documents, or floppy disks. With mass mailings, even a very small fraction could ensure a significant outreach. The question is simply if the explosive phase will be delayed enough to put extra countermeasures into place.
Well, I think you'll find that apps of that era were NOT resilient to malformed input. Maybe we could get them right if we aimed for the same functionality now, but I almost doubt it. (Well: if you put a workforce equivalent to the complete Excel team onto making a console app with the functionality of the original 1-2-3, I guess they could make it reasonable safe. At least until you press some F key to recalculate.)
Part of the problem is the internal cache in the disks. If you yank the USB HD out (not your common stick), the OS has hard time knowing how much of the data was actually written. Trying to resume could (at least theoretically) trash the FS up even more, as there would be a gap in what would otherwise be part of a perfectly fine journaling FS.
For IP television, they can put the servers where they want. They can get true multicast things done more easily when they control the whole stack as well, possibly up to and including proprietary software/hardware at your end to actually watch the stuff.
Did you read the parent? You do not answer his concerns regarding what should have been done, had the damage been determined beyond doubt at that point, already in orbit.
The fact that a 3 body system is chaotic doesn't mean that the mass will suddenly annihilate or change its total mass/energy. The exact positions might be unknown, but not being able to time-step doesn't mean that you can't say useful things about the end result. I can say that we'll all be dead in 200 years with what's probably pretty good accuracy, while not being able to account for our future lives in any detail at all.
Actually, for a long time, the refinements were highly in the field of litography, decreasing the wavelength and so on. Performance made breakthroughs, the actually technology "just" progressed. The last few years, that's been coupled with a lot more materials research. True, that's been going on for decades as well, but lots of the supposed advancements during the 80s never made it. Now, it seems like we actually need to reevaluate every piece of the process to do those things.
Cancelling I/O has been in Windows for long, "just" not always done properly. I have seen similar issues while killing processes in other OSes where they are stuck in some I/O. One reason for why this happens more frequently in Windows (in addition to bad drivers/a complicated driver model) is the fact that asynchronous I/O is so common. That way, you might not see the that the IO got stuck until you try to kill the process.
Gates has been talking about how part of the next Windows UI/UX would include a universal "command bar" (from the description something like this, but add a bit of Bob/Clippy "helpfulness" to it). If and when it appears, it won't exactly be like this product was the first time anyone ever came up with something similar.
Your argument about drive platters rather indicates exactly why area density makes quite a bit of sense, as long as the technology used is inherently two-dimensional.
It was some years ago, but I think that the book also stresses the problem for HAL in that the full mission was never revealed to the human crew, which meant that even too good thinking on their part, at the wrong point in time, would be considered a failure. HAL was programmed/ordered to obey the crew, but also respect the mission objectives, and the contradiction only grew worse.
Apple could pull that off in 2001, because no one expected them to do come in huge in that market. Even if all competitors had known exactly what the device would be like, that still wouldn't have changed too many things. Now, a lot of competitors in many neighboring "gadget" fields should be expected to track pre-release info regarding Apple products. They would do so even if Jobs didn't announce it officially. The relevant effect of the announcement is rather the public (as in mainstream) awareness of the upcoming product. That can certainly go both ways, as TFA speculates, but I think it might be an advantage for Apple.
Well, peripheral nerve stimulation is a very real effect and concern during whole-body MRI. You can induce currents within single nerves without creating chemical reactions. You still get the gradient and that's all that's needed. (Of course, that gradient will activate chemical reactions in the actual synapse.)
Do you use Aero or not? What encoding was used? One thing here is that both Office 2007, and Aero, and some other configurations of media player (including the free mplayerc, when used in XP with some subtitle modes) will default to not using video overlays, but rather an adapted 3D pipeline mechanism, which makes all kinds of transition effects/sharpening filters etc possible. A lot of cards fail on that in some situations where they work very well with traditional overlays.
Overlays are certainly not problem-free, though. On many early dual-screen cards (including laptops), playing a video could mean that the external output only saw a black or purple box. To me, this sounds like a driver issue that's more related to a general move towards rendering video in a generalized way, rather than a hack that was needed ten years ago, just like many other 2D acceleration cases are just border cases of what's now possible to do in a generalized manner with 3D hardware.
It completely boggles the mind to you that every individual Registry key in Windows can have a complete access control list...? Right? Security checks are not (very) expensive if done right. Even if a check was made for every single video frame from a specific source, the time needed to do the check could be very small, if related to the calculations needed to decode, or even transfer, a MPEG4 stream.
It's not hard to read dates. In classic IBM PC BIOS it's outright trivial. It should be quite simple in EFI as well, at least compared to the work needed to load up a fake environment for booting an OS that expects a classic BIOS.
Energy, and hence frequency, isn't well-defined. You have a probability distribution there, just like anything else. (It helps to remember how energy and momentum relates for a photon.) The method used for emitting, and the history of the beam, will determine what that distribution looks like, but you can "easily" be able to send signals with a very well-determined average frequency (let's say 30 digits), but where the variance in each individual instrument, even without introducing any error in the measuring process is far less exact.
Slashdot Mirror
But do they get you NP hard?
Anyway, I'm surprised to see Access in the list of "possibly vulnerable". I guess it might be some part of the VBA parsing, since, except for that, lots of the file logic is different (the databases are not compound OLE documents).
Yeah, cause we know that pyramid schemes and MLM require each and every recipient to join the game. If only 50 % of the population used Office, but each infected machine sent out two copies (and each was opened), we would have a steady state of fresh infections. Logic like yours might have worked when the primary vector was the actual work documents, or floppy disks. With mass mailings, even a very small fraction could ensure a significant outreach. The question is simply if the explosive phase will be delayed enough to put extra countermeasures into place.
Well, I think you'll find that apps of that era were NOT resilient to malformed input. Maybe we could get them right if we aimed for the same functionality now, but I almost doubt it. (Well: if you put a workforce equivalent to the complete Excel team onto making a console app with the functionality of the original 1-2-3, I guess they could make it reasonable safe. At least until you press some F key to recalculate.)
Part of the problem is the internal cache in the disks. If you yank the USB HD out (not your common stick), the OS has hard time knowing how much of the data was actually written. Trying to resume could (at least theoretically) trash the FS up even more, as there would be a gap in what would otherwise be part of a perfectly fine journaling FS.
There is this new version called Vista. You might have heard of it. DRM and floppy-less driver install!
Because we all know how cheap and permissive (some) font licenses actually are.
For IP television, they can put the servers where they want. They can get true multicast things done more easily when they control the whole stack as well, possibly up to and including proprietary software/hardware at your end to actually watch the stuff.
Did you read the parent? You do not answer his concerns regarding what should have been done, had the damage been determined beyond doubt at that point, already in orbit.
Yep, a Netscape 4.77.3141592 experience.
The fact that a 3 body system is chaotic doesn't mean that the mass will suddenly annihilate or change its total mass/energy. The exact positions might be unknown, but not being able to time-step doesn't mean that you can't say useful things about the end result. I can say that we'll all be dead in 200 years with what's probably pretty good accuracy, while not being able to account for our future lives in any detail at all.
Actually, for a long time, the refinements were highly in the field of litography, decreasing the wavelength and so on. Performance made breakthroughs, the actually technology "just" progressed. The last few years, that's been coupled with a lot more materials research. True, that's been going on for decades as well, but lots of the supposed advancements during the 80s never made it. Now, it seems like we actually need to reevaluate every piece of the process to do those things.
Cancelling I/O has been in Windows for long, "just" not always done properly. I have seen similar issues while killing processes in other OSes where they are stuck in some I/O. One reason for why this happens more frequently in Windows (in addition to bad drivers/a complicated driver model) is the fact that asynchronous I/O is so common. That way, you might not see the that the IO got stuck until you try to kill the process.
Gates has been talking about how part of the next Windows UI/UX would include a universal "command bar" (from the description something like this, but add a bit of Bob/Clippy "helpfulness" to it). If and when it appears, it won't exactly be like this product was the first time anyone ever came up with something similar.
Your argument about drive platters rather indicates exactly why area density makes quite a bit of sense, as long as the technology used is inherently two-dimensional.
Government in and of itself is a bad thing. Specific goals, handled by competent people, might make it a good thing in specific cases.
It was some years ago, but I think that the book also stresses the problem for HAL in that the full mission was never revealed to the human crew, which meant that even too good thinking on their part, at the wrong point in time, would be considered a failure. HAL was programmed/ordered to obey the crew, but also respect the mission objectives, and the contradiction only grew worse.
AFAIK, the number of "N" versions actually sold is pretty abysmal.
Apple could pull that off in 2001, because no one expected them to do come in huge in that market. Even if all competitors had known exactly what the device would be like, that still wouldn't have changed too many things. Now, a lot of competitors in many neighboring "gadget" fields should be expected to track pre-release info regarding Apple products. They would do so even if Jobs didn't announce it officially. The relevant effect of the announcement is rather the public (as in mainstream) awareness of the upcoming product. That can certainly go both ways, as TFA speculates, but I think it might be an advantage for Apple.
Well, peripheral nerve stimulation is a very real effect and concern during whole-body MRI. You can induce currents within single nerves without creating chemical reactions. You still get the gradient and that's all that's needed. (Of course, that gradient will activate chemical reactions in the actual synapse.)
Overlays are certainly not problem-free, though. On many early dual-screen cards (including laptops), playing a video could mean that the external output only saw a black or purple box. To me, this sounds like a driver issue that's more related to a general move towards rendering video in a generalized way, rather than a hack that was needed ten years ago, just like many other 2D acceleration cases are just border cases of what's now possible to do in a generalized manner with 3D hardware.
It completely boggles the mind to you that every individual Registry key in Windows can have a complete access control list...? Right? Security checks are not (very) expensive if done right. Even if a check was made for every single video frame from a specific source, the time needed to do the check could be very small, if related to the calculations needed to decode, or even transfer, a MPEG4 stream.
It's not hard to read dates. In classic IBM PC BIOS it's outright trivial. It should be quite simple in EFI as well, at least compared to the work needed to load up a fake environment for booting an OS that expects a classic BIOS.
Energy, and hence frequency, isn't well-defined. You have a probability distribution there, just like anything else. (It helps to remember how energy and momentum relates for a photon.) The method used for emitting, and the history of the beam, will determine what that distribution looks like, but you can "easily" be able to send signals with a very well-determined average frequency (let's say 30 digits), but where the variance in each individual instrument, even without introducing any error in the measuring process is far less exact.
Some systems don't even use XP, but rather a quite XP-like version of XP Embedded.