>On Sun, 17 May 2009 23:11:25 -0400, MEB <
meb-not-here@hotmail.com> wrote:
>legg wrote:
>>> On Sun, 17 May 2009 03:59:10 -0400, MEB <
meb-not-here@hotmail.com> wrote:
>>
>>>> legg wrote:
>>>> On Sat, 16 May 2009 22:40:07 -0400, MEB <
meb-not-here@hotmail.com>
>>>> wrote:
>>>>
>>> large snip
>> <bigger snip>
>>> Well, we finally got to the registry modifications. Might have helped
>>> to advise of that from the start...
>>>
>>> So these were done manually?
>>>
>> Note that this was done over a year ago. It's just an example of the
>> methods used, and the records kept.
>>
>> Invalid keys were deleted through the Norton "WinDoctor" GUI. These
>> deletions are supposedly 'undo'able, though I've never reverted in
>> this manner - prefering to restore from registry back-up when needed
>> and to try again (or not).
>>
>> Missing dll and excutable files, if suitable ones be found, were
>> relocated (copied) manually to correspond to the noted registry
>> expectation.
>>
>> Shortcuts that could be redirected were altered manually (not a
>> registry issue)
>>
>> The only times I've altered the registry manually has been under the
>> direction of the 'owners' of the relevent line - such as in getting
>> Word2K to switch from unicode characters, or restoring stolen file
>> associations. Once I went on a rampage with Norton entries, to clean
>> out later revisions of their AV and other software.
>>
>> RL
>
>Okay, glad you had posted that you HAD made registry modifications and
>you had kept track, and that these are old, hence potentially not
>related to the present condition.
>
> Not knowing where you are on your backup procedures:
> *IF* you have a recent version from prior to the errors, you might try
>exporting the backed-up registry files for a trial at replacement. OR,
> *IF* you have a back-up from before [prior to] the issue and you
>haven't added anything recently [and no major hardware changes], you
>might be able to try just that much of a "repair" [the user.dat and
>system.dat] or pull one of the ones from the automatic back-ups done
>from %windir%/sysbckup/rb*.cab [not the bad if there is one]. Modify the
>date to one within your present backup dates and within the 1-5 format
>available.
> Save the present before replacement and compare the differences
>between the two sets.
>
> *OR* you're back to "trial and error", or using the diagnostics I
>previously provided.
>
> The issue of the one hour file difference is something you will need
>to research as you have negated our attempted explanations and directions.
>
> *IF* you wish, you might post the file names [system only] that you
>think are at issue, along with OS installation date and other that might
>be relevant. You checked for similar dates [changed date] within the
>system, right?
>
I ignored last-mod timestamps with the single hour difference in SFC.
I don't know if this will prevent their future identification, using
the same tool. Haven't done anything except make a few notes and run a
few hard drive tests, lately.
In doing so, there was an explorer.exe page fault (Kernel32) in safe
mode - a first. This was in the process of closing a running program -
Conversions Plus Quickview - looking at the ansi text file contents of
'default.sf0'. As in normal mode, all this fault did was close windows
and loose window viewing preferences, effecively restarting
explorer.exe.
This might reduce candidate sources for the error, at least to those
supported by or actively supporting safe mode. These parts of the
operating system might be expected not to change much, possibly
increasing the usefulness of a past back-up. It also indicates that
file transfers will have to be made from outside of the environment ~
easiest option being to use the secondary boot W2K OS.
Even if these errors eventually are avoided, there will likely be new
issues surrounding the use of the IE repair tool. The final act of
this 'repair' redeposited an IE5.5SP2 link icon on the desktop. This
is an icon I recall naming many years ago, on the day of installation
of that version. IE6 and the last KBs/security patches were installed
over 3 years ago. I hate to think what else might have been undone.
IE6.1 at the pre-repair rev still runs from the toolbar. Perhaps this
is one of the benefits (?) of using the non-default installation
directory. The original installation and update cabs for IE6 and its
KBs remain in this directory.
I will ignore Internet Explorer issues until explorer.exe behavior is
dealt with.
RL