• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
Sign in to follow this  
Followers 0
Nomen

Running Foobar2000 with SACD input DLL

6 posts in this topic

What version of foobar2000 is compatible with the foo_input_sacd.dll driver - and will run on win-98 with kernelEx? I can install the newest stable version of foobar2000, but it gives this error when I run it -> SHARED.DLL is linked to missing export kernel32.dll: HeapQueryInformation. An old version of Foobar (that I already had installed) doesn't seem to want to load the sacd dll file.

Or - does anything else play SACD iso files?

0

Share this post


Link to post
Share on other sites

kernel32.dll: HeapQueryInformation is supported by KernelEx with a little help from Kexstubs.

Foobar2000 has changed their api and older optional components don't work with the latest app and vice versa. See the FAQ for details.

0

Share this post


Link to post
Share on other sites

kernel32.dll: HeapQueryInformation is supported by KernelEx with a little help from Kexstubs.

I downloaded Kstub730.zip and Kstub822.zip and extracted both of them to my windows\kernelex directory. I modified core.ini to read: contents=std,kexbases,kexbasen,Kstub822 and restarted the system. It didn't restart properly the first time, but it did start ok the second time. When I run foobar (version 1, 1, 0, 0) I now get a different error:

Shared.dll is linked to missing export SHELL32.DLL: SHParseDisplayName.

0

Share this post


Link to post
Share on other sites

Shared.dll is linked to missing export SHELL32.DLL: SHParseDisplayName.

Set the compatibility mode for shared.dll to "Windows XP SP2".

0

Share this post


Link to post
Share on other sites

Set the compatibility mode for shared.dll to "Windows XP SP2".

That makes the error message go away, but now nothing seems to happen when foobar2000.exe is started. I started cctask.exe and set it to auto-update mode and tried foobar again. Foobar threw up a small menu window (start in safe mode, check online troubleshooter, start normally). I tried start normally, and foobar2000.exe was loaded into memory according to cctask, and it stayed there for about 8 seconds before it disappeared. I started foobar again, tried "check online troubleshooter", and again nothing apparent seemed to happen. Same thing happens when I select "start in safe mode".

Any other ideas? Has anyone gotten foobar2000 version 1.1.x or higher runs under win-98?

What is shared.dll? There is no Version tab when you look at it's file-properties.

0

Share this post


Link to post
Share on other sites

>That makes the error message go away, but now nothing seems to happen when foobar2000.exe is started....

We can get an app to load by using stubs, but functioning properly is often another story. :(

>Any other ideas?

Oldapps.com lists these four builds as being compatible with Win2000. They are our best chance for success. Use compatibility mode "Windows 2000". We don't want to advertise as XP since faking it clearly has not worked!

> Has anyone gotten foobar2000 version 1.1.x or higher runs under win-98?

:no:

>What is shared.dll? There is no Version tab when you look at it's file-properties.

A shared dll that plugs-ins use to access the foobar2000 API.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.