Simviation Forum - Gauge Sound .dll

	Search the archive:
	News: These are the archived forums. Click here to visit our new forums.

Simviation Main Site | Site Search | Upload Images

Simviation Forum › Current Flight Simulator Series › FS 2004 - A Century of Flight › Gauge Sound .dll

(Moderators: Mitch., Fly2e, ozzy72, beaky, Clipper, JBaymore, Bob70, BigTruck)

� Previous Topic | Next Topic �

Pages: 1 2

Send Topic

Print

Gauge Sound .dll (Read 9743 times)

Dec 8^th, 2009 at 11:57am

xerxes Offline
Colonel
I Like Flight Simulation!
Michigan

Gender:
Posts: 40

I'm trying to install the DeHavilland Otter. The readme says to put the guage sound .dll into the main FS9 folder but there already is one there and it asks if I want to overwrite it. I have a lot of other add on AC and I dont want to mess up another a/c gauge sound file. Can I change the name of the new file so they both can exist in the same folder?

Dumbest guy on the planet.

IP Logged

Reply #1 - Dec 8^th, 2009 at 12:09pm

BSW727 Offline
Colonel
Please upload all images
to SimV.
Inside a Boeing 727

Gender:
Posts: 202

I don't think so. It is looking specifically for the name of this .dll.

IP Logged

Reply #2 - Dec 8^th, 2009 at 12:11pm

Hagar Offline
Colonel
My Spitfire Girl
Costa Geriatrica

Posts: 33159

As you already have the file installed there's no need do anything. It probably came with another aircraft.

If the new file is a later version than the old one you can safely overwrite it if you wish.

Founder & Sole Member - Grumpy's Over the Hill Club for Veteran Virtual Aviators
Member of the Fox Four Group

Need help? Try Grumpy's Lair

My photo gallery

IP Logged

Reply #3 - Dec 8^th, 2009 at 12:52pm

Opa Offline
Colonel
Fly FS
Plano, Texas

Gender:
Posts: 634

It is also very important to check your FS9.cfg file for the presence of the following lines:

[OLDMODULES]
GaugeSound.dll=1

If not present, you can just add it at the end of the FS9.cfg file and FS will locate it properly when you start up FS again.

That just tells FS that it is OK to use the Gaugesound.dll - as it may think it is not compatible.

As has already been suggested, do not overwrite the existing dll unless the new one has a later date.

David "Opa" Marshall

IP Logged

Reply #4 - Dec 8^th, 2009 at 1:25pm

HoratioWondersocks Offline
Colonel
Fly FS

Posts: 23

Hello
You could also make a backup of your present sound.dll and put it somewhere safe and then try the new one.I am sure you wont have problems.
cheers Andy

IP Logged

Reply #5 - Dec 8^th, 2009 at 1:52pm

xerxes Offline
Colonel
I Like Flight Simulation!
Michigan

Gender:
Posts: 40

Thanks everyone for the quick response. I'll give it a shot.

Dumbest guy on the planet.

IP Logged

Reply #6 - Dec 8^th, 2009 at 3:26pm

patchz Offline
Colonel
What, me worry?
IN THE FUNNY PAPERS

Gender:
Posts: 10589

Opa wrote on Dec 8^th, 2009 at 12:52pm:

It is also very important to check your FS9.cfg file for the presence of the following lines:

[OLDMODULES]
GaugeSound.dll=1

If not present, you can just add it at the end of the FS9.cfg file and FS will locate it properly when you start up FS again.

That just tells FS that it is OK to use the Gaugesound.dll - as it may think it is not compatible.

As has already been suggested, do not overwrite the existing dll unless the new one has a later date.

I have a similar problem Opa. When I open FS9, I get an error message stating FSsound.dll is not compatible. I checked, and I have the FSsound.dll=1 entry in FS9.cfg. Any thoughts?

If God intended aircraft engines to have horizontally opposed engines, Pratt and Whitney would have made them that way.

IP Logged

Reply #7 - Dec 8^th, 2009 at 6:45pm

Opa Offline
Colonel
Fly FS
Plano, Texas

Gender:
Posts: 634

patchz wrote on Dec 8^th, 2009 at 3:26pm:

Opa wrote on Dec 8^th, 2009 at 12:52pm:

It is also very important to check your FS9.cfg file for the presence of the following lines:

[OLDMODULES]
GaugeSound.dll=1

If not present, you can just add it at the end of the FS9.cfg file and FS will locate it properly when you start up FS again.

That just tells FS that it is OK to use the Gaugesound.dll - as it may think it is not compatible.

As has already been suggested, do not overwrite the existing dll unless the new one has a later date.

I have a similar problem Opa. When I open FS9, I get an error message stating FSsound.dll is not compatible. I checked, and I have the FSsound.dll=1 entry in FS9.cfg. Any thoughts?

Are you sure you are looking at FS9.cfg?� There is another file in the same folder which is named FS9.cfg.txt

I have known a few simmers who edited that one instead of the FS9.cfg file.

Might be worth checking.

If you are indeed looking at the FS9.cfg file, be absolutely sure the fssound.dll=1 is spelled correctly and that there are no empty spaces after the 1

