problems with 32.dll when loading drivers

In message <OB#H76GhJHA.1288@TK2MSFTNGP02.phx.gbl>, MEB
<MEB@not.?.invalid> writes:
>
> You MAY be experiencing conflicts with an installation of one of the
>'generic' driver libraries that might have been installed.
>I admit I haven't used the UBCD, however, when testing some of these
>compiled "upgrades/updates", I found similar issues.

Thanks for thinking.

> If I remember correctly, you installed this UBCD over an already updated OS
>[besides the "lite" aspect], and with other "unofficially updates"

I don't think I'd done many if any updates, other than the lite,
official or otherwise; this is a non-internet machine, and besides I
don't usually like to do updates unless I am very sure what they do.
However, the system has certainly had assorted third-party utilities
installed over the years, which probably has the same effect.

>previously installed. This makes it more than slightly difficult to diagnose
>as there are likely too many "unknown" [to us] modifications [and which you
>may not remember].

You're right there (both in that it makes it hard for you to diagnose,
and that I won't remember!).
>
> You can try monitoring the installs with *sysinternals' filemon* [available
>on Microsoft] for the exact failure.

Hmm. I have a lot of work to do.
>
> You can also attempt a "fake install" - unzip the driver to some folder,
>use Dependency Walker to open the file, and *profile* the setup file [if
>applicable] or by opening the individual files, searching for the breakdown
>[usually shown in red, ignore the two normal ones {missing XP files}].

I don't _think_ it's the installer, as I've had it for a variety of
drivers from a variety of sources - the sound hardware (Realtek), a
couple of cameras (a microscope and a binoculars camera), and assorted
novelties (dreamcheeky). It seems to stop at the same place during the
driver install, or in the case of the sound hardware if I "remove" it
and restart the machine, it locks up at the driver load during the
restart. I have tried unzipping the driver installers (usually
executables these days) and manually installing, pointing to where I'd
unzipped when prompted, and it's always the driver loading process
(usually blaming rundll32, but I know that's usually just a scapegoat)
that seems to fail, always at the same point.
>
>Here's an old diagnostic page I created for general reference:
>http://peoplescounsel.org/ref/gen/sys_diagnos.htm
>
Thanks for that - I clearly have a LOT of work to do.

Why is driver installation so complicated )-:! (It seems such a simple
process when it works.)
--
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. **

WANTED, Dead AND Alive: Schrodinger's Cat

"J. P. Gilliver (John)" <G6JPG DeleteThis @soft255.demon.co.uk> wrote in message
news:qK6nGywsSbhJFwiP@soft255.demon.co.uk...
> In message <OB#H76GhJHA.1288@TK2MSFTNGP02.phx.gbl>, MEB
> <MEB@not.?.invalid> writes:
> >
> > You MAY be experiencing conflicts with an installation of one of the
> >'generic' driver libraries that might have been installed.
> >I admit I haven't used the UBCD, however, when testing some of these
> >compiled "upgrades/updates", I found similar issues.
>
> Thanks for thinking.
>
> > If I remember correctly, you installed this UBCD over an already updated
OS
> >[besides the "lite" aspect], and with other "unofficially updates"
>
> I don't think I'd done many if any updates, other than the lite,
> official or otherwise; this is a non-internet machine, and besides I
> don't usually like to do updates unless I am very sure what they do.
> However, the system has certainly had assorted third-party utilities
> installed over the years, which probably has the same effect.
>
> >previously installed. This makes it more than slightly difficult to
diagnose
> >as there are likely too many "unknown" [to us] modifications [and which
you
> >may not remember].
>
> You're right there (both in that it makes it hard for you to diagnose,
> and that I won't remember!).
> >
> > You can try monitoring the installs with *sysinternals' filemon*
[available
> >on Microsoft] for the exact failure.
>
> Hmm. I have a lot of work to do.
> >
> > You can also attempt a "fake install" - unzip the driver to some folder,
> >use Dependency Walker to open the file, and *profile* the setup file [if
> >applicable] or by opening the individual files, searching for the
breakdown
> >[usually shown in red, ignore the two normal ones {missing XP files}].
>
> I don't _think_ it's the installer, as I've had it for a variety of
> drivers from a variety of sources - the sound hardware (Realtek), a
> couple of cameras (a microscope and a binoculars camera), and assorted
> novelties (dreamcheeky). It seems to stop at the same place during the
> driver install, or in the case of the sound hardware if I "remove" it
> and restart the machine, it locks up at the driver load during the
> restart. I have tried unzipping the driver installers (usually
> executables these days) and manually installing, pointing to where I'd
> unzipped when prompted, and it's always the driver loading process
> (usually blaming rundll32, but I know that's usually just a scapegoat)
> that seems to fail, always at the same point.
> >
> >Here's an old diagnostic page I created for general reference:
> >http://peoplescounsel.org/ref/gen/sys_diagnos.htm
> >
> Thanks for that - I clearly have a LOT of work to do.
>
> Why is driver installation so complicated )-:! (It seems such a simple
> process when it works.)
> --
> J. P. Gilliver. UMRA: 1960/<1985
MB++G.5AL(+++)IS-P--Ch+(p)Ar+T[?]H+Sh0!:`)DNAf

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.

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.

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.

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..

--
~
--
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)" <G6JPG.DeleteThis@soft255.demon.co.uk> wrote in
news:1MHAXxvY9ahJFwQG@soft255.demon.co.uk:

> In message <Xns9BA49C4371CDEthanexit.DeleteThis@209.197.15.184>,
> thanatoid <waiting.DeleteThis@the.exit.invalid> writes:
>>"J. P. Gilliver (John)" <G6JPG.DeleteThis@soft255.demon.co.uk> wrote
>>in news:2m$gdbn70ChJFwzP@soft255.demon.co.uk:
>>
>><SNIP>
>>
>>> Thanks in advance for positive suggestions ...
>>
>>FINALLY start using an imaging program a kind company
>>provided you with for free...
>>
> Won't help me restore an image of a system from before I
> received it though ... (-:

Would have if you didn't take your sweet time installing it, IF
you ever did.

--
"Who knows what the OP is talking about?"
(about thanatoid)

In message <Xns9BA589661AD05thanexit.DeleteThis@209.197.15.184>, thanatoid
<waiting.DeleteThis@the.exit.invalid> writes:
[]
>>>FINALLY start using an imaging program a kind company
>>>provided you with for free...
>>>
>> Won't help me restore an image of a system from before I
>> received it though ... (-:
>
>Would have if you didn't take your sweet time installing it, IF
>you ever did.
>
How would using a backup/image program help me restore the system to how
it was before I received the backup/image program? That's what I meant,
sorry if not clear.
--
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...

In message <#EZHI$JhJHA.5000@TK2MSFTNGP04.phx.gbl>, MEB
<MEB@not.?.invalid> 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...

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)" <G6JPG RemoveThis @soft255.demon.co.uk> wrote in message
news:1TDwQwHL9$hJFwBw@soft255.demon.co.uk...
> In message <#EZHI$JhJHA.5000@TK2MSFTNGP04.phx.gbl>, MEB
> <MEB@not.?.invalid> 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...