---------------------------------------------------------------------------------------------------
WARNING!!!
All my findings are result of unconfirmed suppositions, so take these assumptions with the necessary doubt and experiment at your own risk.
---------------------------------------------------------------------------------------------------
I had several problems accessing cds from Windows Explorer and/or SFP or other apps (cd burning etc...).
In details my system was experiencing:
- freezing
- slowdowns
- drives not accessible
- scope not able to read cds if not restarted every time.
Here the things I addressed to made my system behave a little better:
1) SafeDisc driver installed in form of secdrv.sys in windows\system32\drivers\ caused a lot of trouble.
This driver is for protected discs like games or other stuff that requires some sort of authentication of the disc session in order to start correctly. (See on Wikipedia...)
The authentication process slows significantly down the access to drives causing system or apps to hang. (i.e. Explorer takes minutes to show newly inserted discs, it tries and retries to read them but fails several times...)
I disabled this by renaming the driver file (I also modified some registry entries...) and after a reboot things got definitely better, however I cannot play anymore Civilization4 which is responsible for putting a fresh copy of that file in that directory everytime I try to start the game...
...Thanks Civilization4 and my girl friend who gave it to me! ...and also thanks to the people there at MacroVision for fooling our computers this way! This is the way customers are rewarded for buying original stuff!

2) SFP causing drives to misbehave, locking access, some drives not being accessible or some discs readable until SFP is running. After shutting down sfp all is right.
Plus it is not possible to read changed akai cds without restarting sfp.
Thanks to Unlocker (http://ccollomb.free.fr/unlocker/) I found that when sfp is loaded it keeps an open handle on the file SFP\\App\Bin\CDAccess\CD2000.dll.
In that folder there are three dlls (I suppose file system wrappers for different osses), the other ones are:
CD98Me.dll
CDXP.dll
My system is WinXP sp2, not Win 2000, so why isn't loaded the corresponding XP dll?
I really can't imagine why the detection of the os fails. I checked aspi installation, but the problem seems not related to aspi in any way, though without it SFP can't access akai discs. Anyone can confirm what dll is loaded on your PCs?
So I thought to try to force the use of the XP dll and I did this trick:
- I renamed the 2000 dll to something else
- I made a copy of the XP dll and renamed it "CD2000.dll", exactly like the original 2000 was named.
With this simple trick most of my problems now are SOLVED, SFP loads successfully changed cd roms and doesn't lock anymore the cd drive, doesn't cause any more problems to the system or other cd apps.
Akai cdroms are read only if they are substituted with other akai cdroms. If one normal cd is inserted in the the drive, it's not possible anymore to read akais on that drive without restarting SFP. This seems to be an unmounting issue of the akai engine: after unloading it for a normal cd SFP can't re-instantiate it.
Substituting akai.dll in the folder SFP\\App\Bin\ with a previous version (3.1a in my case) seems to solve also this last problem making akai cds being always read correctly.
Please let me know if you experience similar problems and what cd dll is loaded in your case
Hope it may be of help
Fede