That would be enough for FS not to process the entry correctly. Place your cursor right after the 1 and hit enter to place a blind marker there.

Keep us posted.

David "Opa" Marshall

IP Logged

Reply #8 - Dec 8^th, 2009 at 7:21pm

patchz Offline
Colonel
What, me worry?
IN THE FUNNY PAPERS

Gender:
Posts: 10589

Opa wrote on Dec 8^th, 2009 at 6:45pm:

patchz wrote on Dec 8^th, 2009 at 3:26pm:

Opa wrote on Dec 8^th, 2009 at 12:52pm:

It is also very important to check your FS9.cfg file for the presence of the following lines:

[OLDMODULES]
GaugeSound.dll=1

If not present, you can just add it at the end of the FS9.cfg file and FS will locate it properly when you start up FS again.

That just tells FS that it is OK to use the Gaugesound.dll - as it may think it is not compatible.

As has already been suggested, do not overwrite the existing dll unless the new one has a later date.

I have a similar problem Opa. When I open FS9, I get an error message stating FSsound.dll is not compatible. I checked, and I have the FSsound.dll=1 entry in FS9.cfg. Any thoughts?

Are you sure you are looking at FS9.cfg?� There is another file in the same folder which is named FS9.cfg.txt

I have known a few simmers who edited that one instead of the FS9.cfg file.

Might be worth checking.

If you are indeed looking at the FS9.cfg file, be absolutely sure the fssound.dll=1 is spelled correctly and that there are no empty spaces after the 1

That would be enough for FS not to process the entry correctly.� Place your cursor right after the 1 and hit enter to place a blind marker there.

Keep us posted.

Yes, I'm looking at .cfg, not .cfg.txt. The entry is:

[OLDMODULES]
FSSound.dll=1
SOARRec.dll=1
GaugeSound.dll=1

and there are no spaces after the 1.

Also, I have no problem with my duplicate install and the entry there is:
[OLDMODULES]
FSSound.dll=1
SOARRec.dll=1

And I have some of the same aircraft in both installs that use the FSsound.dll file.

I also get the same error message for the SOARRec.dll in the original install.

If God intended aircraft engines to have horizontally opposed engines, Pratt and Whitney would have made them that way.

IP Logged

Reply #9 - Dec 8^th, 2009 at 7:35pm

Opa Offline
Colonel
Fly FS
Plano, Texas

Gender:
Posts: 634

patchz wrote on Dec 8^th, 2009 at 7:21pm:

Opa wrote on Dec 8^th, 2009 at 6:45pm:

patchz wrote on Dec 8^th, 2009 at 3:26pm:

Opa wrote on Dec 8^th, 2009 at 12:52pm:

It is also very important to check your FS9.cfg file for the presence of the following lines:

[OLDMODULES]
GaugeSound.dll=1

If not present, you can just add it at the end of the FS9.cfg file and FS will locate it properly when you start up FS again.

That just tells FS that it is OK to use the Gaugesound.dll - as it may think it is not compatible.

As has already been suggested, do not overwrite the existing dll unless the new one has a later date.

I have a similar problem Opa. When I open FS9, I get an error message stating FSsound.dll is not compatible. I checked, and I have the FSsound.dll=1 entry in FS9.cfg. Any thoughts?

Are you sure you are looking at FS9.cfg?� There is another file in the same folder which is named FS9.cfg.txt

I have known a few simmers who edited that one instead of the FS9.cfg file.

Might be worth checking.

If you are indeed looking at the FS9.cfg file, be absolutely sure the fssound.dll=1 is spelled correctly and that there are no empty spaces after the 1

That would be enough for FS not to process the entry correctly.� Place your cursor right after the 1 and hit enter to place a blind marker there.

Keep us posted.

Yes, I'm looking at .cfg, not .cfg.txt. The entry is:

[OLDMODULES]
FSSound.dll=1
SOARRec.dll=1
GaugeSound.dll=1

and there are no spaces after the 1.

Also, I have no problem with my duplicate install and the entry there is:
[OLDMODULES]
FSSound.dll=1
SOARRec.dll=1

And I have some of the same aircraft in both installs that use the FSsound.dll file.

I also get the same error message for the SOARRec.dll in the original install.

If I understand you correctly you don't get the warning message regarding FSSound.dll in one installation while you do get it another. Is that basically correct?

Are the Operating Systems the same?� I use XP.

Also my FSSound.dll and the SOARRec.dll are in my Modules folder.

Just trying to see what differences between our setups might be.

David "Opa" Marshall

IP Logged

Reply #10 - Dec 8^th, 2009 at 7:49pm

patchz Offline
Colonel
What, me worry?
IN THE FUNNY PAPERS

Gender:
Posts: 10589

Opa wrote on Dec 8^th, 2009 at 7:35pm:

If I understand you correctly you don't get the warning message regarding FSSound.dll in one installation while you do get it another. Is that basically correct?

Correct.

Are the Operating Systems the same?� I use XP.

Same computer, same op sys, minor differences in FS9.cfg due to Oz on second install.

Also my FSSound.dll and the SOARRec.dll are in my Modules folder.

Ditto.

Just trying to see what differences between our setups might be.

It's not a big deal, I just click no on both error msgs each time. More of a irritation than anything else.

If God intended aircraft engines to have horizontally opposed engines, Pratt and Whitney would have made them that way.

IP Logged

Reply #11 - Dec 8^th, 2009 at 8:46pm

Opa Offline
Colonel
Fly FS
Plano, Texas

Gender:
Posts: 634

[/quote]

It's not a big deal, I just click no on both error msgs each time. More of a irritation than anything else.

[/quote]

An annoyance that should not be happening though.

Just one more idea -

1. CUT your entire [OLDMODULES] section and paste it into temporary text file in you Desktop (so you can easily copy it later).

[OLDMODULES]
FSSound.dll=1
SOARRec.dll=1
GaugeSound.dll=1

The above is mine.

2. Save you FS9.cfg file and then restart FS2004 and then exit it.

3. Open your FS9.cfg file and Paste your Old Modules data - including the label of course) between the [FACILITIES] label and data and the� [DISPLAY.Device etc label.

Mine looks like this:

[FACILITIES]
COUNTRY=United States
STATE=Nevada
CITY=Las Vegas
GTL_BUTTON=6225

[OLDMODULES]
FSSound.dll=1
SOARRec.dll=1
GaugeSound.dll=1

[DISPLAY.Device.NVIDIA GeForce 7900 GS .0]

4. Save your edits and restart FS2004 - see if you still get the warning message.

Be SURE FS2004 is not running any time you edit the FS9.cfg file as it will NOT save edits if it is running.

David "Opa" Marshall

IP Logged

Reply #12 - Dec 8^th, 2009 at 11:19pm

patchz Offline
Colonel
What, me worry?
IN THE FUNNY PAPERS

Gender:
Posts: 10589

Opa wrote on Dec 8^th, 2009 at 8:46pm:

Quote:

It's not a big deal, I just click no on both error msgs each time. More of a irritation than anything else.

An annoyance that should not be happening though.

Just one more idea -

1. CUT your entire [OLDMODULES] section and paste it into temporary text file in you Desktop (so you can easily copy it later).

[OLDMODULES]
FSSound.dll=1
SOARRec.dll=1
GaugeSound.dll=1

The above is mine.

2. Save you FS9.cfg file and then restart FS2004 and then exit it.

3. Open your FS9.cfg file and Paste your Old Modules data - including the label of course) between the [FACILITIES] label and data and the� [DISPLAY.Device etc label.

Mine looks like this:

[FACILITIES]
COUNTRY=United States
STATE=Nevada
CITY=Las Vegas
GTL_BUTTON=6225

[OLDMODULES]
FSSound.dll=1
SOARRec.dll=1
GaugeSound.dll=1

[DISPLAY.Device.NVIDIA GeForce 7900 GS .0]

4. Save your edits and restart FS2004 - see if you still get the warning message.

Be SURE FS2004 is not running any time you edit the FS9.cfg file as it will NOT save edits if it is running.

I discovered, after removing
[OLDMODULES]
FSSound.dll=1
SOARRec.dll=1
GaugeSound.dll=1
and pasting in a notepad doc, that my facilities label was several labels below my display label. I completed the process. I then removed my facilities label and pasted it, following the above procedure. Then I replaced the facilities label above the old modules label. Every time I opened FS9, I still got the error message. Now what coach?� Grin

Grin

Edited:

This is what mine looks like now.

[FACILITIES]
COUNTRY=United States
STATE=Hawaii
CITY=
GTL_BUTTON=6225
[OLDMODULES]
FSSound.dll=1
SOARRec.dll=1
GaugeSound.dll=1
[DISPLAY.Device.RADEON 9800 PRO.0]

If God intended aircraft engines to have horizontally opposed engines, Pratt and Whitney would have made them that way.

IP Logged

Reply #13 - Dec 9^th, 2009 at 4:16am

Hagar Offline
Colonel
My Spitfire Girl
Costa Geriatrica

Posts: 33159

It's possible you have an early version of FSSound.dll. You can check the version from Right-click/Properties. Mine is Version 1.5.0.1

Founder & Sole Member - Grumpy's Over the Hill Club for Veteran Virtual Aviators
Member of the Fox Four Group

Need help? Try Grumpy's Lair

My photo gallery

IP Logged

Reply #14 - Dec 9^th, 2009 at 5:52am

Opa Offline
Colonel
Fly FS
Plano, Texas

Gender:
Posts: 634

May have to file this one under the "

Great Mysteries of Life

" category.

These old eyes do not see anything wrong with your FS9.cfg entries.

The only other thing I can suggest is to let XP do a search to be absolutely sure you do not have a second copy of GaugeSound.dll (and/or the others) anywhere else in the sim.

David "Opa" Marshall

IP Logged

Pages: 1 2

Send Topic

Print

� Previous Topic | Next Topic �

Top of this page

Simviation Forum » Powered by YaBB 2.5 AE!
YaBB Forum Software © 2000-2010. All Rights Reserved.

Valid XHTML

Valid CSS

Powered by Perl

Source Forge