For older hardware and OSs ask in Marvin Marvin, the Paranoid Android

Have you tried dgVoodoo? (Yes, it would be strange for the graphics drivers to be interfering with sound playback, but I have seen something like that happen before.)

barfingjake wrote:

I've tried disabling a core in the task manager, but it just freezes the whole desktop.

You mean by setting the affinity for the process?

I tried using dgvoodoo with Rogue Squadron when I was trying to get it to run in a higher resolution, but I couldn't get it to work. Is there a version that's compatible with XP? I did try wine with the game, but it didn't do anything.

And yes, I set the affinity to one core. It just crashes the game and the whole desktop freezes for some reason.

The desktop-freezing thing is strange. Perhaps it would work better if you used a utility that sets the affinity before the process is launched?

I forget what the optimal way of doing that is. A moment of Googling suggests http://www.adsciengineering.com/StartAffinity/ and https://www.portablefreeware.com/?id=1393 .

I tried THG, but it doesn't work. I do everything instructed, but the program just starts with both cores set. I can't figure out how to use StartAffinity at all. They gave little to no instructions on what I'm supposed to do. Too confusing for me.

I even tried setting it to one core in the shortcut target, but it just flashes the command prompt and does nothing. The game doesn't even start.

What sucks is that I really think that is what's causing the sound issue, because I disable one of the cores while the game was running with Process Hacker, and waited (for about an hour) for the game to go to the menu, because disabling a core causes so much of a performance drop that's unplayable. But I did however hear some of the menu music, a second of it looping over and over again.

I don't know what to do about this game.

Okay, I just tried another program, called Launch N' Set. It allowed me to start the game with only one core set.

UNFORTUNATELY, the performance still dropped significantly, and there was still no sound. 😒

I don't know, this game seems to use quite a lot of the CPU. It's usually maxxed out at about 99% in the task manager. 17 year old game doing this doesn't make a whole lot of sense.

Ok I've just tried naboo on xp sp3
dell latitude d430 (dual core) https://www.cnet.com/products/dell-latitude-d … e-series/specs/
and it works fine there is no dual core problem
back in the day I played it on a hyperthreaded cpu

What if you completely disable NVidia HD Audio in your Device Manager?

I had it disabled on my old video card, and I think there was still no sound. However, after upgrading to a GT 730, I tried to disable the Nvidia HD audio, and I got a BSD.

I will try it again.

Well, it didn't BSD this time after disabling them. But still no sound.

Of the 50 or so games I have installed on my PC, this is the only one to do this. I really don't get it. The game itself runs fine, I've even got it running in 1920x1080. But there's just no sound.

your installing from the original cd ?

Yes. I've tried from two different copies.

Have you ever been able to get the game to run correctly, i.e. by disabling sound entirely?

I might suggest trying to get a cheap USB sound device. (There's not necessarily anything wrong with those.)

His game runs correctly but without sound
My laptop uses intel hd audio
and my pc years ago used either a sblive or an audigy

USB sound device? I'm not familiar, like an adapter?

I forgot to mention that I've run the game through both onboard sound and through my TV via HDMI (from the NVIDIA card). Both had no sound output.

I've reinstalled the Intel drivers and Direct X 9.0c, but it did nothing.

here
http://www.ebay.co.uk/itm/like/172488784120?l … 38081070&crdt=0

just make sure the card has drivers for xp the one above does

Sorry for necro-posting but this thread comes up on Google often when searching for solutions to the no sound problem in Battle For Naboo and I found a fix that I want to post so other Googlers might be aided.

TL;DR: If you're getting no sound in Battle For Naboo, it is likely that your CPU is too fast/strong for what the game expects. You need to throttle your CPU by some means. The method discussed below worked for me on a Pentium 4 3.0 Ghz system running Windows XP.

The fix:

You will need:
- .NET Framework 3.5 (possibly higher will work but confirmed working with 3.5)
- Application Compatibility Toolkit for 32-bit applications

First, install .NET Framework if you don't already have it. This is a pre-requisite for the ACT (Application Compatibility Toolkit) to install and function.

Next, install the Application Compatibility Toolkit. I found it on archive.org, I think.

Once you have ACT installed, you want to open the "Compatibility Administrator (32-bit)" program.

If you haven't used this program before (I hadn't), it can look pretty complicated and overwhelming, but what we need to do is actually pretty simple.

First, when you open the program, in the left pane, you should see something that says "Custom Databases" and beneath it (you may need to click the "+" symbol for it to drop down), you should see something like "New Database(1) [Untitled_1]."

This is where we are going to create and then apply the fix.

With the "New Database" selected, click the "Fix" button on the menu bar near the top of the screen (it should be the fourth option after New, Open, and Save); it has an icon of an orange gear on a dark-colored spindle next to it).

Put in the name of the program to be fixed. (I'm pretty sure you can name this whatever. I just did "Battle For Naboo.")

Name of vendor can be left blank.

Now, importantly, for the program location, you need to point to the ACTUAL game EXE and NOT the launcher. So, click the browse button and DO NOT select the BattleForNaboo.exe file (that is just the launcher). Instead, inside your Battle For Naboo installation directory, go into the "data_pc" folder and then select the BFN.EXE file. This is the actual game exe (what we need to patch/fix).

After selecting BFN.exe, click "Next."

Do not select any options on the next screen. We do not need to mess with any compatibility modes. Just click "Next."

You should now see a new screen with a window list filled with a bunch of "Fixes" in alphabetical order. My list began with "AddProcessParametersFlag," for example.

Scroll down until you find "EmulateSlowCPU" and put a checkmark next to it. This is the fix. Now, you want to test it. With the checkmark checked, click "Test Run..."

The game will launch and you should hear audio now.

Simply close the game down like normal ("Quit" from the main menu) and return to Compatibility Administrator.

YOU ARE NOT DONE YET! (I made this mistake...)

Click Next... on the final screen, where it says "Matching Information" just click "Finish."

The wizard should close and return you to the main Compatibility Admin screen beneath it.

Select your "New Database" (the same one as before) if it is not already selected.

At this point, you might want to save the database with the fix. I'm pretty sure this is optional but just click "Save" and give your database a name and save it as an sdb file somewhere for safe-keeping.

If you want to skip this save step, I'm pretty sure it is optional.

Now, right-click the same new database (it should still be selected) and select "Install."

This should apply the fix. If you want to double-check, you should now see it under "Installed Databases."

Close Compatibility Admin and try running the game like normal. You should have audio.

And that's it.

I hope this helps someone out there. This game is a favorite of mine and I was very sad that it wasn't working on my old P4 rig. But this fix does not seem to alter performance in any meaningful way. It just makes the audio timing work.

FINAL NOTE: In general, I believe this game has other timing issues linked to framerate. Depending on your setup, you may also need to use something like RivaTuner to limit FPS to 60 or 30.

There is a known bug where your ship won't fly at all if you have a framerate that is too high. If you encounter this issue, try limiting the framerate somehow.

Enjoy!