All of the places I have searched on the net list HP #15 @ ~ $30 and HP #78 at ~$35 & ~$55. Where'd you find a black for $15? Just curious because I just bought this and haven't bought ink yet, and this article has me freaked out.
"Usage Note: Decimate originally referred to the killing of every tenth person, a punishment used in the Roman army for mutinous legions. Today this meaning is commonly extended to include the killing of any large proportion of a group. Sixty-six percent of the Usage Panel accepts this extension in the sentence The Jewish population of Germany was decimated by the war, even though it is common knowledge that the number of Jews killed was much greater than a tenth of the original population. However, when the meaning is further extended to include large-scale destruction other than killing, as in The supply of fresh produce was decimated by the nuclear accident at Chernobyl, only 26 percent of the Panel accepts the usage."
This usage does not include actually killing users of Windows or the people who make it, which puts it in the latter 26% category, so it's probably not a great term to use in this context. Ah, english.
Offtopic, but this is my opinion dammit
on
4l-j4z333ra 0wn3d
·
· Score: 1
To all those against the war:
These Fedayeen Sadaam ***are*** the same as Al-Quaeda. There are 40,000 of these fuckers. Suicidal, homicidal, amoral, powerful, connected. We//are// fighting the terrorists. A whole damn country-ful of them.
To those who are from Arab countries or support them:
You must admit your people come across as awfully savage and unloveable. Fix the problem.
To those who will claim that the US actions are morally equivalent to the terrorists: Yeah, so what. Life's a bitch, get over it.
Our POWs are dead meat, fuck 'em, move on. There's only one winner, last man standing.
A positive way to spin it (or, "How I learned to stop worrying and Love Free Software:")
One way to look at this as it further reduces the "gene pool" for Windows software, limits innovative products, and makes it more boring. People forced to live with the same boring-assed apps that stay strictly within the narrow limits of what works in Windows will eventually pine for the richness of what used to be in the Shareware community, and only find it in Open source. That's why I switched.
It's hard to argue that argue that businesses won't like boring, stable software. But *people* like rich, exciting, and new, which by definition requires a little lovin'. The latter is the market-driver.
Project has huge dependencies on Office but not vice versa. Typically Project team picks up office bits around 90 days after Office stabilizes..MSP files are Jet databases (Access). There is always a new version of Project released based on the current Office codebase.
All of the common code is in MSO9.dll, or MSO10.dll, whatever, as well as "external" dependencies like MSXML.dll or MDAC from Web Data, or Trident (MSHTML). I'm not going to claim that you can't GPL Project without releasing the rest (don't know enough), but I can tell you the codebases are very intertwined. Does GPL still make sense given this info?
Basically all Project is is a specialized Access database application. (BTW, did you know that Exchange storage engine and Microsoft Access are both based on Jet? Exchange == Jet Blue. Access == Jet Red. And DHCP and Crypto DBs are stored in.EDB files, which shares Jet ancestry.) Funny, huh?
Y'all can mod this as a troll all you want, but that's totally not my intention.
These are the facts (who knows why):
(1) Google usually takes you to the information you want. (2) Few months back, last time google got lots of big press, for about two months my searches stopped taking me where I wanted to go and started to take me to more dubious places. Around this time there was a whole lot of press about google monkeying with the Page Rank system, how they wouldn't discuss it, etc. All I know is, during that time, the quality of my searches decreased dramatically. (3) After a while, the quality of my searches went back up. Again, who knows why.
When I say "quality of my searches went down" I mean that instead of going to the DEFINIITIVE source of some information I searched for (unless I was extremely specific, like you used to have to be pre-google), I was much more likely to be taken to some large-scale commercial and less-definitive source of information. It might not have been google doing it specifically, but whatever, I came damn close to saying google has "jumped the shark."
And Google will fail too. A few months back I noticed my "Web" searches were taking me less and less to the "right" page and more and more often to some clearinghouse page that some sponsored link wanted me to go to. That's stopped a bit for now, but if google IPO's, it will become rampant then people will abandon google.
Face it, nothing on the internet is ever going to make a whole pile of money. The more popular you get the greater the likelihood of impending failure.
I played real-live D&D about four times. Three times in Junior High, with a bunch of fellow nerds. That was fun! Once, in college, with a bunch of stoner friends, smoking tons of weed, eating shrooms, and being WAY too into it. Anybody else play a game like the latter? I just went for the weed; these guys took the game way seriously, and all the psychedilics kind of added an extra seriousness to their game. D&D wasn't always dweeby.
Windows has encrypting filesystem built in, which if you store your private keys on something like a smartcard will be secure if attacker has physical access to the drive.
If you have secure data or source code on your drive, you should set that bit. It's under File Attributes (Advanced), like Compressed.
Judging from the flood of stories the past couple of days, it's obvious that Andover has replaced the editors with a bot that searches the Net for "Microsoft" and "Open Source".
In IE you can trap the NewWindow2 argument and optionally give it the IDispatch of a WebBrowser2 to open into. That's how the popup blocker I wrote works. At the worst case I'll just have to open the crap into a hidden window which is then killed. Best case is I invent the next replacement for the internet, because this model has clearly broken down!
http://microsoft.com/windows.netserver/default.msp x
Windows.NET Server 2003 is in Release Candidate right now. Look for it in April.
After Windows 2000, in late 2000 and 2001, you used to get "Whistler Beta 1" &c. builds. This code base was forked to become Windows XP and Windows.NET Server. Windows XPSP1 essentially merges the trees again.
They're just going to do the same thing for Longhorn and Blackcombe.
ESR posts unattributed documents on his own site. This guy offers his "expert" opinion on a case to which he was not a party. And the ABM camp posts it like these are authoritative sources.
You need to stop these straw man arguments, and inventing your own news and then publishing it. Just because the mainstream computer press is too dumb to realize you're making up the agenda and then reporting on it, doesn't mean the rest of us don't see through it.
Now, before y'all get out that flamebait thing, tell me how I'm wrong.
But as a Windows programmer you have to know how hopelessly amateurish this makes you all sound?
I guess since Windows sucks so bad at shitloads of processes, programming on 4 or more CPUs, you really quickly have to learn how to write multithreaded code that works, and correctly. You poor Unix guys are struggling through something we all went through years ago -- learning how to think more sophisticated than a single thread of control correctly.
CPU-bound tasks (spinning in a loop calculating PI) are easy to saturate all the resources using any model. How come y'all are switching to a thread-based model now? Was the other way running out of steam?
-1 Redundant. Void where prohibited is listed twice.
about 24 hours straight (once); 100/hr weeks lots
on
Programming Marathons?
·
· Score: 2, Interesting
Once in 1999, when I took six months off, I started around 8 am and stopped coding at 8 am next day.
When I was 24 I used to do a lot of 100 hr weeks; once after my third 16 hour workday I had a "panic attack"; it felt like a stroke; left side numb; couldn't move left arm; felt like I couldn't breath. I basically learned at that point working craploads of hours doesn't mean you're a hero; it actually means you're an inefficient person who cannot complete their job in a normal 40 hour week.
If you want to earn some REAL geek cred, learn how to do what you do in a normal 8 hour day. Trust me, it's far more rewarding to be efficient. Plus it's just so cool to be done with your shit by 5pm while everybody else is there all night:-)
BTW I recommend taking six months off if you ever can. I just paid my rent in advanced, coded, fished, and went to bars. I was broke as hell by the end of it, but I wouldn't trade that experience for nothing.
I also kept my Win2k boxes up for weeks, and do the same for XP. It's called "knowing how the thing works". You need to spend as much time tweaking and setting up that Windows box as you do that Linux box.
For instance, you should log out occasionally, kill.exe bad processes, apply the latest patches, stop a lot of crap services enabled by default, and generally know what happens when what happens.
Really, I get a kick out of watching y'all complain about Windows stability, because at least 50% of the complaints are bogus.
Now, to not troll, sometimes you are right: You can't keep a Windows box up indefinitely because some crap patch comes out every couple weeks.
We did *exactly* the same thing in college... A friend was testing it out b/c he was going to use it at a rock show. It puts out *a lot* of smoke.
He got a misdimeanor from the fire dept. When they knocked on the door, he tried to play it off like he was in the bathroom and didn't know what had happened.
Oh, one thing: these things leave oily residue all over *everything*....
I've created over 200,000 process on a PIII 550 laptop with 256 mb of ram running Windows XP. Of course, it took a while (swapping).
The process is called nothing.exe. Source Code: int WinMain(...) {Sleep(INFINITE);}
I work at a lab, so I also ran it on a Compaq 8-way with 4-GB of ram. It worked but I don't remember how fast it went.
However, there is a big gnarley limit in Windows that will limit the # of processes: the amount of memory allocated to virtual desktops or something. We researched it -- Look it up. This is why you get limited to a few thousand processes or threads if they all do GUI stuff. The bad thing is basically any function you call in user32 will register the thread as a GUI thread. It explains it all in the book Inside Windows 2000.
Not meaning to troll, I'm just going to share basic fact: It sucks that Windows threads are so expensive, but tens of thousands of threads *DOES* suck (read: thread per client) on Windows. However, this is not the same thing as saying Windows doesn't scale -- you just have to code it differently. (Check out how many SQL Server uses when it's processing thousands of clients.) Stuff like IO Completion ports, AWE memory, and Scatter/Gather IO is the way that you have to go.
Just because you *can* create hundreds of thousands of threads, doesn't mean it's a good idea or that your app won't run like shit on a 32-CPU machine!
Slashdot Mirror
All of the places I have searched on the net list HP #15 @ ~ $30 and HP #78 at ~$35 & ~$55. Where'd you find a black for $15? Just curious because I just bought this and haven't bought ink yet, and this article has me freaked out.
Here's a segment from dictionary.com:
"Usage Note: Decimate originally referred to the killing of every tenth person, a punishment used in the Roman army for mutinous legions. Today this meaning is commonly extended to include the killing of any large proportion of a group. Sixty-six percent of the Usage Panel accepts this extension in the sentence The Jewish population of Germany was decimated by the war, even though it is common knowledge that the number of Jews killed was much greater than a tenth of the original population. However, when the meaning is further extended to include large-scale destruction other than killing, as in The supply of fresh produce was decimated by the nuclear accident at Chernobyl, only 26 percent of the Panel accepts the usage."
This usage does not include actually killing users of Windows or the people who make it, which puts it in the latter 26% category, so it's probably not a great term to use in this context. Ah, english.
To all those against the war:
//are// fighting the terrorists. A whole damn country-ful of them.
These Fedayeen Sadaam ***are*** the same as Al-Quaeda. There are 40,000 of these fuckers. Suicidal, homicidal, amoral, powerful, connected. We
To those who are from Arab countries or support them:
You must admit your people come across as awfully savage and unloveable. Fix the problem.
To those who will claim that the US actions are morally equivalent to the terrorists: Yeah, so what. Life's a bitch, get over it.
Our POWs are dead meat, fuck 'em, move on. There's only one winner, last man standing.
A positive way to spin it (or, "How I learned to stop worrying and Love Free Software:")
One way to look at this as it further reduces the "gene pool" for Windows software, limits innovative products, and makes it more boring. People forced to live with the same boring-assed apps that stay strictly within the narrow limits of what works in Windows will eventually pine for the richness of what used to be in the Shareware community, and only find it in Open source. That's why I switched.
It's hard to argue that argue that businesses won't like boring, stable software. But *people* like rich, exciting, and new, which by definition requires a little lovin'. The latter is the market-driver.
Project has huge dependencies on Office but not vice versa. Typically Project team picks up office bits around 90 days after Office stabilizes.
All of the common code is in MSO9.dll, or MSO10.dll, whatever, as well as "external" dependencies like MSXML.dll or MDAC from Web Data, or Trident (MSHTML). I'm not going to claim that you can't GPL Project without releasing the rest (don't know enough), but I can tell you the codebases are very intertwined. Does GPL still make sense given this info?
Basically all Project is is a specialized Access database application. (BTW, did you know that Exchange storage engine and Microsoft Access are both based on Jet? Exchange == Jet Blue. Access == Jet Red. And DHCP and Crypto DBs are stored in
Y'all can mod this as a troll all you want, but that's totally not my intention.
These are the facts (who knows why):
(1) Google usually takes you to the information you want.
(2) Few months back, last time google got lots of big press, for about two months my searches stopped taking me where I wanted to go and started to take me to more dubious places. Around this time there was a whole lot of press about google monkeying with the Page Rank system, how they wouldn't discuss it, etc. All I know is, during that time, the quality of my searches decreased dramatically.
(3) After a while, the quality of my searches went back up. Again, who knows why.
When I say "quality of my searches went down" I mean that instead of going to the DEFINIITIVE source of some information I searched for (unless I was extremely specific, like you used to have to be pre-google), I was much more likely to be taken to some large-scale commercial and less-definitive source of information. It might not have been google doing it specifically, but whatever, I came damn close to saying google has "jumped the shark."
And Google will fail too. A few months back I noticed my "Web" searches were taking me less and less to the "right" page and more and more often to some clearinghouse page that some sponsored link wanted me to go to. That's stopped a bit for now, but if google IPO's, it will become rampant then people will abandon google.
Face it, nothing on the internet is ever going to make a whole pile of money. The more popular you get the greater the likelihood of impending failure.
+1 Fell out of my chair
well, at least I had it for two months before it got obsoleted..
I played real-live D&D about four times. Three times in Junior High, with a bunch of fellow nerds. That was fun! Once, in college, with a bunch of stoner friends, smoking tons of weed, eating shrooms, and being WAY too into it. Anybody else play a game like the latter? I just went for the weed; these guys took the game way seriously, and all the psychedilics kind of added an extra seriousness to their game. D&D wasn't always dweeby.
Windows has encrypting filesystem built in, which if you store your private keys on something like a smartcard will be secure if attacker has physical access to the drive.
If you have secure data or source code on your drive, you should set that bit. It's under File Attributes (Advanced), like Compressed.
The Jet engine supports transactions, nested transactions, and distributed transactions.
As are file system filter drivers, which is how things like Encrypting File Systed and Compressed File System are implemented.
"Adventures of Buckaroo Banzai Across the 8th Dimension, The"
How can you forget the alien with the Jamaican accent?
-
"Wherever you go, there you are."
I've had customers bring me DLT tape backups of their databases, and 4 out of 5 times I can't get the tape to read the catalog.
Tape works great same system same system, but it quickly becomes an arcane science beyond that.
Judging from the flood of stories the past couple of days, it's obvious that Andover has replaced the editors with a bot that searches the Net for "Microsoft" and "Open Source".
It's SO insightful.
In IE you can trap the NewWindow2 argument and optionally give it the IDispatch of a WebBrowser2 to open into. That's how the popup blocker I wrote works. At the worst case I'll just have to open the crap into a hidden window which is then killed. Best case is I invent the next replacement for the internet, because this model has clearly broken down!
http://microsoft.com/windows.netserver/default.msp x
Windows.NET Server 2003 is in Release Candidate right now. Look for it in April.
After Windows 2000, in late 2000 and 2001, you used to get "Whistler Beta 1" &c. builds. This code base was forked to become Windows XP and Windows.NET Server. Windows XPSP1 essentially merges the trees again.
They're just going to do the same thing for Longhorn and Blackcombe.
ESR posts unattributed documents on his own site. This guy offers his "expert" opinion on a case to which he was not a party. And the ABM camp posts it like these are authoritative sources.
You need to stop these straw man arguments, and inventing your own news and then publishing it. Just because the mainstream computer press is too dumb to realize you're making up the agenda and then reporting on it, doesn't mean the rest of us don't see through it.
Now, before y'all get out that flamebait thing, tell me how I'm wrong.
But as a Windows programmer you have to know how hopelessly amateurish this makes you all sound?
I guess since Windows sucks so bad at shitloads of processes, programming on 4 or more CPUs, you really quickly have to learn how to write multithreaded code that works, and correctly. You poor Unix guys are struggling through something we all went through years ago -- learning how to think more sophisticated than a single thread of control correctly.
CPU-bound tasks (spinning in a loop calculating PI) are easy to saturate all the resources using any model. How come y'all are switching to a thread-based model now? Was the other way running out of steam?
Honestly curious...
-1 Redundant. Void where prohibited is listed twice.
Once in 1999, when I took six months off, I started around 8 am and stopped coding at 8 am next day.
:-)
When I was 24 I used to do a lot of 100 hr weeks; once after my third 16 hour workday I had a "panic attack"; it felt like a stroke; left side numb; couldn't move left arm; felt like I couldn't breath. I basically learned at that point working craploads of hours doesn't mean you're a hero; it actually means you're an inefficient person who cannot complete their job in a normal 40 hour week.
If you want to earn some REAL geek cred, learn how to do what you do in a normal 8 hour day. Trust me, it's far more rewarding to be efficient. Plus it's just so cool to be done with your shit by 5pm while everybody else is there all night
BTW I recommend taking six months off if you ever can. I just paid my rent in advanced, coded, fished, and went to bars. I was broke as hell by the end of it, but I wouldn't trade that experience for nothing.
I also kept my Win2k boxes up for weeks, and do the same for XP. It's called "knowing how the thing works". You need to spend as much time tweaking and setting up that Windows box as you do that Linux box.
For instance, you should log out occasionally, kill.exe bad processes, apply the latest patches, stop a lot of crap services enabled by default, and generally know what happens when what happens.
Really, I get a kick out of watching y'all complain about Windows stability, because at least 50% of the complaints are bogus.
Now, to not troll, sometimes you are right: You can't keep a Windows box up indefinitely because some crap patch comes out every couple weeks.
We did *exactly* the same thing in college... A friend was testing it out b/c he was going to use it at a rock show. It puts out *a lot* of smoke.
He got a misdimeanor from the fire dept. When they knocked on the door, he tried to play it off like he was in the bathroom and didn't know what had happened.
Oh, one thing: these things leave oily residue all over *everything*....
I've created over 200,000 process on a PIII 550 laptop with 256 mb of ram running Windows XP. Of course, it took a while (swapping).
The process is called nothing.exe. Source Code: int WinMain(...) {Sleep(INFINITE);}
I work at a lab, so I also ran it on a Compaq 8-way with 4-GB of ram. It worked but I don't remember how fast it went.
However, there is a big gnarley limit in Windows that will limit the # of processes: the amount of memory allocated to virtual desktops or something. We researched it -- Look it up. This is why you get limited to a few thousand processes or threads if they all do GUI stuff. The bad thing is basically any function you call in user32 will register the thread as a GUI thread. It explains it all in the book Inside Windows 2000.
Not meaning to troll, I'm just going to share basic fact: It sucks that Windows threads are so expensive, but tens of thousands of threads *DOES* suck (read: thread per client) on Windows. However, this is not the same thing as saying Windows doesn't scale -- you just have to code it differently. (Check out how many SQL Server uses when it's processing thousands of clients.) Stuff like IO Completion ports, AWE memory, and Scatter/Gather IO is the way that you have to go.
Just because you *can* create hundreds of thousands of threads, doesn't mean it's a good idea or that your app won't run like shit on a 32-CPU machine!
Look at the availability date: 03/05/03. That's six months from now.