Driver is Invalid error - additional possibilities to check?

How do you get into the BIOS on the XP
-----Original Message-----
I've read a number of past posts where people got
the "Driver is invalid"
message with Windows XP when trying to install a driver,
and have been
through Google (and other) searches that turned up
information on registry
permission problems and reseting the driver.cab file
(e.g. at
http://www.theinquirer.net/?article=2567,
http://support.microsoft.com/default.aspx?scid=kb;en-
us;810882, and
http://support.microsoft.com/?kbid=810509). However,
none of those seem to
work for my particular case, so I am wondering if anyone
has any ideas on
other possibilities. The exact error message received
is:

Cannot install this hardware.

There was a problem installing this hardwa

Media

An error occurred during the installation of this
device.

The data is invalid

Sometimes instead of "Media" above, it gives the
specific driver name I'm
trying to install (either the MOTU PCI GSIF driver or
the MOTU PCI Wave
Driver, for an MOTU PCI Audio device where the basic
driver installs and
works fine in ASIO mode, but these additional driver
protocols, which seem
to ride on top of the base driver won't install
properly).

I should note that things were working just fine until a
couple of weeks
back, when I did a system disk replacement (by backing
up files and system
state information with NTBACKUP, then installing the OS,
which is WinXP Home
here, installing SP1, then restoring the files and
system state information)
for the purposes of gaining more disk space. Most
everything else on the
system seems to be working fine, but there is the
problem with installing
these specific drivers.

While it is possible there may indeed be a registry
permissions issue
involved, it may be that the multiple parts of the MOTU
driver make this a
more complex issue than a similar problem with, say, an
Ethernet adapter or
video card. One suspicion on this is that there may be
some other part of
the registry beyond the PCI section of the hardware
enumeration section that
comes into play. In fact, I noted that an MotuAW
section gets added into
the hardware enumeration area, and seems to be the place
where the GSIF and
Wave drivers would go, so I tried a similar thing with
permissions on that
thread, but that also did not seem to make a
difference. But perhaps there
are still more areas that come into play?

In my research on this issue, I also learned that
attempts at installing a
device create entries in a file called
C:\Windows\setupapi.log. What
appears to be the lines corresponding to my most recent
attempt to install
the GSIF driver are as follows:

[2003/05/15 00:25:35 748.201]
#-198 Command line processed: "C:\WINDOWS\System32
\mmc.exe"
C:\WINDOWS\system32\devmgmt.msc /s
#I060 Set selected driver.
#-019 Searching for hardware ID(s): motuaw\mawgsif
#I022 Found "MotuAW\MAWGSIF" in
C:\WINDOWS\inf\mawgsif.inf; Device: "MOTU
PCI GSIF Driver"; Driver: "MOTU PCI GSIF Driver";
Provider: "Mark of the
Unicorn"; Mfg: "Mark of the Unicorn"; Section
name: "DriverInstall".
#I087 Driver node not trusted, rank changed from
0x00000000 to 0x00008000.
#I023 Actual install section: [DriverInstall.NT]. Rank:
0x00008000.
Effective driver date: 01/01/1601.
#-019 Searching for hardware ID(s): motuaw\mawgsif
#-124 Doing copy-only install of "MOTUAW\MAWGSIF\0000".
#W334 Failed to verify catalog when scanning file queue.
Error 1168: Element
not found.
#E366 An unsigned or incorrectly signed
file "c:\windows\inf\mawgsif.inf"
for driver "MOTU PCI GSIF Driver" will be installed
(Policy=Warn, user said
ok). Error 1168: Element not found.
#W187 Install failed, attempting to restore original
files.
#E362 An unsigned or incorrectly signed
file "c:\windows\inf\mawgsif.inf"
for driver "MOTU PCI GSIF Driver" will be installed
(Policy=Warn). Error
1168: Element not found.
#W187 Install failed, attempting to restore original
files.
#-188 Restoring File: "C:\WINDOWS\system32
\drivers\portcls.sys" from
"C:\WINDOWS\Temp\OLD7.tmp".
#E243 Exemption obtained for protected system file
"C:\WINDOWS\system32\drivers\portcls.sys".
#-188 Restoring File: "C:\WINDOWS\system32
\drivers\stream.sys" from
"C:\WINDOWS\Temp\OLD4.tmp".
#E243 Exemption obtained for protected system file
"C:\WINDOWS\system32\drivers\stream.sys".
#I060 Set selected driver.
#I125 Installing NULL driver for "MOTUAW\MAWGSIF\0000".
#I121 Device install of "MOTUAW\MAWGSIF\0000" finished
successfully.

I am particularly wondering about the lines that include
the message, "Error
1168: Element not found." Those seem to come at the
point where some kind
of failure is detected, but it isn't clear to me what
specifically is
failing there, and the searches I did on the net didn't
seem to turn up
anything useful.

That is really all I know with respect to the symptoms
and the little I know
of the actual problem. If anyone has any ideas on other
things to try, I'd
greatly appreciate them as I am mostly out of ideas at
the moment.

Rick
--
==========================================
Rick Paul
Closet Cowboy Music (ASCAP)
Lake Forest, California
E-mail:
Web: http://home.earthlink.net/~rickpaul
MP3s: http://rickpaul.iuma.com
"Ho Ho Ho Spice" (benefit Christmas CD for HOSPICE):
http://www.cdbaby.com/hohohospice
==========================================


.

wrote in message
...
: How do you get into the BIOS on the XP

I'm not sure I understand the relevance of the question, but I think the
answer is you don't get into the BIOS under XP, but rather under whichever
motherboard you are using. On mine (IWILL KK266plus), it is simply hitting
the DEL key at a certain point early in the bootup sequence. Different
motherboards may use different key sequences to do that.

Rick

--
==========================================
Rick Paul
Closet Cowboy Music (ASCAP)
Lake Forest, California
E-mail:
Web: http://home.earthlink.net/~rickpaul
MP3s: http://rickpaul.iuma.com
"Ho Ho Ho Spice" (benefit Christmas CD for HOSPICE):
http://www.cdbaby.com/hohohospice
==========================================