Re: XP Problems
From: k smith (anonymous_at_discussions.microsoft.com)
Date: 03/08/04
- Next message: Kristin: "event viewer error.."
- Previous message: Plato: "Re: Password Protect"
- In reply to: Carey Frisch [MVP]: "Re: XP Problems"
- Next in thread: Carey Frisch [MVP]: "Re: XP Problems"
- Reply: Carey Frisch [MVP]: "Re: XP Problems"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 8 Mar 2004 11:56:51 -0800
>-----Original Message-----
>Some Questions:
>
> 1. Why is the success rate of "System Restore" less than
>20%? I have the same results on all 4 machines I
>control. "System Restore" is a worthless resource hog
>which I no longer have enabled. I am rolling 2 machines
>back to "windows 98SE", installing "Lindows" on the third,
>and resell those 3 copies of XP.
>
>A. System Restore has always worked 100% of the time on
> every machine I installed XP it on. Your problems
may be related
> to using inadequate RAM or other hardware issues.
>
>2. Why does XP force you to download and reinstall all of
>the updates when you do a "Repair"? Shouldn't it be called
>a "Re-install"? because it also forces you to "Re-
>Activate" every time. I ran out of "Activations" 2 years
>ago. Fortunately I found a crack that works for me. I
>shouldn't have to ask for permission to use something I
>PAID FOR! and; I WON'T!
>
>A. A repair install uses the original system files on
the XP CD.
> The is no such thing as "running out of
activations". One
> can always use the "activate by telephone" method.
>
>3. Why does XP deny access to corrupted system files by
>anti-virus software, or when logged on as an
administrator?
>
>A. HOW TO: Take Ownership of a File or Folder in Windows
XP
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;308421
>
>4. Why was XP designed to be so unfriendly and difficult
>to maintain?
>
>A. Windows XP is easy to maintain.
>
>5. Why do all of the "critical" and "recommended" updates
>leave so much clutter in the registry? I'm talking about
>hundreds of broken links and invalid entries. Thank God
>for good (properly written) 3rd party apps to clean up the
>mess that Micro$oft is unwilling or incapable of getting
>right.
>
>A. Stay out of the registry unless you know what you are
doing.
>
>6. Will I wait for "Longhorn"?........HELL NO!
>
>A. Chances are your old computer hardware won't even be
adequate for Longhorn.
> Windows XP is the last operating system you can
upgrade to from Windows 98.
>
>7. Will I download SP2?........HELL NO!
>
>A. SP2 will be a major security enhancement to Windows
XP.
>
>8. Why is SP2 written to break so many good applications?
>
>A. SP2 is still in beta testing. You should not install
any SP2 beta version
> on any production machine. If you do not
understand the ramifications
> of installing beta software, do not install it.
>
>9. Why was XP designed to crash when installing or using
>disk imaging applications for disaster recovery?
>
>A. Seems like the disaster is sitting right across the
keyboard.....
>
>You need to read some good books:
>
>Windows XP For Dummies
>http://www.dummies.com/WileyCDA/DummiesTitle/productCd-
0764508938.html
>
>Video Professor - Microsoft Windows XP
>http://www.freevideoprofessorcds.net/video-professor-
microsoft-windows-xp.php
>
>Microsoft® Windows® XP Inside Out
>http://www.microsoft.com/mspress/books/5206.asp
>
>--
>Carey Frisch
>Microsoft MVP
>Windows XP - Shell/User
>
>Be Smart! Protect your PC!
>http://www.microsoft.com/security/protect/
>
>----------------------------------------------------------
---------------------------
>
>"k smith" <anonymous@discussions.microsoft.com> wrote in
message:
> news:8f2c01c40532$ef8d6020$a001280a@phx.gbl...
>
>|I started out in the XP Beta period with the 2500 series
>| and have to say that XP is still BETA! It hasen't even
>| gone "tin" yet...let alone "gold".
>|
>| Every time I have to "repair" XP I have to redownload
and
>| re-install all of the "critical" and "recommended"
>| updates; with many problems along the way. I'm really
>| tiring of having to re-install XP every couple of
weeks. I
>| never had to do that with "98"......just a "clean
install"
>| every 3 months or so. I expected more with "XP"....what
a
>| mistake! The piece of crap "ME" was is better than "XP"!
>|
>| This last time was the worst. I couldn't select all of
>| the "critical" updates and install them without getting
>| a "BSOD".
>|
>| I had to download and install each update individually;
>| which meant I had to reboot and log on 40 times just to
>| get all of the "critical" updates. However: "KB826939
>| update rollup 1" gives a "BSOD" every time I try to
>| download it.
>|
>| Some Questions:
>|
>| 1. Why is the success rate of "System Restore" less than
>| 20%? I have the same results on all 4 machines I
>| control. "System Restore" is a worthless resource hog
>| which I no longer have enabled. I am rolling 2 machines
>| back to "windows 98SE", installing "Lindows" on the
third,
>| and resell those 3 copies of XP.
>|
>| 2. Why does XP force you to download and reinstall all
of
>| the updates when you do a "Repair"? Shouldn't it be
called
>| a "Re-install"? because it also forces you to "Re-
>| Activate" every time. I ran out of "Activations" 2 years
>| ago. Fortunately I found a crack that works for me. I
>| shouldn't have to ask for permission to use something I
>| PAID FOR! and; I WON'T!
>|
>| 3. Why does XP deny access to corrupted system files by
>| anti-virus software, or when logged on as an
administrator?
>|
>| 4. Why was XP designed to be so unfriendly and difficult
>| to maintain?
>|
>| 5. Why do all of the "critical" and "recommended"
updates
>| leave so much clutter in the registry? I'm talking about
>| hundreds of broken links and invalid entries. Thank God
>| for good (properly written) 3rd party apps to clean up
the
>| mess that Micro$oft is unwilling or incapable of getting
>| right.
>|
>| 6. Will I wait for "Longhorn"?........HELL NO!
>|
>| 7. Will I download SP2?........HELL NO!
>|
>| 8. Why is SP2 written to break so many good
applications?
>|
>| 9. Why was XP designed to crash when installing or using
>| disk imaging applications for disaster recovery?
>|
>| There appears to be a stock answer to many of my
>| questions: Greed, indifference, and the arrogance of a
>| MONOPLY!
>|
>
>.
The machine I have the most problems with is not cutting
edge...I stay one step behind and let others have the
debugging headaches.
hardware:
1. Shuttle AK32VN mainboard w/via KT266A chipset, latest
4in1 drivers and bios flash. powered by an Antec 350 watt
PS both 2 months old.
2. Athlon XP 2600+ (underclocked for stability at 1.94 GHZ)
2 months old
3. 1 GB DDR SDRAM 2 months old (These 3 components
replaced due to a mainboard failure).
4. IBM deskstar 120 GB IDE HD 1 year old (no bad sectors
or clusters)
5. WD 60 GB IDE HD 2 years old (no bad sectors or clusters)
6. Sanyo DVD ROM 1 year old
7. NEC DVD+/-R/RW (with latest firmware)1 month old.
8. All machines are connected to a good UPS with enough
capacity to run 8 hours on battery back-up.
Power surges or voltage drops (which a surge protector
alone can't compensate for) are no problem as far as
possible data corruption.
I run a "burn-in" with "Sisoft Sandra" every 3 months to
cull out any failing hardware.
My oldest machine is an IBM Aptiva w/450 MHZ AMD K5 and
256MB SDRAM.
According to Micro$oft all of my hardware is adequate at
this time.
thanks for the info about acquiring ownership of files. I
figured that one out yesterday when I had to drill all the
way down via "safe mode" to delete a corrupted (PE_JEEFO.A
virus infection) "system volume information" file.
When is Micro$oft going to make it a little easier for the
average user to fix things? It's a waste of time to have
to reinstall EVERYTHING when there's one little problem.
As for the registry: I only manually edit the registry
when a poorly written uninstall routine leaves something
that causes a conflict which is easy to find just by
searching for the program name and deleting only those
references. Other than that I let "V-Com system suite"
clean things up.
I haven't tried any beta versions of SP2. I have enough
debugging to do in my work with video and other data
recovery. It is my understanding that the final release of
SP2 is still going to break a lot of older apps by design.
That's why I won't be installing SP2. As for the security
issues I run with the latest AV defs from behind 2 NAT
routers connected in series and one software router with 2
software firewalls on each machine and have "Spybot Search
and Destroy" with "Adaware" on each machine. I don't think
SP2 will do anything more about my security level but
force me to trash most of my apps (they might be old but
they do the job). I also visit "Gibson Research"
frequently, they're more concerned and dedicated to
security issues than Micro$oft has been.
As for the "Activate by phone"....will I have to call
every time I crash? How much spam can I expect if I do
call? What kind of personal detail does one have to give?
We all know that "privacy policies" can be changed on a
whim without notice especially when dealing with a monoply
such as Micro$oft.
I know I'm not as informed as the MS clones. My experience
only goes back to the "IBM 360" and "Commodore 64". But:
I'm learning!
- Next message: Kristin: "event viewer error.."
- Previous message: Plato: "Re: Password Protect"
- In reply to: Carey Frisch [MVP]: "Re: XP Problems"
- Next in thread: Carey Frisch [MVP]: "Re: XP Problems"
- Reply: Carey Frisch [MVP]: "Re: XP Problems"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
