Driver is Invalid error - additional possibilities to check?

[Rick Paul]

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 hardware:

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

[BobS]

What is the device you are trying to install? Do you have the latest device
driver for this product? Is the device actually supported by XP SP1?
Bob

"Rick Paul" > wrote in 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 hardware:
>
> 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
> ==========================================
>
>

[Rick Paul]

"BobS" > wrote in message
...
: What is the device you are trying to install? Do you have the latest
device
: driver for this product? Is the device actually supported by XP SP1?

The actual hardware device is a MOTU PCI-324, which is the PCI card that
supports the MOTU 2408 mkII. It is a reasonably high-end audio interface
for digital recording work.

The low level hardware drivers actually installed just fine, as I can use
the device in ASIO mode (a semi-open low latency protocol designed by
Steinberg but usable in a number of pro audio applications). It is two
additional audio protocol drivers, which sit on top of the lower layers,
that are having the problems. In particular the Wave driver (used for WDM
kernel streaming, which is another low latency protocol blessed by MS and
used in a smaller number of pro audio applications -- this one also is the
generic MME-style interface to the OS, such as for Media Player and similar
apps) and the GSIF driver (used specifically for Tascam GigaStudio) are the
ones having the installation problems.

I do have the latest driver for the product, and the same exact drivers
worked just fine (for well over a year with WinXP Home, and ever since SP1
was out with that) before my hard disk replacement.

In terms of the "supported by XP SP1" question, if you mean whether MS
provides the driver or blesses the driver, it would not be supported -- i.e.
the vendor has not certified the drivers with MS (this is pretty common for
pro audio hardware due to the economics of the certification process).
However, the vendor does support XP SP1, and I was previously running it all
just fine on XP SP1. It is only after my system disk replacement that
things went awry.

I might add that, despite the stock advice on registry permissions' not
having worked in my case, I still think there is some possibility it is a
registry permissions problem. However, it isn't the simple PCI device
thing, and I'm not sure how to trace down all potential parts of the
registry that could be involved, or, for that matter, what the permissions
should be should I find something in another part of the registry. However,
I'd think the issue could be similar for others with devices that have
multiple layers, where there is a low layer that actually talks to the
hardware and some higher layers available for use with different protocols
and which talk to the lower layer. I'm hoping someone out there may have
had experience with such a scenario, and might be able to shed some light on
how they got to the bottom of their problem. (I'm pretty good at doing
detective work in general, including within the registry in many cases.)

Unfortunately, the device vendor's support leaves a huge amount to be
desired. I sent them a query on this issue over a week ago, and they have
yet to even acknowledge the message, no less respond with anything
meaningful. This is consistent with past experience, too, unfortunately.
Luckily the device usually just works fine, and it provides a lot more
connectivity than most of the other similar devices out there, so the
vendor's support hasn't been a critical issue for me in the past. This
time, though, I haven't had any luck as yet finding a solution elsewhere,
and the two drivers are required for applications I use pretty frequently.

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

[Quaoar]

Rick Paul wrote:
> 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 hardware:
>
> 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

Is it possible that you need to remove all the card drivers, then the
card itself, then reinstall the drivers, and then the card? I.E.,
reverting to a new install of the entire card, just like you did
originally?

Q

[Rick Paul]

"Quaoar" > wrote in message
...
: Is it possible that you need to remove all the card drivers, then the
: card itself, then reinstall the drivers, and then the card? I.E.,
: reverting to a new install of the entire card, just like you did
: originally?

Thanks for the idea. I have tried all but the physical deinstallation of
the card portion of that. Perhaps that might be something else to try, but
I'm extremely skeptical that it will make a difference and it is a real
hassle to do with all the cables hooked up to my system and the location of
the system.

In particular, I have never had to remove the card before to deal with the
drivers or driver updates. While the vendor does suggest that, what has
generally worked for me is to delete the devices (in Device Manager), remove
the software (through add/remove programs in Control panel), install any
updated software, then reboot to allow redetecting the devices. The only
difference doing this versus the actual hardware removal is one boot up
without the device in it, but that seems not to have been necessary in the
past.

