S.O.S. - need M.V.P H-E-L-P for corruption of critical systems-files

[HSH]

microsoft.public.windowsxp.general
-------------------------------------------------------
Please bear with me as I attempt to describe
the SYMPTOMS & the SITUATION:

Yesterday, during a session of
test-driving some shareware & freeware
(i.e. Install/UN-install/RE-Install/etc],
I believe that some critical elements of my
Windows XP Home SP2 may have been
damaged or corrupted.

The primary sympotom is that
any attempt to execute an option-Button
by Clicking the any Button inside an opened Window
or within a windows-popup Dialog-Box
causes an immediate Lockup of the KB, the Mouse & the OS-system.

This is most troublesome because
this occurs inside any popup Dialog-Box
that contains options-buttons such as
[Yes] [No] [Cancel] [Proceed?]
which are crucial to conducting simple system-operations !
Moreover, the alternate pathway of executing option-selection inputs
by navigating with the ArrowCursor-keys is crippled
because presssing the Enter-key to execute
the selected option-Button also causes a system-freezeup.
Therefore, I cannot access a RestorePoint
or any backup DriveImage ! (more details to follow)

However, the Mouse functions NORMALLY
when applying Mouse-clicks
--- to any Icons or objects that are on the Desktop,
--- to any Menu-item or sub-Menu-option
--- to any [+] plus/expand-symbol of the Directory-Tree-pane
BUT then clicking on a Folder-icon on the Tree
to view the Folder-contents will cause a lockup.
This inability to view Folder-contents means
I cannot examine any file-attributes or file-dates,
and cannot execute any commands
such a Copy, Paste, Delete to a selected Folder or File.

Although I haven't checked every possibility,
I would SUMMARIZE by saying: Generally,
the Mouse & Keyboard is able to execute "systemic-commands",
but any attempt to execute a user-selected Button-option
causes the system to freeze.

This is Mouse-disablement is a particularly critical
because it prevents me from performing
an XP-System Restore Point:
--- after the clicking on my selected RestorePoint,
a [Yes]-button must be clicked to proceed.
=== the Click-action or pressinf the Enter-key
causes an immediate lockup!
Similarly, this Mouse-disablement prevents me from
using PowerQuest Drive Image 7.0
to restore my C:drive to an earlier-state
because a Button-click is required to initiate the operation.

I ran a virus-scan of all my HDD-devices
using AVG (AntiVirus) 7 Free Edition,
and No viruses were found,
BUT there were 4 AVG Alerts
that warned of changes to my system-areas:
:::verbatim-quote:::
Boot sector of disc C: "changed"
C:\WINDOWS\system32\user32.dll "changed"
C:\WINDOWS\system32\\shell32.dll "changed"
C:\WINDOWS\system32\\ntoskrnl.exe "changed"

I strongly suspect that these reported 'changes"
are related to my session of test-driving
various shareware/freeware applets.

During one of the earliest occurences
of these input system lockups
I found that my Desktop-Appearance
had somehow been altered from my personalized-version
of the Windows CLASSIC THEME.
The machine had spontaneously
changed to the (system-default) Windows XP THEME,
and while retaining only a few of my personalizations.
And although this was just a trivial matter...
perhaps this offers some clue to the alterations or corruption
that has occured to my OS-system, .INI configurations, or Registry?

HARDWARE CHECK:
1. I've inspected the >Hardware >DeviceManager,
and have found DeviceStatus of both
the Keyboard & Mice and all other listed Devices are
reported as "working properly."

2. I checked all the config-settings of
my Logitech Wireless KB & Mouse,
and everything also checks out OK..

I SUSPECT that during the course of my shareware
Install / Uninstall / Reinstall session,
there was some sort of file-corruption
has occured to some critical system-files.
(i.e. such as the C:\WINDOWS\system32\\ntoskrnl.exe warning)

I believe the most direct solution would be
to regain access to perform a simple DriveImage restore.

And tt would seem to be a fairly simple matter
to bootup into the DriveImage Rescue-diskettes...
(based pm Dr.Caldera DOS)

I've searched my drawers for those Rescue-diskettes,
BUT NOOOooo...
I've only been able to find the RescueDiskettes for the
PREVIOUS version PQ DriveImage 2002 !!!
(and I've tried booting into this older set of Rescue-diskettes
but the #2 application-diskette appears to
search for a specific file on Drive 1
that does not exist on the HDD.)

During the initial-install of PQ DriveImage v7.0.
I apparently POSTPONED the creation
of those critical v7.0 RescueDiskettes...
and I guess I'm now paying the price for that meathead manuever.
=====so this seems to be a Dead-End for now...

I have looked into my book "Windows XP Inside Out" 2nd Ed."
to learn that booting into [F8] Safe Mode
(@ 640x480 resolution with minimal generic drivers, etc.)
might enable me to access & execute a RestorePoint
BUT when I attempt to enter [F8] Safe Mode,
a listing of "\Windows\system32\drivers\* .SYS" drivers
scrolls up across the screen
----- and THEN proceeds into a normal bootup into Windows XP
(with my usueal 1024x768 res.olution & my usual Startup-Prog.options)

