Ripping Audio CD Problems

[Mike M]

It's good to read that you've now managed to solve the problem and that a
pooched ASPI layer was the cause of your problems. I'm not sure what you
meant when you said the copy of aspichk from Adaptec didn't work
correctly - was the download perhaps incomplete or damaged?

> I ran the aspi_chk.exe and it gave the following results:
> Component Version Date Size
> WNASPI32.DLL 4.711(0) 09/30/3 45056
> WINASPI.DLL 1.00(65) 05/08/100 3536
> APIX.VXD 4.711(0) 09/30/3 27723
> ASPIENUM.VXD N/A N/A N/A

WNASPI.32.DLL and APIX.VXD are not the original copies, running an older
version of aspichk (v1.0.0.6) on a Win Me system with EAC working as it
should and that has never installed an application that modifies the ASPI
layer such as EasyCD Creator or DirectCD, I see

Component Version Date Size
WNASPI32.DLL 1.00(65) 05/08/100 36864
WINASPI.DLL 1.00(65) 05/08/100 3536
APIX.VXD 4.00(952) 05/08/100 29497
ASPIENUM.VXD N/A N/A N/A

ASPI is not properly installed. One or more components
have been replaced with older versions of the software.

I was unable to install Any of Adaptec's Aspi v4.60, 4.70 or 4.71.2 due to
there being no Adaptec adapter or an existing copy of Adaptec's aspi layer
so used an old copy of ForceASPI to install v4.60 of the Adaptec ASPI
layer after which I rebooted and then ran aspichk where I now saw

Component Version Date Size
WNASPI32.DLL 4.60(1021) 09/10/99 46056
WINASPI.DLL 4.60(1021) 09/10/99 5600
APIX.VXD 4.60(1021) 09/10/99 22603
ASPIENUM.VXD 4.60(1021) 09/10/99 7743

ASPI is properly installed and is fully operational
One host adapter has been detected

Note that it is ESSENTIAL to reboot following updating the ASPI layer.


Reinstalled EAC v0.99pb3 and all proceeded as it should, my CD-ROM
recognised and CD ripped.

Having forced the installation of the Adaptec ASPI layer I then tried
installing Adaptec's last release of their aspi layer (v4.71-2), after
which I rebooted and ran aspichk which now reported the ASPI layer as
being broken!

Component Version Date Size
WNASPI32.DLL 4.712(0) 07/17/02 45056
WINASPI.DLL 4.60(1021) 09/10/99 5600
APIX.VXD 4.712(0) 07/17/02 23115
ASPIENUM.VXD 4.60(1021) 09/10/99 7743

ASPI is not properly installed. One or more components
have been replaced with older versions of the software.

Just as with your example it appears that only WNASPI32.DLL and APIX.VXD
were updated to the version being installed. However despite this
apparently broken ASPI layer EAC continued to work without problem. I now
uninstalled EAC and attempted to reinstall to see if the broken ASPI layer
would prevent the installation. It did not. I was still able to install
EAC and rip a CD. It would appear that having mixed Adaptec versions of
the four aspi files (as I did) works but not if the files are a mixture of
native Win Me and Adaptec files as was the case in your example.

So what I have learned? Not much other than that EAC can be installed and
work with both Win Me's native aspi layer and also Adaptec's layer if
forcibly installed using ForceASPI. I was even able to run EAC where the
Adaptec ASPI layer was broken, or rather had mixed components from
versions v4.60 and v4.71.2.

I should perhaps add that I had none of these problems when running Win Me
as my main system in 1999/2000 however that was an all scsi system that
included an Adaptec 2940UW scsi card. As a result I was always able to
install Adaptec's aspi layer without problem.

One final, OT, comment. I just wish I could get my second hand Nikon
LS2000 slide scanner to work correctly on my XP box. This is a scsi
scanner and the Nikon Scan software requires a working scsi layer and I've
never managed to get it to work and instead have to use Ed Hamrick's
VueScan software instead. I've been told the problem might be because
that box has a Tekram scsi card and that the Nikon Scan software might
work if I were to instead use an Adaptec scsi card. Time perhaps to dig
out that old 29040UW, either that or fork out for a slide scanner that
connects via USB 2.0.
--
Mike Maltby
mike.maltby@gmail.com