Also, I think it is relevant that the lower level device drivers, which are
the part that actually talk to the hardware, are installed and working
properly. (For example, I can use the device with SONAR in ASIO mode.)
What isn't installing is the higher level protocol drivers (i.e. Wave, which
is also for WDM kernel streaming, and GSIF).

My main theory is that the problem may be similar to the one that has been
documented with permissions in the PCI device enumeration section of the
registry, but that the higher level drivers involved have to do something
elsewhere that I'm not properly identifying to be able to inspect and modify
the permissions. (I did find one other area that I thought might be
promising, but it didn't end up making a difference, so either my theory is
all wet or that just wasn't the right area.)

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

[Quaoar]

Rick Paul wrote:
> "Quaoar" > wrote in message
> ...
>> Is it possible that you need to remove all the card drivers, then the
>> card itself, then reinstall the drivers, and then the card? I.E.,
>> reverting to a new install of the entire card, just like you did
>> originally?
>
> Thanks for the idea. I have tried all but the physical
> deinstallation of the card portion of that. Perhaps that might be
> something else to try, but I'm extremely skeptical that it will make
> a difference and it is a real hassle to do with all the cables hooked
> up to my system and the location of the system.
>
> In particular, I have never had to remove the card before to deal
> with the drivers or driver updates. While the vendor does suggest
> that, what has generally worked for me is to delete the devices (in
> Device Manager), remove the software (through add/remove programs in
> Control panel), install any updated software, then reboot to allow
> redetecting the devices. The only difference doing this versus the
> actual hardware removal is one boot up without the device in it, but
> that seems not to have been necessary in the past.
>
> Also, I think it is relevant that the lower level device drivers,
> which are the part that actually talk to the hardware, are installed
> and working properly. (For example, I can use the device with SONAR
> in ASIO mode.) What isn't installing is the higher level protocol
> drivers (i.e. Wave, which is also for WDM kernel streaming, and GSIF).
>
> My main theory is that the problem may be similar to the one that has
> been documented with permissions in the PCI device enumeration
> section of the registry, but that the higher level drivers involved
> have to do something elsewhere that I'm not properly identifying to
> be able to inspect and modify the permissions. (I did find one other
> area that I thought might be promising, but it didn't end up making a
> difference, so either my theory is all wet or that just wasn't the
> right area.)
>
> Rick

With all the other similar driver and device problems in XP, I'm still
betting that card removal/reinstall will be necessary. Good Luck!

Q

[Paul]

Did you try going to start/run/regedit? Then
going here?

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\PCI. The links you gave isnt
for this.

Then you click on the device, then permission.
and ticking Full control? then reboot. Then
the driver may load for the device.


"Quaoar" > wrote in message
...
> Rick Paul wrote:
> > 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 hardware:
> >
> > 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
>
> Is it possible that you need to remove all the card drivers, then the
> card itself, then reinstall the drivers, and then the card? I.E.,
> reverting to a new install of the entire card, just like you did
> originally?
>
> Q
>
>

[Rick Paul]

"Paul" > wrote in message
...
: Did you try going to start/run/regedit? Then
: going here?
:
: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\PCI. The links you gave isnt
: for this.
:
: Then you click on the device, then permission.
: and ticking Full control? then reboot. Then
: the driver may load for the device.

I thought one of the links I had was for this, but, in any event, yes, I did
try this, and it didn't help.

One thing I should clarify (or maybe just summarize since it was mentioned
in my longer post), the basic low level driver for this device installs and
works fine. That is sufficient for ASIO (a low latency audio protocol)
support. It is two higher level drivers, the Wave driver (which is also for
WDM kernel streaming) and GSIF (for GigaStudio), that won't install properly
and give the "data is invalid" message.

My strong suspicion is that there is a similar permissions issue elsewhere
in the registry, but, if so, I've had no luck tracking it down, or the
changes I've made have not helped. For example, I tried a similar thing at
the Services level (same basic place in the registry, but Services instead
of PCI), which seemed like it might be logical, but it didn't help.

I started trying to trace down what the INF files for the driver
installation do the other day, but they also call reference ks.inf and
wdmaudio.inf, and I didn't get so far in grokking them, at least to this
point.

Also, I know I mentioned it previously, but this did work at one point --
i.e. before my disk replacement (which involved system backup, install of
WinXP Home and SP1 on the new disk, then restore from backups, including
system state). So it seems like it is probably something that went awry in
the process of restoring system state.

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

[Paul]

Whats your PC? Rick Paul?

Brand/model etc?

This is some kind of Music thing? right?

With firewire? Have you tried deleting
the entry in Device Manager. And going
to Windowsupdate site, to see if that picks
up a driver?

Also, I found this site, which notes
some probs. It says if u have a Dell Dimension
8100 u may need a bios update if u use 2000 or XP.

Has yours got the firewire interface?

http://www.swee****er.com/insync/11/26/2001/

"Rick Paul" > wrote in message
...
> "Paul" > wrote in message
> ...
> : Did you try going to start/run/regedit? Then
> : going here?
> :
> : HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\PCI. The links you gave
isnt
> : for this.
> :
> : Then you click on the device, then permission.
> : and ticking Full control? then reboot. Then
> : the driver may load for the device.
>
> I thought one of the links I had was for this, but, in any event, yes, I
did
> try this, and it didn't help.
>
> One thing I should clarify (or maybe just summarize since it was mentioned
> in my longer post), the basic low level driver for this device installs
and
> works fine. That is sufficient for ASIO (a low latency audio protocol)
> support. It is two higher level drivers, the Wave driver (which is also
for
> WDM kernel streaming) and GSIF (for GigaStudio), that won't install
properly
> and give the "data is invalid" message.
>
> My strong suspicion is that there is a similar permissions issue elsewhere
> in the registry, but, if so, I've had no luck tracking it down, or the
> changes I've made have not helped. For example, I tried a similar thing
at
> the Services level (same basic place in the registry, but Services instead
> of PCI), which seemed like it might be logical, but it didn't help.
>
> I started trying to trace down what the INF files for the driver
> installation do the other day, but they also call reference ks.inf and
> wdmaudio.inf, and I didn't get so far in grokking them, at least to this
> point.
>
> Also, I know I mentioned it previously, but this did work at one point --
> i.e. before my disk replacement (which involved system backup, install of
> WinXP Home and SP1 on the new disk, then restore from backups, including
> system state). So it seems like it is probably something that went awry
in
> the process of restoring system state.
>
> 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
> ==========================================
>
>

[Paul]

Or have u tried www.motu.com

For the updated drivers?

"Rick Paul" > wrote in message
...
> "Paul" > wrote in message
> ...
> : Did you try going to start/run/regedit? Then
> : going here?
> :
> : HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\PCI. The links you gave
isnt
> : for this.
> :
> : Then you click on the device, then permission.
> : and ticking Full control? then reboot. Then
> : the driver may load for the device.
>
> I thought one of the links I had was for this, but, in any event, yes, I
did
> try this, and it didn't help.
>
> One thing I should clarify (or maybe just summarize since it was mentioned
> in my longer post), the basic low level driver for this device installs
and
> works fine. That is sufficient for ASIO (a low latency audio protocol)
> support. It is two higher level drivers, the Wave driver (which is also
for
> WDM kernel streaming) and GSIF (for GigaStudio), that won't install
properly
> and give the "data is invalid" message.
>
> My strong suspicion is that there is a similar permissions issue elsewhere
> in the registry, but, if so, I've had no luck tracking it down, or the
> changes I've made have not helped. For example, I tried a similar thing
at
> the Services level (same basic place in the registry, but Services instead
> of PCI), which seemed like it might be logical, but it didn't help.
>
> I started trying to trace down what the INF files for the driver
> installation do the other day, but they also call reference ks.inf and
> wdmaudio.inf, and I didn't get so far in grokking them, at least to this
> point.
>
> Also, I know I mentioned it previously, but this did work at one point --
> i.e. before my disk replacement (which involved system backup, install of
> WinXP Home and SP1 on the new disk, then restore from backups, including
> system state). So it seems like it is probably something that went awry
in
> the process of restoring system state.
>
> 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
> ==========================================
>
>

[Rick Paul]

"Paul" > wrote in message
...
: Whats your PC? Rick Paul?
:
: Brand/model etc?

No brand. It is an IWILL KK266plus motherboard with Athlon XP 1600+ CPU. I
might note, this is the same PC on which all this was working prior to my
system disk upgrade.

: This is some kind of Music thing? right?

Yes, the MOTU PCI-324 interface for the MOTU 2408 mkII. It is a digital
audio interface with multiple software level interfaces (i.e. ASIO,
Wave/WDM-KS, GSIF).

: With firewire? Have you tried deleting
: the entry in Device Manager. And going
: to Windowsupdate site, to see if that picks
: up a driver?

It is not FireWire, but I have tried deleting the devices and so on.
Windowsupdate won't help, though because the driver is not built into
Windows.

: Also, I found this site, which notes
: some probs. It says if u have a Dell Dimension
: 8100 u may need a bios update if u use 2000 or XP.

No Dell system here, and the very same system was working with all the very
same ingredients prior to my hard disk upgrade. Since just replacing the
system hard disk should not cause any new issues with the MOTU hardware at
the system level, this basically means it *has* to be a software-level
and/or settings-level issue.

: Has yours got the firewire interface?

No. I will say, though, that I was in contact with a guy who had very
similar symptoms to mine installing a FireWire interface, and, as yet, has
still not gotten to the bottom of it even after some lengthy experience with
MS support. I suspect there could be a similar issue there, in particular
because I suspect there is probably a low-level firewire interface (similar
to the low level PCI-324 interface that is actually working on my MOTU
hardware in concept) and then higher level interfaces for whatever devices
sit on top of the firewire (similar to the GSIF and Wave drivers that sit on
top of the lower level PCI-324 interface in my case).

I suspect the simple cases given with respect to the PCI thread permissions
in the registry are probably limited to devices that don't have the same
kinds of layers.

: http://www.swee****er.com/insync/11/26/2001/

I read this, and, beyond my not having Dell, I'm confident it is not
applicable. The PCI-324 has had problems working in a number of
motherboards. Basically it isn't very friendly about PCI bus sharing, and
is very demanding of bus bandwidth. Historically, there have been a number
of motherboards, especially relatively new ones, that it doesn't get along
with very well, and I strongly suspect the BIOS patches being talked about
here, which make reference to ATA 133 disks, which could conceivably also be
pretty demanding, are to address issues in this area.

Thanks for the ideas. I am 99.99% certain there is no hardware issue here
because, other than the disk drive change, nothing has changed on that front
since when it was working.

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

[Rick Paul]

"Paul" > wrote in message
...
: Or have u tried www.motu.com
:
: For the updated drivers?

I do have the latest drivers, and these same drivers worked previously, too.
Unfortunately, MOTU's tech support has been totally useless -- they didn't
even reply to acknowledge my message on this to them, no less to suggest
anything to try.

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

[Paul]

OK hmmm how many PCI devices have
u got installed Rick? A common prob with some
mobos, is depending on what PCI cards
you have, and what slot you've put them in.

If u put a PCI card in a certain
PCI slot, it wont work. I had this prob with
this mobo. I dont know if the modem was
conflicting with another PCI card / PCI address
(but it didnt show it was conflicting in device
manager), (or whether the PCI slot is actually dead)!
BUT when I moved it to another PCI slot,
it worked.

And Windows picked it up so it could install
the driver. That maybe another thing to check.

You could try moving it to another PCI slot

To see what happens.
"Rick Paul" > wrote in message
...
> "Paul" > wrote in message
> ...
> : Whats your PC? Rick Paul?
> :
> : Brand/model etc?
>
> No brand. It is an IWILL KK266plus motherboard with Athlon XP 1600+ CPU.
I
> might note, this is the same PC on which all this was working prior to my
> system disk upgrade.
>
> : This is some kind of Music thing? right?
>
> Yes, the MOTU PCI-324 interface for the MOTU 2408 mkII. It is a digital
> audio interface with multiple software level interfaces (i.e. ASIO,
> Wave/WDM-KS, GSIF).
>
> : With firewire? Have you tried deleting
> : the entry in Device Manager. And going
> : to Windowsupdate site, to see if that picks
> : up a driver?
>
> It is not FireWire, but I have tried deleting the devices and so on.
> Windowsupdate won't help, though because the driver is not built into
> Windows.
>
> : Also, I found this site, which notes
> : some probs. It says if u have a Dell Dimension
> : 8100 u may need a bios update if u use 2000 or XP.
>
> No Dell system here, and the very same system was working with all the
very
> same ingredients prior to my hard disk upgrade. Since just replacing the
> system hard disk should not cause any new issues with the MOTU hardware at
> the system level, this basically means it *has* to be a software-level
> and/or settings-level issue.
>
> : Has yours got the firewire interface?
>
> No. I will say, though, that I was in contact with a guy who had very
> similar symptoms to mine installing a FireWire interface, and, as yet, has
> still not gotten to the bottom of it even after some lengthy experience
with
> MS support. I suspect there could be a similar issue there, in particular
> because I suspect there is probably a low-level firewire interface
(similar
> to the low level PCI-324 interface that is actually working on my MOTU
> hardware in concept) and then higher level interfaces for whatever devices
> sit on top of the firewire (similar to the GSIF and Wave drivers that sit
on
> top of the lower level PCI-324 interface in my case).
>
> I suspect the simple cases given with respect to the PCI thread
permissions
> in the registry are probably limited to devices that don't have the same
> kinds of layers.
>
> : http://www.swee****er.com/insync/11/26/2001/
>
> I read this, and, beyond my not having Dell, I'm confident it is not
> applicable. The PCI-324 has had problems working in a number of
> motherboards. Basically it isn't very friendly about PCI bus sharing, and
> is very demanding of bus bandwidth. Historically, there have been a
number
> of motherboards, especially relatively new ones, that it doesn't get along
> with very well, and I strongly suspect the BIOS patches being talked about
> here, which make reference to ATA 133 disks, which could conceivably also
be
> pretty demanding, are to address issues in this area.
>
> Thanks for the ideas. I am 99.99% certain there is no hardware issue here
> because, other than the disk drive change, nothing has changed on that
front
> since when it was working.
>
> 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
> ==========================================
>
>

[Rick Paul]

"Paul" > wrote in message
...
: OK hmmm how many PCI devices have
: u got installed Rick? A common prob with some
: mobos, is depending on what PCI cards
: you have, and what slot you've put them in.
:
: If u put a PCI card in a certain
: PCI slot, it wont work. I had this prob with
: this mobo. I dont know if the modem was
: conflicting with another PCI card / PCI address
: (but it didnt show it was conflicting in device
: manager), (or whether the PCI slot is actually dead)!
: BUT when I moved it to another PCI slot,
: it worked.

I appreciate the ideas -- and, believe me, I'm getting near the point of
grasping for straws, so even really far-fetched ideas are welcome. However,
on this particular issue the PCI level is working just fine, and the whole
thing was working in the same exact configuration -- i.e. same PCI slots,
same motherboard, same RAM, same OS, same drivers, ... same everything --
prior to my system disk replacement. It is only the higher level drivers
that won't install, not the PCI-level stuff (and the ASIO driver doesn't
require the higher level stuff, so it is working fine in ASIO-compliant
applications, like Cakewalk's SONAR 2.2, just not in applications that need
a Wave or GSIF interface, such as Sound Forge 5 and GigaStudio 2.5x,
respectively). It really does have to be something at the software setup or
registry level.

