For a moment I thought he had something do with the backslash that separates directories in M$, the one they got changed from the frontslash so as to cause confusion between a frontslash and backslash (I know many Windoze lusers who call these backwards) and introduce terms such as reverse-backslash. No, this was the good guy. What a relief.
they have done a great job of improving it over the next few years Since you seem to be able to look into the future, can you please tell us when Jeremy is going to win that lottery?
I don't know this first-hand, but I am pretty sure that the response to the next question is also meant to be a joke. I don't want you to worry when you get to that part of the post. Fear not, he Jeremy does not work for MicroSoft.
I noticed several replies that said they had registered just to reply to that thread, which I found a little strange until I realized that you have to *pay* to be a member of this forum.
I have been using cygwin at least since b12; as a user, not as a developer. That is, I don't develop software using gcc and all, I just use bash and the other tools. I have found this to be hugely beneficial, because I can do many things much faster with bash and awk and sed and grep then I can them with... err.... I don't know....
Care to explain why you think Cygwin is "an intuitive way"?
About five years ago I realized that MicroSoft sets the computer user community back by about 10 years. The reason is that they provide features that don't really work. Right now we have Windows that would some times not maximize, a task manager that sometimes cannot kill a process, an explorer that hangs and needs to be restarted by hand and an OS that some time is not be able to shut-down. By contrast, I claimed to friends in 1997, if all this was done on more stable platforms -- Linux for example -- they would be late in coming and it would be some time before the grandma can send the pictures to the family by e-mail but the technology will be dependable when it is available. This I believe to be one of the greatest harm M$ has done -- created features that don't really work. Most computer uses believe that the computer does need to shut down every night and that it does need to keep getting slow as time passes. But I am happy to see that the features are becoming available in more stable environments and that these are taking less then 10 years to catch up.
I still have faith. Some day the computers will work as they aught to.
If haven't RTFA (and I won't) but the post here is not saying that the exploits are caused by the patches but that patches expose the vulnerabilities. This means is that the people who discover vulnerabilities inform M$ of them instead of exploiting them. Very nice of them, but I find that hard to believe. Are there examples of exploits that came out before their respective patches did? How does it happen is the OSS world? I know that vulnerabilities are discovered (and published) and patches are released very soon after that. Are there exploits that happen within that short time? The reason for this is that the vulnerabilities are also open. In case of M$, they are not.
A followup question: Does it make sense to capture analog (Hi8) and then convert to digital? Is that better value for money? Some digital midrange camera I saw (can recall the brandname) was rather slow at auto-focus etc.
From TFA: Since I brought my new purchase home, my IBM T-40 has been hiding in the corner.
I can pick up the T-40 and provide it a nice home with caring parents. Heck, I'll even throw in a free wash & wax job for your ferrari.
Most recently, Windows NT was released again as Windows Server 2003. Before that it was released again as Windows XP and before that by the loveable name of W2K. Hmmm. You asked when. Sorry, I don't know the dates.
Reminds me of the technologies that never die/should die/should not have died discussion from yesterday.
Ten years ago I used to voice-chat with my friends in US from India using powwwow from TribalVoice. It used to work pretty well, over the low band-width and even full-duplex. Today, google can find a match but my DNS cannot find its number.
Yahoo has had voice/video chat for a long time now. My alomost-computer-illeterate Dad has learnt to use it so he can look at his granddaughter at the rate of 1 fps, low resolution. Works for him.
from buying a cell phone is that you are unable to find a plain vanilla phone that lets you make calls and store numbers exactly the point of the story.
The security bulletin says: Caveats: None Did you consider telling me a bunch of my bookmarks will not work anymore, nevermind that they depended on "microsoft extensions"?
And can someone please explain why these issues are of only moderate to important (not critical) severity in Windows Server 2003?
I was always amazed at how a Windows SP would replace most executables, even stuff like calc.exe etc. Either their dependencies are horribly mixed up or its "lets be safe and replace everything".
Slashdot Mirror
For a moment I thought he had something do with the backslash that separates directories in M$, the one they got changed from the frontslash so as to cause confusion between a frontslash and backslash (I know many Windoze lusers who call these backwards) and introduce terms such as reverse-backslash.
No, this was the good guy. What a relief.
What time of the day are you horniest?
circa $100
I know time is money, but really, this is taking it too far, or should I say too costly?
they have done a great job of improving it over the next few years
Since you seem to be able to look into the future, can you please tell us when Jeremy is going to win that lottery?
I don't know this first-hand, but I am pretty sure that the response to the next question is also meant to be a joke. I don't want you to worry when you get to that part of the post. Fear not, he Jeremy does not work for MicroSoft.
I noticed several replies that said they had registered just to reply to that thread, which I found a little strange until I realized that you have to *pay* to be a member of this forum.
I have been using cygwin at least since b12; as a user, not as a developer. That is, I don't develop software using gcc and all, I just use bash and the other tools. I have found this to be hugely beneficial, because I can do many things much faster with bash and awk and sed and grep then I can them with... err.... I don't know....
Care to explain why you think Cygwin is "an intuitive way"?
About five years ago I realized that MicroSoft sets the computer user community back by about 10 years. The reason is that they provide features that don't really work. Right now we have Windows that would some times not maximize, a task manager that sometimes cannot kill a process, an explorer that hangs and needs to be restarted by hand and an OS that some time is not be able to shut-down.
By contrast, I claimed to friends in 1997, if all this was done on more stable platforms -- Linux for example -- they would be late in coming and it would be some time before the grandma can send the pictures to the family by e-mail but the technology will be dependable when it is available.
This I believe to be one of the greatest harm M$ has done -- created features that don't really work. Most computer uses believe that the computer does need to shut down every night and that it does need to keep getting slow as time passes.
But I am happy to see that the features are becoming available in more stable environments and that these are taking less then 10 years to catch up.
I still have faith. Some day the computers will work as they aught to.
If haven't RTFA (and I won't) but the post here is not saying that the exploits are caused by the patches but that patches expose the vulnerabilities.
This means is that the people who discover vulnerabilities inform M$ of them instead of exploiting them. Very nice of them, but I find that hard to believe. Are there examples of exploits that came out before their respective patches did?
How does it happen is the OSS world? I know that vulnerabilities are discovered (and published) and patches are released very soon after that. Are there exploits that happen within that short time? The reason for this is that the vulnerabilities are also open. In case of M$, they are not.
- Write down the problem.
- Think very hard.
- Write down the solution.
It has worked for me many many timesDidn't you know? A restart cleanses the soul of the computer and therefore the problems go away.
I posted this exact same story about 12 hours earlier, but it got rejected!
Anyway, good to get this out in the light.
A followup question: Does it make sense to capture analog (Hi8) and then convert to digital? Is that better value for money? Some digital midrange camera I saw (can recall the brandname) was rather slow at auto-focus etc.
From TFA: Since I brought my new purchase home, my IBM T-40 has been hiding in the corner.
I can pick up the T-40 and provide it a nice home with caring parents. Heck, I'll even throw in a free wash & wax job for your ferrari.
When was windows NT released again ?
Most recently, Windows NT was released again as Windows Server 2003. Before that it was released again as Windows XP and before that by the loveable name of W2K.
Hmmm. You asked when. Sorry, I don't know the dates.
Reminds me of the technologies that never die/should die/should not have died discussion from yesterday.
Ten years ago I used to voice-chat with my friends in US from India using powwwow from TribalVoice. It used to work pretty well, over the low band-width and even full-duplex. Today, google can find a match but my DNS cannot find its number.
Yahoo has had voice/video chat for a long time now. My alomost-computer-illeterate Dad has learnt to use it so he can look at his granddaughter at the rate of 1 fps, low resolution. Works for him.
So what market share does AOL control? 80%?
from buying a cell phone is that you are unable to find a plain vanilla phone that lets you make calls and store numbers exactly the point of the story.
The security bulletin says:
Caveats: None
Did you consider telling me a bunch of my bookmarks will not work anymore, nevermind that they depended on "microsoft extensions"?
And can someone please explain why these issues are of only moderate to important (not critical) severity in Windows Server 2003?
I was always amazed at how a Windows SP would replace most executables, even stuff like calc.exe etc. Either their dependencies are horribly mixed up or its "lets be safe and replace everything".