Job <iam@best.slow> wrote:

> Hi Mike,
>
> I wanted to share this with you since you were so willing to
> help. I just ripped some tunes from a CD on my ME system
> using Exact Audio Copy.
>
> These are the steps that made it possible. First I went and
> read the instructions at
> http://radified.com/ASPI/forceaspi.htm . I then downloaded
> the "older version of aspi_check" from
> http://radified.com/Files/. (I had got a copy of
> ASPICHK.exe from Adaptec yesterday but it didn't work well
> in my opinion.)
>
> I ran the aspi_chk.exe and it gave the following results:
> Component Version Date Size
> WNASPI32.DLL 4.711(0) 09/30/3 45056
> WINASPI.DLL 1.00(65) 05/08/100 3536
> APIX.VXD 4.711(0) 09/30/3 27723
> ASPIENUM.VXD N/A N/A N/A
>
> ASPI is not properly installed. One or more
> components
> have been replaced with older versions of the
> software.
>
> I then downloaded and extracted ForceASPI17.zip shown in
> Installation instructions at
> http://radified.com/ASPI/forceaspi.htm
>
> Next I initiated the KILLASPI.BAT, then initiated the
> INSTASPI.BAT, then rebooted.
>
> Another run of aspi_chk.exe showed the following:
> Component Version Date Size
> WNASPI32.DLL 4.60(1021) 09/10/99 45056
> WINASPI.DLL 4.60(1021) 09/10/99 5600
> APIX.VXD 4.60(1021) 09/10/99 22603
> ASPIENUM.VXD 4.60(10210) 09/10/99 7743
>
> ASPI is properly installed and is fully
> operational.
> One host adapter has been detected.
>
> I downloaded and installed EAC from the EAC_095pb5.zip at
> http://radified.com/Files/
> and GLORYBE I can rip now.

 

[Job]

>I'm not sure what you meant when you said the copy of
aspichk from Adaptec
>didn't work correctly

The results showed only ASPI32.DLL and APIX.VXD. More
bothersome leading me to question validity was that the
comment ""ASPI is properly installed and is fully
operational." was very dim when I expected a darker, more
positive print.

Mike I really like your method of troubleshooting, takes me
back to my electronic technic'ing days.

>So what I have learned? Not much

If you can't make sense of it I for sure don't stand a
chance of understanding. I guess I'm happy that I can (at
least for now) use Rippers.

The only thing I can offer in regards to your slide scanner
problem is moral support. If anyone can resolve it I
believe you can.

Cheers to you guy.




"Mike M" <No_Spam@Corned_Beef.Only> wrote in message
news:e6WpkpLQIHA.3400@TK2MSFTNGP03.phx.gbl...
It's good to read that you've now managed to solve the
problem and that a
pooched ASPI layer was the cause of your problems. I'm not
sure what you
meant when you said the copy of aspichk from Adaptec didn't
work
correctly - was the download perhaps incomplete or damaged?

> I ran the aspi_chk.exe and it gave the following results:
> Component Version Date Size
> WNASPI32.DLL 4.711(0) 09/30/3 45056
> WINASPI.DLL 1.00(65) 05/08/100 3536
> APIX.VXD 4.711(0) 09/30/3 27723
> ASPIENUM.VXD N/A N/A N/A

WNASPI.32.DLL and APIX.VXD are not the original copies,
running an older
version of aspichk (v1.0.0.6) on a Win Me system with EAC
working as it
should and that has never installed an application that
modifies the ASPI
layer such as EasyCD Creator or DirectCD, I see

Component Version Date Size
WNASPI32.DLL 1.00(65) 05/08/100 36864
WINASPI.DLL 1.00(65) 05/08/100 3536
APIX.VXD 4.00(952) 05/08/100 29497
ASPIENUM.VXD N/A N/A N/A

ASPI is not properly installed. One or more components
have been replaced with older versions of the software.

I was unable to install Any of Adaptec's Aspi v4.60, 4.70 or
4.71.2 due to
there being no Adaptec adapter or an existing copy of
Adaptec's aspi layer
so used an old copy of ForceASPI to install v4.60 of the
Adaptec ASPI
layer after which I rebooted and then ran aspichk where I
now saw