Similarly, when I attempt to boot into
[F8] Safe Mode with Command Prompt,
the same screenful of "\system32\drivers\*.SYS" scrolls up,
and THEN the machine Loops-back
to the previous [F8] Safe Mode option-menu screen.
===== [F8] Safe Mode with Command Prompt is disabled/unavailable.

Using the "Last Known Good Configuration" option
has no effect and does not correct any of my machine's ills.

So it seems that my machine cannot access
ANY form of [F8] Safe Mode bootup.
(Could this be related to the warning of
"change" to the Boot sector of disc C: ???)

I read further in the book to learn that WMI scripts
can selectively execute a Restore Point,
and the book refers to the following webpage & webpage-text:

=======================================
http://www.microsoft.com/windowsxp/using/productdoc/scriptsamples.mspx
:::quote:::
" The System Restore parameters are configurable remotely or locally
by using a Windows Management Instrumentation (WMI) script.
A WMI script can also be used to create restore points, list them,
select a restore point to restore to,
and view the status of a restore operation. "
:::quote:::
"Scriptingexamples.doc contains functions and parameter descriptions,
along with script samples, which are provided as a guide to
administrators who need remote access to the System Restore features
and settings.")
=======================================

I've downloaded the scriptsamples.DOC from the link on that webpage,
but quite honestly have no freakin' idea
how to implement a WMI script
or how to adapt & utilize the script-samples to address my situation.

