"Million dollar mail not followed up with phone call is fool's gold." Seriously, though, what important correspondence isn't followed up on in one manner or another? It's like other situations where short-sighted management looks at e-mail as foolproof, ironclad, mission-critical, real-time communication.
The recent times I've been in hospitals I've checked to see what they're running. The two major hospitals near me don't appear to have the real "life and death" equipment running Windows. I'm talking about vital stat monitors and other surgical recovery equipment. I've seen certain medical records being accessed on Windows-based systems. Perhaps then there could be issues with lost information as to current prescription or observational data being lost or corrupted.
But even then wouldn't such systems be running separate from the public Internet? If so, on top of that wouldn't they be secure enough so that executives with their laptops can't just plug in and hose things up? With even entry-level expertise IT staff should be able to separate these boxes onto some sort of a VLAN that would secure them by default. What are the IT folks' take on this who are working front line in the medical arena?
It sounds as if nearly every other news story I read regarding Sun Microsystems make the picture for them look progressively more grim. They have been trying to realign themselves and have changed their strategies somewhat but is it too late?
I recall years ago working with Sun/Solaris systems alongside i86/Linux systems. I was amazed at the hardware costs associated with servicing some of the Sun product line. The prices were outrageous. Something like 5 to 10 times what the i86 servers were demanding. What's the point? I even recall when Sun started deploying supposedly lower-end, lower-cost i86 hardware. The costs were still 3 times what I was expecting.
Can't say I'm sorry to see them hitting hard times. Java will be the only legacy they have left over looking back at this 3-5 years from now.
I believe you are correct. When I try to pull in a wireless signal around this frequency the microwave in my kitchen drops the signal strength down at least 10% or so when it's cooking something.
Good point. This has certainly happened in the past. The XML standards is one counterexample but there aren't that many of them. I can only hope that they won't "extend" a broken supposed standard and wind up falling short of the mark.
I guess this just points out the Darwinism that comes with healthy competition. I know that there are still some regulatory matters which can affect regional availability, tariffs, etc. but competition is rarely a bad thing.
Think back about 10-15 years ago. If someone would have told me that AT&T would be getting out of this segment I wouldn't laughed for awhile...
The 840315 HTML Help vulnerability is supposedly deemed Critical for Windows 98 and ME systems. But checking their downloads there isn't a patch released yet. Although these products are still covered under product support for critical issues. Reading the fine print there's no guarantee that patches for these systems will be released en masse along with the other OS versions.
By any chance do you have a newer Dell? I know newer ones came bundled with AOL software already installed on them with this URL in the Trusted Sites list.
That's the way I see it. If my company has certain IE-only external apps that force our hand then I can lock down the ActiveX and Active Scripting registry settings to prevent the typical cross-site and cross-zone exploits that have been making their rounds for awhile now.
I realize this doesn't mean much to Joe Sixpack or Grandma Ethel since the fixes might not be as easy as an automatic download. But checking Microsoft's website I have seen simple instructions showing folks how to lock things down. Microsoft's flawed attempt at seamless integration between their OS and apps left huge security holes. But at least there are ways to lock them down. As for whether the barn door has been closed too late for some is another story I guess:-(
Checking the WindowsUpdate site I see that finally the ADODB.Stream hole has been patched (see http://www.microsoft.com/downloads/details.aspx?Fa milyID=4d056748-c538-46f6-b7c8-2fbfd0d237e3&displa ylang=en for details). This was a major flaw that had been present all along through the numerous IE exploits. Combining this with some hardened security zone settings that disable Active Scripting and IE shouldn't be the total joke that everyone is making it out to be. It's still a lot patching and modifying compared to recent releases of Mozilla-type apps but...
With the right Ccller ID tools (or if you ask the telemarkter whom they are calling on behalf of) you can still complain against the true source of the infraction.
Just like tracing back spam. I think the companies whose goods and services are being pushed should be the ones ultimately boycotted/protested/fined.
SBC (Ameritech) is where I am too. They provide the last mile for some other carriers and their network is stretched pretty thin here as well. I know when they were bringing in a private DS1 connecting two of our sites they tried to cross connect it using an available HDSL2 circuit. Just a single pair of copper wires just like the POTS lines going into residential homes. Due to bridge taps and other issues they had to give up on that and use more sophisticated transport.
Wireless phone carrier spend billions improving their cellular networks. I know that the company I used to work for (PrimeCo, now part of Verizon Wireless) spent boatloads on replacing Motorola MSC's with Lucent MSC's. Plus look at all of the 2.5G, 3G, etc. cellular data infrastructure upgrades competing out there. The old copper pairs are a beat street.
between cable and DSL. One is shared coaxial bandwidth while the other consists of dedicated copper pairs. The availability of one or the other doesn't have to be interdependent. After all there are places that have telephones but no cable out in the boonies, right??
Although on principle I agree regarding trusting telco. They can be like the Enron traders, shuffling around things and playing the shell game to the company's own benefit, largely discounting any hardships endured by the customers.
If it's that mission critical of an application I wouldn't recommend DSL or cable anyway. A (fractional?) T1 or something for dedicated Internet access would be a better option.
As a business customer of a competing telco outfit we had issues a few years ago with their provided DSL uptime too. But unfortunately there wasn't an official Service Level Agreement in place. All I could so was complain and issue status updates to our endusers.
Back at a prior job we had an SLA in place with another carrier. But it paid pennies on the dollar in terms of compenstation for downtime. Just some meaningless service credits.
Here's an example. You state that your client is down up to 45 minutes per week. Basing a week on 10,080 minutes that means that the DSL circuit has > 99.5% uptime. If your client were to be compensated for the downtime as a credit on a typical monthly bill that would mean for a $200 monthly bill they would see a whopping $1 credit! And this is only if the carrier guaranteed that Unavailable Seconds (UAS) as measured by teclo couldn't exceed 0.5% in a typical reporting period (typically a range between 1 hour to 24 hours).
Slashdot Mirror
Mistake.
Does this bridge filter traffic as well?
802.11i should be the shiznit. It's not officially adopted yet on production equipment I'm aware of though.
The recent times I've been in hospitals I've checked to see what they're running. The two major hospitals near me don't appear to have the real "life and death" equipment running Windows. I'm talking about vital stat monitors and other surgical recovery equipment. I've seen certain medical records being accessed on Windows-based systems. Perhaps then there could be issues with lost information as to current prescription or observational data being lost or corrupted.
But even then wouldn't such systems be running separate from the public Internet? If so, on top of that wouldn't they be secure enough so that executives with their laptops can't just plug in and hose things up? With even entry-level expertise IT staff should be able to separate these boxes onto some sort of a VLAN that would secure them by default. What are the IT folks' take on this who are working front line in the medical arena?
It sounds as if nearly every other news story I read regarding Sun Microsystems make the picture for them look progressively more grim. They have been trying to realign themselves and have changed their strategies somewhat but is it too late?
I recall years ago working with Sun/Solaris systems alongside i86/Linux systems. I was amazed at the hardware costs associated with servicing some of the Sun product line. The prices were outrageous. Something like 5 to 10 times what the i86 servers were demanding. What's the point? I even recall when Sun started deploying supposedly lower-end, lower-cost i86 hardware. The costs were still 3 times what I was expecting.
Can't say I'm sorry to see them hitting hard times. Java will be the only legacy they have left over looking back at this 3-5 years from now.
Detected. Probably. But how far after the fact? Even a matter of a few weeks of escaping into mainstream usage could prove dangerous.
Does that come before or after your TPS reports?
I believe you are correct. When I try to pull in a wireless signal around this frequency the microwave in my kitchen drops the signal strength down at least 10% or so when it's cooking something.
XML is a data definition language. XHTML is not.
Good point. This has certainly happened in the past. The XML standards is one counterexample but there aren't that many of them. I can only hope that they won't "extend" a broken supposed standard and wind up falling short of the mark.
To me this sounds like a positive step. I'm just wondering what the Microsoft haters will post about it to make it sound like a bad thing...
An uncut 182 carats is roughly the size of your fist. Not too huge really...
Think back about 10-15 years ago. If someone would have told me that AT&T would be getting out of this segment I wouldn't laughed for awhile...
Does that water there still circulate in a counterclockwise direction when going down the drain? What's up with that anyway?
Good guess though...
Hmmm...
By any chance do you have a newer Dell? I know newer ones came bundled with AOL software already installed on them with this URL in the Trusted Sites list.
I realize this doesn't mean much to Joe Sixpack or Grandma Ethel since the fixes might not be as easy as an automatic download. But checking Microsoft's website I have seen simple instructions showing folks how to lock things down. Microsoft's flawed attempt at seamless integration between their OS and apps left huge security holes. But at least there are ways to lock them down. As for whether the barn door has been closed too late for some is another story I guess :-(
Checking the WindowsUpdate site I see that finally the ADODB.Stream hole has been patched (see http://www.microsoft.com/downloads/details.aspx?Fa milyID=4d056748-c538-46f6-b7c8-2fbfd0d237e3&displa ylang=en for details). This was a major flaw that had been present all along through the numerous IE exploits. Combining this with some hardened security zone settings that disable Active Scripting and IE shouldn't be the total joke that everyone is making it out to be. It's still a lot patching and modifying compared to recent releases of Mozilla-type apps but...
Just check the site listed in the article. Secunia.Com lists them month by month for your enjoyment.
With the right Ccller ID tools (or if you ask the telemarkter whom they are calling on behalf of) you can still complain against the true source of the infraction.
Just like tracing back spam. I think the companies whose goods and services are being pushed should be the ones ultimately boycotted/protested/fined.
SBC (Ameritech) is where I am too. They provide the last mile for some other carriers and their network is stretched pretty thin here as well. I know when they were bringing in a private DS1 connecting two of our sites they tried to cross connect it using an available HDSL2 circuit. Just a single pair of copper wires just like the POTS lines going into residential homes. Due to bridge taps and other issues they had to give up on that and use more sophisticated transport. Wireless phone carrier spend billions improving their cellular networks. I know that the company I used to work for (PrimeCo, now part of Verizon Wireless) spent boatloads on replacing Motorola MSC's with Lucent MSC's. Plus look at all of the 2.5G, 3G, etc. cellular data infrastructure upgrades competing out there. The old copper pairs are a beat street.
between cable and DSL. One is shared coaxial bandwidth while the other consists of dedicated copper pairs. The availability of one or the other doesn't have to be interdependent. After all there are places that have telephones but no cable out in the boonies, right??
Although on principle I agree regarding trusting telco. They can be like the Enron traders, shuffling around things and playing the shell game to the company's own benefit, largely discounting any hardships endured by the customers.
If it's that mission critical of an application I wouldn't recommend DSL or cable anyway. A (fractional?) T1 or something for dedicated Internet access would be a better option.
As a business customer of a competing telco outfit we had issues a few years ago with their provided DSL uptime too. But unfortunately there wasn't an official Service Level Agreement in place. All I could so was complain and issue status updates to our endusers.
Back at a prior job we had an SLA in place with another carrier. But it paid pennies on the dollar in terms of compenstation for downtime. Just some meaningless service credits.
Here's an example. You state that your client is down up to 45 minutes per week. Basing a week on 10,080 minutes that means that the DSL circuit has > 99.5% uptime. If your client were to be compensated for the downtime as a credit on a typical monthly bill that would mean for a $200 monthly bill they would see a whopping $1 credit! And this is only if the carrier guaranteed that Unavailable Seconds (UAS) as measured by teclo couldn't exceed 0.5% in a typical reporting period (typically a range between 1 hour to 24 hours).