Apr 022013

Frog ASPIToday I would like to discuss a few useful tricks for Windows XP x64. Yeah. Again. But this time around, it’s at least partially about stuff that you can’t easily find on the Internet anymore, whether it’s the information or the actual software part that’s missing. There are several software components that are sometimes hard to use or find for XP x64. Some are even hard to set up for regular 32-bit Windows XP. The following solutions will be discussed:

  • 1.) The ASPI Layer (digital media access)
  • 2.) UDF 2.5 (for Blu-Ray and HD-DVD access)
  • 3.) exFAT (some modern cameras etc. need this file system)
  • 4.) EXT2/3/4 (for Linux and UNIX compatibility)
  • 5.) Universal SSD TRIM (keep your SSD clean, tidy and fast, like on modern systems)

So, let’s start with #1:

1.) The ASPI layer:

Edit: Note that in the meantime, the FrogASPI solution described here is no longer the only option. Another one that works even for 64-bit applications accessing the ASPI layer has been found, see further below!

1.a) FrogASPI:

One of those things that have been abandoned by Microsoft is the ASPI layer, the Advanced SCSI Programming Interface. Meant as a way for digital storage media access it was most prominently used to read from optical drives digitally (also on ATA, not just SCSI), so you didn’t need to rip audio CDs via MSCDEX on Win98 or via the crappy analog link from your drive to the sound card. ASPI can also be used to access other types of storage devices, but this is the most important part. Some older software, like my beloved Xing AudioCatalyst (an ancient CD ripper including the Fraunhofer mp3 encoder) might still need ASPI to access audio CDs.

However, Adaptec stopped shipping ASPI drivers for Microsoft Windows after Microsoft had abandoned the API and introduced its own replacement called SPTI, the SCSI PassThrough Interface. As a matter of fact, you can still install Adaptecs ASPI layer on 32-Bit Windows XP, as it includes a working 32-Bit kernel driver. So for 32-Bit XP, it’s still fine. However, there is no such driver for XP x64 (and also not for 32/64-Bit Vista/7/8). So, no ASPI at all?

For a loong time I indeed had to live without it, until I found that french guy named Millenod (That’s his nick name, I will not disclose his real name) who had written a 100% userspace ASPI layer, that would work on any newer Windows operating system on x86, no matter the bitness. This is called FrogASPI, and unfortunately, Millenods website for it is down by now. In its core, it is actually just an SPTI wrapper. Back in those days, I even wrote the guy an email, thanking him for his work. Here is a part of his reply:

“FrogAspi is effectively an SPTI wrapper. I decided to work in “user” mode, instead of kernel ones, for many reasons.. It was for me the fastest way to implement a generic ASPI layer, which is not OS specific as drivers.”

-Millenod, Developer of FrogASPI

After renaming the FrogAspi.dll to the proper name wnaspi32.dll and putting it into %WINDIR%\SysWOW64\ for 64-Bit Windows, it can be used by any ASPI-enabled application. For 32-Bit Windows, please use %WINDIR%\system32! See, what Adaptecs own aspichk.exe has to say about what we just did:

Adaptec ASPI Check

You’ll see that some files are reported as missing. You do not have to care about that though, ASPI32.SYS would’ve been the 32-Bit kernel driver, WOWPOST.EXE is a 16-Bit Windows ASPI helper tool, WINASPI.DLL the corresponding 16-Bit Windows driver. None of those are needed. Now, that FrogASPI is mapping all ASPI calls to SPTI, we can begin to actively use it even on 64-Bit Windows. See AudioCatalyst for instance, with ASPI being available:

AudioCatalyst using FrogASPI

AudioCatalyst reading the Postal Original Soundtrack CD using FrogASPI

As you can see, everything works just fine. Oh, and besides, in case you want AudioCatalysts CDDB feature back (as shown in this screenshot), just add the following lines to your AudioCatalyst.ini, sitting in the programs installation folder, this’ll switch from the now-broken CDDB to FreeDB:

  1. CDDBServer=freedb.org
  2. CDDBHTTPPath=/~freedb/cddb.cgi
  3. CDDBLocation=Random FreeDB Site
  4. CDDBTCPIPPort=8880
  5. CDDBConnectVia=TCP/IP

You can download FrogASPI right here:

Unfortunately I cannot give you a download link for Xing AudioCatalyst, as it’s commercial software even today.

1.b) StarBurn ASPI (An update from 2016-12-05):

In the meantime, user Steve Sybesma has [commented] about a different solution provided by [StarBurn Software]. With their recording software comes a native ASPI layer for both 32-bit and 64-bit systems with full compatibility for even 64-bit programs that want to use ASPI. I decided to fetch the necessary DLLs from their SDK and release them in the form of a standalone InnoSetup installer for Windows 2000 and newer. The installer will auto-detect your operating systems’ bitness and will install the 32-bit ASPI layer on 32-bit systems as well as both the 32-bit as well as the 64-bit one on 64-bit systems.

Here it is:

It has been successfully tested on Windows 2000 Pro SP4, Windows XP Pro SP3, Windows XP Pro x64 Edition SP2 as well as Windows 10 Pro x64. If you don’t want to trust my installer, that’s fine as well of course. You can just install the StarBurn software from its original source, it should give you the same level of ASPI support, just with more additional stuff being installed!

Now, to #2, the UDF 2.5 file system for HD-DVDs and Blu-Rays:

2.) UDF 2.5:

Now this one was a real bitch. It took me months to finally get it nailed! UDF 2.5 is a file system. And it’s used for basically two type of media: HD-DVD discs and Blu-Ray discs, including the most modern 3D Blu-Rays. It just bugged me like hell, that I couldn’t access the discs as I normally would in Windows Explorer or on the command line. Windows XP simply does not have the proper file system kernel driver. And while it’s relatively easy to find one for 32-Bit WinXP, it’s immeasurably harder to find the single one existing driver for Windows XP x64. I’m not even sure if it still exists on the web..

One day I came across a person whose name I forgot, but that guy had searched the web for months just like me, and he found the driver just before it went offline. So he re-uploaded it, with his single file sharing link in some post on some unknown website being the only thing that saved my bacon. Maybe one day, somebody will find the XP x64 UDF 2.5 driver here on my site after desperate searching? Who knows.

So, the only existing driver has been developed by Panasonic/Matsushita, a company that also builds optical drives. It works on Windows XP x64 as well as Server 2003 x64. And here it is, together with the Toshiba-made UDF 2.5 driver for regular 32-Bit Windows XP just for completeness:

Again, I would like to emphasize that it took me months to find that freaking 64-Bit XP driver, I’m not even sure what Panasonic/Matsushita developed it for, but here it is for your enjoyment. After installation and reboot, you can browse a HD-DVD or Blu-Ray just like any CD or DVD disc, see here:

UDF 2.5 at work in XP x64

