I wrote a dinky little stopwatch app (no networking involved) using the System.Timer class that has a reset button that stops the timer and sets the display to 0. But the elapsedEventHandler somehow gets called after the reset button changes the display, and sets the display to the current timer value. I even inserted a variable that gets cleared first thing in the reset-button handler and wrapped the timer event handler code in it, and the timer handler still updates the display after the reset handler has run. It became apparent when I set the timer to refresh the display every few milliseconds. If I set the refresh interval somewhat higher (100 ms or so) I no longer have the patience needed to keep clicking buttons until it shows up, so maybe it goes away.
The only way this could happen is if the display update code inside of the = operator for editBox allows the two values to get mixed up. I'm guessing there's some message passing going on in there, and XP and/or the CLR are hosing me.
I'd post the code (the problem is reduced to about 30 lines) but/. says 'Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted.'
If I had the same insight into the source of the crash, yes. For every new problem.
But Windows' default behavior (especially in Win95) is to lock up hard or BSOD, leaving the user with no information. Hit the reset button, wait for the disk check to finish, and try to remember what you were doing before it barfed.
NT was the first MS OS that had the capability of keeping the OS running if a program crashed, and XP is the first one that actually does something with the crash dump.
So Bill's statistic wasn't saying what he was saying it was saying.
Ever looked in one of those XP dumps? MS already has copious information on my config (registration sent it), and a core dump can tell an experienced programmer who has knowledge of the code quite a bit.
But I don't expect MS to put those people on the dump-pile team. For the OE thing, I got email from a support center in China. Went back and forth for a couple of emails and even reinstalled the OS and OE and determined that neither of those repairs the parts of the OE registry that the original install of XP had miscommunicated with. No more OE for me. So I started using Outlook. But it doesn't play well. It still doesn't send mail from other apps unless an instance of Outlook is running in the background.
I'd use Netscape mail, but I'd have to install Netscape, and I don't want to, because it went off the rails about three years ago. I have IE and Phoenix.
Which brings us back to bugzilla. I reported a bug to those clowns, and they took their sweet time on it, then told me it was misclassified and closed it. So I resubmitted it, and a couple of weeks later was told it was misclassified again, so they closed it. Each time, they had to analyze it to find the cause, to decide it was misclassified. I submitted it a third time and haven't heard back. That was four months ago or so. So there's a bug in bugzilla: the ass-heads who think they're doing the world a favor by working the bug list and don't want to be bothered acting like they're performing customer service. Other than that, I kind of like Phoenix (soon to be named something else). It's faster in some ways, slower in others, and the tab controls are great for getting info from sites behind a long list of selections (eBay, FARK, Google, etc.) while continuing to read the list.
And complaining isn't cool. It marks one as a whiner. Bill is just trying to justify his aloof attitude towards his bugs.
It's not the OS. MS apps (Outlook (not OE, which won't run at all), IE, etc.) tend to crap out, and XP catches them and does a dump and phones it home.
XP itself is nearly bulletproof, as far as I can see. Despite the race conditions when using C#.
Bill thinks it's cool to waggle back and forth in his chair like an unloved monkey.
What are the other 99% of calls about? Oh yeah. Crap documentation that tells you the obvious half of what the tool or call does, but doesn't bother to tell you what its actual behavior or use is.
I wonder if he's counting the 3-10 times a week my XP machine says it's sending a bug report back to Microsoft.
I've had to stop using Outlook Express entirely because it won't work, and Microsoft was no help.
And I've already run into race conditions in the event handling for C#.
People report bugs not because it's cool, but because they think Microsoft might just have a desire to help.
I still don't use the hotmail account I got five years ago, because there is no way to stop advertising emails from "staff". They can't be filtered, and have no reply buttons. MS, as usual, are hypocrites about their criminal activity.
...is all about bragging about your method of searching online blogs......cribbing memes......and knowing where to find all of the State of the Union addresses since 1790...
If they'd just gone with the existing, working standard for Japanese HDTV (maybe with necessary compatibility adjustments and maybe incremental quality improvements) we'd have had HD sets below $1k before the Millennium.
Instead, we got a "standard" that was a combination of 6 competing standards and a system that will be supported in all the different permutations and never actually look like it's been standardized.
The cost of building TVs to work with all those permutations (because you know the end-user will never accept being unable to see Matlock reruns; or rather, the advertisers will never accept that the end-user will have an hour to not watch commercials) has resulted in TVs that are hideously expensive despite being poor in amenities (beyond the HD, of course).
Any company that doesn't have this in place already as either a copyright-infringement policy or an unnecessary burden on resources is too dumb to read the RIAA's threats anyway.
I've been talking for 8 years about the decrepitude, hypocrisy, and lameness of Sun. They blew the game with Solaris (a bad bells-and-whistles commercial repackaging of Unix), and proceeded to spend the rest of the '90s sucking hind tit instead of leading. McNealy didn't want to beat Bill Gates, he wanted to be Bill Gates. In the end, Sun is just a distro house that builds its own hardware and doesn't have even the juice IBM had at its worst.
Older men have money. Women enjoy sex, but they're really after economic security for their offspring. In the other direction, older men know they can provide for the children of any aged woman, so they choose entirely for sex. That's why the skew is the way it is.
The reporting, whining, and handwringing over Slammer has cost me more than the virus did. I saw zero downtime from the virus, but wading through this wailing has taken up valuable time.
THE INTERNET IS NOT SECURE
Go back to your pr0n. There's nothing to see here.
Slashdot Mirror
I hate hate, but I hate those that hate hate even more. And hats. Hats really piss me off.
Man, I hate posts like that.
Sorry, it's the = operator as in
timeBox.Text = "...";
where timeBox is a System.Windows.Forms.TextBox control.
I wrote a dinky little stopwatch app (no networking involved) using the System.Timer class that has a reset button that stops the timer and sets the display to 0. But the elapsedEventHandler somehow gets called after the reset button changes the display, and sets the display to the current timer value. I even inserted a variable that gets cleared first thing in the reset-button handler and wrapped the timer event handler code in it, and the timer handler still updates the display after the reset handler has run. It became apparent when I set the timer to refresh the display every few milliseconds. If I set the refresh interval somewhat higher (100 ms or so) I no longer have the patience needed to keep clicking buttons until it shows up, so maybe it goes away.
/. says 'Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted.'
The only way this could happen is if the display update code inside of the = operator for editBox allows the two values to get mixed up. I'm guessing there's some message passing going on in there, and XP and/or the CLR are hosing me.
I'd post the code (the problem is reduced to about 30 lines) but
If I had the same insight into the source of the crash, yes. For every new problem.
But Windows' default behavior (especially in Win95) is to lock up hard or BSOD, leaving the user with no information. Hit the reset button, wait for the disk check to finish, and try to remember what you were doing before it barfed.
NT was the first MS OS that had the capability of keeping the OS running if a program crashed, and XP is the first one that actually does something with the crash dump.
So Bill's statistic wasn't saying what he was saying it was saying.
Ever looked in one of those XP dumps? MS already has copious information on my config (registration sent it), and a core dump can tell an experienced programmer who has knowledge of the code quite a bit.
But I don't expect MS to put those people on the dump-pile team. For the OE thing, I got email from a support center in China. Went back and forth for a couple of emails and even reinstalled the OS and OE and determined that neither of those repairs the parts of the OE registry that the original install of XP had miscommunicated with. No more OE for me. So I started using Outlook. But it doesn't play well. It still doesn't send mail from other apps unless an instance of Outlook is running in the background.
I'd use Netscape mail, but I'd have to install Netscape, and I don't want to, because it went off the rails about three years ago. I have IE and Phoenix.
Which brings us back to bugzilla. I reported a bug to those clowns, and they took their sweet time on it, then told me it was misclassified and closed it. So I resubmitted it, and a couple of weeks later was told it was misclassified again, so they closed it. Each time, they had to analyze it to find the cause, to decide it was misclassified. I submitted it a third time and haven't heard back. That was four months ago or so. So there's a bug in bugzilla: the ass-heads who think they're doing the world a favor by working the bug list and don't want to be bothered acting like they're performing customer service. Other than that, I kind of like Phoenix (soon to be named something else). It's faster in some ways, slower in others, and the tab controls are great for getting info from sites behind a long list of selections (eBay, FARK, Google, etc.) while continuing to read the list.
And complaining isn't cool. It marks one as a whiner. Bill is just trying to justify his aloof attitude towards his bugs.
It's not the OS. MS apps (Outlook (not OE, which won't run at all), IE, etc.) tend to crap out, and XP catches them and does a dump and phones it home.
XP itself is nearly bulletproof, as far as I can see. Despite the race conditions when using C#.
Bill thinks it's cool to waggle back and forth in his chair like an unloved monkey.
What are the other 99% of calls about? Oh yeah. Crap documentation that tells you the obvious half of what the tool or call does, but doesn't bother to tell you what its actual behavior or use is.
I wonder if he's counting the 3-10 times a week my XP machine says it's sending a bug report back to Microsoft.
I've had to stop using Outlook Express entirely because it won't work, and Microsoft was no help.
And I've already run into race conditions in the event handling for C#.
People report bugs not because it's cool, but because they think Microsoft might just have a desire to help.
How wrong they are, Mr Gates seems to be saying.
I still don't use the hotmail account I got five years ago, because there is no way to stop advertising emails from "staff". They can't be filtered, and have no reply buttons. MS, as usual, are hypocrites about their criminal activity.
"Inanimate Carbon Rod"
New! From Mattel!
http://buzz.yahoo.com/
...is all about bragging about your method of searching online blogs... ...cribbing memes... ...and knowing where to find all of the State of the Union addresses since 1790...
--Blair
"AAAAaaaaaaaayyyyyyyyyyyyyy..."
Google keeps their site clean and fast. They cruft it up as little as they reasonably can. Yahoo is a clot. Overture who?
"routinely sweep a 30-mile box"
.0015 h = 5.4 s
"20,000 mph"
"softball"
30 miles / 20,000 mph =
So, basically, the tech on the radar will have enough time to tell his supe that the spacecraft is about to be annihilated.
Send in Captain Quark.
If they'd just gone with the existing, working standard for Japanese HDTV (maybe with necessary compatibility adjustments and maybe incremental quality improvements) we'd have had HD sets below $1k before the Millennium.
Instead, we got a "standard" that was a combination of 6 competing standards and a system that will be supported in all the different permutations and never actually look like it's been standardized.
The cost of building TVs to work with all those permutations (because you know the end-user will never accept being unable to see Matlock reruns; or rather, the advertisers will never accept that the end-user will have an hour to not watch commercials) has resulted in TVs that are hideously expensive despite being poor in amenities (beyond the HD, of course).
They didn't do it in release 0.5, btw.
They only said in 0.5 (scroll down to items 14 & 15) that they would do it in the future.
The codename for the 0.6 beta is "Glendale", but I'm not downloading it just to see what's inside. Maybe after dinner.
Personally, I think they should change the name to Pheonix and tell Phoenix to go shove an EPROM up their ass.
Any company that doesn't have this in place already as either a copyright-infringement policy or an unnecessary burden on resources is too dumb to read the RIAA's threats anyway.
I've been talking for 8 years about the decrepitude, hypocrisy, and lameness of Sun. They blew the game with Solaris (a bad bells-and-whistles commercial repackaging of Unix), and proceeded to spend the rest of the '90s sucking hind tit instead of leading. McNealy didn't want to beat Bill Gates, he wanted to be Bill Gates. In the end, Sun is just a distro house that builds its own hardware and doesn't have even the juice IBM had at its worst.
Actually, man doesn't care so much about niches any more, except as they can be destroyed to make way for comfortable surroundings.
Because why should the users of the largest number of chips on Earth get better performance for the programs they write.
The first person who writes and validates a working, bulletproof software system for collecting votes wins $$billions.
That's the kind of patriotism we need.
Older men have money. Women enjoy sex, but they're really after economic security for their offspring. In the other direction, older men know they can provide for the children of any aged woman, so they choose entirely for sex. That's why the skew is the way it is.
The reporting, whining, and handwringing over Slammer has cost me more than the virus did. I saw zero downtime from the virus, but wading through this wailing has taken up valuable time.
THE INTERNET IS NOT SECURE
Go back to your pr0n. There's nothing to see here.
Just what is the allure of obsessive resource management?