I do have one new possible hint, though, which I may possibly have mentioned
previously, but, if so, probably buried it in the details. In particular,
I've noticed that my printer, a Canon BJC-610, causes the OS to put a "new
hardware detected" message in certain cases (haven't quite figured out what
those cases are as it isn't every time I power up the printer), and the
automatic attempt to install the driver there also results in the "Data is
Invalid" message.

Now, in this case, the printer is fully working in Windows as far as I can
tell, so I'm not real clear on what isn't installing -- perhaps an automatic
driver update I suppose, but, then, why would it have the "new hardware
detected message" instead of just a normal "there are new updates to
install" message?

But what strikes me here is whatever the area is that is causing the printer
to get this message might well be common with what is causing the
higher-level MOTU PCI drivers to get the message. And perhaps since the
printer is a lot more popular a device, if for no other reason than it's
consumer-oriented market compared to the semi-pro and up audio production
market of the MOTU, there may be more experience out there to be found. I
haven't even started researching it from that angle yet, but at least it
provides another ray of hope since that one also would have nothing to do
with the PCI level which is the main area where this problem has been
documented to date. :-)

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

[Paul]

Have u tried this Rick?

I saw this on a forum site.

the MOTU card is quite picky for me during installation. Be sure to run the
setup file on the CD-rom before installing the card. Check under device
manager that all 3 drivers are added under "sound devices" ....there should
be two MOTU drivers and a "wave" driver as well.

