microsoft to discontinue SP1 support by October 2006

[Supreme2k]

tekkie, you're just mad cuz your not 1337 like us :P

Before installing any program (or even saving a text file), I reformat my drive and re-install Windows (starting with 2.0).

[Faustus]

I don't think I ran into a single software issue that hadn't been pretty much patched within a month or two of it coming out. Thats all I'm saying...

[chesterfield]

i was under the original impression that SP2 FU%&& things up. IT DOES NOT. if you have an origial windows xp disc, or an xp disc with sp1, then i suggest you get an SP2 update DISC and install immediately after installing windows---NO PROBLEMS HERE.......slipstreamed discs are, IMHO, not good.....


@ JIMMALENKO...whats up???????

[pepegot1]

Jimmalenko Wrote:
<<You possibly could have still baulked SP2 and just upgraded MDAC to V2.81 with this: >>

I did try to install the MDAC 2.8 SP1 download, but it refused to install-message not compatible with this OS, or something similar. I spoke with MS and they advised me to install SP2 as it would install the correct code, which it did do. So, I had no choice. Now, I am glad I did. I hope others can be as fortunate as I was. I will be able to improve my computer as a result of it-IE 7.0, etc., etc.

[jimmalenko]

Who's fault is it? Well, let's see: working app, Microsoft changes code, app breaks. No doubt about it, it's Microsoft's fault. Do they have the right to do it? Of course they do, but it doesn't make it not their fault.

I agree that they are the cause of the problem, but at the end of the day the onus is then on the app's developers who need to deal with it and rewrite the app so that it works under SP2.

Be it right or wrong, if the app's developers choose to blame Microsoft and refuse to fix it, they won't last very long, as they need Windows much more than Windows needs them. I'm not saying it's right - just the way of the world, unfortunately.

[tekkieman]

Who's fault is it? Well, let's see: working app, Microsoft changes code, app breaks. No doubt about it, it's Microsoft's fault. Do they have the right to do it? Of course they do, but it doesn't make it not their fault.

I agree that they are the cause of the problem, but at the end of the day the onus is then on the app's developers who need to deal with it and rewrite the app so that it works under SP2.

No argument there. I was just making the case that it was Microsoft's fault.

if the app's developers choose to blame Microsoft and refuse to fix it, they won't last very long

Very true, but is it fair to blame them for non working apps for two months every time MS changes their code? MS isn't exactly forthcoming with information about their code changes. Then everyone has to run around playing catch up.

as they need Windows much more than Windows needs them.

Even if that were true, then the winds are a changin'. The reason I say if that were true is because I believe Windows needs them more. What is Windows without applications? Solitaire? There are other OSes they could write apps for, and if MS doesn't start seeing that picture, they will.

[lenti_75]

most of the people use their pc for surfing the net....

I had problems with it, after install some software just crashed.

Then update the software instead of blaming SP2. Technology evolves. If you run in place, the world will pass you by.

thanks man, but that shouldn't happen. I let you spend more for your updates if this solves your problem....

[Dv8ted2]

I let you spend more for your updates if this solves your problem....

What problem?

I have no problem.

:P

[mazinz]

I have not checked this post in a few days and had no clue it was taking off. Well to verify a few things from my original post. This also relates to when sp2 crashed my pc a long time ago

1. I keep my PC clean, I do not have tons and tons of garbage on it
(always scanned for spyware, vurus, etc, though I do not go to most places that would have that anyway)
2. I keep all critical updates and some hardware current
3. my last sp2 install was via MS download as I am on cable

the install seemed to go ok with no problems. After the pc was restarted I could no longer use my firewall (sygate), nor uninstall or reinstall it (the exe file would just die right out)

Also my sound was gone. In fact it was greyed out on the pc (soundblaster 2k card). Eventually I had to reformat the system. I also did not like that sp2 put on other garbage that I already had other software for


At anyrate I ordered the sp2 cd which came in 3 days ago. Since I have till October, I will keep things as they are until SP1 is no longer supported. Back then after I was on my feet again, I did some searching to find out that a ton of people were having similar issues with sp2. Its wonderful that most of you had no issues with it, but their are still quite a lot of people that do. Sp2 is still a somewhat massive pc upgrade (so to speak), the odds of it screwing something up are still high

[MrTmar]

I needed to update to support the applications for which I was responsible as clients were preparing to update their machines. Only problem of SP2 I knew was the Novell Client (not my decision) so I could not upgrade at work. Otherwise, SP2 has been relatively good for me - anything I saw that was a problem (like DEP) ended up in 2003 Server so the problem resolution experience was good. Yes, this includes a PC with a Creative Dxr2 DVD decoder (unsupported in XP), Videum capture card (ISA-again unsupported) and 5.25 inch drive.

Here's a funny story, though, and I did not see this software mentioned in the thread. While sifting through some old code I decided to dust off the VS6 disks and install to check out the sources I found. I have run VS6 under SP1 of XP just fine. VS6 does not install under SP2. What is interesting is the timeline of nearly 9 months Microsoft was "officially supporting" VS6 but never truly released an upgraded installer to correctly address MS Java. Upgrading SP1 to SP2 with VS6 installed works fine - just cannot install afterwards.

I'll scrap the VS6 and upgrade the VB code someday but it is amusing that Microsoft does not keep all of its own software updated to its latest service packs while under support.

[jimmalenko]

While sifting through some old code I decided to dust off the VS6 disks and install to check out the sources I found. I have run VS6 under SP1 of XP just fine. VS6 does not install under SP2. What is interesting is the timeline of nearly 9 months Microsoft was "officially supporting" VS6 but never truly released an upgraded installer to correctly address MS Java. Upgrading SP1 to SP2 with VS6 installed works fine - just cannot install afterwards.

I'll scrap the VS6 and upgrade the VB code someday but it is amusing that Microsoft does not keep all of its own software updated to its latest service packs while under support.

Really ?

I also have (and still use) VS6 Pro Edition, and it has installed fine on 3 x freshly-installed Win XP with SP2 slipstreamed PCs. When I start the installer and enter my details, I get the following message:



... and then it upgrades the VM, reboots and continues to install (and operate) without a hitch

[tekkieman]

VS6 does not install under SP2.

I don't know if this will help, but I have an XP home with SP1 upgraded to XP Pro SP1, then SP2 applied, with VS6 Enterprise installed after. Then, just to finish it off, SP5 for VS6 installed on top.

[MrTmar]

Very interesting. When I drop the CD into the tray, I receive "Setup has encountered a problem and needs to close. We are sorry for the inconvenience."

The system was re-installed a few months ago from a slipstreamed XP SP2 CD. Following the original VS6 problem a few weeks ago, I tried the basics, such as disable AV, stop all programs and services, and reboot with no luck. Loaded msjava and patched it prior to installation with no luck. I tried copying the CD contents to hard disk and running SETUP.EXE in 98 and 2000 compatibility mode with no luck but at least it tried to register the files. Tried some Goodle workarounds with no luck, either.

From what I read, VS6 was designed for Windows '98. Problem is it worked under SP1 for me (slipstreamed) AND the product was supported officially by MS after SP2 was released. I will try formatting my machine at some point to see if it is something I did but there are plenty of Google articles on this same problem.

Otherwise, I cannot say I had major difficulties with SP2.