problems with 32.dll when loading drivers

In message , thanatoid
writes:
"J. P. Gilliver (John)" wrote in
:

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

In message , thanatoid
writes:
"J. P. Gilliver (John)" wrote in
:

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

In message , MEB
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

In message , MEB
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)" wrote in message
...
In message , MEB
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)" wrote in message
...
In message , MEB
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)" wrote in
:

In message ,
thanatoid writes:
"J. P. Gilliver (John)" wrote
in :

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)

"J. P. Gilliver (John)" wrote in
:

In message ,
thanatoid writes:
"J. P. Gilliver (John)" wrote
in :

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