VOGONS


First post, by Otter

User metadata
Rank Newbie
Rank
Newbie

I was rather excited to see the fix for this problem here on this forum. I followed the procedure stated by Snover -(thanks for the help by the way 😁 )
and found that it worked.... until I close down the game and try and play again. I have closely followed the procedure and short of deleting the RBPREFS.DAT file everytime I still can't get any sound. Any other help would be appreciated greatly 😕

thanks,
Otter

Reply 2 of 7, by Nicht Sehr Gut

User metadata
Rank l33t
Rank
l33t

Originally posted by Otter found that it worked.... until I close down the game and try and play again

Unless you forgot to set the READ ONLY attribute, that shouldn't be happening.

Try it again. This time, after you set your preferences and the read only attribute (note the time), now go to the menu just before you actually quit and do nothing for a few minutes, then quit. After you quit, check the timestamp on your RBPREFS.DAT file.

Is it set to the time you set the READ ONLY attribute?
Or the time you quit the program?

Reply 3 of 7, by Otter

User metadata
Rank Newbie
Rank
Newbie
Nicht Sehr Gut wrote:
Unless you forgot to set the READ ONLY attribute, that shouldn't be happening. […]
Show full quote

Unless you forgot to set the READ ONLY attribute, that shouldn't be happening.

Try it again. This time, after you set your preferences and the read only attribute (note the time), now go to the menu just before you actually quit and do nothing for a few minutes, then quit. After you quit, check the timestamp on your RBPREFS.DAT file.

Is it set to the time you set the READ ONLY attribute?
Or the time you quit the program?

Went through your suggested procedure. It time stamps the RBPREFS.DAT file after adjusting the read only attribute. Still no sound. This is a bit flustering. Thanks for the suggestions though. To answer Craig's post, the origional problem occurs (to quote Snover)

"For some reason, RB is upset by USB joysticks when running XP. It detects a non-existent conflict with your sound card and disables the sound for you; making the RBPREFS.DAT read-only stops RB from doing this"

He's right in addressing the pref dat file because upon deleting I do have glorious sound on RB, but it disappears after I exit and reboot Rb. Any other Ideas guys?

Reply 4 of 7, by Nicht Sehr Gut

User metadata
Rank l33t
Rank
l33t

Originally posted by Otter It time stamps the RBPREFS.DAT file after adjusting the read only attribute.

Well that makes a whole lot of no sense. All I can suggest at the moment is to set up a batch file that copies your good RBPREFS.DAT file on top of the corrupted one from a backup directory after starting each game.

Reply 5 of 7, by Snover

User metadata
Rank l33t++
Rank
l33t++

So, you

  1. Deleted RBPREFS.DAT
  2. Started Red Baron
  3. Alt+Tab'd out of Red Baron while it was running
  4. Turned on the Read-Only attribute of RBPREFS.DAT

?
If you don't have sound to begin with, this won't fix it.

Yes, it’s my fault.

Reply 6 of 7, by Glidos

User metadata
Rank l33t
Rank
l33t
Nicht Sehr Gut wrote:

Try it again. This time, after you set your preferences and the read only attribute (note the time), now go to the menu just before you actually quit and do nothing for a few minutes, then quit. After you quit, check the timestamp on your RBPREFS.DAT file.

Is it set to the time you set the READ ONLY attribute?
Or the time you quit the program?

Like it Nicht. What an excellent bit of remote fault finding.

Reply 7 of 7, by Unregistered

User metadata
Snover wrote:
So, you […]
Show full quote

So, you

  1. Deleted RBPREFS.DAT
  2. Started Red Baron
  3. Alt+Tab'd out of Red Baron while it was running
  4. Turned on the Read-Only attribute of RBPREFS.DAT

?
If you don't have sound to begin with, this won't fix it.

I do have sound prior to exiting red baron. It's only upon reboot.
Found a curious notation about it here;

http://www.wings-of-valor.org/files/documents … workarounds.pdf

guess I'm not the only one having this problem. In the pdf the also suggested unplugging the usb joystick prior to booting the game. This seems to work everytime, but not a particularly attractive way to fix it. Somewhere in the middle of this and patching the game with sierra's last update I've now lost my forcefeedback *sigh* if this game didn't kick arse I"d quit on it long ago.

thanks again guys,
Otter