Page 1 of 1
Posted: Thu May 30, 2002 5:22 pm
by Lugian
System: PIII/800, 512MB, Win2K (with all service packs & patches), Pulsar Mk1 (the original 4DSP model), and SFP 3.1a. This also happens with SFP 3.1
1. Start SFP
2. Put a CD in the CD-ROM drive
3. Open Windows Explorer and go to the CD.
4. SFP stops responding. Go figure.
5. Use Task Manager to kill the task
If only Creamware's software was as good as their hardware ....
Posted: Thu May 30, 2002 5:56 pm
by Round1
Hi,
I've tried this on my system, but it doesn't crash....works just fine. (BUT, of course I have a different system....Luna II, A16, WinXP, SFP 3.1a, PIII-1gig, Asus mobo etc). In fact 3.1a fixed the couple of minor bugs I was having with 3.1
Posted: Thu May 30, 2002 7:54 pm
by bassdude
Have you tried the latest adaptec ASPI drivers?
Posted: Thu May 30, 2002 11:56 pm
by Quifster
I've had exactly the same problem. I've solved it indeed with the installation of the adaptec aspi drivers. Then this problem is gone.
Posted: Fri May 31, 2002 1:42 am
by topaz
come back and let us know what happens when you do what it sais in the release notes
"you must have the latest aspi layer"
creamware s/w is a very big project the only way they will get bug free releases is to offer a public preview version to iron out the many variables. of coarse in your case it might not be a bug but a system fault ?
we await.
On 2002-05-30 18:22, Lugian wrote:
System: PIII/800, 512MB, Win2K (with all service packs & patches), Pulsar Mk1 (the original 4DSP model), and SFP 3.1a. This also happens with SFP 3.1
1. Start SFP
2. Put a CD in the CD-ROM drive
3. Open Windows Explorer and go to the CD.
4. SFP stops responding. Go figure.
5. Use Task Manager to kill the task
If only Creamware's software was as good as their hardware ....
Posted: Fri May 31, 2002 3:39 am
by Lugian
On 2002-05-30 20:54, bassdude wrote:
Have you tried the latest adaptec ASPI drivers?
No I hadn't ... I (incorrectly) guessed that adaptec drivers are only required for adaptec hardware - I assumed for SCSI cards (which I don't have in my system). Subsequent research has enlightened me to the fact that ASPI drivers also affect ATAPI devices.
That would seem to be the solution, but I will not be able to confirm or deny sorry. I'm going to stick with 3.01, just in case there's any other problems with 3.1a. I only use my Pulsar for I/O and 3.01 does that just fine.
Thanks for the RTFM heads-up though
Posted: Fri May 31, 2002 6:47 am
by Music Manic
V4.7 ASPI crashes my sytem v4.6 works though.weird!
Posted: Fri May 31, 2002 9:20 am
by krizrox
I've been crashing my 3.1a installation frequently in the past day since I've installed it with 3DAT.
I'd like a better understanding of this Adaptec thing before I go ruining a prefectly good and running Win ME install. Is there any reason to believe that installing Adpatec's ASPI version on Win ME (with no SCSI or Adaptec products in my PC) will improve the situation?
Posted: Fri May 31, 2002 9:59 am
by subhuman
ASPI has never 'ruined' any installations of mine. Seems like if you use 3DAT frequently the best version to use is the 3.01... 3DAT seems more or less deprecated (I was surprised they even did the version that works with the DSP system...)
Posted: Sat Jun 01, 2002 4:18 am
by topaz
you will not damage anything using aspi
as far as I know this is not just needed for scsi, cdr uses this..
if in doubt always back up with norton ghost before adding any new software.
On 2002-05-31 10:20, krizrox wrote:
I've been crashing my 3.1a installation frequently in the past day since I've installed it with 3DAT.
I'd like a better understanding of this Adaptec thing before I go ruining a prefectly good and running Win ME install. Is there any reason to believe that installing Adpatec's ASPI version on Win ME (with no SCSI or Adaptec products in my PC) will improve the situation?