reading further in the book (Windows XP Inside Out" 2nd Ed.)
I learned that the the last-ditch option is to use the
Recovery Console by booting-up into the Windows XP CD-disk.
The book goes on to describe the range of command-operations
that can be performed from the Recovery Console, including:
- [ BOOTCFG/REBUIILD] command to replace a faulty Boot.ini
- ( COPY ] command to manually restore damaged
Ntdlr, Ntoskrnl.exe, Ntdetect.com, and driver-files.

HOWEVER, I recognize that I should NOT pursue this pathway
1. UNTIL I can diagnose the source/Cause of my predicament and
2. UNLESS I am able to navigate, locate & access the faulty
system-files or boot-areas. (using a plain DOS-style command-line
or somehow avoiding the faulty Windows GUI.)

My questions:

1. Does anyone RECOGNIZE these symptoms & behaviors?

2. Can anyone DIAGNOSE which of thecritical system-files
or system-areas might have been corrupted?

3. Would the RECOVER PANEL enable me to correct the situation?

4. Would a REPAIR INSTALL be feasible or recommended
given the fact that this inability to "execute" any operations
Move, Copy or Backup any of my Data-files
or to prepare for such a major-operation to my boot-disk?
(i.e. I'm presuming that booting into the WinXP Setup-disc
bypasses the machine's cripple XP-OS & input-system)

Please, PLEASE, P-L-E-A-S-E
1. I desperately need an informed & expert diagnosis of the
of critical system-files that might be causing my crippled
input-system,

2. I'm seeking any recommendations whether the
RecoveryPanel or a RepairInstall might repair by OS-system.
And if so, which of these methods or which sequence of
both methods should be taken.

Thanks to all for reading this message
& Much gratitude to any who can respond.

===============================================
===============================================

 

[Og]

To paraphrase your lengthy dissertation:

"I urinated on my foot. Now my foot is wet. How did my foot get wet, and how
do I get it unwet?"

It appears that you have installed one or more scumware programs that
over-wrote several critical System files.

Format your hard drive, do a fresh install of Windows XP, re-install your
REAL applications, and stop urinating on your foot.


steve

microsoft.public.windowsxp.general
-------------------------------------------------------
Please bear with me as I attempt to describe
the SYMPTOMS & the SITUATION:

Yesterday, during a session of
test-driving some shareware & freeware
(i.e. Install/UN-install/RE-Install/etc],
I believe that some critical elements of my
Windows XP Home SP2 may have been
damaged or corrupted.

The primary sympotom is that
any attempt to execute an option-Button
by Clicking the any Button inside an opened Window
or within a windows-popup Dialog-Box
causes an immediate Lockup of the KB, the Mouse & the OS-system.

This is most troublesome because
this occurs inside any popup Dialog-Box
that contains options-buttons such as
[Yes] [No] [Cancel] [Proceed?]
which are crucial to conducting simple system-operations !
Moreover, the alternate pathway of executing option-selection inputs
by navigating with the ArrowCursor-keys is crippled
because presssing the Enter-key to execute
the selected option-Button also causes a system-freezeup.
Therefore, I cannot access a RestorePoint
or any backup DriveImage ! (more details to follow)

However, the Mouse functions NORMALLY
when applying Mouse-clicks
--- to any Icons or objects that are on the Desktop,
--- to any Menu-item or sub-Menu-option
--- to any [+] plus/expand-symbol of the Directory-Tree-pane
BUT then clicking on a Folder-icon on the Tree
to view the Folder-contents will cause a lockup.
This inability to view Folder-contents means
I cannot examine any file-attributes or file-dates,
and cannot execute any commands
such a Copy, Paste, Delete to a selected Folder or File.

Although I haven't checked every possibility,
I would SUMMARIZE by saying: Generally,
the Mouse & Keyboard is able to execute "systemic-commands",
but any attempt to execute a user-selected Button-option
causes the system to freeze.

This is Mouse-disablement is a particularly critical
because it prevents me from performing
an XP-System Restore Point:
--- after the clicking on my selected RestorePoint,
a [Yes]-button must be clicked to proceed.
=== the Click-action or pressinf the Enter-key
causes an immediate lockup!
Similarly, this Mouse-disablement prevents me from
using PowerQuest Drive Image 7.0
to restore my C:drive to an earlier-state
because a Button-click is required to initiate the operation.

I ran a virus-scan of all my HDD-devices
using AVG (AntiVirus) 7 Free Edition,
and No viruses were found,
BUT there were 4 AVG Alerts
that warned of changes to my system-areas:
:::verbatim-quote:::
Boot sector of disc C: "changed"
C:\WINDOWS\system32\user32.dll "changed"
C:\WINDOWS\system32\\shell32.dll "changed"
C:\WINDOWS\system32\\ntoskrnl.exe "changed"

I strongly suspect that these reported 'changes"
are related to my session of test-driving
various shareware/freeware applets.

During one of the earliest occurences
of these input system lockups
I found that my Desktop-Appearance
had somehow been altered from my personalized-version
of the Windows CLASSIC THEME.
The machine had spontaneously
changed to the (system-default) Windows XP THEME,
and while retaining only a few of my personalizations.
And although this was just a trivial matter...
perhaps this offers some clue to the alterations or corruption
that has occured to my OS-system, .INI configurations, or Registry?

HARDWARE CHECK:
1. I've inspected the >Hardware >DeviceManager,
and have found DeviceStatus of both
the Keyboard & Mice and all other listed Devices are
reported as "working properly."

2. I checked all the config-settings of
my Logitech Wireless KB & Mouse,
and everything also checks out OK..

I SUSPECT that during the course of my shareware
Install / Uninstall / Reinstall session,
there was some sort of file-corruption
has occured to some critical system-files.
(i.e. such as the C:\WINDOWS\system32\\ntoskrnl.exe warning)

I believe the most direct solution would be
to regain access to perform a simple DriveImage restore.

And tt would seem to be a fairly simple matter
to bootup into the DriveImage Rescue-diskettes...
(based pm Dr.Caldera DOS)

I've searched my drawers for those Rescue-diskettes,
BUT NOOOooo...
I've only been able to find the RescueDiskettes for the
PREVIOUS version PQ DriveImage 2002 !!!
(and I've tried booting into this older set of Rescue-diskettes
but the #2 application-diskette appears to
search for a specific file on Drive 1
that does not exist on the HDD.)

During the initial-install of PQ DriveImage v7.0.
I apparently POSTPONED the creation
of those critical v7.0 RescueDiskettes...
and I guess I'm now paying the price for that meathead manuever.
=====so this seems to be a Dead-End for now...

I have looked into my book "Windows XP Inside Out" 2nd Ed."
to learn that booting into [F8] Safe Mode
(@ 640x480 resolution with minimal generic drivers, etc.)
might enable me to access & execute a RestorePoint
BUT when I attempt to enter [F8] Safe Mode,
a listing of "\Windows\system32\drivers\* .SYS" drivers
scrolls up across the screen
----- and THEN proceeds into a normal bootup into Windows XP
(with my usueal 1024x768 res.olution & my usual Startup-Prog.options)

Similarly, when I attempt to boot into
[F8] Safe Mode with Command Prompt,
the same screenful of "\system32\drivers\*.SYS" scrolls up,
and THEN the machine Loops-back
to the previous [F8] Safe Mode option-menu screen.
===== [F8] Safe Mode with Command Prompt is disabled/unavailable.

Using the "Last Known Good Configuration" option
has no effect and does not correct any of my machine's ills.

So it seems that my machine cannot access
ANY form of [F8] Safe Mode bootup.
(Could this be related to the warning of
"change" to the Boot sector of disc C: ???)

I read further in the book to learn that WMI scripts
can selectively execute a Restore Point,
and the book refers to the following webpage & webpage-text:

=======================================
http://www.microsoft.com/windowsxp/using/productdoc/scriptsamples.mspx
:::quote:::
" The System Restore parameters are configurable remotely or locally
by using a Windows Management Instrumentation (WMI) script.
A WMI script can also be used to create restore points, list them,
select a restore point to restore to,
and view the status of a restore operation. "
:::quote:::
"Scriptingexamples.doc contains functions and parameter descriptions,
along with script samples, which are provided as a guide to
administrators who need remote access to the System Restore features
and settings.")
=======================================

I've downloaded the scriptsamples.DOC from the link on that webpage,
but quite honestly have no freakin' idea
how to implement a WMI script
or how to adapt & utilize the script-samples to address my situation.

reading further in the book (Windows XP Inside Out" 2nd Ed.)
I learned that the the last-ditch option is to use the
Recovery Console by booting-up into the Windows XP CD-disk.
The book goes on to describe the range of command-operations
that can be performed from the Recovery Console, including:
- [ BOOTCFG/REBUIILD] command to replace a faulty Boot.ini
- ( COPY ] command to manually restore damaged
Ntdlr, Ntoskrnl.exe, Ntdetect.com, and driver-files.

HOWEVER, I recognize that I should NOT pursue this pathway
1. UNTIL I can diagnose the source/Cause of my predicament and
2. UNLESS I am able to navigate, locate & access the faulty
system-files or boot-areas. (using a plain DOS-style command-line
or somehow avoiding the faulty Windows GUI.)

My questions:

1. Does anyone RECOGNIZE these symptoms & behaviors?

2. Can anyone DIAGNOSE which of thecritical system-files
or system-areas might have been corrupted?

3. Would the RECOVER PANEL enable me to correct the situation?

4. Would a REPAIR INSTALL be feasible or recommended
given the fact that this inability to "execute" any operations
Move, Copy or Backup any of my Data-files
or to prepare for such a major-operation to my boot-disk?
(i.e. I'm presuming that booting into the WinXP Setup-disc
bypasses the machine's cripple XP-OS & input-system)

Please, PLEASE, P-L-E-A-S-E
1. I desperately need an informed & expert diagnosis of the
of critical system-files that might be causing my crippled
input-system,

2. I'm seeking any recommendations whether the
RecoveryPanel or a RepairInstall might repair by OS-system.
And if so, which of these methods or which sequence of
both methods should be taken.

Thanks to all for reading this message
& Much gratitude to any who can respond.

===============================================
===============================================

 

[S.Sengupta]

For how to repair/clean install:-
http://www.michaelstevenstech.com/mscontactinfo.htm

regards,
ssg MS-MVP

microsoft.public.windowsxp.general
-------------------------------------------------------
Please bear with me as I attempt to describe
the SYMPTOMS & the SITUATION:

Yesterday, during a session of
test-driving some shareware & freeware
(i.e. Install/UN-install/RE-Install/etc],
I believe that some critical elements of my
Windows XP Home SP2 may have been
damaged or corrupted.

The primary sympotom is that
any attempt to execute an option-Button
by Clicking the any Button inside an opened Window
or within a windows-popup Dialog-Box
causes an immediate Lockup of the KB, the Mouse & the OS-system.

This is most troublesome because
this occurs inside any popup Dialog-Box
that contains options-buttons such as
[Yes] [No] [Cancel] [Proceed?]
which are crucial to conducting simple system-operations !
Moreover, the alternate pathway of executing option-selection inputs
by navigating with the ArrowCursor-keys is crippled
because presssing the Enter-key to execute
the selected option-Button also causes a system-freezeup.
Therefore, I cannot access a RestorePoint
or any backup DriveImage ! (more details to follow)

However, the Mouse functions NORMALLY
when applying Mouse-clicks
--- to any Icons or objects that are on the Desktop,
--- to any Menu-item or sub-Menu-option
--- to any [+] plus/expand-symbol of the Directory-Tree-pane
BUT then clicking on a Folder-icon on the Tree
to view the Folder-contents will cause a lockup.
This inability to view Folder-contents means
I cannot examine any file-attributes or file-dates,
and cannot execute any commands
such a Copy, Paste, Delete to a selected Folder or File.

Although I haven't checked every possibility,
I would SUMMARIZE by saying: Generally,
the Mouse & Keyboard is able to execute "systemic-commands",
but any attempt to execute a user-selected Button-option
causes the system to freeze.

This is Mouse-disablement is a particularly critical
because it prevents me from performing
an XP-System Restore Point:
--- after the clicking on my selected RestorePoint,
a [Yes]-button must be clicked to proceed.
=== the Click-action or pressinf the Enter-key
causes an immediate lockup!
Similarly, this Mouse-disablement prevents me from
using PowerQuest Drive Image 7.0
to restore my C:drive to an earlier-state
because a Button-click is required to initiate the operation.

I ran a virus-scan of all my HDD-devices
using AVG (AntiVirus) 7 Free Edition,
and No viruses were found,
BUT there were 4 AVG Alerts
that warned of changes to my system-areas:
:::verbatim-quote:::
Boot sector of disc C: "changed"
C:\WINDOWS\system32\user32.dll "changed"
C:\WINDOWS\system32\\shell32.dll "changed"
C:\WINDOWS\system32\\ntoskrnl.exe "changed"

I strongly suspect that these reported 'changes"
are related to my session of test-driving
various shareware/freeware applets.

During one of the earliest occurences
of these input system lockups
I found that my Desktop-Appearance
had somehow been altered from my personalized-version
of the Windows CLASSIC THEME.
The machine had spontaneously
changed to the (system-default) Windows XP THEME,
and while retaining only a few of my personalizations.
And although this was just a trivial matter...
perhaps this offers some clue to the alterations or corruption
that has occured to my OS-system, .INI configurations, or Registry?

HARDWARE CHECK:
1. I've inspected the >Hardware >DeviceManager,
and have found DeviceStatus of both
the Keyboard & Mice and all other listed Devices are
reported as "working properly."

2. I checked all the config-settings of
my Logitech Wireless KB & Mouse,
and everything also checks out OK..

I SUSPECT that during the course of my shareware
Install / Uninstall / Reinstall session,
there was some sort of file-corruption
has occured to some critical system-files.
(i.e. such as the C:\WINDOWS\system32\\ntoskrnl.exe warning)

I believe the most direct solution would be
to regain access to perform a simple DriveImage restore.

And tt would seem to be a fairly simple matter
to bootup into the DriveImage Rescue-diskettes...
(based pm Dr.Caldera DOS)

I've searched my drawers for those Rescue-diskettes,
BUT NOOOooo...
I've only been able to find the RescueDiskettes for the
PREVIOUS version PQ DriveImage 2002 !!!
(and I've tried booting into this older set of Rescue-diskettes
but the #2 application-diskette appears to
search for a specific file on Drive 1
that does not exist on the HDD.)

During the initial-install of PQ DriveImage v7.0.
I apparently POSTPONED the creation
of those critical v7.0 RescueDiskettes...
and I guess I'm now paying the price for that meathead manuever.
=====so this seems to be a Dead-End for now...

I have looked into my book "Windows XP Inside Out" 2nd Ed."
to learn that booting into [F8] Safe Mode
(@ 640x480 resolution with minimal generic drivers, etc.)
might enable me to access & execute a RestorePoint
BUT when I attempt to enter [F8] Safe Mode,
a listing of "\Windows\system32\drivers\* .SYS" drivers
scrolls up across the screen
----- and THEN proceeds into a normal bootup into Windows XP
(with my usueal 1024x768 res.olution & my usual Startup-Prog.options)

Similarly, when I attempt to boot into
[F8] Safe Mode with Command Prompt,
the same screenful of "\system32\drivers\*.SYS" scrolls up,
and THEN the machine Loops-back
to the previous [F8] Safe Mode option-menu screen.
===== [F8] Safe Mode with Command Prompt is disabled/unavailable.

Using the "Last Known Good Configuration" option
has no effect and does not correct any of my machine's ills.

So it seems that my machine cannot access
ANY form of [F8] Safe Mode bootup.
(Could this be related to the warning of
"change" to the Boot sector of disc C: ???)

I read further in the book to learn that WMI scripts
can selectively execute a Restore Point,
and the book refers to the following webpage & webpage-text:

=======================================
http://www.microsoft.com/windowsxp/using/productdoc/scriptsamples.mspx
:::quote:::
" The System Restore parameters are configurable remotely or locally
by using a Windows Management Instrumentation (WMI) script.
A WMI script can also be used to create restore points, list them,
select a restore point to restore to,
and view the status of a restore operation. "
:::quote:::
"Scriptingexamples.doc contains functions and parameter descriptions,
along with script samples, which are provided as a guide to
administrators who need remote access to the System Restore features
and settings.")
=======================================

I've downloaded the scriptsamples.DOC from the link on that webpage,
but quite honestly have no freakin' idea
how to implement a WMI script
or how to adapt & utilize the script-samples to address my situation.

reading further in the book (Windows XP Inside Out" 2nd Ed.)
I learned that the the last-ditch option is to use the
Recovery Console by booting-up into the Windows XP CD-disk.
The book goes on to describe the range of command-operations
that can be performed from the Recovery Console, including:
- [ BOOTCFG/REBUIILD] command to replace a faulty Boot.ini
- ( COPY ] command to manually restore damaged
Ntdlr, Ntoskrnl.exe, Ntdetect.com, and driver-files.

HOWEVER, I recognize that I should NOT pursue this pathway
1. UNTIL I can diagnose the source/Cause of my predicament and
2. UNLESS I am able to navigate, locate & access the faulty
system-files or boot-areas. (using a plain DOS-style command-line
or somehow avoiding the faulty Windows GUI.)

My questions:

1. Does anyone RECOGNIZE these symptoms & behaviors?

2. Can anyone DIAGNOSE which of thecritical system-files
or system-areas might have been corrupted?

3. Would the RECOVER PANEL enable me to correct the situation?

4. Would a REPAIR INSTALL be feasible or recommended
given the fact that this inability to "execute" any operations
Move, Copy or Backup any of my Data-files
or to prepare for such a major-operation to my boot-disk?
(i.e. I'm presuming that booting into the WinXP Setup-disc
bypasses the machine's cripple XP-OS & input-system)

Please, PLEASE, P-L-E-A-S-E
1. I desperately need an informed & expert diagnosis of the
of critical system-files that might be causing my crippled
input-system,

2. I'm seeking any recommendations whether the
RecoveryPanel or a RepairInstall might repair by OS-system.
And if so, which of these methods or which sequence of
both methods should be taken.

Thanks to all for reading this message
& Much gratitude to any who can respond.

===============================================
===============================================

 

[kurttrail]

HSH wrote:
<snipped>

Obviously someone that read Crusty's assumptions!

Assume, that if you post is of the length of the Odyssey, no one is
gonna read it to the end.

--
Peace!
Kurt
Self-anointed Moderator
microscum.pubic.windowsexp.gonorrhea
http://microscum.com/mscommunity
"Trustworthy Computing" is only another example of an Oxymoron!
"Produkt-Aktivierung macht frei"

 

[Leythos]

HSH wrote:
<snipped>

Obviously someone that read Crusty's assumptions!

Assume, that if you post is of the length of the Odyssey, no one is
gonna read it to the end.

What I thought was funny was that he didn't tell us the name of the
software that he was installing/uninstalling/reinstalling...

 

[kurttrail]

What I thought was funny was that he didn't tell us the name of the
software that he was installing/uninstalling/reinstalling...

I never got that far. When I saw my scroll bar was hardly moving, I
gave up on the post.

--
Peace!
Kurt
Self-anointed Moderator
microscum.pubic.windowsexp.gonorrhea
http://microscum.com/mscommunity
"Trustworthy Computing" is only another example of an Oxymoron!
"Produkt-Aktivierung macht frei"

 

[Rock]

microsoft.public.windowsxp.general
-------------------------------------------------------
Please bear with me as I attempt to describe
the SYMPTOMS & the SITUATION:

Yesterday, during a session of
test-driving some shareware & freeware
(i.e. Install/UN-install/RE-Install/etc],
I believe that some critical elements of my
Windows XP Home SP2 may have been
damaged or corrupted.

<snip>

If you don't have a backup of important data, slave the drive in another
XP computer and backup the data.

Try a repair install first,
http://michaelstevenstech.com/XPrepairinstall.htm

If that doesn't work do a clean install:
http://michaelstevenstech.com/cleanxpinstall.html

 

[HSH]

For how to repair/clean install:-
http://www.michaelstevenstech.com/mscontactinfo.htm

regards,
ssg MS-MVP

S.Sengupta:

Thanks for this helpful pointer.

I will take some time to read through
the article & resources to see
which of the procedures
might actually be feasible on my faulty-OS.

I plan to post a followup
to seek further guidance
before I attempt any major operatiojns.

Thanks for your contribution.

HSH

 

[HSH]

To paraphrase your lengthy dissertation:

"I urinated on my foot. Now my foot is wet. How did my foot get wet, and how
do I get it unwet?"

It appears that you have installed one or more scumware programs that
over-wrote several critical System files.

Format your hard drive, do a fresh install of Windows XP, re-install your
REAL applications, and stop urinating on your foot.


steve

Steve:

A very astute observation !

After I've exhausted all the other possibillities,
I may have no choice but to accede to the
fresh-OS-installation + APPs-Reinstallation.

Thanks for your response.

meanwhile, you can call me,

" WetFoot Willie "
.. the ol' windbag ;-)

 

[HSH]

HSH wrote:
<snipped>

Obviously someone that read Crusty's assumptions!

Assume, that if you post is of the length of the Odyssey, no one is
gonna read it to the end.

Kurt:

roger that...
thanks anyhow for taking the time
to click on the header
to post a response...

regards from

ol' WetFoot Willie ;-)

 

[HSH]

<snip>

If you don't have a backup of important data, slave the drive in another
XP computer and backup the data.

Try a repair install first,
http://michaelstevenstech.com/XPrepairinstall.htm

If that doesn't work do a clean install:
http://michaelstevenstech.com/cleanxpinstall.html

Rock:

Thanks for your helpful recommendations.
I am pleased to report that I am slowly progressing
towards a resolution.

One of the few things that are tilted in my favor
is that I had setup the My Documents folder
to to utilize a different Folder on my secondary SATA-2,
so any loss of data-files on my boot-disk SATA-1
will be minimal.

I'm currently reading through the procdures & links
at the resources you've suggested,
During the course of investigating the precautionary-steps
in the "Warning! #1" section of the article.
I've learned that by using the right-Mouse-click options.
(i.e. Explore/Send To/Cut/Copy/Delete/etc.).
I am able perform operations on Folders & Files
without causing a lockup.

I have succeed in using the "Send To" option
to make backup-copies of:
wpa.dbl
wpa.bak
C:\Windows\repair

When I examine the C: root directory,
I find that the AUTOEXEC.BAT & CONFIG.SYS
are both 0 KB files.
that date back to my initial XP-Setup install in Feb 2005.
I also have made backups of these files,
but presume they won't come into play.

ODDLY, I cannot locate any file named:
c:\WINDOWS\system32\undo_guimode.txt.
I have utilized the Search Companion
and also manually-explored the C:\Windows stucture.
(I have set >Tools >Folder Options...
enabled "Show hidden files and folders", and
disabled "Hide protected operating system files"
So this particular file does not exist on my machine.
(But-no-matter, because the article advises to Delete
this particualar file anyway!)

But more ODD, I cannot find a file named
\boot.ini
anywhere in the \Windows or the boot-partition.
I have only found a file named
C:\WINDOWS\pss\boot.ini.backup
that was last modified 3/16/2005.

When I examine the C:root directory,
I find that the AUTOEXEC.BAT & CONFIG.SYS
that originate from my initial XP-Setup install
are both 0 KB files.
I've made backups of these files,
but presume they won't come into play.

Do you have any recommedations regarding
these oddball findings or should I just ignore them?

I am somewhat relieved that the outllook for
a successful Repair-Install
is beginning looking much better! (sigh...)

At the risk of getting looking too far ahead of myself,
do I understand correctly that:
after performing a successful Repair-Install,
restoring the backup-copy of C:\Windows\repair
will enable me to regain full access
to all my prior XP-system Restore Points?

and IF SO, would it be advisable to
stay with the post-disaster, Repair-Install of the OS
or revert back to a (known-to-be-Good)
pre-disaster Restore Point configuration?

I will review & retrace the all procedures again
before I actually undetake the the Repair-Install,

Thanks again to S.Sengupta for your contribution,

and Much Thanks to Rock your recommendations.

I appreciate your contributions,
and hope you are able to continue!
I will post a followup
when I have any further progress or results.


HSH
......... < they call me "Wetfoot Willie" ;-} >

 

[S.Sengupta]

You are most welcome.

regards,
ssg MS-MVP

S.Sengupta:

Thanks for this helpful pointer.

I will take some time to read through
the article & resources to see
which of the procedures
might actually be feasible on my faulty-OS.

I plan to post a followup
to seek further guidance
before I attempt any major operatiojns.

Thanks for your contribution.

HSH

 

[Curmudgeon]

If you don't have a backup of important data, slave
the drive in another XP computer and backup the data.

OH yeah. That'll work.

Most households have several XP computers to use for such an operation
- and lots of inhabitants that know HOW to do that.

You related to Carey?

 

[Rock]

Rock:

Thanks for your helpful recommendations.
I am pleased to report that I am slowly progressing
towards a resolution.

One of the few things that are tilted in my favor
is that I had setup the My Documents folder
to to utilize a different Folder on my secondary SATA-2,
so any loss of data-files on my boot-disk SATA-1
will be minimal.

I'm currently reading through the procdures & links
at the resources you've suggested,
During the course of investigating the precautionary-steps
in the "Warning! #1" section of the article.
I've learned that by using the right-Mouse-click options.
(i.e. Explore/Send To/Cut/Copy/Delete/etc.).
I am able perform operations on Folders & Files
without causing a lockup.

I have succeed in using the "Send To" option
to make backup-copies of:
wpa.dbl
wpa.bak
C:\Windows\repair

When I examine the C: root directory,
I find that the AUTOEXEC.BAT & CONFIG.SYS
are both 0 KB files.
that date back to my initial XP-Setup install in Feb 2005.
I also have made backups of these files,
but presume they won't come into play.

ODDLY, I cannot locate any file named:
c:\WINDOWS\system32\undo_guimode.txt.
I have utilized the Search Companion
and also manually-explored the C:\Windows stucture.
(I have set >Tools >Folder Options...
enabled "Show hidden files and folders", and
disabled "Hide protected operating system files"
So this particular file does not exist on my machine.
(But-no-matter, because the article advises to Delete
this particualar file anyway!)

But more ODD, I cannot find a file named
\boot.ini
anywhere in the \Windows or the boot-partition.
I have only found a file named
C:\WINDOWS\pss\boot.ini.backup
that was last modified 3/16/2005.

When I examine the C:root directory,
I find that the AUTOEXEC.BAT & CONFIG.SYS
that originate from my initial XP-Setup install
are both 0 KB files.
I've made backups of these files,
but presume they won't come into play.

Do you have any recommedations regarding
these oddball findings or should I just ignore them?

I am somewhat relieved that the outllook for
a successful Repair-Install
is beginning looking much better! (sigh...)

At the risk of getting looking too far ahead of myself,
do I understand correctly that:
after performing a successful Repair-Install,
restoring the backup-copy of C:\Windows\repair
will enable me to regain full access
to all my prior XP-system Restore Points?

and IF SO, would it be advisable to
stay with the post-disaster, Repair-Install of the OS
or revert back to a (known-to-be-Good)
pre-disaster Restore Point configuration?

I will review & retrace the all procedures again
before I actually undetake the the Repair-Install,

Thanks again to S.Sengupta for your contribution,

and Much Thanks to Rock your recommendations.

I appreciate your contributions,
and hope you are able to continue!
I will post a followup
when I have any further progress or results.


HSH
........ < they call me "Wetfoot Willie" ;-} >

<snip>

Don't worry about those file issues you mentioned. With respect to the
restore points, doing a repair install will remove the restore points so
you can't go back, IIRC. Make sure you backup all essential data first.
What you will need to do after the repair install is install all updates.

 

[Og]

)

I've been accused neither of being tactful nor of being diplomatic.

Good luck,

steve

 

[kurttrail]

OH yeah. That'll work.

Most households have several XP computers to use for such an operation
- and lots of inhabitants that know HOW to do that.

You related to Carey?

I guess you don't have any friends.

--
Peace!
Kurt
Self-anointed Moderator
microscum.pubic.windowsexp.gonorrhea
http://microscum.com/mscommunity
"Trustworthy Computing" is only another example of an Oxymoron!
"Produkt-Aktivierung macht frei"

 

[Rock]

Rock wrote:




OH yeah. That'll work.

Most households have several XP computers to use for such an operation
- and lots of inhabitants that know HOW to do that.

You related to Carey?

Why does one have to use another XP (or win2k for that matter) computer
in the same household? Crawl back into your hole.

 

[HSH]

)

I've been accused neither of being tactful nor of being diplomatic.

Good luck,

steve

----------------------------------------------------
HeyYa Steve:

ummm... uhhh... Congrats on that..... (i think...)

i thought the wetness
was the result of finding myself
knee-deep in doo-doo?

i'm edging towards an attempt to Repair Install.

& Thanks.

HSH

 

[HSH]

<snip>

Don't worry about those file issues you mentioned. With respect to the
restore points, doing a repair install will remove the restore points so
you can't go back, IIRC. Make sure you backup all essential data first.
What you will need to do after the repair install is install all updates.

------------------------------------------------------------------------

HeyYa Rock (& all y'all):

Thanks for the followup posting.

I will follow your recommendation
to disregard the files:
C:\AUTOEXEC.BAT & c:\CONFIG.SYS
C:\WINDOWS\system32\undo_guimode.txt
C:\WINDOWS\pss\boot.ini.backup

===============================================
FINAL (long-winded) REVIEW & my last QUESTIONS:
===============================================

RE: REINSTALLING WindowsXP UPDATES
Will the Update-wizard automatically start downloading the
Updates?
OR is there a local-cache of all the
previously downloaded&installed Updates
saved somewhere on my boot-disk?
(including the Microsoft .NET Framework 1.1 + recent Hotfix)

(My unreliable 56K-Dialup forces me to pre-plan
the duration my download-sessions, etc...)
-----------------------------------------------

RE: RESTORE POINTS
The REPAIR INSTALL article (www.michaelstevenstech.com)
contains a hyperlink under the section "Warning #1"
that refers to the webpage
"Windows XP Crashed? Here's Help" by Charlie White
(www.digitalwebcast.com/2002/03_mar/tutorials/cw_boot_toot.htm)
that addresses using the RECOVERY CONSOLE on the XP-SetupCD
to access (the otherwise inaccesible) saved Restore Points.

This appears to be a fairly complex set of procedures.
Any comments or recommendations on this Restoration approach?
-----------------------------------------------

RE: Drive Restoration using DRIVE-IMAGE
It occurs to me that IF I can regain access to PQ DriveImage,
I could rebuild my entire boot-disk & OS-system back
to an earlier "known good" state;
which might allow me to bypass the issues of Restore Points
and/or reapplying the Windows XP Updates...

Is this wishful thinking on my part?
Any obstacles that could derail a DriveImage restoration?

----------------------------------------------------------------------------------

I will devote a little more time to re-examine
the Repair-Install instructions to fully grasp
the procedures...
and will then start the Repair-Install process later tonight,
(lateSundaynight / earlyMondaymorning)

If you happen to read this message within that timeframe
& care to offer any further recommendations or warnings,
I'll check back here just before I get on with it..

Much thanks for your (virtual) presence out there...

Making the leap from a Pentium 200mHz on Win95
to a DIY Pentium4 machine running WinXP Home SP2
these past few months has been a real mindblower!

Best Regards,

HSH



============================================
PS: Please feel free to DISREGARD THIS ADDENDUM.
It is my LOG of precautionary measures & backups preps.
I include it down here in the event it might be helpful
to someone else facing a Repair Install.
============================================
(I recognize that some of these backups may be superfluous.)
----------------------------------------
1. executed the in-depth command-line-operation:
[ CHKDSK /F /R ]
----------------------------------------
2. created a backup-copy of the Folder-contents of:
[ C:\WINDOWS\repair ]
(per Recovery console => Restore Points above)
----------------------------------------
3. created backup-copies of the 2 Activation files:
[ WPA.DBL and WPA.BAK ]
----------------------------------------
4. used the F.A.S.T wizard to create a local-backup
of ALL the available Folders and Files options,
generating: [ IMG00001.DAT ] 402,636 KB
----------------------------------------
5. created backup-copies of my 3 superfluous files:
AUTOEXEC.BAT
CONFIG.SYS
boot.ini.backup
----------------------------------------
6. went into TweakUI to reexamine any "Change Location"
mods that were applied to "My Computer - Special Folders".
=== recognized the implictions of "Change Location" to the
[ C:\Documents and Settings\(myusername)\My Documents ].
Any potential loss or damage to [ C:\Documents and Settings ]
could impact those redirected Folders on my secondary
data-drive.

 

[Kelly]

Most households do!

--

All the Best,
Kelly (MS-MVP)

Troubleshooting Windows XP
http://www.kellys-korner-xp.com