I have since gotten the MOTU working, without the use of the CD. I
uninstalled the software that I got from MOTU's website, uninstaled the PCI
card, reinstalled the software, reinstalled the PCI card, and all worked
great. The cd was not even needed, although I'm sure it would have made
things easier. Thaks for the help here, and remember, if all else fails,
read the instructions.




"Rick Paul" > wrote in message
...
> "Paul" > wrote in message
> ...
> : OK hmmm how many PCI devices have
> : u got installed Rick? A common prob with some
> : mobos, is depending on what PCI cards
> : you have, and what slot you've put them in.
> :
> : If u put a PCI card in a certain
> : PCI slot, it wont work. I had this prob with
> : this mobo. I dont know if the modem was
> : conflicting with another PCI card / PCI address
> : (but it didnt show it was conflicting in device
> : manager), (or whether the PCI slot is actually dead)!
> : BUT when I moved it to another PCI slot,
> : it worked.
>
> I appreciate the ideas -- and, believe me, I'm getting near the point of
> grasping for straws, so even really far-fetched ideas are welcome.
However,
> on this particular issue the PCI level is working just fine, and the whole
> thing was working in the same exact configuration -- i.e. same PCI slots,
> same motherboard, same RAM, same OS, same drivers, ... same everything --
> prior to my system disk replacement. It is only the higher level drivers
> that won't install, not the PCI-level stuff (and the ASIO driver doesn't
> require the higher level stuff, so it is working fine in ASIO-compliant
> applications, like Cakewalk's SONAR 2.2, just not in applications that
need
> a Wave or GSIF interface, such as Sound Forge 5 and GigaStudio 2.5x,
> respectively). It really does have to be something at the software setup
or
> registry level.
>
> I do have one new possible hint, though, which I may possibly have
mentioned
> previously, but, if so, probably buried it in the details. In particular,
> I've noticed that my printer, a Canon BJC-610, causes the OS to put a "new
> hardware detected" message in certain cases (haven't quite figured out
what
> those cases are as it isn't every time I power up the printer), and the
> automatic attempt to install the driver there also results in the "Data is
> Invalid" message.
>
> Now, in this case, the printer is fully working in Windows as far as I can
> tell, so I'm not real clear on what isn't installing -- perhaps an
automatic
> driver update I suppose, but, then, why would it have the "new hardware
> detected message" instead of just a normal "there are new updates to
> install" message?
>
> But what strikes me here is whatever the area is that is causing the
printer
> to get this message might well be common with what is causing the
> higher-level MOTU PCI drivers to get the message. And perhaps since the
> printer is a lot more popular a device, if for no other reason than it's
> consumer-oriented market compared to the semi-pro and up audio production
> market of the MOTU, there may be more experience out there to be found. I
> haven't even started researching it from that angle yet, but at least it
> provides another ray of hope since that one also would have nothing to do
> with the PCI level which is the main area where this problem has been
> documented to date. :-)
>
> 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
> ==========================================
>
>