The Blu-Ray folder structure of the german uncut version of “The Boondock Saints”, viewed using the Panasonic/Matsushita UDF 2.5 driver for XP x64

And now, #3, the exFAT file system:

3.) exFAT:

exFAT is a successor to the older FAT32 file system that uses a 64-bit address field instead, allowing for larger than 4GB files, the most notorious limitation of regular FAT. exFAT is now being used on newer cameras and other handheld devices for memory card formatting. Since the comparably heavy-weight NTFS is typically not used on such devices, exFAT is the replacement we get. Also, exFAT is the official file system for SDXC and Memory Stick XC cards, so they may very well come exFAT-preformatted! The only sour part is, that exFAT is kind of proprietary (Microsoft), like NTFS. That’s a bit crappy, but well.

I have however already written an article about exFAT on XP x64, so I will just link to it. exFAT is also very easy to get for both 32-Bit and 64-Bit flavors of Windows XP:

And now, finally, some free file systems from the Linux world:

4.) EXT2/3/4:

EXT is one of the most widely if not the most widely used file system in the entire world of Linux. It has also been ported to other systems like BSD, Solaris or ReactOS. And also Windows actually, although the implementation is not the most seamless you can dream up. But still, you can get read/write access to all currently used EXT versions under Windows, even the fast new EXT4.

The software that I found most useful for this is called [ext2fsd], short for EXT2 file system driver. It comes with the actual driver plus a helper tool for mounting and for enabling write access. It would be nice to just be able to mount EXT filesystems seamlessly from the start, without having to use that mounting tool, but we’re not that far yet it seems. However, drives can be configured to auto-mount later, so you need the tool only once for each drive. Write access has to be enabled by hand.

Currently, ext2fsd supports the following systems: NT 5.0 (Windows 2000), NT 5.1 (Windows XP 32-Bit), NT 5.2 (Windows XP x64, Server 2003), NT 6.0 (Windows Vista), NT 6.1 (Windows 7, Server 2008). Where not explicitly mentioned, it supports both 32-Bit and 64-Bit versions of said operating systems. And here is what it looks like in action:

EXT4 mounted on XP x64

A Linux-created EXT4 filesystem mounted on XP x64 for read/write using ext2fsd

The only strange thing is, that ext2fsd calls the EXT4 file system “EXT3”. It shouldn’t. But other than that, it works just fine. I haven’t tested a lot of r/w, but so far it worked fine, without any corruption or anything. The helper tool also gives you a function for flushing the write cache, and a nice statistics window for monitoring the file system usage while mounted. It also allows the user to manually unmount of course. Even mkfs is there, so you can format drives as EXT under Windows, the only useful tool missing would be fsck for checking & repairing such filesystems. But you can’t have everything I guess.

So, usage is not as seamless as it would be with native NTFS/FAT32/exFAT drivers, but it’s ok and it greatly boosts the Linux interoperability of XP x64 and other Windows systems. Also, EXT filesystems can easily be used in other UNIX-style systems like Solaris, BSD or MacOS X, so this allows a lot of different systems to exchange data easily using removable sticks or harddrives. Since it of course supports large files (>4GB) and it’s more easy to handle across a wide spectrum of operating systems, unlike exFAT it might one day become the #1 choice for data exchange, replacing FAT32 and NTFS in that field. However, today, NTFS on Linux is probably a lot more widespread than this EXT driver on Windows, so there is still a long way to go.

Of course, there is a downside to this too: All the POSIX permissions like ownership, read/write/execute bits etc. just do not work on Windows. You can neither read nor write any such meta data using ext2fsd. I have neither checked the umask that ext2fsd uses yet, nor what ownership it sets, but I would guess it’s root:root with permissions 777 or rwxrwxrwx. But whatever it is, you will most likely need to take care of that when mounting on your UNIX-style system.

I hope this was helpful, if you have any comments about these helpful add-ons, just post away!

5.) Universal SSD TRIM:

This is a 2014-11-03 edit of the original article.

Usually, I would tell users who would like to use an SSD on Windows XP or XP x64 to re-align their partitions with a [gparted ISO] after installation to get proper alignment, and more importantly to use either Intel, Corsair or Samsung SSDs so that they can TRIM their SSDs properly using their respective manufacturers’ XP-compatible software tools, maintaining full write speed over the entire life time of the SSD drive.

It seems that I can now finally confirm, that the latter criterion no longer needs to be met. Basically, I found an easy way to TRIM any SSD on Windows XP or Windows XP x64, as long as the following logical criteria are met:

  • The SSD itself needs to support TRIM. Well, that was obvious.
  • The controller driver needs to support TRIM. Now I can’t speak for just any driver, but I have tested this on Intels ICH10-R and an ancient ICH7-M, both worked just fine with AHCI drivers installed. Usually, AHCI is what you want. Avoid IDE/legacy PATA modes. You may need to configure this properly in your systems BIOS and you may need to retrofit AHCI drivers in XP if your system was installed using IDE mode to avoid bluescreens on boot. If you need help doing that, please ask away in the comments.

So, what’s the solution? It’s called the ADATA SSD Toolbox! Basically, ADATA developers seem to have forgot or were actually never instructed to install an artificial vendor obstruction inside their software. So what they did was to write an SSD toolbox that just complies to the SATA standard, implementing its TRIM command for any compatible SSD, no-holds-barred! I have tested this on an Intel 320 SSD, as well as on a Crucial m500 SSD now, despite no official XP support being present:

So there you go! Now pretty much any TRIM capable SSD can be made to accept TRIM on Windows XP and XP x64! Together with gparted for partition alignment, we have a full-featured SSD solution for XP, leaving nothing to be desired!

Download the ADATA SSD Toolbox here: [ADATA SSD Toolbox v2.0.1].