Component Version Date Size
WNASPI32.DLL 4.60(1021) 09/10/99 46056
WINASPI.DLL 4.60(1021) 09/10/99 5600
APIX.VXD 4.60(1021) 09/10/99 22603
ASPIENUM.VXD 4.60(1021) 09/10/99 7743

ASPI is properly installed and is fully operational
One host adapter has been detected

Note that it is ESSENTIAL to reboot following updating the
ASPI layer.


Reinstalled EAC v0.99pb3 and all proceeded as it should, my
CD-ROM
recognised and CD ripped.

Having forced the installation of the Adaptec ASPI layer I
then tried
installing Adaptec's last release of their aspi layer
(v4.71-2), after
which I rebooted and ran aspichk which now reported the ASPI
layer as
being broken!

Component Version Date Size
WNASPI32.DLL 4.712(0) 07/17/02 45056
WINASPI.DLL 4.60(1021) 09/10/99 5600
APIX.VXD 4.712(0) 07/17/02 23115
ASPIENUM.VXD 4.60(1021) 09/10/99 7743

ASPI is not properly installed. One or more components
have been replaced with older versions of the software.

Just as with your example it appears that only WNASPI32.DLL
and APIX.VXD
were updated to the version being installed. However
despite this
apparently broken ASPI layer EAC continued to work without
problem. I now
uninstalled EAC and attempted to reinstall to see if the
broken ASPI layer
would prevent the installation. It did not. I was still
able to install
EAC and rip a CD. It would appear that having mixed Adaptec
versions of
the four aspi files (as I did) works but not if the files
are a mixture of
native Win Me and Adaptec files as was the case in your
example.

So what I have learned? Not much other than that EAC can be
installed and
work with both Win Me's native aspi layer and also Adaptec's
layer if
forcibly installed using ForceASPI. I was even able to run
EAC where the
Adaptec ASPI layer was broken, or rather had mixed
components from
versions v4.60 and v4.71.2.

I should perhaps add that I had none of these problems when
running Win Me
as my main system in 1999/2000 however that was an all scsi
system that
included an Adaptec 2940UW scsi card. As a result I was
always able to
install Adaptec's aspi layer without problem.

One final, OT, comment. I just wish I could get my second
hand Nikon
LS2000 slide scanner to work correctly on my XP box. This
is a scsi
scanner and the Nikon Scan software requires a working scsi
layer and I've
never managed to get it to work and instead have to use Ed
Hamrick's
VueScan software instead. I've been told the problem might
be because
that box has a Tekram scsi card and that the Nikon Scan
software might
work if I were to instead use an Adaptec scsi card. Time
perhaps to dig
out that old 29040UW, either that or fork out for a slide
scanner that
connects via USB 2.0.
--
Mike Maltby
mike.maltby@gmail.com


Job <iam@best.slow> wrote:

> Hi Mike,
>
> I wanted to share this with you since you were so willing
to
> help. I just ripped some tunes from a CD on my ME system
> using Exact Audio Copy.
>
> These are the steps that made it possible. First I went
and
> read the instructions at
> http://radified.com/ASPI/forceaspi.htm . I then
downloaded
> the "older version of aspi_check" from
> http://radified.com/Files/. (I had got a copy of
> ASPICHK.exe from Adaptec yesterday but it didn't work well
> in my opinion.)
>
> I ran the aspi_chk.exe and it gave the following results:
> Component Version Date Size
> WNASPI32.DLL 4.711(0) 09/30/3 45056
> WINASPI.DLL 1.00(65) 05/08/100 3536
> APIX.VXD 4.711(0) 09/30/3 27723
> ASPIENUM.VXD N/A N/A N/A
>
> ASPI is not properly installed. One or more
> components
> have been replaced with older versions of the
> software.
>
> I then downloaded and extracted ForceASPI17.zip shown in
> Installation instructions at
> http://radified.com/ASPI/forceaspi.htm
>
> Next I initiated the KILLASPI.BAT, then initiated the
> INSTASPI.BAT, then rebooted.
>
> Another run of aspi_chk.exe showed the following:
> Component Version Date Size
> WNASPI32.DLL 4.60(1021) 09/10/99 45056
> WINASPI.DLL 4.60(1021) 09/10/99 5600
> APIX.VXD 4.60(1021) 09/10/99 22603
> ASPIENUM.VXD 4.60(10210) 09/10/99 7743
>
> ASPI is properly installed and is fully
> operational.
> One host adapter has been detected.
>
> I downloaded and installed EAC from the EAC_095pb5.zip at
> http://radified.com/Files/
> and GLORYBE I can rip now.

 

[Mike M]

>> I'm not sure what you meant when you said the copy of aspichk from
>> Adaptec didn't work correctly
>
> The results showed only ASPI32.DLL and APIX.VXD. More

I think that you were using the more recent version of aspichk which is
why I decided to use the older version which is I suspect is also the
version you ended up using.

> Mike I really like your method of troubleshooting, takes me
> back to my electronic technic'ing days.

Being another "ole timer" I don't know any other way. It does mean that
some problems takes a lot longer to resolve (if ever) but at least I know
I will have tried most options in trying to find a solution.

Cheers,

Mike M


Job <iam@best.slow> wrote:

>> I'm not sure what you meant when you said the copy of aspichk from
>> Adaptec didn't work correctly
>
> The results showed only ASPI32.DLL and APIX.VXD. More
> bothersome leading me to question validity was that the
> comment ""ASPI is properly installed and is fully
> operational." was very dim when I expected a darker, more
> positive print.
>
> Mike I really like your method of troubleshooting, takes me
> back to my electronic technic'ing days.
>
>> So what I have learned? Not much
>
> If you can't make sense of it I for sure don't stand a
> chance of understanding. I guess I'm happy that I can (at
> least for now) use Rippers.
>
> The only thing I can offer in regards to your slide scanner
> problem is moral support. If anyone can resolve it I
> believe you can.
>
> Cheers to you guy.

 

[Job]

How about an OT question Mike.

In the past posters have reported getting errors that a
particular .exe, .dll, etc. was not found. You responded
that the particular file was not part of the basic ME load.
How can I determine what files constitutes an ME load?

Take care.


"Mike M" <No_Spam@Corned_Beef.Only> wrote in message
news:%23XQK9LYQIHA.2396@TK2MSFTNGP02.phx.gbl...
>> I'm not sure what you meant when you said the copy of
aspichk from
>> Adaptec didn't work correctly
>
> The results showed only ASPI32.DLL and APIX.VXD. More

I think that you were using the more recent version of
aspichk which is
why I decided to use the older version which is I suspect is
also the
version you ended up using.

> Mike I really like your method of troubleshooting, takes
me
> back to my electronic technic'ing days.

Being another "ole timer" I don't know any other way. It
does mean that
some problems takes a lot longer to resolve (if ever) but at
least I know
I will have tried most options in trying to find a solution.

Cheers,

Mike M


Job <iam@best.slow> wrote:

>> I'm not sure what you meant when you said the copy of
aspichk from
>> Adaptec didn't work correctly
>
> The results showed only ASPI32.DLL and APIX.VXD. More
> bothersome leading me to question validity was that the
> comment ""ASPI is properly installed and is fully
> operational." was very dim when I expected a darker, more
> positive print.
>
> Mike I really like your method of troubleshooting, takes
me
> back to my electronic technic'ing days.
>
>> So what I have learned? Not much
>
> If you can't make sense of it I for sure don't stand a
> chance of understanding. I guess I'm happy that I can (at
> least for now) use Rippers.
>
> The only thing I can offer in regards to your slide
scanner
> problem is moral support. If anyone can resolve it I
> believe you can.
>
> Cheers to you guy.

 

[Mike M]

Job <iam@best.slow> wrote:

> How about an OT question Mike.

No problem. It's quiet here and it's not as if anyone else is posting
anything interesting.

> In the past posters have reported getting errors that a
> particular .exe, .dll, etc. was not found. You responded
> that the particular file was not part of the basic ME load.
> How can I determine what files constitutes an ME load?
>
> Take care.

