If your coffee is too hot, add an ice cube or let it cool off. If your coffee is too cold, you curse McDonalds for making cold coffee. Coffee is supposed to be hot. Most domestic coffee brewers percolate boiling water up; the steam condenses and drips into the filter basket, and enters the pot at a temperature very close to boiling. No one sues Mr. Coffee or Black and Decker.
Anyhow, as you simultaneously manage to frustrate and bore me, this thread is now extinct. Maybe once you can shave daily and manage to become remotely cosmopolitan, your perspective will adjust somewhat.
My ISP (www.dsl.ca) specifically allows you to run servers - and even rents a static IP. Then, one day recently, they surprised me by firewalling all outgoing SMTP. Of course, this coincided with a BIND change on my nameserver, and so when my mail spool started to fill up, my first assumption was that I'd killed the reverse lookup! I spent an hour or so trying to figure out how I'd gone wrong, but I didn't think I did. Finally, I contacted 'em about it. They just shut it off because there were too many spammers and they didn't want to do a mass-mailing, which would become a tech support nightmare ("uhh... this port 25 thing, do I need it?").
Anyway, I'm started to get really annoyed by Code Red II. My webserver log file is full of IIS crap. I hold Microsoft responsible for marketing a faulty product.
Yes I'm lame, I'm running IIS (patched) on my cable modem.
You are lame, for sure. You know, it's really not that much work to set up an old 486 or something with FreeBSD and NAT, add Apache from the ports collection, and laugh at all the IIS lusers. Please ditch IIS; I'll provide a helping hand if I can.
I don't care what temperature you set it to when YOU worked at mcdonalds, dumbass. The woman got THIRD DEGREE burns. That is TOO HOT for coffee. Idiot.
Yeah. So, she's apparently not intelligent enough to be trusted with coffee, or tea, or hot chocolate... I'd also draw the line at giving her a driver's license. In fact, I'd legislate that people like her should have to wear helmets everywhere they go.
I can't drink coffee at 73C, let alone 85C. But I also know that at 85C, people complain that the coffee is too cold. Those are the edicts from McDonalds, not the temperature at which I independently chose to set the Bunn's thermostat.
So? I carefully put my coffee aside and let it cool.
As for the third degree burns, you can get third degree burns from something that is a mere 50C. Note that is the temperature to which most hot water heaters are set. Are you therefore a proponent of a law requiring everyone to turn down their hot water heaters to 37C so that they can't burn people? Heck, there are lots of other things that can burn you. If you're stupid, take the back cover off your monitor. Right at the back of the picture tube's neck, you'll find that there is an area of glass heated by radiant heat leaving the cathodes. Rest your finger there and see how many yucks you have. Let's ban monitors because they can hurt people. Let's ban stoves because a child could turn on a burner and scorch himself. Let's ban cars because the radiator gets warm. Of course, we can't let people have bicycles, either, there are many ways to get hurt on *those*, least of which being the elevated temperature of the brake pads after stopping.
You, sir, like the bovine hausfrau who was too stupid to ensure that her coffee didn't spill on her lap, are the idiot. If I were President, I'd find you and your peers a nice little padded cell somewhere so that you may avoid any sort of risk or personal responsibility for your activities.
And, PS. While you're in the monitor, look for the big coils of wire around the funnel of the tube. Okay. Find the wires that go to the area of the big plastic block and the big red wire that goes to the suction cup on the back of the tube. Now, this is very important... turn on the monitor and lick your hands. Touch the sheetmetal shielding inside the monitor with your left hand. With your right hand, simultaneously touch the solder connection where the horizontal deflection voltage leaves the PC board (near the big plastic box, remember). Feeling warm yet? If your skin isn't on fire within a few seconds, you didn't follow the instructions right.
The McDonals coffee case judge was not braindead. get teh facts straight, they have been mentioned even here hundreds of times already. The coffee was hot enough to cause severe burns on contact, and McD knew it was so and they still sold the coffee at such temperature.
You're kidding, right? I think you are, but I'm not sure. Okay. Well, I'll treat my response as if you're serious.
I worked at a McDonalds, aeons ago, when I was in high school. Like, 1991. Probably when you were still in kindergarten.
I worked there for four years. My first year, it was hell, I was minimum wage scum, but McDonalds is like the army: you get out of it exactly what you put into it.
Well, I was nice with everyone, and I always arrived on time, and I always worked hard. And I was quickly awarded Employee of the Month. Less than a week after that, I was asked to come in for a staff meeting. I thought I was in trouble for something. All the managers sat me down very seriously, and asked me if I knew why I was there. They passed me a package and told me to sign for its receipt. I did, then I opened the package. It was a manager's uniform with my name on the little gold tag.
I got to know a lot about McDonalds and its customers in the 3 years that followed. It was, believe it or not, a great job and I made a lot of friends working at McDonalds with whom I'm still in touch.
As a part time ("Swing") manager, I got to help ensure that the restaurant ran smoothely. Ordering supplies, ensuring the staff have everything they need, resolving conflicts, assuring quality control, and dealing with customer complaints.
One of the most common customer complaints was that the coffee was too cold. And yet, as part of my quality control role, I was responsible for ensuring that the temperatures on every cooking appliance were correct when I started my shift. The coffee, at the time, was to be kept at 85C.
Now, of course, since some slovenly white trash got rich because of her own stupidity, I'm sure the customer complaints about cold coffee are even more common. From what I understand, the coffee is to be kept at 73C now.
Of course it's hot. Coffee is supposed to be hot. Next thing is people will start suing over Eskimo Pie migraines they get when they drink their cold Coke too quickly.
GM recently got sued for several billion dollars. It was Christmas Eve in about 1995 when this tragedy occured. A family was riding along in their 1978 Chevy Malibu (already an old car). They were stopped at a red light, and a drunk driver hit them from behind. The car's gas tank exploded, and while the family were all concious and relatively unhurt, when they got out, one of the kids had third degree burns to his leg. So they sued GM for faulty fuel tank design.
Now, one thing about this case that terrifies me is that this was a 17-year-old car at the time of the accident. Who knows what nature of wear had been experienced? Rusted out gas tank? For all we know, this car shouldn't have been on the road to begin with.
The other thing that terrifies me is that the jury wasn't allowed to hear how fast the vehicle that rear-ended them was travelling. Remember, they were stopped at a traffic light. They were hit by a drunk driver in a full-size pickup truck travelling at 75MPH. Approximately 120km/h.
Changes things a little, doesn't it? How survivable is that accident?
Rather than suing GM because a 17 year old car blew up when it was rear-ended by a 4,000lb mass travelling at 75MPH, I think I'd be writing a letter to GM to thank them for the fact that despite such a horrific accident, I still had both my kids.
Your remark suggests a tacit support of the excessive litigation against businesses. My wish upon you is that you mortgage your house, open a business, and get sued by someone who gets a paper cut off your first invoice.
Yelling, "There should be a law!" just makes you look like a
dumb liberal that needs the government to protect him from himself.
For sure, and such a law would stifle innovation far more than Microsoft has. Imagine the liability in releasing a beta (or... gasp! an alpha) version?
Now, I think there have to be other ways to go after Microsloth, more than legislation. What's needed is a judge - perhaps one as braindead as the one who awarded millions to the dumb woman who spilled coffee on her lap - who can be used to our advantage in a class-action lawsuit from all victims of the default-dangerous Microsoft machines in the field.
:0 B
* > 100000
* mDmcOaA5pDmoOaw5sDnAOeA56DnsOfA59Dn4Ofw5ADoEOgg6HD o8OkQ6SD /dev/null
Okay. Forgive me if the syntax is off, I've never had to play with procmail filters. But it strikes me that this one would be significantly more useful:
Microsoft's products spew pollution into the information space like a burning mountain of tires.
For sure! Take a look at my webserver (which pioneers the great new feature of a "Log File Chat Room" (tm 2001 Lawrence Wade)).
This new variant seems to have been especially active, it's eating up a lot of my bandwidth. Last time, my IP address wasn't getting scanned as much as many other people I spoke with; I'm wondering if this one includes a better random number seed. I'm also seeing IIS victims from my ISP.
Also, I wonder if a disclaimer stating that infected IIS servers are not allowed to visit my website would be sufficient to work towards suing Microsoft for their ongoing gross negligence and complicity causing material and financial damage.
Speaking of neat junk I've scrounged, anyone want three Eimac 450TH transmitting tubes? 450 watts RMS in class A mode (lots more in class C), thoriated filament directly heated. Filaments are good, no shorts with an ohmmeter, were replaced from a big Toronto radio station as part of a normal maintenance cycle.
To reply to an e-mail message I got about this, no, not a worm, no way. I'm not a malicious 14 year old. And while it would be fun, this script would be entirely to give me a warm fuzzy, force a reboot and know that there's one less infected machine every time the *#$%#$%^#$ damn worm tries to hit my box.
I'd ignore it as Microsoft point-and-drool "I've-never-known-anything-better" user idiocy, if it weren't taking up so much of my bandwidth. On the last attack, I was getting a peak of 17 hits a minute by the worm.
If it were not for Microsoft's carefully worded user license agreement, which holds the company blameless for absolutely anything, they would probably have been awash in class action lawsuits by now.
But can't sysadmins sue Microsloth for the gross negligence that consumes our bandwidth?
I know the license agreement that I made when I opened my Windows 2000 CD only affected my Windows 2000 desktop. It has *nothing* to do with the bandwidth - which I pay for - that this stupid [expletive deleted - Ed.] worm has consumed.
I'm not normally litigious, but Microsoft needs to clean up their act.
Hey guys, this is somewhat unrelated to the stuff in this conversation, but it's about M$ vulnerabilities, so I'll ask anyway.
If we all set up out webservers to send a ping of death or some other blue-screen/reboot DoS attack automatically to anything that shows the signature request of the IIS worm, wouldn't that help to at least slow the spread of this thing?
The shell script to tail the log file and run a script would be pretty easy, but does anyone have anything tried and true for Linux/UNIX that will force a reboot of an affected Win NT/2000 server?
At this point, I see this as an eye for an eye, I'm kinda tired of all don't patch their systems despite big media attention. Besides, it'll definitely give me a sense of satisfaction to confirm a kill when the server doesn't respond to an automated regular ping a few seconds later.
I know you've got this great vision for a wonderful Internet and a computer
on every desktop and all that stuff. I've met you in person on two occasions,
and found you to be friendly, personable, brilliantly intelligent, and I know
you believe very strongly that your vision of the computer industry isn't
flawed. I even grudginly like you for your passion, courage, vision, strength
and business acumen. Most damningly towards wanting to hate you, I also believe
you and Melinda are true philanthropists.
But I'll still bet money that I had an e-mail address before you did. And
you and I both know that this has to stop. At this point, I tell my
consulting customers that running IIS is as irresponsible as drinking and
driving. My procmail filter automatically sends all e-mails from Outlook
mail clients to/dev/null. Like drinking and driving affects all road users,
the many blatant security flaws in Windows and related programs affect all
Internet users.
Please make it stop.
Copied and pasted from my (Apache on UNIX) webserver log:
(D'oh! Slashdot Lameness filter sees all the capital Ns of the Code Red worm buffer overflow and won't let me paste, so you'll have to see it here.)
That Dimension desktop or Inspiron laptop will always have the latest copy of MS whatever, with MS-Works. Which I am sure they are getting a little revenue off of that.
Which really shoots them in the foot for the low-end market. I mean, what's a Windows Me license running these days? $100? On a sub-$1000 system, that's a *big* chunk of your total system price.
For general newbies, preinstalled Linux makes things easy, and let's face it, most of these people are looking for nothing more than a web and e-mail grinder that lacks the intelligence-insulting AOL crap.
Especially if you advertised that Linux came preinstalled and configured with Netscrape and an e-mail client, maybe StarOffice too. Little different for a newbie to learn, but this guy is a newbie whose only other net experience was AOL on Windows 98, and *hated* it. (Crashes, found it counterintuitive to click "Start" to shutdown, nasty AOL point-and-drool, silly sound effects, etc.)
I was actually pretty impressed how easy it was to select Linux instead of Windows. You can't say they didn't try.
This was a month ago on an entry-level Dimension L. Here's the link that *didn't* offer Linux. (Did I miss it? I can't see how to get it without Windows. Dell lost the sale as a result.)
I was on there two weeks ago getting something for my brother. RH6.2 and 7.1 were on the list of operating systems to install on the laptop.
This was a month ago on an entry-level Dimension L. Here's the link that *didn't* offer Linux. (Did I miss it? I can't see how to get it without Windows. Dell lost the sale as a result.)
Maybe there'd be more demands for Linux on Dell desktops and notebooks if I could actually select it on their website. If it was available as an option on that machine, I couldn't find it.
As it was, I was hunting around for a Dell desktop for a friend of mine. Nothing spectacular, but he didn't want to pay the Microsoft tax, and liked the look of Linux on one of my machines.
We chose the link to customize the machine, and Linux wasn't on the list. In the end, he went with a generic clone because he could get it without the liability of a copy of Windows Me. Oh, and we downloaded an RH 7.1 ISO from their website.
Wanna hire a computer geek who can configure BIND and whip out a soldering iron to hack a monitor? www.glowingplate.com
I thought it was fake, since the blue screen shifted in "slowly" from the right insteat of just popping up, which it normally does. So, yet another setup to get some more publicity?
Nope, I used to set up video projectors for a living.
Next time you get a BSOD on a Windows 9x box, take a look at the sync rates. The blue screen, if I recall, runs at normal VGA - 640x480x16 with a horizontal sync of 31kHz and a vertical sync of about 60Hz. As far as a video projector is concerned, that's quite different from the scan rates most people keep their desktops at.
As the video scanning speeds change, it will take a moment for the horizontal and vertical oscillators in the video projector to lock onto the new rate. Hence the little burble and roll.
When you change the scanning rate on a normal monitor, you'll often hear little clicks from relays switching windings in and out of the flyback transformer and the deflection yoke. Since the flyback and yoke must resonate (like tuning forks) pretty closely to the vertical and horizontal frequencies, these relays cut windings in and out like cutting the end off a tuning fork, or adding length to it to change the resonant frequency.
Lots of cheap monitors don't do this. This is why they're cheap, why they often run hotter, and why they more often seem to blow flyback transformers and horizontal output transistors.
Finally, with a video projector - and in 1998 it would have been a three-tube CRT projector for a screen of that size - the deflection currents and second anode voltages are higher. Generally, that would mean bigger deflection yokes and flyback transformers, with more ferrite or iron laminate core to saturate with magnetic flux. When you change the sync rate, the hysterisis of the core will cause its magnetic properties to have a little bit of inertia to the change.
You can hire me! Imagine a computer geek who knows how to configure BIND and can also whip out a soldering iron and hack a monitor! www.glowingplate.com
Maybe someone has a TI up on eBay or whatever for not much...it'd be nice to have one again, just for the hell of it. If all the goodies (more RAM, the enhanced BASIC cartridge, etc.) are also available with it, that'd be a bonus.
And when you are 10 years old with one of those things(PEB), they are a royal bitch to carry around.
Tell me about it. I was the buffest ten-year-old on the playground, with bigger biceps and triceps than most of the bullies, and I thank Texas Instruments for that.
Oh yeah, I've also got 4 1981-era Electrohome/Mitsubishi 13" RGB color monitors. There are two color demodulators (for CGA use, or with Apple IIs or TI-99/4As or whatever), and I put together a sync inverter to make them run with Amiga 500/1000/2000 machines. Matching set of 4, and as I recall, three of them work. They're not at the curb yet, but if you want them, e-mail me. FOB Toronto, Canada.
Want 'em? Come scoop 'em, they're at the curb. 1352 Victoria Park Avenue, Toronto, halfway between Eglinton and St. Clair on the west (southbound) side of the road.)
On the other hand, I could beat someone over the head with a stick of SDRAM, but it would be more memorable to the DIMM than to the individual requiring the physical behavior modification.
For all those Slashdotters who don't have access to webserver logs and therefore can't see the Code Red worm searching for victim hosts, check out this dynamically created view of my log file. For legibility, a reverse lookup is done on the incoming visitors.
The party should start shortly after 8:PM Eastern time tonight.
I was, however, involved in a development project that required video overlay. The chip of choice was the TMS9918 because it was the only one on the market that even claimed the ability.
Well, we have to make a distinction here, then. Was there a suffix on the chip number?
I assure you, once you use a sync separator circuit and recombine it into the video stream, the TMS9918ANL, which was the version in every TI-99/4A (as opposed to the TMS9918 in the/4), the video overlay works just fine. I've even done it on a variety of consoles, including the older black and aluminum ones.
Early problems I had were having the video bleed through the solid overlay colors. It was easily fixed by reducing the video gain using (urk) a potentiometer. I did this after the sync separator/recombiner stage because I guessed that if I was overdriving the video (white clip and bleed-thru), I was probably overdriving the sync.
The TMS9918ANL - which was the chip in every TI-99/4A I've ever seen - never so much hiccupped. Unless the VCR was mistracking... the TMS9918 was pretty strict about timing, and could't lock very far away from normal fh and fv.
Slashdot Mirror
If your coffee is too hot, add an ice cube or let it cool off. If your coffee is too cold, you curse McDonalds for making cold coffee. Coffee is supposed to be hot. Most domestic coffee brewers percolate boiling water up; the steam condenses and drips into the filter basket, and enters the pot at a temperature very close to boiling. No one sues Mr. Coffee or Black and Decker.
Anyhow, as you simultaneously manage to frustrate and bore me, this thread is now extinct. Maybe once you can shave daily and manage to become remotely cosmopolitan, your perspective will adjust somewhat.
If @home blocks my port 80 i'll be quite pissed.
My ISP (www.dsl.ca) specifically allows you to run servers - and even rents a static IP. Then, one day recently, they surprised me by firewalling all outgoing SMTP. Of course, this coincided with a BIND change on my nameserver, and so when my mail spool started to fill up, my first assumption was that I'd killed the reverse lookup! I spent an hour or so trying to figure out how I'd gone wrong, but I didn't think I did. Finally, I contacted 'em about it. They just shut it off because there were too many spammers and they didn't want to do a mass-mailing, which would become a tech support nightmare ("uhh... this port 25 thing, do I need it?").
Anyway, I'm started to get really annoyed by Code Red II. My webserver log file is full of IIS crap. I hold Microsoft responsible for marketing a faulty product.
Yes I'm lame, I'm running IIS (patched) on my cable modem.You are lame, for sure. You know, it's really not that much work to set up an old 486 or something with FreeBSD and NAT, add Apache from the ports collection, and laugh at all the IIS lusers. Please ditch IIS; I'll provide a helping hand if I can.
I don't care what temperature you set it to when YOU worked at mcdonalds, dumbass. The woman got THIRD DEGREE burns. That is TOO HOT for coffee. Idiot.
Yeah. So, she's apparently not intelligent enough to be trusted with coffee, or tea, or hot chocolate... I'd also draw the line at giving her a driver's license. In fact, I'd legislate that people like her should have to wear helmets everywhere they go.
I can't drink coffee at 73C, let alone 85C. But I also know that at 85C, people complain that the coffee is too cold. Those are the edicts from McDonalds, not the temperature at which I independently chose to set the Bunn's thermostat.
So? I carefully put my coffee aside and let it cool.
As for the third degree burns, you can get third degree burns from something that is a mere 50C. Note that is the temperature to which most hot water heaters are set. Are you therefore a proponent of a law requiring everyone to turn down their hot water heaters to 37C so that they can't burn people? Heck, there are lots of other things that can burn you. If you're stupid, take the back cover off your monitor. Right at the back of the picture tube's neck, you'll find that there is an area of glass heated by radiant heat leaving the cathodes. Rest your finger there and see how many yucks you have. Let's ban monitors because they can hurt people. Let's ban stoves because a child could turn on a burner and scorch himself. Let's ban cars because the radiator gets warm. Of course, we can't let people have bicycles, either, there are many ways to get hurt on *those*, least of which being the elevated temperature of the brake pads after stopping.
You, sir, like the bovine hausfrau who was too stupid to ensure that her coffee didn't spill on her lap, are the idiot. If I were President, I'd find you and your peers a nice little padded cell somewhere so that you may avoid any sort of risk or personal responsibility for your activities.
And, PS. While you're in the monitor, look for the big coils of wire around the funnel of the tube. Okay. Find the wires that go to the area of the big plastic block and the big red wire that goes to the suction cup on the back of the tube. Now, this is very important... turn on the monitor and lick your hands. Touch the sheetmetal shielding inside the monitor with your left hand. With your right hand, simultaneously touch the solder connection where the horizontal deflection voltage leaves the PC board (near the big plastic box, remember). Feeling warm yet? If your skin isn't on fire within a few seconds, you didn't follow the instructions right.
The McDonals coffee case judge was not braindead. get teh facts straight, they have been mentioned even here hundreds of times already. The coffee was hot enough to cause severe burns on contact, and McD knew it was so and they still sold the coffee at such temperature.
You're kidding, right? I think you are, but I'm not sure. Okay. Well, I'll treat my response as if you're serious.
I worked at a McDonalds, aeons ago, when I was in high school. Like, 1991. Probably when you were still in kindergarten.
I worked there for four years. My first year, it was hell, I was minimum wage scum, but McDonalds is like the army: you get out of it exactly what you put into it.
Well, I was nice with everyone, and I always arrived on time, and I always worked hard. And I was quickly awarded Employee of the Month. Less than a week after that, I was asked to come in for a staff meeting. I thought I was in trouble for something. All the managers sat me down very seriously, and asked me if I knew why I was there. They passed me a package and told me to sign for its receipt. I did, then I opened the package. It was a manager's uniform with my name on the little gold tag.
I got to know a lot about McDonalds and its customers in the 3 years that followed. It was, believe it or not, a great job and I made a lot of friends working at McDonalds with whom I'm still in touch.
As a part time ("Swing") manager, I got to help ensure that the restaurant ran smoothely. Ordering supplies, ensuring the staff have everything they need, resolving conflicts, assuring quality control, and dealing with customer complaints.
One of the most common customer complaints was that the coffee was too cold. And yet, as part of my quality control role, I was responsible for ensuring that the temperatures on every cooking appliance were correct when I started my shift. The coffee, at the time, was to be kept at 85C.
Now, of course, since some slovenly white trash got rich because of her own stupidity, I'm sure the customer complaints about cold coffee are even more common. From what I understand, the coffee is to be kept at 73C now.
Of course it's hot. Coffee is supposed to be hot. Next thing is people will start suing over Eskimo Pie migraines they get when they drink their cold Coke too quickly.
GM recently got sued for several billion dollars. It was Christmas Eve in about 1995 when this tragedy occured. A family was riding along in their 1978 Chevy Malibu (already an old car). They were stopped at a red light, and a drunk driver hit them from behind. The car's gas tank exploded, and while the family were all concious and relatively unhurt, when they got out, one of the kids had third degree burns to his leg. So they sued GM for faulty fuel tank design.
Now, one thing about this case that terrifies me is that this was a 17-year-old car at the time of the accident. Who knows what nature of wear had been experienced? Rusted out gas tank? For all we know, this car shouldn't have been on the road to begin with.
The other thing that terrifies me is that the jury wasn't allowed to hear how fast the vehicle that rear-ended them was travelling. Remember, they were stopped at a traffic light. They were hit by a drunk driver in a full-size pickup truck travelling at 75MPH. Approximately 120km/h.
Changes things a little, doesn't it? How survivable is that accident?
Rather than suing GM because a 17 year old car blew up when it was rear-ended by a 4,000lb mass travelling at 75MPH, I think I'd be writing a letter to GM to thank them for the fact that despite such a horrific accident, I still had both my kids.
Your remark suggests a tacit support of the excessive litigation against businesses. My wish upon you is that you mortgage your house, open a business, and get sued by someone who gets a paper cut off your first invoice.
Yelling, "There should be a law!" just makes you look like a dumb liberal that needs the government to protect him from himself.
For sure, and such a law would stifle innovation far more than Microsoft has. Imagine the liability in releasing a beta (or... gasp! an alpha) version?
Now, I think there have to be other ways to go after Microsloth, more than legislation. What's needed is a judge - perhaps one as braindead as the one who awarded millions to the dumb woman who spilled coffee on her lap - who can be used to our advantage in a class-action lawsuit from all victims of the default-dangerous Microsoft machines in the field.
* > 100000
* mDmcOaA5pDmoOaw5sDnAOeA56DnsOfA59Dn4Ofw5ADoEOgg6H
Okay. Forgive me if the syntax is off, I've never had to play with procmail filters. But it strikes me that this one would be significantly more useful:
* X-mailer=Outlook
:)
Microsoft's products spew pollution into the information space like a burning mountain of tires.
For sure! Take a look at my webserver (which pioneers the great new feature of a "Log File Chat Room" (tm 2001 Lawrence Wade)).
This new variant seems to have been especially active, it's eating up a lot of my bandwidth. Last time, my IP address wasn't getting scanned as much as many other people I spoke with; I'm wondering if this one includes a better random number seed. I'm also seeing IIS victims from my ISP.
Also, I wonder if a disclaimer stating that infected IIS servers are not allowed to visit my website would be sufficient to work towards suing Microsoft for their ongoing gross negligence and complicity causing material and financial damage.
Speaking of neat junk I've scrounged, anyone want three Eimac 450TH transmitting tubes? 450 watts RMS in class A mode (lots more in class C), thoriated filament directly heated. Filaments are good, no shorts with an ohmmeter, were replaced from a big Toronto radio station as part of a normal maintenance cycle.
Want 'em? Visit my site!
To reply to an e-mail message I got about this, no, not a worm, no way. I'm not a malicious 14 year old. And while it would be fun, this script would be entirely to give me a warm fuzzy, force a reboot and know that there's one less infected machine every time the *#$%#$%^#$ damn worm tries to hit my box.
I'd ignore it as Microsoft point-and-drool "I've-never-known-anything-better" user idiocy, if it weren't taking up so much of my bandwidth. On the last attack, I was getting a peak of 17 hits a minute by the worm.
Quoted from Cringely:
If it were not for Microsoft's carefully worded user license agreement, which holds the company blameless for absolutely anything, they would probably have been awash in class action lawsuits by now.But can't sysadmins sue Microsloth for the gross negligence that consumes our bandwidth?
I know the license agreement that I made when I opened my Windows 2000 CD only affected my Windows 2000 desktop. It has *nothing* to do with the bandwidth - which I pay for - that this stupid [expletive deleted - Ed.] worm has consumed.
I'm not normally litigious, but Microsoft needs to clean up their act.
Anyone know a good class-action lawyer?
Hey guys, this is somewhat unrelated to the stuff in this conversation, but it's about M$ vulnerabilities, so I'll ask anyway.
If we all set up out webservers to send a ping of death or some other blue-screen/reboot DoS attack automatically to anything that shows the signature request of the IIS worm, wouldn't that help to at least slow the spread of this thing?
The shell script to tail the log file and run a script would be pretty easy, but does anyone have anything tried and true for Linux/UNIX that will force a reboot of an affected Win NT/2000 server?
At this point, I see this as an eye for an eye, I'm kinda tired of all don't patch their systems despite big media attention. Besides, it'll definitely give me a sense of satisfaction to confirm a kill when the server doesn't respond to an automated regular ping a few seconds later.
As posted to microsoft.public.win2000.general:
Come on, Bill.
I know you've got this great vision for a wonderful Internet and a computer on every desktop and all that stuff. I've met you in person on two occasions, and found you to be friendly, personable, brilliantly intelligent, and I know you believe very strongly that your vision of the computer industry isn't flawed. I even grudginly like you for your passion, courage, vision, strength and business acumen. Most damningly towards wanting to hate you, I also believe you and Melinda are true philanthropists.
But I'll still bet money that I had an e-mail address before you did. And you and I both know that this has to stop. At this point, I tell my consulting customers that running IIS is as irresponsible as drinking and driving. My procmail filter automatically sends all e-mails from Outlook mail clients to /dev/null. Like drinking and driving affects all road users,
the many blatant security flaws in Windows and related programs affect all
Internet users.
Please make it stop.
Copied and pasted from my (Apache on UNIX) webserver log:
(D'oh! Slashdot Lameness filter sees all the capital Ns of the Code Red worm buffer overflow and won't let me paste, so you'll have to see it here.)
That Dimension desktop or Inspiron laptop will always have the latest copy of MS whatever, with MS-Works. Which I am sure they are getting a little revenue off of that.
Which really shoots them in the foot for the low-end market. I mean, what's a Windows Me license running these days? $100? On a sub-$1000 system, that's a *big* chunk of your total system price.
For general newbies, preinstalled Linux makes things easy, and let's face it, most of these people are looking for nothing more than a web and e-mail grinder that lacks the intelligence-insulting AOL crap.
Especially if you advertised that Linux came preinstalled and configured with Netscrape and an e-mail client, maybe StarOffice too. Little different for a newbie to learn, but this guy is a newbie whose only other net experience was AOL on Windows 98, and *hated* it. (Crashes, found it counterintuitive to click "Start" to shutdown, nasty AOL point-and-drool, silly sound effects, etc.)
I was actually pretty impressed how easy it was to select Linux instead of Windows. You can't say they didn't try.
This was a month ago on an entry-level Dimension L. Here's the link that *didn't* offer Linux. (Did I miss it? I can't see how to get it without Windows. Dell lost the sale as a result.)
I was on there two weeks ago getting something for my brother. RH6.2 and 7.1 were on the list of operating systems to install on the laptop.
This was a month ago on an entry-level Dimension L. Here's the link that *didn't* offer Linux. (Did I miss it? I can't see how to get it without Windows. Dell lost the sale as a result.)
Maybe there'd be more demands for Linux on Dell desktops and notebooks if I could actually select it on their website. If it was available as an option on that machine, I couldn't find it.
As it was, I was hunting around for a Dell desktop for a friend of mine. Nothing spectacular, but he didn't want to pay the Microsoft tax, and liked the look of Linux on one of my machines.
We chose the link to customize the machine, and Linux wasn't on the list. In the end, he went with a generic clone because he could get it without the liability of a copy of Windows Me. Oh, and we downloaded an RH 7.1 ISO from their website.
Wanna hire a computer geek who can configure BIND and whip out a soldering iron to hack a monitor? www.glowingplate.com
You know your shit, Lawrence.
Thanks! So do you, apparently, judging from the cute little workshop fire.
I've yet to have one of those. Anywhere I break out breadboards, so too do I break out the fire extinguisher. :)
www.glowingplate.com
I thought it was fake, since the blue screen shifted in "slowly" from the right insteat of just popping up, which it normally does. So, yet another setup to get some more publicity?
Nope, I used to set up video projectors for a living.
Next time you get a BSOD on a Windows 9x box, take a look at the sync rates. The blue screen, if I recall, runs at normal VGA - 640x480x16 with a horizontal sync of 31kHz and a vertical sync of about 60Hz. As far as a video projector is concerned, that's quite different from the scan rates most people keep their desktops at.
As the video scanning speeds change, it will take a moment for the horizontal and vertical oscillators in the video projector to lock onto the new rate. Hence the little burble and roll.
When you change the scanning rate on a normal monitor, you'll often hear little clicks from relays switching windings in and out of the flyback transformer and the deflection yoke. Since the flyback and yoke must resonate (like tuning forks) pretty closely to the vertical and horizontal frequencies, these relays cut windings in and out like cutting the end off a tuning fork, or adding length to it to change the resonant frequency.
Lots of cheap monitors don't do this. This is why they're cheap, why they often run hotter, and why they more often seem to blow flyback transformers and horizontal output transistors.
Finally, with a video projector - and in 1998 it would have been a three-tube CRT projector for a screen of that size - the deflection currents and second anode voltages are higher. Generally, that would mean bigger deflection yokes and flyback transformers, with more ferrite or iron laminate core to saturate with magnetic flux. When you change the sync rate, the hysterisis of the core will cause its magnetic properties to have a little bit of inertia to the change.
You can hire me! Imagine a computer geek who knows how to configure BIND and can also whip out a soldering iron and hack a monitor! www.glowingplate.com
Maybe someone has a TI up on eBay or whatever for not much...it'd be nice to have one again, just for the hell of it. If all the goodies (more RAM, the enhanced BASIC cartridge, etc.) are also available with it, that'd be a bonus.
Where are you located? E-mail me back.
And when you are 10 years old with one of those things(PEB), they are a royal bitch to carry around.
Tell me about it. I was the buffest ten-year-old on the playground, with bigger biceps and triceps than most of the bullies, and I thank Texas Instruments for that.
Oh yeah, I've also got 4 1981-era Electrohome/Mitsubishi 13" RGB color monitors. There are two color demodulators (for CGA use, or with Apple IIs or TI-99/4As or whatever), and I put together a sync inverter to make them run with Amiga 500/1000/2000 machines. Matching set of 4, and as I recall, three of them work. They're not at the curb yet, but if you want them, e-mail me. FOB Toronto, Canada.
Hey! Two of those Zenith Data Systems monitors are sitting in my garbage right now. They both work!
Want 'em? Come scoop 'em, they're at the curb. 1352 Victoria Park Avenue, Toronto, halfway between Eglinton and St. Clair on the west (southbound) side of the road.)
Unlike wine, computers do not get more potent with age.
I beg to differ. Here's a picture of the 32K RAM expansion card (and a few other cards) in a 1981 Texas Instruments TI-99/4A Peripheral Expansion Box. Yes, they're clad in cast aluminum. Yes, the steel chassis is stamped of far thicker metal than the unibody of a Toyota Tercel.
On the other hand, I could beat someone over the head with a stick of SDRAM, but it would be more memorable to the DIMM than to the individual requiring the physical behavior modification.
For all those Slashdotters who don't have access to webserver logs and therefore can't see the Code Red worm searching for victim hosts, check out this dynamically created view of my log file. For legibility, a reverse lookup is done on the incoming visitors.
The party should start shortly after 8:PM Eastern time tonight.
I was, however, involved in a development project that required video overlay. The chip of choice was the TMS9918 because it was the only one on the market that even claimed the ability.
Well, we have to make a distinction here, then. Was there a suffix on the chip number?
I assure you, once you use a sync separator circuit and recombine it into the video stream, the TMS9918ANL, which was the version in every TI-99/4A (as opposed to the TMS9918 in the /4), the video overlay works just fine. I've even done it on a variety of consoles, including the older black and aluminum ones.
Early problems I had were having the video bleed through the solid overlay colors. It was easily fixed by reducing the video gain using (urk) a potentiometer. I did this after the sync separator/recombiner stage because I guessed that if I was overdriving the video (white clip and bleed-thru), I was probably overdriving the sync.
The TMS9918ANL - which was the chip in every TI-99/4A I've ever seen - never so much hiccupped. Unless the VCR was mistracking... the TMS9918 was pretty strict about timing, and could't lock very far away from normal fh and fv.