[Rick Paul]

Thanks, Paul. Yes, I've tried that. As mentioned before, I've had the card
working. The problem is only since my system disk replacement. I really
think something got messed up in registry permissions or something similar.

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


"Paul" > wrote in message
...
: Have u tried this Rick?
:
: I saw this on a forum site.
:
: the MOTU card is quite picky for me during installation. Be sure to run
the
: setup file on the CD-rom before installing the card. Check under device
: manager that all 3 drivers are added under "sound devices" ....there
should
: be two MOTU drivers and a "wave" driver as well.
:
: I have since gotten the MOTU working, without the use of the CD. I
: uninstalled the software that I got from MOTU's website, uninstaled the
PCI
: card, reinstalled the software, reinstalled the PCI card, and all worked
: great. The cd was not even needed, although I'm sure it would have made
: things easier. Thaks for the help here, and remember, if all else fails,
: read the instructions.
:
:
:
:
: "Rick Paul" > wrote in message
: ...
: > "Paul" > wrote in message
: > ...
: > : OK hmmm how many PCI devices have
: > : u got installed Rick? A common prob with some
: > : mobos, is depending on what PCI cards
: > : you have, and what slot you've put them in.
: > :
: > : If u put a PCI card in a certain
: > : PCI slot, it wont work. I had this prob with
: > : this mobo. I dont know if the modem was
: > : conflicting with another PCI card / PCI address
: > : (but it didnt show it was conflicting in device
: > : manager), (or whether the PCI slot is actually dead)!
: > : BUT when I moved it to another PCI slot,
: > : it worked.
: >
: > I appreciate the ideas -- and, believe me, I'm getting near the point of
: > grasping for straws, so even really far-fetched ideas are welcome.
: However,
: > on this particular issue the PCI level is working just fine, and the
whole
: > thing was working in the same exact configuration -- i.e. same PCI
slots,
: > same motherboard, same RAM, same OS, same drivers, ... same
everything --
: > prior to my system disk replacement. It is only the higher level
drivers
: > that won't install, not the PCI-level stuff (and the ASIO driver doesn't
: > require the higher level stuff, so it is working fine in ASIO-compliant
: > applications, like Cakewalk's SONAR 2.2, just not in applications that
: need
: > a Wave or GSIF interface, such as Sound Forge 5 and GigaStudio 2.5x,
: > respectively). It really does have to be something at the software
setup
: or
: > registry level.
: >
: > I do have one new possible hint, though, which I may possibly have
: mentioned
: > previously, but, if so, probably buried it in the details. In
particular,
: > I've noticed that my printer, a Canon BJC-610, causes the OS to put a
"new
: > hardware detected" message in certain cases (haven't quite figured out
: what
: > those cases are as it isn't every time I power up the printer), and the
: > automatic attempt to install the driver there also results in the "Data
is
: > Invalid" message.
: >
: > Now, in this case, the printer is fully working in Windows as far as I
can
: > tell, so I'm not real clear on what isn't installing -- perhaps an
: automatic
: > driver update I suppose, but, then, why would it have the "new hardware
: > detected message" instead of just a normal "there are new updates to
: > install" message?
: >
: > But what strikes me here is whatever the area is that is causing the
: printer
: > to get this message might well be common with what is causing the
: > higher-level MOTU PCI drivers to get the message. And perhaps since the
: > printer is a lot more popular a device, if for no other reason than it's
: > consumer-oriented market compared to the semi-pro and up audio
production
: > market of the MOTU, there may be more experience out there to be found.
I
: > haven't even started researching it from that angle yet, but at least it
: > provides another ray of hope since that one also would have nothing to
do
: > with the PCI level which is the main area where this problem has been
: > documented to date. :-)
: >
: > 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
: > ==========================================
: >
: >
:
: