If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#16
|
|||
|
|||
XP SP3 Details?
Unknown added these comments in the current discussion du jour
.... Look closely at all the postings in this group. You'll be amazed that most problems are not caused by MS but by Non MS programs, reg cleaners, and virus detect/scan protection? programs. That may well be true, but the major developers are wed at the hips body and soul to the God of Microsoft because they must play ball or risk losing their certification. But, it is certainly true that reg cleaners in the hands of the novices will wreck an otherwise good system and are more harm than good most of the time. -- HP, aka Jerry |
Ads |
#17
|
|||
|
|||
XP SP3 Details?
Wed at the hips----------???? Supposing you wrote the OS. How would you
control it and/or keep your customers happy. Many companies write programs to run with XP (the OS) and when a problem occurs, MS is immediately blamed. Be objective. "HEMI-Powered" wrote in message ... Unknown added these comments in the current discussion du jour ... Look closely at all the postings in this group. You'll be amazed that most problems are not caused by MS but by Non MS programs, reg cleaners, and virus detect/scan protection? programs. That may well be true, but the major developers are wed at the hips body and soul to the God of Microsoft because they must play ball or risk losing their certification. But, it is certainly true that reg cleaners in the hands of the novices will wreck an otherwise good system and are more harm than good most of the time. -- HP, aka Jerry |
#18
|
|||
|
|||
XP SP3 Details?
"Ken Blake, MVP" wrote: No. No announcements have been made. It is reasonable to expect that it will include as the post-SP2 updates, possibly plus some others. We'll see when it happens. Anything before that is rumor, and again I caution you not to depend on rumors. "SP3 for Windows XP Professional is currently planned for 1H CY2008. This date is preliminary." http://www.microsoft.com/windows/lif...vicepacks.mspx |
#19
|
|||
|
|||
XP SP3 Details?
"ANONYMOUS" wrote in message ... | "SP3 for Windows XP Professional is currently planned for 1H CY2008. | This date is preliminary." | | http://www.microsoft.com/windows/lif...vicepacks.mspx BTW, this is the third change MS has made to the date for SP3. And, they always say it's preliminary ;-) |
#20
|
|||
|
|||
XP SP3 Details?
On Tue, 14 Aug 2007 20:49:54 +0100, ANONYMOUS
wrote: "Ken Blake, MVP" wrote: No. No announcements have been made. It is reasonable to expect that it will include as the post-SP2 updates, possibly plus some others. We'll see when it happens. Anything before that is rumor, and again I caution you not to depend on rumors. "SP3 for Windows XP Professional is currently planned for 1H CY2008. This date is preliminary." http://www.microsoft.com/windows/lif...vicepacks.mspx As I said, no announcement has been made. "Currently planned" and "preliminary" does not amount to an announcement. It is very common that such dates turn out not to be met. -- Ken Blake, Microsoft MVP Windows - Shell/User Please Reply to the Newsgroup |
#21
|
|||
|
|||
XP SP3 Details?
ms not responsible even when the app is an ms app?
On 2007-08-14, Unknown wrote: Wed at the hips----------???? Supposing you wrote the OS. How would you control it and/or keep your customers happy. Many companies write programs to run with XP (the OS) and when a problem occurs, MS is immediately blamed. Be objective. "HEMI-Powered" wrote in message ... Unknown added these comments in the current discussion du jour ... Look closely at all the postings in this group. You'll be amazed that most problems are not caused by MS but by Non MS programs, reg cleaners, and virus detect/scan protection? programs. That may well be true, but the major developers are wed at the hips body and soul to the God of Microsoft because they must play ball or risk losing their certification. But, it is certainly true that reg cleaners in the hands of the novices will wreck an otherwise good system and are more harm than good most of the time. -- HP, aka Jerry |
#22
|
|||
|
|||
XP SP3 Details?
Tom Willett wrote: "ANONYMOUS" wrote in message ... | "SP3 for Windows XP Professional is currently planned for 1H CY2008. | This date is preliminary." | | http://www.microsoft.com/windows/lif...vicepacks.mspx BTW, this is the third change MS has made to the date for SP3. And, they always say it's preliminary ;-) Perhaps that is what "preliminary" means |
#23
|
|||
|
|||
XP SP3 Details?
From Webster's online;
Main Entry: 1pre·lim·i·nary Pronunciation: pri-'li-m&-"ner-E Function: noun Inflected Form(s): plural -nar·ies Etymology: French préliminaires, plural, from Medieval Latin praeliminaris, adjective, preliminary, from Latin prae- pre- + limin-, limen threshold : something that precedes or is introductory or preparatory: as a : a preliminary scholastic examination b plural, British : FRONT MATTER c : a preliminary heat or trial (as of a race) d : a minor match preceding the main event (as of a boxing card) -- ---- Crosspost, do not multipost http://www.blakjak.demon.co.uk/mul_crss.htm How to ask a question http://support.microsoft.com/kb/555375 How to Post http://www.dts-l.org/goodpost.htm ---------------------------------------------------------------------------------------------------------------------- "ANONYMOUS" wrote in message ... Tom Willett wrote: "ANONYMOUS" wrote in message ... | "SP3 for Windows XP Professional is currently planned for 1H CY2008. | This date is preliminary." | | http://www.microsoft.com/windows/lif...vicepacks.mspx BTW, this is the third change MS has made to the date for SP3. And, they always say it's preliminary ;-) Perhaps that is what "preliminary" means |
#24
|
|||
|
|||
XP SP3 Details?
Unknown added these comments in the current discussion du jour
.... Wed at the hips----------???? Supposing you wrote the OS. How would you control it and/or keep your customers happy. Many companies write programs to run with XP (the OS) and when a problem occurs, MS is immediately blamed. Be objective. Let's just say that I've been around MS more than long enough, all the way back to the original PC that didn't even have DOS, that came in with the XT, to understand them pretty well. I don't mean to be vindictively critical, but surely you will admit they have less than a stellar record of their own releases, they have a rep for hiding key parts of their various APIs even from those who buy their development packages all the way back to the SDK, reverse engineering of several versions of the major components of MS Office have been found to contain fairly large percentages of commands and API calls that seem not to be documented, and MS like all commercial companies reserves the rights to control its copyrighted software and give "guidance" to developers. I didn't say, BTW, that all problems are MS, I am not at all that naive and not at all an anti-MS bigot to believe that. Rogue and misbehaving applications, especially systems utilities of all kinds, are rampant throughout the 25 years since the first PC, they suffer from their own bugs, side-effects bugs, and the rush to bring new versions to market no matter what. This super competitiveness all the way around makes for not only strange bedfellows but interlocking dependencies that can make full diagnosis of major or even minor systems issue deceptively difficult. I hung up my programmer clothes circa 1995 or so, thus I am more than a little out-of-date for direct knowledge of whence I speak, but in monitoring this and many other NGs, I see no real signs of improvement, if anything, I think the situation is deteriorating. I'm sorry if you feel I am not being objective, let's just say that I am a pragmatist and always suspicious of extravagent claims from ANY developer on either side of problems. Thanks for listening. "HEMI-Powered" wrote in message ... Unknown added these comments in the current discussion du jour ... Look closely at all the postings in this group. You'll be amazed that most problems are not caused by MS but by Non MS programs, reg cleaners, and virus detect/scan protection? programs. That may well be true, but the major developers are wed at the hips body and soul to the God of Microsoft because they must play ball or risk losing their certification. But, it is certainly true that reg cleaners in the hands of the novices will wreck an otherwise good system and are more harm than good most of the time. -- HP, aka Jerry -- HP, aka Jerry |
#25
|
|||
|
|||
XP SP3 Details?
Tom Willett added these comments in the current discussion du
jour ... "ANONYMOUS" wrote in message ... | "SP3 for Windows XP Professional is currently planned for 1H | CY2008. This date is preliminary." | | http://www.microsoft.com/windows/lif...vicepacks.mspx BTW, this is the third change MS has made to the date for SP3. And, they always say it's preliminary ;-) Nobody pre-announces without caveats, not software, not hardware, not anything. Too much possibility of bad PR if the date is missed for any reason good, bad, or indifferent. I cannot fault MS for being vague about SP3, especially since they would much rather sell a Vista upgrade or a new PC with Vista installed than encourage it's installed base to stay on XP any longer than necessary. But, they will do an SP because it saves THEM manpower and money they'd rather put towards the next better mousetrap. -- HP, aka Jerry |
#26
|
|||
|
|||
XP SP3 Details?
Ken Blake, MVP added these comments in the current discussion du
jour ... "SP3 for Windows XP Professional is currently planned for 1H CY2008. This date is preliminary." http://www.microsoft.com/windows/lif...vicepacks.mspx As I said, no announcement has been made. "Currently planned" and "preliminary" does not amount to an announcement. It is very common that such dates turn out not to be met. Certainly cannot fault you or MS for this statement, which I highly agree with. If I may be allowed yet another car analogy, we do NOT announce future products unless and until there is a sales and marketing reason, e.g., at a major car show such as NAIAS where almost all the major new products for the fall season are shown for the first time. -- HP, aka Jerry |
#27
|
|||
|
|||
XP SP3 Details?
If indeed you were a programmer particularly a micro-programmer then you
should have enough experience to recognize the complexity of an operating system plus all the micro-code that operates the hardware. If you were in development you would know that regardless of the amount of testing some bugs will show up after release. How can you possibly be so critical of a few bugs? Compare today's PC's with those of just a few years ago. Be objective not emotional. "HEMI-Powered" wrote in message ... Unknown added these comments in the current discussion du jour ... Wed at the hips----------???? Supposing you wrote the OS. How would you control it and/or keep your customers happy. Many companies write programs to run with XP (the OS) and when a problem occurs, MS is immediately blamed. Be objective. Let's just say that I've been around MS more than long enough, all the way back to the original PC that didn't even have DOS, that came in with the XT, to understand them pretty well. I don't mean to be vindictively critical, but surely you will admit they have less than a stellar record of their own releases, they have a rep for hiding key parts of their various APIs even from those who buy their development packages all the way back to the SDK, reverse engineering of several versions of the major components of MS Office have been found to contain fairly large percentages of commands and API calls that seem not to be documented, and MS like all commercial companies reserves the rights to control its copyrighted software and give "guidance" to developers. I didn't say, BTW, that all problems are MS, I am not at all that naive and not at all an anti-MS bigot to believe that. Rogue and misbehaving applications, especially systems utilities of all kinds, are rampant throughout the 25 years since the first PC, they suffer from their own bugs, side-effects bugs, and the rush to bring new versions to market no matter what. This super competitiveness all the way around makes for not only strange bedfellows but interlocking dependencies that can make full diagnosis of major or even minor systems issue deceptively difficult. I hung up my programmer clothes circa 1995 or so, thus I am more than a little out-of-date for direct knowledge of whence I speak, but in monitoring this and many other NGs, I see no real signs of improvement, if anything, I think the situation is deteriorating. I'm sorry if you feel I am not being objective, let's just say that I am a pragmatist and always suspicious of extravagent claims from ANY developer on either side of problems. Thanks for listening. "HEMI-Powered" wrote in message ... Unknown added these comments in the current discussion du jour ... Look closely at all the postings in this group. You'll be amazed that most problems are not caused by MS but by Non MS programs, reg cleaners, and virus detect/scan protection? programs. That may well be true, but the major developers are wed at the hips body and soul to the God of Microsoft because they must play ball or risk losing their certification. But, it is certainly true that reg cleaners in the hands of the novices will wreck an otherwise good system and are more harm than good most of the time. -- HP, aka Jerry -- HP, aka Jerry |
#28
|
|||
|
|||
XP SP3 Details?
Also, ask yourself "why is the situation deteriorating". The advancement of
PC's has been absolutely phenomenal. Look what they do today compared to two years ago. Advancement???? Windows 95, 98, NT, XP, now Windows Vista. "HEMI-Powered" wrote in message ... Unknown added these comments in the current discussion du jour ... Wed at the hips----------???? Supposing you wrote the OS. How would you control it and/or keep your customers happy. Many companies write programs to run with XP (the OS) and when a problem occurs, MS is immediately blamed. Be objective. Let's just say that I've been around MS more than long enough, all the way back to the original PC that didn't even have DOS, that came in with the XT, to understand them pretty well. I don't mean to be vindictively critical, but surely you will admit they have less than a stellar record of their own releases, they have a rep for hiding key parts of their various APIs even from those who buy their development packages all the way back to the SDK, reverse engineering of several versions of the major components of MS Office have been found to contain fairly large percentages of commands and API calls that seem not to be documented, and MS like all commercial companies reserves the rights to control its copyrighted software and give "guidance" to developers. I didn't say, BTW, that all problems are MS, I am not at all that naive and not at all an anti-MS bigot to believe that. Rogue and misbehaving applications, especially systems utilities of all kinds, are rampant throughout the 25 years since the first PC, they suffer from their own bugs, side-effects bugs, and the rush to bring new versions to market no matter what. This super competitiveness all the way around makes for not only strange bedfellows but interlocking dependencies that can make full diagnosis of major or even minor systems issue deceptively difficult. I hung up my programmer clothes circa 1995 or so, thus I am more than a little out-of-date for direct knowledge of whence I speak, but in monitoring this and many other NGs, I see no real signs of improvement, if anything, I think the situation is deteriorating. I'm sorry if you feel I am not being objective, let's just say that I am a pragmatist and always suspicious of extravagent claims from ANY developer on either side of problems. Thanks for listening. "HEMI-Powered" wrote in message ... Unknown added these comments in the current discussion du jour ... Look closely at all the postings in this group. You'll be amazed that most problems are not caused by MS but by Non MS programs, reg cleaners, and virus detect/scan protection? programs. That may well be true, but the major developers are wed at the hips body and soul to the God of Microsoft because they must play ball or risk losing their certification. But, it is certainly true that reg cleaners in the hands of the novices will wreck an otherwise good system and are more harm than good most of the time. -- HP, aka Jerry -- HP, aka Jerry |
#29
|
|||
|
|||
XP SP3 Details?
On Tue, 14 Aug 2007 15:00:05 -0500, "Tom Willett"
wrote: "ANONYMOUS" wrote in message ... | "SP3 for Windows XP Professional is currently planned for 1H CY2008. | This date is preliminary." | | http://www.microsoft.com/windows/lif...vicepacks.mspx BTW, this is the third change MS has made to the date for SP3. No, they have made *no* changes because they have announced no dates. Words like "preliminary" and "currently plan" indicate that these are rough estimates, not promises. If they announce a firm release date and then miss it, or change it, that's a failure to keep their promises. Changing an estimate is not. And, they always say it's preliminary ;-) Just like almost everyone else does, they use words like that when the date is far enough in the future that they are unsure of it. When they are closer to a release date and feel assured of making it, *then* they will announce a date. -- Ken Blake, Microsoft MVP Windows - Shell/User Please Reply to the Newsgroup |
#30
|
|||
|
|||
XP SP3 Details?
Unknown added these comments in the current discussion du jour
.... If indeed you were a programmer particularly a micro-programmer then you should have enough experience to recognize the complexity of an operating system plus all the micro-code that operates the hardware. If you were in development you would know that regardless of the amount of testing some bugs will show up after release. How can you possibly be so critical of a few bugs? Compare today's PC's with those of just a few years ago. Be objective not emotional. Sorry, can't follow the quotes. Are you talking to me or someone else? If me, then see my other post just a minute ago. While I never did O/S or systems software, I was always an applications programmer, I DO understand the complexity of even a 2-bit O/S such as Apple's old Dos 3.1 on the ][, so yes, by the time we got to Win 3.1, 95/98, XP, and now Vista, there is no longer any hope of a free ride. And, I hope that sounds reasonably objective and realistic, and NOT either emotional or at all MS-bashing. -- HP, aka Jerry |
Thread Tools | |
Display Modes | |
|
|