Well, you can waltz around the issue, or you "can get to it".

Download Dependency Walker and try the "profiling" aspect. I have
repeatedly used it to show issues for various programs, files, and
installation routines, sending these REPORTS back to the original
programmers so they could correct their programming problems.. It was such a
good program, that Microsoft suggested its use on many of its old support
pages to help diagnose issues, and for sending reports back to Microsoft
[during the actual 98 support cycle, not at the end when IE was the only
concern].
I have also used it to locate the exact areas/issues within my own systems,
during testing of unofficial updates, and other.
Of course its just part of the tool set I use, but it is invaluable.

--
~
--
MEB
http://peoplescounsel.org/ref/windows-main.htm
Windows Diagnostics, Security, Networking
http://peoplescounsel.org
The *REAL WORLD* of Law, Justice, and Government
_______



"J. P. Gilliver (John)" wrote in message
...
In message , MEB
writes:
[]
I realize that was more of a rant than a question, however, you answered
the issue.

(-:

The key is ALWAYS: when it works, when it doesn't the world turns on
edge
and time flashes by... hours wasted, generally to find it was something
staring us in the face all the time.

If you mean always backup, I've in general been doing an ERU before and
after installing new, and also when it's been running well for a while,
just to mop up little tweaks I may have made. This has rescued me many a
time; however, it isn't a full backup. If I ever get it sorted, I think
a full backup with Acronis will be in order.

ANYWAY, Dependency Walker can generally be used effectively to find the
issue [its basically a generic 32bit Windows debugger]. TRY just
expanding
the installer{s} and running it on the individual files *if* PROFILING
can't
find the issues.

I clearly have to do that, though I still think it's the part of the
_system_ that _handles_ new drivers, rather than the drivers themselves,
that's fubared.

You might want to go into Safe Mode and make sure everything that should
be
gone is actually gone [like old programs and drivers]. If it were me, I
would also run my trusty registry reviewing program {RegSeeker] and see
what
it finds.

I've used the one in EasyCleaner from time to time.

You aren't running something like WinPatrol or some other registry or
scripting protection program are you? And you did disable anti-virus and
as
much else as you could before attempting installation, right..

Interesting question about scripting. I know I've in the past changed
the default file association for script files (to Notepad IIRR); I can't
remember if anything has changed that back, though. The machine on which
I have this problem is not connected to anything, so I don't have AV
running all the time on it anyway (I have it there, and scan any new
executable - or disc - with it).

Sorry, I'm dragging my feet in getting round to dealing with the
problem, but I have definitely marked your posts as keep for when I do.
--
J. P. Gilliver. UMRA: 1960/1985
MB++G.5AL(+++)IS-P--Ch+(p)Ar+T[?]H+Sh0!:`)DNAf
** http://www.soft255.demon.co.uk/G6JPG-PC/JPGminPC.htm for ludicrously
outdated thoughts on PCs. **

Imagine a world with no hypothetical situations...