So much built in advertising for so little gain vs the alternatives. But so long as they're bundling Firefox with Real downloads, and not the other way around, I suppose there's no problem with that, unless Mozilla is paying them.
If most of that isn't changing, you can archive it to removable hard disks. Get two removable hard disks, keep one at home, the other in a secure place, and swap them from time to time. Keep your recent (since last swap) work in its own folder, and back only that folder up online.
Or you can set up a backup server on the other side of your house and hope both servers aren't taken out by the same disaster.
Our company has about 200gb of important, frequently updated data that we need backed up nightly. $260 a month for peace of mind for a business sounds pretty cheap.
I've checked out probably a dozen backup services, and most were around 5x as expensive. These guys for example, charge $65/month for only 10gb. Another called me to give a quote and when I told them that another company quoted $300/month (before I found rsync.net), they laughed a bit and said they couldn't go anywhere near that cheap. Granted, this was probably 7 months ago that I was scoping out our options, so prices may have gone down a bit.
Taking a quick look on Froogle, the tape drive alone will cost about $900, and 80gb tapes cost about $70 each. You can buy hard drives for less, and have an employee take a hard drive home each week. That's not cheap by any measure. Tapes aren't very reliable if you reuse them. They'll appear to backup ok, but most will be bad after several uses. If you have a terabyte to back up, you're going to need about a dozen tapes a night, no matter how little has changed. Tapes are old, expensive, dying technology. The only way tape backups can be cheaper is if you accept extreme unreliability, or you limit your backup frequency to weekly or monthly, and you already own a tape drive. Losing a week of important data will cost most businesses more than they'll ever spend on backups.
With nightly rsync backups, you reduce hard disk activity by only copying parts of files that change, and you can restore files selectively. I have about 300gb on a file server that I can keep in sync with a backup server for only about 150-200mb of nightly traffic, with occasional spikes. I can restore files that were deleted a year ago.
They use rsync over ssh: http://www.rsync.net/ Base rate: $1.80/gb/month Volume discounts: 25-49GB - 10% Off 50-99GB - 20% Off 100-199GB - 30% Off 200-399GB - 40% Off 400-999GB - 50% Off 1TB+ - 60% Off
You get supposedly unlimited storage, and pay for only what you use. I haven't actually tried them though.
I think if you own a valid product key the exact same edition that you pirated, you can download a product key changer from MS that'll let you substitute your valid product key in place of the pirated one. They offer it in the WGA support forums to people who's systems came with XP, but later reinstalled the same exact edition with a pirated key. http://go.microsoft.com/fwlink/?LinkId=50346&clcid =0x409
They send the diagnostics tool to everyone who reports problems. I was getting the notifications, and their tool reported my copy as "Genuine", proving that their WGA notifications update was buggy and full of crap. It still pisses me off to this day, but their free online support was pretty friendly and responsive.
A good thing about the diagnostics tool is that if it does report that it's not genuine, it'll tell you exactly why. For most of the non-genuine copies it reports "Blocked VLK", VLK meaning volume license key. If I just grab one partial key at random (2X6T7-D7R6Q-7GRQJ) from Microsoft's support forums, and search for it on Google, I get 46 results, all of them pages containing lists of pirated volume license keys.
The 2nd most common failure code, "Invalid Product Key", is a lot harder to support with evidence, but is also lot rarer (only 6 Google matches vs 76 for "Genuine Validation Status: Blocked VLK").
Still, nothing's proven. Paul didn't give us enough information to know how it was detected as non-genuine or why he got it from. Even if he did, we could only take his word for it.
I was bitten too. Got it fixed pretty quickly, but I'm still a bit angry about it. Try reinstalling the WGA notifications update, revalidating, and rebooting. Seems to work for a lot of people. If it doesn't, download and install the MGA diagnostics tool and see if it reports "Genuine". If it does, and you're getting the notifications, post the output to Microsoft's WGA forum. In my case I just had to revalidate and reboot.
I accepted his initial report because it was perfectly consistent with my own experience. I have a system at work that has always validated as genuine. After I installed the update, it displayed the annoying and accusational WGA counterfeit notifications. Re-validating on Microsoft's website and rebooting a couple times made the notifications go away, and their MGA diagnostics tool confirms that it's genuine. Microsoft's WGA notifications update was buggy, and erred on the side of accusing legitimate users (at least myself) of piracy, despite that it was correct in Paul Thurrott's case.
Roughly same dimensions. 8 systems. 3 24 port switches. And a security system with a monitor that can't be turned off independently.
I've mentioned several times that it'll all go to hell when the small single room household A/C dies. They won't even approve my offsite backup plans. There is a backup server, but it too is in the server closet. They even had a heating vent going into the server closet until I convinced them to seal it this last winter, after it reached the 90's during the coldest time of year.
The thing gives me nightmares. I imagine the A/C failing, the servers dying, and the room catching fire and taking the building with it.
If Microsoft has a corporate search product, I've never heard of it until now. Their past attempts at desktop search haven't exactly been spectacular either.
How do you calibrate a new atomic clock, if you have nothing more accurate to compare it against? And if we have clocks that won't lose or gain a second in 70 million years, why do we need to develop one that won't lose or gain a second in 400 million years?
Not far from the truth at all. In their mind, every reported vulnerability serves to give customers an impression that IE is riddled with security problems. No matter that the damage is already done. If they looked at what's on a typical home Windows system, they'd know that already.
"We believe the commonly accepted practice of reporting vulnerabilities directly to a vendor serves everyone's best interests."
From the looks of it, most if not all of those were reported months before they were published.
Give a vendor 90 days. If they fix it, never, ever release the details of how to exploit the vulnerability, as a reward and to help users who are slow to update. But if they willfully choose not to fix it, release the exploit to educate their userbase, and to help them to reevaluate their dangerous security policy.
If you push off perpendicular to the station's orbit and tangent to the earth, you'll come very close to hitting it a half revolution later. If you push off in another direction, you'll still approach it on the other side, but not come nearly as close.
If you push off from another object in orbit, and if you and the object are still going roughly the same speed, with roughly the same orbital period, but in different directions, you can expect to meet up with that object again on the other side of the earth. The ISS orbits about once every 92 minutes.
The act of launching into space in a gigantic 22 year old space shuttle protected by ceramic tiles sounds pretty risky on its own.
Their suits hold enough oxygen to last up to 9 hours. If you slowly push away from the space station, you won't keep moving away from it in a straight line, because you and the space station are both orbiting the earth. In 46 minutes or so you may find yourself passing by it again.
So much built in advertising for so little gain vs the alternatives. But so long as they're bundling Firefox with Real downloads, and not the other way around, I suppose there's no problem with that, unless Mozilla is paying them.
If most of that isn't changing, you can archive it to removable hard disks. Get two removable hard disks, keep one at home, the other in a secure place, and swap them from time to time. Keep your recent (since last swap) work in its own folder, and back only that folder up online.
Or you can set up a backup server on the other side of your house and hope both servers aren't taken out by the same disaster.
Our company has about 200gb of important, frequently updated data that we need backed up nightly. $260 a month for peace of mind for a business sounds pretty cheap.
I've checked out probably a dozen backup services, and most were around 5x as expensive. These guys for example, charge $65/month for only 10gb. Another called me to give a quote and when I told them that another company quoted $300/month (before I found rsync.net), they laughed a bit and said they couldn't go anywhere near that cheap. Granted, this was probably 7 months ago that I was scoping out our options, so prices may have gone down a bit.
Taking a quick look on Froogle, the tape drive alone will cost about $900, and 80gb tapes cost about $70 each. You can buy hard drives for less, and have an employee take a hard drive home each week. That's not cheap by any measure. Tapes aren't very reliable if you reuse them. They'll appear to backup ok, but most will be bad after several uses. If you have a terabyte to back up, you're going to need about a dozen tapes a night, no matter how little has changed. Tapes are old, expensive, dying technology. The only way tape backups can be cheaper is if you accept extreme unreliability, or you limit your backup frequency to weekly or monthly, and you already own a tape drive. Losing a week of important data will cost most businesses more than they'll ever spend on backups.
With nightly rsync backups, you reduce hard disk activity by only copying parts of files that change, and you can restore files selectively. I have about 300gb on a file server that I can keep in sync with a backup server for only about 150-200mb of nightly traffic, with occasional spikes. I can restore files that were deleted a year ago.
They use rsync over ssh:
http://www.rsync.net/
Base rate: $1.80/gb/month
Volume discounts:
25-49GB - 10% Off
50-99GB - 20% Off
100-199GB - 30% Off
200-399GB - 40% Off
400-999GB - 50% Off
1TB+ - 60% Off
You get supposedly unlimited storage, and pay for only what you use.
I haven't actually tried them though.
I think if you own a valid product key the exact same edition that you pirated, you can download a product key changer from MS that'll let you substitute your valid product key in place of the pirated one. They offer it in the WGA support forums to people who's systems came with XP, but later reinstalled the same exact edition with a pirated key. http://go.microsoft.com/fwlink/?LinkId=50346&clcid =0x409
They send the diagnostics tool to everyone who reports problems. I was getting the notifications, and their tool reported my copy as "Genuine", proving that their WGA notifications update was buggy and full of crap. It still pisses me off to this day, but their free online support was pretty friendly and responsive.
A good thing about the diagnostics tool is that if it does report that it's not genuine, it'll tell you exactly why. For most of the non-genuine copies it reports "Blocked VLK", VLK meaning volume license key. If I just grab one partial key at random (2X6T7-D7R6Q-7GRQJ) from Microsoft's support forums, and search for it on Google, I get 46 results, all of them pages containing lists of pirated volume license keys.
The 2nd most common failure code, "Invalid Product Key", is a lot harder to support with evidence, but is also lot rarer (only 6 Google matches vs 76 for "Genuine Validation Status: Blocked VLK").
Still, nothing's proven. Paul didn't give us enough information to know how it was detected as non-genuine or why he got it from. Even if he did, we could only take his word for it.
I was bitten too. Got it fixed pretty quickly, but I'm still a bit angry about it. Try reinstalling the WGA notifications update, revalidating, and rebooting. Seems to work for a lot of people. If it doesn't, download and install the MGA diagnostics tool and see if it reports "Genuine". If it does, and you're getting the notifications, post the output to Microsoft's WGA forum. In my case I just had to revalidate and reboot.
I accepted his initial report because it was perfectly consistent with my own experience. I have a system at work that has always validated as genuine. After I installed the update, it displayed the annoying and accusational WGA counterfeit notifications. Re-validating on Microsoft's website and rebooting a couple times made the notifications go away, and their MGA diagnostics tool confirms that it's genuine. Microsoft's WGA notifications update was buggy, and erred on the side of accusing legitimate users (at least myself) of piracy, despite that it was correct in Paul Thurrott's case.
Roughly same dimensions. 8 systems. 3 24 port switches. And a security system with a monitor that can't be turned off independently.
I've mentioned several times that it'll all go to hell when the small single room household A/C dies. They won't even approve my offsite backup plans. There is a backup server, but it too is in the server closet. They even had a heating vent going into the server closet until I convinced them to seal it this last winter, after it reached the 90's during the coldest time of year.
The thing gives me nightmares. I imagine the A/C failing, the servers dying, and the room catching fire and taking the building with it.
Most of the blocked users I see complaining in Microsoft's WGA forum are using volume license keys.
I used to have to make sure all my pages worked in Netscape 4. Some pages just had to be written twice. By comparison, supporting IE is a breeze.
https://bugzilla.mozilla.org/show_bug.cgi?id=9458
Voted.
He had 500 bytes of html formatting tags and attributes in every , and that's the way he liked it.
The "Features at a Glance" table is very inaccurate with respect to Opera. For one, Opera has very good theme support.
And the author mixes up kb and mb on another page.
If Microsoft has a corporate search product, I've never heard of it until now. Their past attempts at desktop search haven't exactly been spectacular either.
If the error is random, without skew, it may be more like 8.4 seconds vs 3.5 seconds.
How do you calibrate a new atomic clock, if you have nothing more accurate to compare it against? And if we have clocks that won't lose or gain a second in 70 million years, why do we need to develop one that won't lose or gain a second in 400 million years?
Not far from the truth at all. In their mind, every reported vulnerability serves to give customers an impression that IE is riddled with security problems. No matter that the damage is already done. If they looked at what's on a typical home Windows system, they'd know that already.
"We believe the commonly accepted practice of reporting vulnerabilities directly to a vendor serves everyone's best interests."
From the looks of it, most if not all of those were reported months before they were published.
Give a vendor 90 days. If they fix it, never, ever release the details of how to exploit the vulnerability, as a reward and to help users who are slow to update. But if they willfully choose not to fix it, release the exploit to educate their userbase, and to help them to reevaluate their dangerous security policy.
NO MATTER WHAT DIRECTION YOU PUSH.
If you push off perpendicular to the station's orbit and tangent to the earth, you'll come very close to hitting it a half revolution later. If you push off in another direction, you'll still approach it on the other side, but not come nearly as close.
I never said opposite direction. That would be stupid.
If you push off from another object in orbit, and if you and the object are still going roughly the same speed, with roughly the same orbital period, but in different directions, you can expect to meet up with that object again on the other side of the earth. The ISS orbits about once every 92 minutes.
The act of launching into space in a gigantic 22 year old space shuttle protected by ceramic tiles sounds pretty risky on its own.
Their suits hold enough oxygen to last up to 9 hours. If you slowly push away from the space station, you won't keep moving away from it in a straight line, because you and the space station are both orbiting the earth. In 46 minutes or so you may find yourself passing by it again.
Could this affect the release of Duke Nukem Forever?