Do you get decent quality using wireless VOIP? I use a wireless D-Link 660W card in my Pocket PC handheld and with SJPhone the quality is pretty poor. That's just within my LAN holding conversations with other wired or wireless nodes. The delays and breaks were unbearable. And my LAN utilization only averages between 1 and 3 percent.
True. I know their recent KB835732 could result in a Windows 2000 BSOD immediately after rebooting. But the next reboot would be fine. That was the last _patch_ I've seen result in a notable bootup bug. The last really major bug I recall from their _patches_ involved Windows NT 4.0 Service Pack 6. This basically broke TCP/IP and resulted in their rushed release of SP6a. I really loved that in my server environment. Made for a lot of repetitive phone calls coming in!
As for _major client upgrades_ I can't recall A Windows one that wiped out the boot partition tables. I know some hardware driver compatibility issues cropped up between versions (e.g. - 3.1 to 95, 2000 to XP). Those were certainly annoying.
To me hosing up a boot partition is a lot more serious than having to hunt down updated hardware drivers, though. Updating drivers and totally reinstalling an OS are two different things entirely.
I use both Linux and Windows. The former since about 1997 and the latter since about 1991. There are definitely pros and cons with either OS. But I am truly amazed at the tolerance and patience Linux enthusiasts have with some of the imperfections in the OS distributions. It must only go to show how much they abhor Microsoft, their corporate philosophy, and their product line.
This isn't meant to be a troll, but can you imagine the outrage Windows users (and Linux zealots alike) would have if simply upgrading Windows wiped out the partition tables and resulted in an unbootable system? This is a pretty notable flaw for sure!
Grading freely-written essays and structured computer programming code is two separate things *to a degree.* And India isn't the first to do the latter. Indiana is, however, according to the article.
In high school I lived the next town over from Tom Gordon. Tom (Flash) Gordon is still in the big leagues. Here's his bio. He threw a perfect game of strikeouts against our high school. Folks were bragging about even fouling a ball off on him! It was amazing to see someone that young throw like that.
Have you driven by one lately? There are a surprising amount of satellite dishes at some of them. Even before all of the DirecTV and Dish Network varieties there were those behemoth dishes sitting next to the cable spool/picnic tables.
I can empathize with the author's issues and gripes, but a bit of enduser education could have prevented a decent amount of them. Here's a good document on how to survive your first day with Windows XP.
The author's slanted raving is over the top. I could just as easily read about some Linux newbie's nightmare experience trying to get all of his hardware to work or how they had to rebuild the kernel after applying some new module to their system.
My main gripe with how things are is that all new PC's should be delivered fully patched as of their configuration date. And since Microsoft has switched to their license subscription model they should ship out CD's to all licensed customers with all rollup security packs available. Just like a TechNet subscription operates for previewing beta products. I don't mean a user calls into Microsoft to request a CD. It's their place to send them out. Just like an auto company would mail out recall notices.
Because this is the same company that sold hardware comprising the backbone of the Internet but was full of H.323, BGP, SNMP, and TCP flaws. Such flawed implementations led to dozens of different exploits being circulated. But they were able to stay ahead of the 8 ball and release patches JIT every time around.
I was looking around on the Internet yesterday and saw a few American companies maunfacturing new electric vehicles. Not hybrids, but total electrics. Prices that I saw started at around $10-11K for what I would consider a vehicle that could keep up on the highways and byways.
Any of y'all out there have any experiences with such vehicles?
Your ISP apparently doesn't so its part to stop illicit bulk UCE. That's why the entire block of public IP's have been blacklisted. At my place of business we ran into the same situation.
The best advice isn't to call each and every receiving party's IT department to get whitelisted. Nor is the best advice to moan about how some blacklists "suck and that's that." The best advice is to change to an ISP that doesn't support spammers. That is taking an active role in sending a message to the ISP's that allow this sort of thing to happen.
The last statement I personally am making about this story is that from a business standpoint they are putting all of their eggs in one basket. Clients will purchase insurance to alleviate legal fees of being taken to court over Open Source Software usage. If Bruce and the gang on the board of this company thought that SCO would take smaller companies to court en masse then they would be losing their shirts in selling this insurance and therefore it would be a bad business move.
If Bruce "is a pretty smart guy" then I can't see him risking losing his shirt. It would be like a large hurricane like Andrew back in the early 1990's. If it was forecasted to strike South Florida in short order and a start-up company started selling homeowners insurance for just the specific coverage of storm damage and that's it I would think that it would be a losing proposition from a business point of view. Make sense??
That's a PR line. Lawspeak. It indeed is capitalizing on the FUD since any educated person in the technology industry knows that the SCO case doesn't have a leg to stand on. The only potential clients I can see are those who blindly fall for the FUD that SCO has perpetuated.
Just like those consulting companies that were around in 1999 to ensure that no Y2K disaster was going to hit clients. I know some companies would go into people's homes and ensure they were Y2K-compliant. What a freakin' joke! Remember folks stockpiling food and readying themselves for living in bomb shelters? Of course it's an extreme comparison, but the basis is the same. Capitalizing on more ignorant folks' fears.
To me it sounds as if the group Bruce is on the board of is trying to exploit or otherwise captalize on the FUD of SCO actually winning a lawsuit. Which probably won't happen. Kind of reminds me of start-up companies which were around for all of the Y2K madness back in 1999. The FUD helped fuel interest, which really exaggerated the real deal.
Maybe Bruce should start selling underwear to Iraqi prisoners...
Just because it's the #1 OS for mostly-clueless home users. There are security safeguards that *could* prevent spyware from being installed. User-level security has been in place for the NT/2000/XP branch of Windows since Windows NT 3.1 up through Windows XP Professional. This should be equivalent to not running regular Linux sessions logged in as root/superuser. If Windows sessions started out logged on as non-administrator users then spyware couldn't install itself. That plain, that simple.
Reading this makes it obvious why folks with newer PC's constantly complain about their systems running slowly. With dozens of active threads running in the background it's no wonder. I read somewhere the average home user has 20+ active adware/spyware/malware instances on their PC. Amazing.
If you are talking about a corporate setup with some sort of software standardization you could check the HKLM or HKCU Software-->Microsoft-->Windows-->CurrentVersion--> Run key for values present. That's where a lot of malware/adware/spyware hides. I do this through using KixTart as part of the network logon script.
Norton Antivirus 5.0, unfortunately. NAV 2000 and above slowed down other third party apps *significantly* when run in AutoProtect mode. Our company still runs a legacy DOS app that has tons of file handles. Recent NAV versions would drag things down to a crawl when running in the background.
As to why we are still running a legacy DOS app, that's another story entirely:-(
Sure they do. Every week or so I have to issue a kill command to end the VNC Server service that run on my NT 4.0 Server. "kill -f winvnc.exe. Works fine. Services run as processes that can be seen under the Task Manager, so what's the difference? If they didn't I'd be in deep doo doo because the VNC Server service locks up and can't be stopped or started under the Services applet. And I don't like rebooting my mail server every week to fix it.
True. It is a bit misleading when AV vendors posture that their solution is the pinnacle of protection. Theirs is usually the next to last line of defense. The final line is the enduser him/herself.
What makes it tough about the AV angle is that AV definitions have to come out extremely quickly. Look at all the variants of Netsky and Bagle. Every day several variants would be announced. The enduser would have to update their AV definitions on a daily basis at the very worst in order to keep up. Then typical scan engines require a system reboot in order for the updated defs to take effect.
For my corporate user base that means that really the following day these updated definitions would really be active, since I hate to force reboots. I update the AV definitions as part of the network logon script and don't want endusers to have to reboot immediately after logging in. I still run autoupdated AV software on the mail server so hopefully all of these measures is enough.
Years ago system stability and performance were the critical concerns of working with PC's. I can't recall all of the failed hard drives and unstable software I had to deal with. Now all of this has been replaced with security concerns. At least it means job security. **sigh**
Any AV software is vulnerable to being "disabled." Newer worms and virus exploits simply kill these AV processes. For example, the KILL.EXE command was included with the Windows NT 4.0 Resource Kit and from that version on it works like a champ. Simply issue that command with the -f switch to force the processes to terminate. Gives you an idea of what the malware does.
There typically are dozens of EXE process names that are terminated so that the AV software is inactive from that point on during the same session when a host is infected. How pray tell can a fix be issued for this from an AV vendor?
This simply points to the fact that the initial line of defense is a hardware-based Internet firewall and an OS that has all of the latest security patches. By the time that you have to worry about AV software definitions you are already past that initial line of defense.
Actually that is the history behind why that http server was called what it is. It was originally intended to be a series of patches for the httpd process. Ironic, eh?
Slashdot Mirror
Do you get decent quality using wireless VOIP? I use a wireless D-Link 660W card in my Pocket PC handheld and with SJPhone the quality is pretty poor. That's just within my LAN holding conversations with other wired or wireless nodes. The delays and breaks were unbearable. And my LAN utilization only averages between 1 and 3 percent.
You mean blacklisting? Otherwise the negative gravitational pull would tear them apart.
As for _major client upgrades_ I can't recall A Windows one that wiped out the boot partition tables. I know some hardware driver compatibility issues cropped up between versions (e.g. - 3.1 to 95, 2000 to XP). Those were certainly annoying.
To me hosing up a boot partition is a lot more serious than having to hunt down updated hardware drivers, though. Updating drivers and totally reinstalling an OS are two different things entirely.
This isn't meant to be a troll, but can you imagine the outrage Windows users (and Linux zealots alike) would have if simply upgrading Windows wiped out the partition tables and resulted in an unbootable system? This is a pretty notable flaw for sure!
Actually I meant the former, not the latter. Everyone makes mistakes I guess :-)
Grading freely-written essays and structured computer programming code is two separate things *to a degree.* And India isn't the first to do the latter. Indiana is, however, according to the article.
In high school I lived the next town over from Tom Gordon. Tom (Flash) Gordon is still in the big leagues. Here's his bio. He threw a perfect game of strikeouts against our high school. Folks were bragging about even fouling a ball off on him! It was amazing to see someone that young throw like that.
Have you driven by one lately? There are a surprising amount of satellite dishes at some of them. Even before all of the DirecTV and Dish Network varieties there were those behemoth dishes sitting next to the cable spool/picnic tables.
The author's slanted raving is over the top. I could just as easily read about some Linux newbie's nightmare experience trying to get all of his hardware to work or how they had to rebuild the kernel after applying some new module to their system.
My main gripe with how things are is that all new PC's should be delivered fully patched as of their configuration date. And since Microsoft has switched to their license subscription model they should ship out CD's to all licensed customers with all rollup security packs available. Just like a TechNet subscription operates for previewing beta products. I don't mean a user calls into Microsoft to request a CD. It's their place to send them out. Just like an auto company would mail out recall notices.
Because this is the same company that sold hardware comprising the backbone of the Internet but was full of H.323, BGP, SNMP, and TCP flaws. Such flawed implementations led to dozens of different exploits being circulated. But they were able to stay ahead of the 8 ball and release patches JIT every time around.
"Spill the wine, dig that girl...Spill the wine, dig that girl..." I know it's OT, but the song is stuck in my head now.
I was looking around on the Internet yesterday and saw a few American companies maunfacturing new electric vehicles. Not hybrids, but total electrics. Prices that I saw started at around $10-11K for what I would consider a vehicle that could keep up on the highways and byways.
Any of y'all out there have any experiences with such vehicles?
Your ISP apparently doesn't so its part to stop illicit bulk UCE. That's why the entire block of public IP's have been blacklisted. At my place of business we ran into the same situation.
The best advice isn't to call each and every receiving party's IT department to get whitelisted. Nor is the best advice to moan about how some blacklists "suck and that's that." The best advice is to change to an ISP that doesn't support spammers. That is taking an active role in sending a message to the ISP's that allow this sort of thing to happen.
Isn't that what SuSE's OpenExchange Server does? I thought it was a Linux server acting like an Exchange box.
The last statement I personally am making about this story is that from a business standpoint they are putting all of their eggs in one basket. Clients will purchase insurance to alleviate legal fees of being taken to court over Open Source Software usage. If Bruce and the gang on the board of this company thought that SCO would take smaller companies to court en masse then they would be losing their shirts in selling this insurance and therefore it would be a bad business move.
If Bruce "is a pretty smart guy" then I can't see him risking losing his shirt. It would be like a large hurricane like Andrew back in the early 1990's. If it was forecasted to strike South Florida in short order and a start-up company started selling homeowners insurance for just the specific coverage of storm damage and that's it I would think that it would be a losing proposition from a business point of view. Make sense??
That's a PR line. Lawspeak. It indeed is capitalizing on the FUD since any educated person in the technology industry knows that the SCO case doesn't have a leg to stand on. The only potential clients I can see are those who blindly fall for the FUD that SCO has perpetuated.
Just like those consulting companies that were around in 1999 to ensure that no Y2K disaster was going to hit clients. I know some companies would go into people's homes and ensure they were Y2K-compliant. What a freakin' joke! Remember folks stockpiling food and readying themselves for living in bomb shelters? Of course it's an extreme comparison, but the basis is the same. Capitalizing on more ignorant folks' fears.
To me it sounds as if the group Bruce is on the board of is trying to exploit or otherwise captalize on the FUD of SCO actually winning a lawsuit. Which probably won't happen. Kind of reminds me of start-up companies which were around for all of the Y2K madness back in 1999. The FUD helped fuel interest, which really exaggerated the real deal.
Maybe Bruce should start selling underwear to Iraqi prisoners...
Just because it's the #1 OS for mostly-clueless home users. There are security safeguards that *could* prevent spyware from being installed. User-level security has been in place for the NT/2000/XP branch of Windows since Windows NT 3.1 up through Windows XP Professional. This should be equivalent to not running regular Linux sessions logged in as root/superuser. If Windows sessions started out logged on as non-administrator users then spyware couldn't install itself. That plain, that simple.
Reading this makes it obvious why folks with newer PC's constantly complain about their systems running slowly. With dozens of active threads running in the background it's no wonder. I read somewhere the average home user has 20+ active adware/spyware/malware instances on their PC. Amazing.
If you are talking about a corporate setup with some sort of software standardization you could check the HKLM or HKCU Software-->Microsoft-->Windows-->CurrentVersion--> Run key for values present. That's where a lot of malware/adware/spyware hides. I do this through using KixTart as part of the network logon script.
As to why we are still running a legacy DOS app, that's another story entirely :-(
Sure they do. Every week or so I have to issue a kill command to end the VNC Server service that run on my NT 4.0 Server. "kill -f winvnc.exe. Works fine. Services run as processes that can be seen under the Task Manager, so what's the difference? If they didn't I'd be in deep doo doo because the VNC Server service locks up and can't be stopped or started under the Services applet. And I don't like rebooting my mail server every week to fix it.
True. It is a bit misleading when AV vendors posture that their solution is the pinnacle of protection. Theirs is usually the next to last line of defense. The final line is the enduser him/herself.
What makes it tough about the AV angle is that AV definitions have to come out extremely quickly. Look at all the variants of Netsky and Bagle. Every day several variants would be announced. The enduser would have to update their AV definitions on a daily basis at the very worst in order to keep up. Then typical scan engines require a system reboot in order for the updated defs to take effect.
For my corporate user base that means that really the following day these updated definitions would really be active, since I hate to force reboots. I update the AV definitions as part of the network logon script and don't want endusers to have to reboot immediately after logging in. I still run autoupdated AV software on the mail server so hopefully all of these measures is enough.
Years ago system stability and performance were the critical concerns of working with PC's. I can't recall all of the failed hard drives and unstable software I had to deal with. Now all of this has been replaced with security concerns. At least it means job security. **sigh**
Any AV software is vulnerable to being "disabled." Newer worms and virus exploits simply kill these AV processes. For example, the KILL.EXE command was included with the Windows NT 4.0 Resource Kit and from that version on it works like a champ. Simply issue that command with the -f switch to force the processes to terminate. Gives you an idea of what the malware does.
There typically are dozens of EXE process names that are terminated so that the AV software is inactive from that point on during the same session when a host is infected. How pray tell can a fix be issued for this from an AV vendor?
This simply points to the fact that the initial line of defense is a hardware-based Internet firewall and an OS that has all of the latest security patches. By the time that you have to worry about AV software definitions you are already past that initial line of defense.
Actually that is the history behind why that http server was called what it is. It was originally intended to be a series of patches for the httpd process. Ironic, eh?