Perhaps easiest done by checking whether the file is included in the Win
Me cab set which should be found at C:\Windows\Options\Cabs (if the
installation was from OEM media) or C:\Windows\Options\Install (if the
installation was from Microsoft media) or in the Win9x folder if you have
a Win Me install CD (not an OEM recovery disk). Some OEMs have been known
to place the folder containing the cab files in another partition
(incidentally I do this also) or to omit it entirely, the last often being
the cause for many users over the years having problem when installing usb
devices or wanting to create a Win Me boot floppy.

Once you have located the cabs run a search on the folder but rather than
looking for the file by placing its name in the "Search for files or
folders named" box put the file name you are looking for in the
"Containing text" box. This will then located the cab file containing the
required file which can then be extracted from the cab file by double
clicking on the cab file, selecting the required file and dragging it to
the desktop. Be careful however about trying to replace files in this way
as you may hit Win Me's system file protection mechanism and therefore
have to make the actual file replacement from DOS (after booting from a
floppy).

Note that are a few, a very few, special files that for some reason have
different names in the cab files from those used when in Win Me. One that
immediately comes to mind is marscore.dll which is found in win_12.cab but
as marspch.dll. There are other files built during the installation of
the operating system such as sfpdb.db which you won't find in the cab
files.

Note also that the file vmm32.vxd on a Win Me system is a composite file
created during the installation of Win Me that when built contains thirty
or more virtual device drivers (vxd files) and is not the file vmm32.vxd
in win_20.cab which is the container or template used when constructing
the real vmm32.vxd. Files built into vmm32.vxd when installing Win Me
include ifsmgr.vxd, shell.vxd and vcache.vxd.

I hope this helps.
--
Mike M

 

[Job]

It definitely helps. Hope I never need it but am going to
run off a hard copy and keep it safe. This is valuable
information to have available as long as I keep ME (which I
really like and does everything that need). I guess if I
ever upgrade to XP the info will be in an entirely different
location but that's for another day, another time.

Again, I truly appreciate your help and patience. I'll get
out of your hair now and may 2008 bring you good health and
happiness.

Ta.

"Mike M" <No_Spam@Corned_Beef.Only> wrote in message
news:eJU2XRaQIHA.4740@TK2MSFTNGP02.phx.gbl...
Job <iam@best.slow> wrote:

> How about an OT question Mike.

No problem. It's quiet here and it's not as if anyone else
is posting
anything interesting.

> In the past posters have reported getting errors that a
> particular .exe, .dll, etc. was not found. You responded
> that the particular file was not part of the basic ME
load.
> How can I determine what files constitutes an ME load?
>
> Take care.

Perhaps easiest done by checking whether the file is
included in the Win
Me cab set which should be found at C:\Windows\Options\Cabs
(if the
installation was from OEM media) or
C:\Windows\Options\Install (if the
installation was from Microsoft media) or in the Win9x
folder if you have
a Win Me install CD (not an OEM recovery disk). Some OEMs
have been known
to place the folder containing the cab files in another
partition
(incidentally I do this also) or to omit it entirely, the
last often being
the cause for many users over the years having problem when
installing usb
devices or wanting to create a Win Me boot floppy.

Once you have located the cabs run a search on the folder
but rather than
looking for the file by placing its name in the "Search for
files or
folders named" box put the file name you are looking for in
the
"Containing text" box. This will then located the cab file
containing the
required file which can then be extracted from the cab file
by double
clicking on the cab file, selecting the required file and
dragging it to
the desktop. Be careful however about trying to replace
files in this way
as you may hit Win Me's system file protection mechanism and
therefore
have to make the actual file replacement from DOS (after
booting from a
floppy).

Note that are a few, a very few, special files that for some
reason have
different names in the cab files from those used when in Win
Me. One that
immediately comes to mind is marscore.dll which is found in
win_12.cab but
as marspch.dll. There are other files built during the
installation of
the operating system such as sfpdb.db which you won't find
in the cab
files.

Note also that the file vmm32.vxd on a Win Me system is a
composite file
created during the installation of Win Me that when built
contains thirty
or more virtual device drivers (vxd files) and is not the
file vmm32.vxd
in win_20.cab which is the container or template used when
constructing
the real vmm32.vxd. Files built into vmm32.vxd when
installing Win Me
include ifsmgr.vxd, shell.vxd and vcache.vxd.

I hope this helps.
--
Mike M