CC BY-NC-SA 4.0 A few useful XP x64 tricks: ASPI, UDF 2.5, exFAT, EXT2/3/4, universal SSD TRIM by The GAT at XIN.at is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.

  60 Responses to “A few useful XP x64 tricks: ASPI, UDF 2.5, exFAT, EXT2/3/4, universal SSD TRIM”

  1. I’m trying to use Siren Jukebox on Windows 10 64-bit.

    It installed just fine with no error whatsoever, but no joy because the DVD drive is not found by that application.

    The FrogASPI driver is detected by Siren Jukebox, because the Computer tab under About Sonic Foundry Siren Jukebox shows it as you see below:

    Not using ASPI
    Description: Frog ASPI
    Company: Frog ASPI / Millenod

    This shows the same way regardless of which combination of checkmarks are selected for Use ASPI or Use SPTI or detect unknown drives.

    No matter what I do, the DVD drive is not detected by Siren Jukebox.

    I got a small clue on this however…

    A free app called FairStars CD Ripper also has that exact same problem unless you check the box called “Use Native NT SCSI Library”, then it finds the DVD drive just fine.

    So, it seems there’s a little bit more to it than just the ASPI driver or else Windows 10 64-bit isn’t making proper use of FrogASPI as used with Siren Jukebox to allow the DVD drive to be visible.

    FairStars CD Ripper makes use of the identical FrogASPI driver, but again, you have to make a change I mentioned above to allow the DVD drive to be found.

    • I’m finding with a 2nd DVD drive that it also does not find that drive as well.

      Within the program files for Siren Jukebox is one that lists compatible CDs:


      That may be the whole issue. It’s being restricted to use only drives it knows about (even though detect unknown drives is selected). It also claims it’s “Not using ASPI” even though it shows FrogASPI was detected:

      Not using ASPI
      Description: Frog ASPI
      Company: Frog ASPI / Millenod

      I tried every combination of everything I could think of including changing the OS compatibility…no dice.
      I tried Adaptec’s wnaspi32.dll as well (which is also detected).

      • Hello Steve,

        Unfortunately, I’m not a Siren Jukebox user, so whatever advice I can provide will be very limited. Just one thing: “Use Native NT SCSI Library” should indicate the use of SPTI instead of ASPI. Cause that’s what SPTI is: NTs’ native SCSI library.

        What sounds weird is that FrogASPI is being detected and yet Siren Jukebox says “Not using ASPI”? Why?!

        In any case, there is a more detailed discussion about getting Siren Jukebox to work [further down], where some users got it to do its job on Windows 7. Of course, Windows 7 isn’t Windows 10, and that may apply to its SPTI layer as well. So far, I haven’t tried this on Windows 10 at all, as my only Win10 machine is a convertible tablet with no optical disc drive whatsoever.

        Maybe I’ll try and fool around with this stuff on a Windows 10 VM. I have one here, but not enough time right now. If I don’t forget, I can try and look into it for a bit some time next week.

        • Kept poking and poking at this problem. I finally got a huge crack further toward breaking this problem when I used this MUCH NEWER version of an ASPI driver from Rocket Division Software/StarBurn Software.

          Not using ASPI
          Description: ASPI for Windows
          Company: Rocket Division Software, StarBurn Software
          Version: V15.5 ‘Patriot’ Build 20150703

          For the first time ever, my CD-ROM drive was recognized, but it’s not available. I got an Unknown Drive popup saying the drive may be unsuitable. The interface and disc were shown as Unknown.

          Below is the information from the Computer tab of the About Sonic Foundry SIREN Jukebox window:

          CD Drives:
          Drive D:’HL-DT-ST CDRWDVD MU10N A106′
          Interface: (-1)
          Adapter: Port 000 (0)
          Available: No

          I’m going to see if I can edit sfcdi.cfg and add that one in manually to see what happens.

          Checking the box for unknown drives was not enough to get that working.

          When using the ASPI driver you must check the box “Use ASPI on Windows NT” or the drive is not vislble at all.

          • See my latest…I got much further on this problem after I used the new WnASPI32.dll driver I found.

            I cannot believe that was published in 2015, but it’s absolutely the newest I could find out there.

            All I have to do now is figure out how to get the info to SJ about the drive parameters and I think it will actually be able to read discs. LOTS further than before.

            • Hey Steve,

              My apologies, but I’ve rearranged your posts, so that they’re now all in one cohesive thread, making it easier to follow the entire thing. :)

              And thanks for pointing out Starburn! I’ve had no idea that that software existed. It might be a good replacement for FrogASPI I guess, I should definitely give it a shot. It also fits with the original articles’ goal of getting ASPI to work on WinXP x64, because Starburn seems to support everything starting with Windows 98. ;)

              If it works well (=better than FrogASPI), I might wrap a very simple installer around just the WnASPI32.dll files, so a slimmer ASPI-only version of it can be redistributed (Starburns’ license seems to allow for that).

              • Thanks Thrawn, the only trick left is getting Siren Jukebox to be able to recognize the drives that it now acknowledges exist. I had the problem on two drives.

                I wonder if SATA has something to do with it.

                The last time I used Siren Jukebox, my drives were all still 40-PIN ATA/IDE.

                BTW, editing the SFCDI.CFG file didn’t seem to work. I could try reinstalling the app with the new WnASPI32 waiting for it in the folder it will install to, but I worry about the activation codes I just got last week getting tossed out again.

                There is also a trick here (Resolution #6) I will try first:


                After I make the change and reboot, I’ll report back.

                • No dice…I have to figure out how SJ detects drives and if it can detect SATA.

                  I can try to rob an ATA/IDE out of an old machine I have and attach externally via USB.

                  • Hello again Steve,

                    I did several things today, the first part being to rip the ASPI DLLs (Bin\Core\StarBurn Core\msvcrt\Release\i386\WnASPI32.dll & Bin\Core\StarBurn Core\msvcrt\Release\amd64\WnASPI32.dll) out of the StarBurn SDK. Then I built an InnoSetup installer around those. The installer will correctly detect 32-/64-bit Windows and install just the DLLs necessary for each available architecture. With this you don’t need the rest of the StarBurn software at all. The DLLs are freeware as per the [StarBurn SDK license]:

                    I have just tested this to work on the following operating systems:

                    • Windows 2000 Professional SP4 (NT 5.0)
                    • Windows XP Professional SP3 (NT 5.1)
                    • Windows XP Professional x64 Edition SP2 (NT 5.2)
                    • Windows 10 Professional x64 (Build 1607, NT10.0)

                    Now, as for the Siren Jukebox test, I installed it on a Windows 10 VM (my host is 64-bit CentOS 6.8 Linux, so yeah). To make sure I’ve been feeding the right stuff to it, I verified that I’ve been passing a real SATA drive to the VM, see here:

                    VirtualBox setting for the StartBurn ASPI + Siren Jukebox test
                    VirtualBox setting for the StartBurn ASPI + Siren Jukebox test (Click to enlarge)

                    Then I fired Windows 10 up, installed StarBurn ASPI using my own installer as well as Siren Jukebox 2.0c according to [these instructions] by FixitMAD. After that, I set Sirens’ advanced CD settings to force ASPI only:

                    Forcing Siren Jukebox to use ASPI
                    Forcing Siren Jukebox to use ASPI (Click to enlarge)

                    Still, Sirens’ “About” screen reported that ASPI wouldn’t be used on the now-detected (but according to Siren, still unsupported) drive:

                    Sirens system report
                    Siren still not showing ASPI being used?! (Click to enlarge)

                    I just gave it a shot nonetheless, given that my passthrough SATA drive was now being detected! I don’t have any original audio CDs here, but I bought the FLAC version of Hidden Orchestras’ track “Flight” this weekend, so I just burned that to a CD, put the disc in the drive Windows 10 was being fed, and see what happened:

                    Siren Jukebox ripping an audio CD using StarBurn ASPI on Windows 10 Professional x64
                    Siren Jukebox ripping an audio CD using StarBurn ASPI on Windows 10 Professional x64 (Click to enlarge)

                    So this worked for me! Unfortunately I do not have any physical Windows 10 machines with optical drives, but I do have a machine with Windows XP Pro 32-bit using a PATA drive (but connected to a controller working with the SCSI-style drivers of a SiI 0680 ATA/133 controller!). I gave it a shot using StarBurn ASPI as well, and ripping a CD from it worked just as well.

                    So, what was it exactly that I did?

                    1. Installed Sonic Foundry Siren Jukebox 2.0c
                    2. Installed Sonys’ registration repair tool (which fixed Sirens’ registration system)
                    3. Installed StarBurn ASPI using my installer
                    4. Launched & registered Siren
                    5. Switched ASPI (and only ASPI!) on in the advanced CD settings
                    6. Restarted Siren
                    7. Started happily ripping my CD from a SATA drive on Win10 x64 as well as from a PATA/SCSI drive on WinXP x86…

                    I don’t think I did anything too differently from you though, so I’m not sure if any of this can actually help you. :?

                    Edit: I’ve added the StarBurn stuff to the main article, as this has some advantages over FrogASPI.

  2. Thanks for the UDF2.5 driver for XP x64.
    I just wanted to point out that with a bit of fiddling you can install it without the included bloatware. Just follow these steps:

    1. open a window and type “%tmp%” (without quotes) in the address bar, this takes you to the temporary files folder.
    2. now launch the “MEIUDF-” executable.
    3. when it asks you for the first time “do you want to continue?”, click yes, but don’t procede any further!
    4. you’ll notice that in the %tmp% folder some new folders are created. Grab the largest one (3,72MB) and copy it to the desktop (you can’t move it, just copy it).
    5. now you can abort the installation.
    6. now the most important part. Open setupini.txt, delete what’s inside it, and paste the following text (without the initial and final lines, of course):


    ;Setupini.txt for Driver of BD Drive
    ;Setup program         Ver3.2.3.0
    ;Setup information     Ver1.0.2.0
    AppName = DVD-RAM Driver
    Version =
    InstallName = Blu-ray Driver
    UninstallName = Blu-ray Driver
    DiskSpace = 5000000
    ProductName = DVDFORM.EXE
    CompanyName = Panasonic ODSD
    TargetOS = 11
    LicenseTXT = license.txt
    ReadmeTXT = ReadmeXP.txt
    Reboot = 1
    Directory = Blu-ray\Driver
    Folder = Blu-ray
    PackageType = 2
    CopyFileNum = 0
    CopyFileNum = 0
    x64CopyFileNum = 0
    CopyFileNum = 0
    CopyFileNum = 0
    x64CopyFileNum = 2
    x64CopyFile1 = meiudf.sys:NORMAL
    x64CopyFile2 = psecbdr.sys:NORMAL
    CopyFileNum = 0
    RegKeyApp = SOFTWARE\Panasonic ODSD\DVD-RAM Driver
    RegKeyAppPath = SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\DVDFORM.EXE
    AddRegNum = 0
    x64AddRegNum = 0
    x64AddRegNum = 0
    x64AddRegNum = 0
    AddRegNum = 0
    x64AddRegNum = 0
    AddRegNum = 0
    x64AddRegNum = 0
    [SOFTWARE\Panasonic ODSD\DVD-RAM Driver]
    AddRegNum = 0
    [SOFTWARE\Panasonic ODSD\DVD-RAM Driver\DVDForm\Blu-ray]
    AddRegNum = 0
    [SOFTWARE\Panasonic ODSD\DVD-RAM Driver\WPTool\Blu-ray]
    AddRegNum = 0
    AddRegNum = 0
    ModifyRegNum = 0
    ServiceRegNum = 0
    x64ServiceRegNum = 2
    x64ServiceRegKey1 = Service_MEIUDF
    x64ServiceRegKey2 = Service_PSECBDR
    x64ServiceName = meiudf
    x64DisplayName = meiudf
    x64ServiceType = 1
    x64StartType = 1
    x64ErrorControl = 1
    x64PathName = System32\Drivers\meiudf.sys
    x64LoadOrderGroup = File system
    x64TagId = 0
    x64Dependencies = NULL
    x64ImmediateStart = 0
    x64ServiceName = psecbdr
    x64DisplayName = psecbdr
    x64ServiceType = 0
    x64StartType = 0
    x64ErrorControl = 1
    x64PathName = System32\Drivers\psecbdr.sys
    x64LoadOrderGroup = PnP Filter
    x64TagId = 0
    x64Dependencies = NULL
    x64ImmediateStart = 0
    ShortCutNum = 0
    DeleteFileNum = 0
    x64DeleteFileNum = 0
    DeleteRegKeyNum = 0
    x64DeleteRegKeyNum = 0
    DeleteShortCutNum = 0


    1. save the file, launch setup.exe and you’re done! Just remember to delete the Bluray folder that gets created in Program Files. It’s empty and you can safely delete it.
    2. Enjoy!
    • Hi Ric,

      Stripping it down to just the kernel drivers, pretty clever. That’s some nice work, I like it, thanks for contributing! :)

      I think I’ll apply that for the XP x64 workstation I’m just building right now, probably my last one anyway, but still.

      • Hi thrawn,
        I’m using the drivers right now on my Sandy Bridge machine and they work good. :)

        I’m not sure what the psecbdr.sys driver is, so I left it there. The description says “Filter Driver for the BD-R SRM+POW feature.[x64]”.
        Do you have any idea?

        • Hey Ric,

          I heard that before, but wasn’t sure anymore, so I did a bit of research, [here] for instance. It’s related to BD-R burning, with SRM+POW meaning “Sequential Recording Mode + Pseudo-OverWrite”. In essence, this mode is for multi-session discs. If you write a file with the same name and location to the disc in any subsequent session, both files are sitting on the disc physically, as it’s BD-R, not BD-RW. You can’t really overwrite files on a BD-R. However, the newer file will be the only one shown to the user, and this is called “pseudo-overwrite”, because it looks like the file had been overwritten, when in fact that’s not true.

          I guess that POW feature needs some cute little tricks in the UDF file system to work, and it seems that psecbdr.sys filter driver’s doing the magic. I wouldn’t remove it, otherwise such discs may have problems being read on the system I’m guessing.

  3. Thanks a lot………

  4. hello – i’ve tried to install http://wp.xin.at/wp-content/uploads/2013/04/udf25-xp32-toshiba.zip but i can’t get it work. i’ve a samsung writer se-506 attached via USB and the only way to see inside BD is using Isobuster – any suggestion?

    • Hi Marco,

      Just to make sure: What exact operating system are you using? Regular Windows XP 32-Bit or Windows XP x64 Edition? If you click Start / Run or press <WIN>+<r>, enter winver and hit <ENTER>, you should be able to make sure. The 64-Bit version would give you something like this:

      winver.exe on XP x64
      winver.exe on Windows XP Pro x64 Edition SP2

      The regular 32-Bit version would give you something akin to this:

      winver.exe on XP 32-Bit
      winver.exe on Windows XP Pro 32-Bit SP1, image is © IKANO Communications 1998 – 2014

      I have to ask, because you said you installed the Toshiba UDF 2.5 driver, which is exclusively for the 32-Bit version of Windows XP. Just making sure you’re not running XP x64 and trying to run a 32-Bit kernel driver.

      • that’s mine thrawn,


        xp sp3 !

        too high ?? 8(

        • Hi Marco,

          No, thats perfectly ok. Your XP is fine, and you picked the correct driver. I am at a loss as to why it wouldn’t work for you. I just tried it again in an XP Pro SP3 virtual machine using passthrough for full hardware support of my BD-RW drive, installing the driver by right-clicking thdudf.inf and picking Install. This will install and register the kernel driver thdudf.sys. All that should be required after that is a reboot, and Blu-Ray media should become readable.

          I just tried that with the following media (physical Blu-Ray discs, not images!) successfully:

          • …altrimenti ci arrabbiamo! (Bud Spencer & Terrence Hill – Zwei wie Pech und Schwefel)
          • Lo chiamavano Trinità (Bud Spencer & Terrence Hill – Die rechte und die linke Hand des Teufels)
          • Real Men
          • The last Days on Mars

          I cannot reproduce any problem. It just works for me. I also have it set up like that on my subnotebook; XP SP3 + POSReady 2009 Upgrade for continued update support, and it all just works, with a physical BD-RW drive built by Matsushita.

          Did you install the driver by right clicking thdudf.inf and picking Install?

          You may wish to verfiy whether the driver is really loaded by running Nirsofts [DriverView] tool. It’ll show you all currently running software & hardware drivers on your system. The list shown by DriverView should include thdudf.sys, otherwise something went wrong during installation!

          • yes i did “Did you install the driver by right clicking thdudf.inf and picking Install?”

            in my localisation ITALIAN – maybe Xp italy do non work properly???

            i will try and check your tool and do even in a virtual machine & in other two desktop computer (XP ) other than this notebook.

            thank you, happy new year !

          • just a moment !! i put a commercial bly ray ( film) in the drive AND I SEE IT !!!

            well , there is some issue with BD i write by myself ! that’s change things a little bit –

            do you see blu ray home-made by your own?

            • Hi Marco,

              I studied the technical documentation I found, but it seems UDF 2.5 is the standard file system for all BD media, likely including the discs you burned yourself. You may still want to check your burning softwares’ settings, especially regarding file systems. Maybe there is a glitch somewhere, since commercial discs seem to work fine.

              I have to admit, despite owing a burner, I actually never burned any BD-R media, so I only have commercial movie discs available. I don’t even have a BD-R blank media right here, so I can’t test that right now. I may try at a later time, but no promises there…

              In the meantime, your best bet would still be to double-check all the settings of your BD burning application.

              • Some news: if i attach BD usb drive to an Asus netbook running Windows 7 i can see perfectly folder of Blu ray home made. That’s seem to me a lack of my old notebook running Xp.

            • Hey again Marco,

              Today I took the time to buy a BD-R disc at a local electronics store. All I got was a single layer BD25, but that should suffice, UNLESS your drive in the XP machine CANNOT read DUAL layer discs, and that’s what you’re burning to!! In my case, it’s this disc:

              Maxell single layer 25GB BD-R
              Maxell BD-R 25GB (click to enlarge)

              I think the choice of software is critical here, so I used the free tool [ImgBurn], picked all my Timescapes movie files plus Big Buck Bunny, and chose the UDF file system exclusively to make sure there is no “accidental” XP compatibility layer woven into the disc. Check out my settings here:

              Settings for the UDF 2.6 @ XP test burn
              Settings for the UDF 2.6 @ XP test burn (click to enlarge)

              Actually, I pushed the bars a little here and went for [UDF 2.6] instead of just the base [UDF 2.5] used on most Blu-Rays. 2.6 is a minor revision otherwise compatible to 2.5, introducing only pseudo-overwrite support when burning media. So I picked only the newest possible file system here. ImgBurn even gives you this nice warning when telling it to burn the disc like that:

              ImgBurn warning the user about UDF 2.6 compatibility on XP
              ImgBurn warning the user about UDF 2.6 compatibility on XP (click to enlarge)

              Disc summary:

              ImgBurn UDF 2.6 disc summary on XP, just before burning
              ImgBurn UDF 2.6 disc summary on XP, just before burning

              Now, I burned the thing and threw the newly burnt UDF 2.6 disc at both the Panasonic driver on XP x64 as well as the Toshiba driver on XP 32-Bit, and both of them display the contents of the modern disc just fine:

              UDF 2.6 being read on XP just fine
              UDF 2.6 being read on XP just fine (click to enlarge)

              Other than UDF 2.6, the only possible file systems would be ISO9660 or Joliet, and both work with XP out of the box anyway. Unless there is some BD-RE (rewritable) issue here, my newest best bet would be your old laptops BD drive not being able to read dual layer BD50 discs. If it’s not that, I fear I’m out of ideas. I just threw the most modern file system available for BD at both drivers, and they can cope just nicely.

  5. Hi Friend,

    I have a question.

    I have compaq cq41 laptop.

    When I formatted my laptop with windows 32 bit operating system.
    I have also installed w7 service pack 1.

    its dvd drive is not reading UDF dics (burned dvds by nero or any burning software)
    while it reads company level cds normally.

    I have updated all drives using driver booster. and done almost all the tricks which I found over internet.

    When I have updated intel 5 series ATA driver it had worked for first time and again when I chaged the disc it again reading it as a blank disc.

    I am in problem form more than 4 months.

    Please help me if you have any suggestion.


    • Hello Chandan,

      I have to admit, I’m a bit of a loss here… We need to clarify what’s going on exactly. You’re saying you’ve installed WinXP 32-Bit, but also have Windows 7 SP1?! Both show the problem, WinXP and 7? Also I am not sure what a “company level CD” is supposed to be.

      And I have no idea what “driver booster” is? Some of those crappy “we download adware for you” tools? Please don’t use them. They rarely help. Actually, they never really help.

      I presume that installing the [Toshiba UDF 2.5 driver for XP 32-Bit] won’t help either, as that’s exclusively for UDF 2.5 on HD-DVD and Blu-Ray discs. You could still try that, but I don’t think it’s going to do much good.

      Maybe (I know people say this a lot, and it’s rarely actually true, but hey) it’s a drive failure? You could try to create an image of an affected disc using Nero or maybe the free tool [ImgBurn] and then mount the image to a drive letter using [Daemon Tools Lite 4]. That way, we’d know whether the problem is linked to your physical drive or not. This could help in further analyzing and narrowing the problem down.

      I am sorry I can’t be of more help here at the moment, but it’s just hard to figure out what’s going wrong for you remotely. Maybe you can try the image creation and mounting to see whether it’s truly a file system problem?

  6. A goldmine!
    I was beginning to think I was the last person on the planet using xp64! but the stuff here should help me eek out another decade out of the old OS.
    As you offer, I would like your help with retrofitting ACHI drivers.

    I’d like to enable trim for 2 samsung ssds. I tried installing samsung’s magician tool, but it just won’t install, as admin, or anything else. Samsung were no help they said trim wasn’t supported under xp.

    My mobo is an asus P5Q turbo,
    ICH10R, Current driver : Intel ICH10 Family 4 port serial ATA storage Controller 1 -= 3A20 (2 – 2a26 on 2 port)
    Legacy ATA mode selected in bois (I get bsods if I enable ACHI)

    I assume it’s just a case of updating the current driver in device manager with the intel ICH10R ACHI RAID driver I downloaded from asus, then enabling trim with the Adata tool?

    If it isn’t, please let me know!!!

    • Hello maxcellerate,

      It’s not too hard, but it IS dangerous. So I would suggest you use Acronis or Clonezilla or some other tool to back up your system partition first! This might otherwise result in a completely unbootable system!

      First you need the plain ICH10R kernel drivers from the F6 floppy disk, these can be conveniently downloaded from ASUS:

      Please unpack the driver to some arbitrary location, then right click your ATA storage controller in device manager, and update the drivers for it. Point the installer to the location where you unpacked the files, pick the subfolder Driver\64Bit\. Choose the iaAHCI.inf when asked (iaStor.inf is for RAID, don’t pick that, as this may result in failure later on!). Reboot. Windows should now BSOD on boot because the AHCI driver is being loaded, looking at an ATA controller, thus panicking and killing the Windows kernel. Go to BIOS and change your SATA controller mode from legacy ATA to AHCI. Boot. Profit. If all dies painfully, restore backup and switch back to legacy.

      If it worked, all should be good now. What I do not get however is why Samsungs SSD Magician won’t work for you. I just tried to install its latest incarnation – version 4.4 – on an XP x64 test machine and it installed and worked just fine. You got .Net 3/4 with all updates? Maybe some system components are missing…

      • Thank you Sooo much for that. I’ve already got a clonzilla image of my C drive and the AHCI driver, so fingers crossed… I’ll try it when I don’t need the computer for a couple of days, just in case.

        As to Magician, I’ll download the latest, may that it, mine came with the drives and is 3.2. It did seem like it was looking for somthing though, I got this error about half way through installation: “an error occurred while trying to copy a file: Data error (cyclic redundancy check}” – Wot eva that means!
        Thanks again, I’ll let you know how I get on.

        • Hi,

          Hmm, that is a bit strange. CRC (cyclic redundancy checking) is typically used to verify the integrity of files. This indicates that your installer is corrupt/damaged. Sounds a bit weird, but maybe it did come on a damaged storage device (CD or so)? Let me know how it goes with AHCI and the new version of SSD Magician!

  7. Thank you very much for this post. My Asus BD Recorder goes nicely now under XP64.
    Thanks to Panasonic.


    • Hello Polred,

      Always happy to help! :)

      You may also be interested in the [XP x64 post-mortem updates] page here. I’m backporting Server 2003 x64 security and other regular updates to XP x64, as both share a kernel and code base (and always went hand-in-hand when it comes to Windows updates). On that page you can find all Windows updates that Microsoft has held back from XP x64 since May 2014 including security severity ratings, knowledgebase links etc. With that, you can keep your XP x64 fully up to date until Server 2003 x64 support runs out in July 2015. Just make sure to install from oldest to newest.

      Should you not trust my files, you can always use the provided links to search for the original update files by Microsoft of course. :)

  8. The “Panasonic/Matsushita UDF 2.5 driver for Windows XP x64” will not install on Windows 2003 Server R2 x64 until you make a small change to the “setupini.txt” file within the “MEIUDF-” file.

    1) extract “MEIUDF-” using 7zip
    2) open up “setupini.txt” notepad or your favorite text editor
    3) change the line: “TargetOS = 11” to read: “TargetOS =”
    4) run “setup.exe”

    This process removes the system checking by “setup.exe” when you run it.
    If you don’t do this, then you may see an error saying that this driver does not work in this version of Windows.

    And that’s the “magical” patch. :-)

    Thanks, and have fun.

    • Hello Lance,

      Hah, I never actually tried on Server 2003 x64. Good find, this may help other users, so thanks for sharing! :)





      • Hello, DJ-RoGeRs-BS,

        (machine-translated Spanish below / traducidos automáticamente Español abajo)

        I’d like to help, but I’m seeing that you’re using a modern OS (Vista/7). Actually, you shouldn’t have any problems with accessing Blu-Ray media on that OS, as UDF 2.5 is already builtin. So I’m thinking it’s the ASPI part you need?

        Also, please consider that certain kernel space software might block you from accessing media in Windows Explorer when active (AnyDVD HD does this, other products do it too, you’d need to disable that software for plain Windows Explorer Access to work!).

        I need to know what it is that you need exactly.


        Hola, DJ-Rogers-BS,

        Me gustaría ayudar, pero estoy viendo que está utilizando un sistema operativo moderno (Vista / 7). En realidad, no debería tener ningún problema con el acceso a medios Blu-Ray en ese sistema operativo, como UDF 2.5 ya está construido adentro. Así que estoy pensando que es la parte ASPI necesita?

        También, por favor considere que un determinado software el Kernel Space que podría bloquear el acceso a los medios de comunicación en el Explorador de Windows cuando se activa (AnyDVD HD hace esto, otros productos también lo hacen, que había necesidad de desactivar ese software para Windows llanura Explorador de Acceso al trabajo!).

        Necesito saber qué es lo que usted necesita exactamente.

        Inglés prefiere, mientras estoy hablando sólo en alemán e Inglés. De lo contrario, tendría que referirse sobre traducción automática aún más, con la esperanza de que funcione satisfactoriamente.

  9. Yeah, I noticed Microsoft has a history of being stupid with their 32GB/OS version specific/etc. limits to try to force you into using something that’s otherwise useless (who really wants to format a drive that can’t be used on every PC they own? Oh, right… evil mastermind plan.) . It’s stupid because now you have to use a third-party partition utility instead of just being able to plug-and-play. FAT32 can’t be used for 128GB partitions? A joke since there are tools that can get you over 1TB with that old format. Too bad that doing so is a hugely bad idea from a data-safety POV especially past 256GB. Maybe they’re doing us a favor with FAT32, hehe. Note that I’m using normal powers of 1024, not the HDD numbers.

    “The only strange thing is, that ext2fsd calls the EXT4 file system “EXT3″. It shouldn’t. But other than that, it works just fine.”

    Please see: https://wiki.archlinux.org/index.php/ext4#Procedure_2
    “Warning: ext4 is backwards-compatible with ext3 until extents and other new fancy options are enabled.”

    It’s quite likely that it IS mounted as an ext4 file system. Also, any ext4 FS filter (‘driver’) by definition will work with all ext3 partitions as it’s part of the standard(it just can’t create the new features since there’s ‘no where to put them’). Maybe the author only partially implemented the new features and thus allowed you to mount it as ext3 since it didn’t have those optional structures enabled in the partition’s structure. Try creating a test drive with really large files (1GB each or so should do it) writen natively from a Linux driver supporting extents. The files will have ‘e’ next to them as mentioned in linked articles. See if they can be writen back to/copied and if new files created in Windows show up as ‘extents’. I’d be very careful using that with any drive containing a version 4 ext partition unless the author specifically says it’s fully implemented or has some kind of failsafe to prevent writing.

    I’m not sure how uptodate this is: http://en.wikipedia.org/wiki/Ext4#Compatibility_with_Windows_and_Macintosh
    It seems to imply that they all fake it.

    BTW: Extents are neat – it makes the concept of FAT-like clusters kind of obsolete! Too bad it wasn’t designed around those reallllllly big projects with 1000TB+ of storage. It’s a bit like exFAT in that regard.

    • Interesting. I gave it a shot and formatted myself some partition to EXT4 on CentOS 6.5 Linux, enabling extents in the process:

      mkfs.ext4 -O extent /dev/sdb1

      Then, I mounted it and wrote some 2GB file to it, filling it with nothing but zeroes:

      dd bs=1M count=2048 if=/dev/zero of=/mnt/sdb1/testfile-2gb.txt && sync

      Now, I’ve been trying to read the file with gvim for hours on XP x64, and all the HDD LED is doing is blinking a bit each second. Doesn’t seem I can get the file to read. If this is because of it using extents I cannot say. Usually gvim deals with large files rather well. So I aborted that and just tried to append to the file:

      echo "MagicString" >> .\testfile-2gb.txt

      That seemed to work, but only superficially. See here, the file opened with ghex2:

      (Click to enlarge)

      It’s all just zeroes at the end, the string was never appended. So it seems you’re right, there is obviously some serious problem related to extent-based files, as regular ones seem to work fine. filefrag reports 17 extents on that file. Maybe I’ll try to re-create the file on Windows and check it again on Linux afterwards to see whether it’s being created using extents or not. My guess would rather be not.

      Edit: Here we go, creating the file on Windows using dd.exe’s built-in zero device:

      dd.exe bs=1M count=2048 if=/dev/zero of=.\testfile2-2gb.txt
      echo "MagicString" >>.\testfile2-2gb.txt
      sync.exe E:

      Now, let’s remount that on Linux and open the file with ghex2, and lo and behold:

      (Click to enlarge)

      Yeah, it’s definitely there now! The interesting information would however be, why filefrag is showing 6 extents for the file created on Linux and 523 extents for the file created on Windows. So both do seem to be extent based. But something seems to go wrong with the 2GB file created on Linux. Smaller files work that way however (create on Linux, modify on Windows, re-read on Linux). I’m at a loss as to what’s happening here. But it seems you need to be extra-careful when using this driver cross-platform with large files…

      Fun fact: Both files grew by 11 bytes when adding the “MagicString”. But only one file shows it, the one both created and modified on Windows. Pffh. Not what I’d call ready for production deployment. ;)

  10. I have an application that has an embedded ActiveX control that making low level call to ASPI.DLL in Windows 7.0 and its needs Administrator rights to run the Application.
    Under Windows XP formerly we can run under normal User rights.

    Can I use FrogASPI and replaced the wnaspi32.dll of Windows 7.0 (32bits) and my application should work when running User rights ?

    • Hello Woo Mun Foong,

      Now that is a question that I have no clear answer for. Reason being that I have little experience with ActiveX (I have basically given up on ActiveX), and I do not know your application. This might very well just be an issue with your ActiveX configuration, not the ASPI layer. I can’t be sure about that either though, it’s hard to tell without knowing the setup exactly.

      I’m afraid the only thing you can do is to just try it out. This can be done rather quickly, just backup your old ASPI DLL, replace it, test it. If it fails, the error has to be somewhere else, ActiveX being my prime suspect in your setup.

      Is the application you’re using compatible with Windows 7? Maybe it’s doing something that Win7 might see as requiring administrative privileges where Windows XP did not.. but that’s just wild guessing really.

  11. Thank you so much for your effort.

    I got the link for exFAT for Windows XP x64 here.

    Best Wishes,


  12. thrawn,

    Thank You!!!!!! I have been having a heck of a time getting the Sonic Foundry Siren Jukebox v2.0c program to work under Windows 7 since this older jukebox program requires ASPI. Once I followed your instructions and accessed the CD settings under Options | Preferences I CD Settings | Advanced, I checked the Use “SPTI Direct on Windows NT” and everything works great. The program sees both CD/DVD drives as if this were on XP!

    I cannot thank you enough! Thank you for posting and sharing this great information. Because of the help like this, I try to help other users when I can on other forums as well.

    Best Wishes,


    • Hi François,

      Thanks for your kind remarks, even though I am unsure how I might have actually helped you. ;) It seems your Sonic software is able to use SPTI directly, not via FrogASPI wrapping? If I am not mistaken, Microsofts own SPTI layer is implemented starting with at least WinXP, and from there all the way up to Win8.

      But if somehow my article gave you the right idea as to what to look for, I’m glad it works for you now! :)

      Edit: Ah, SPTI is actually quite old as Wikipedia tells me. Support for Microsofts API starts with Windows NT it seems, although I am not sure whether this means NT 4.0 or NT 3.51 or what.. but yeah.

      • Hi thrawn,

        Actually I had set this to use ASPI under Windows NT and it would not recognize the two CD/DVD burners I had. (both of which are SATA). Once I selected the SPTI it worked but only after I had renamed that great Frogaspi program you found.

        Thanks again,


        • I see, how strange. With SPTI, all ASPI dependencies should be gone, and I would expect the software to just talk to Microsofts layer, not needing anything else. Apparently, there is something more going on behind the curtains with Sonics Foundry Siren Jukebox 2.0c.

          But still, if it works now, perfect! :)

          • Yes very strange, but now working perfectly. Thanks again for your great article and for sharing!


            • Same here… Switching to Win7, and unable to use my all-time favourite Siren Jukebox. Only after installing the ASPI driver I was able to configure the drive. So there’s definitely a link to Siren.
              Thank you so much!!!!!!


              • Hey Paul,

                Seems it’s pretty much confirmed then.

                Something must be very wrong with the SPTI support of this software, shouldn’t need to rely on ASPI at all. But it seems Siren Jukebox is roughly from the same time as the Xing AudioCatalyst I’m using, which doesn’t support SPTI at all. Guess it’s a problem Sonic Foundry had during the ASPI->SPTI transition time and never got to fix really?

                Well, doesn’t matter, good to hear it works for you now too!

                Since there are some people who seem to really like that software, maybe I’ll have a look at it too, kinda wanna know what’s good about it now. :)

                • thrawn,

                  If you decide to try out Siren Jukebox 2.0c from now SONY (Sonic Foundry created it) here are some helpful hints:

                  1. Since Sonic Foundry made this, you will not be able to try out the Demo Siren Xpress version until you perform this:

                  Download the Sony Creative Software Online Registration Repair Tool from Here: http://www.sonycreativesoftware.com/download/link?id=3126.0

                  or if you purchase this program, you will still need to perform the above so the internal URLs within Siren Jukebox get routed to SONY Creative Software.

                  2. Run Siren Jukebox 2.0c and Hold down Shift key and click on Options I Preferences

                  3. Click on the Internal Tab that is now visable (this is normally hidden)

                  4. Scoll down in the list and look for “site address for CDDB”

                  5. Double-click on the information under the Value Column and replace it with this: freedb.freedb.org/~cddb/cddb.cgi

                  6. Make sure you click Apply then OK

                  ** This will allow Siren Jukebox to now access the Free CDDB database so you can rip music with all the data **

                  7. Installing your information regarding FrogASPI will also be needed if you are using Windows 7 x64 SP1 system.

                  8. I still find that Siren is one of the Better Media Players and I can create custom playlists, use the MediaFace II program that comes with the Retail CD of Siren to print out Spine or custom CD labels

                  9. If you have a chance to install older Sonic Foundry software, I would so the “shared” Plug-ins with in Siren jukebox 2.0c get updated. What I mean is, Install ACID Pro 4.0, Vegas 4.0 and Sound Forge 6. After you have completed this, your media files will be updated with the “latest” dll. Main example is .ogg formats now support VBR!

                  10. I have a typed out Help Guide that I have been working on that I keep around so when I re-install Siren I can get all my settings back.

                  11. Some helpful things to Backup once you start using Siren Jukebox to rate your music, artists, etc.

                  The following files will need to be backed up:

                  Sfsiren.jdb, sfsiren.jpl, sfsiren.dv and sfcdiddb.cdb

                  These files above contain your Star Rating, Song ID information, Last Played, etc.

                  12. The Following Extra’s for Siren are extremely helpful should you want to create a custom “skin”

                  Full Program: http://download.sonymediasoftware.com/current/siren20_enu.exe

                  – You will need a serial number to run the full program otherwise you can run this in demo mode after fixing the registry issue (from above)

                  Skin program: http://download.sonymediasoftware.com/util/sirenskingrafterskit.exe

                  English Manual: http://download.sonymediasoftware.com/manuals/siren20c_manual_en.exe

                  13. Remember that you can then remove Vegas, Sound Forge and ACID once you have verified your file formats are working under Siren. Install the above are only to update the Shared plug-ins folder

                  14. Please e-mail me if you have questions!

                  Vegas 4 download: http://www.sonycreativesoftware.com/download/updates/vegasfamily

                  ACID 4 download:

                  Sound Forge download: http://www.sonycreativesoftware.com/download/updates/soundforgefamily

                  Siren Jukebox has been found on ebay for cheap. I have purchased extra copies for myself in the past just so I have extra serial numbers.

                  • Hey, thank you for all the information and the links, I am downloading right now! :)

                    And it seems my cascaded reply system here has its limits when it comes to width. ;)

                    • Ugh, such headaches have made me just switch rather than use one I paid for. ;( At least there’s some good programs for free like EAC or ImgBurn or Audacity.

                      • Joe,

                        I should have mentioned, that once you have installed the FrogASPI per the instructions from earlier in this article, you will then need to access the “Hidden” settings under SIREN Jukebox to be able to access the CD Settings that normally will lock up SIREN Jukebox because by default SIREN uses Aspi. We need to switch this to SPTI.


                        1. Start SIREN Jukebox
                        2. Click on Options
                        3. Hold down your Shift-key then click on Preferences
                        4. Release the Shift-Key
                        5. Click on the new tab showing called “Internal”
                        6. Scroll down and look for something called Use Aspi (disable on NT only) section. This should be the 6 paragraph or so. Even though it looks like an Excel spreadsheet, each blank line I consider that a paragraph
                        7. If you are using Windows 7 x64 use the follwing

                        Use Aspi (Disable on NT only) FALSE
                        Use SPTI Direct (enable on NT only) TRUE

                        If you are using Windows 7 x86 (32 bit) reverse the above settings

                        8. Make sure to click on another cell so the Apply button will become clickable.
                        9. Click Apply
                        10. Click OK
                        11. Close out of SIREN Jukebox
                        12. Go back into SIREN Jukebox
                        13. NOW, when you click under Options | Preferences | CD Settings, the program will no longer Lock Up and Freeze.

                        It took me awhile to figure this out but this is another way to make sure you can edit those settings!

                        This really applies to anyone having the issues. Thanks again to thrawn for the initial help on ASPI!

                    • Joe,

                      I have been using Siren Jukebox 2.0c since Windows 98se and I am currently using this fine piece of software still under Windows 7 x64 with 8gb of Ram. I know this is older software, but the features it offers and the fact that someone found an easy solution to get CDDB information from the Free service working is why I still use this program. I know there are other programs but for me, I like the feel and the look of this program.

                      Hopefully you will get it working. SONY for some reason never updated it and I think that is a mistake.

  13. A nice article with very useful info.

    The [Panasonic/Matsushita UDF 2.5 driver for Windows XP x64] I found on 4shared, via http://de.wikibooks.org/wiki/DVD-RAM/_Weblinks
    ~Note the line Passwort: „DVD-RAM-Wikibook“ – Use “DVD-RAM-Wikibook” as the password.

    What I don’t get is all the obfuscation and secrecy regarding XP64 and Blu-ray. Bizzaro world.


    • I don’t think it’s really secrecy, it’s just a very, very rare operating system. So stuff that needs to be adapted specifically to run on this OS (or Server 2003 x64, which isn’t exactly wide-spread on the Desktop either) is just harder to find.. or doesn’t exist at all.

      Password protecting the download on 4shared isn’t too much of an issue anyway as long as the password is publicly known. Not that the password would make much sense in that way, but yeah, whatever.

      Good thing to see that I am not the only one hosting the driver though! :)

  14. Thank you very much for your effort.
    I’ve been searching for the UDF driver for XP x64 for a long time.
    Found it via your link, and it works great.

 Leave a Reply

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong> <pre lang="" line="" escaped="" cssfile="">