winaspi32.dll

  • Thread starter Thread starter oldgit
  • Start date Start date
O

oldgit

Hi can anyone tell me me where to look to find this file which i need,
apparently, to play DVD's on my pc. since my system crashed in june
and had to reinstall XP etc i cant play these. have tried tucows for
players but none have worked so far1 thanx for any help.Don
 
oldgit said:
Hi can anyone tell me me where to look to find this file which i need,
apparently, to play DVD's on my pc. since my system crashed in june
and had to reinstall XP etc i cant play these. have tried tucows for
players but none have worked so far1 thanx for any help.Don
Click to expand...

I think the file you need is wnaspi32.dll, not winaspi32.dll

Try this:
http://www.dll-files.com/dllindex/dll-files.shtml?wnaspi32

Copy it to your \windows\system32 folder and then register it:

Start/Run and enter:

regsvr32 wnaspi32.dll
 
oldgit said:
Hi can anyone tell me me where to look to find this file which i need,
apparently, to play DVD's on my pc. since my system crashed in june
and had to reinstall XP etc i cant play these. have tried tucows for
players but none have worked so far1 thanx for any help.Don
Click to expand...

The suggestion here, is Microsoft SPTI is a substitute for ASPI.

http://en.wikipedia.org/wiki/Aspi

I have a clean install of WinXP SP3, and there is no winaspi32.dll
present.

You can run Nero Infotool, and it has an ASPI_check section, for
listing ASPI files. I seem to remember, with some older OS I used,
needing to visit Adaptec and download their package. Adaptec
still offers an ASPI package, which includes ASPIchk.exe so you
can list what versions of ASPI are present. Having different
versions of ASPI, or having burner packages add their own
particular release, was a recipe for trouble in the past.
The last tab on this InfoTool window, is also capable of listing
the version of ASPI which is present or not. Mine is empty.
One of the reasons for having ASPI_check capabilities around,
is to unravel "ASPI mess syndrome" when multiple burner packages
were installed.

http://www.cdspeed2000.com/files/NeroInfoTool_403.zip

So I'm not clear on whether having an ASPI layer present, as well
as whatever Microsoft uses, would lead to future problems.
Perhaps some older application is specifically searching for
those extensions, without even attempting to reach the hardware ?

I downloaded this a few days ago (not installed, but unzipped for
examination). This would be an example of ASPI files. You may
want to drill down the Adaptec site, and make sure you're getting
a correct version for your OS. I didn't bookmark the page I got
this from. This is just the downloaded file itself.

http://download.adaptec.com/software_pc/aspi/aspi_471a2.exe

To handle that file safely, what you could try, is setting
a System Restore point, install the ASPI drivers, reboot as
required. If any testing you do fails, you can immediately
use the Restore Point to get your system back the way it
was.

You could also try the Knowledgebase, for more comments on ASPI.

http://support.microsoft.com/search/?adv=1

For example here, they recommend reinstalling Nero 5, if you
upgrade to WinXP. Note that the Infotool above, has a separate
menu item for "ASPI" versus "Nero ASPI", implying Nero is
capable of installing its own version of ASPI.

http://support.microsoft.com/kb/302809

How's that for confusing ? :-)

Paul
 
Paul said:
The suggestion here, is Microsoft SPTI is a substitute for ASPI.

http://en.wikipedia.org/wiki/Aspi

I have a clean install of WinXP SP3, and there is no winaspi32.dll
present.

You can run Nero Infotool, and it has an ASPI_check section, for
listing ASPI files. I seem to remember, with some older OS I used,
needing to visit Adaptec and download their package. Adaptec
still offers an ASPI package, which includes ASPIchk.exe so you
can list what versions of ASPI are present. Having different
versions of ASPI, or having burner packages add their own
particular release, was a recipe for trouble in the past.
The last tab on this InfoTool window, is also capable of listing
the version of ASPI which is present or not. Mine is empty.
One of the reasons for having ASPI_check capabilities around,
is to unravel "ASPI mess syndrome" when multiple burner packages
were installed.

http://www.cdspeed2000.com/files/NeroInfoTool_403.zip

So I'm not clear on whether having an ASPI layer present, as well
as whatever Microsoft uses, would lead to future problems.
Perhaps some older application is specifically searching for
those extensions, without even attempting to reach the hardware ?

I downloaded this a few days ago (not installed, but unzipped for
examination). This would be an example of ASPI files. You may
want to drill down the Adaptec site, and make sure you're getting
a correct version for your OS. I didn't bookmark the page I got
this from. This is just the downloaded file itself.

http://download.adaptec.com/software_pc/aspi/aspi_471a2.exe

To handle that file safely, what you could try, is setting
a System Restore point, install the ASPI drivers, reboot as
required. If any testing you do fails, you can immediately
use the Restore Point to get your system back the way it
was.

You could also try the Knowledgebase, for more comments on ASPI.

http://support.microsoft.com/search/?adv=1

For example here, they recommend reinstalling Nero 5, if you
upgrade to WinXP. Note that the Infotool above, has a separate
menu item for "ASPI" versus "Nero ASPI", implying Nero is
capable of installing its own version of ASPI.

http://support.microsoft.com/kb/302809

How's that for confusing ? :-)

Paul
Click to expand...

The Adaptec download page is here. And makes no mention of
when you should use it.

http://www.adaptec.com/en-US/speed/software_pc/aspi/aspi_471a2_exe.htm

Paul
 
Back
Top