Re: VC++ 6.0 Execution Environment

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Adam W. Montville (adam_at_montvillearchives.net)
Date: 02/24/04 

Date: Mon, 23 Feb 2004 19:00:39 -0800

sashan wrote:
> Adam W. Montville wrote:
>
>> Forgive me if this is not the proper place for a post, however, I'm in
>> a spot of trouble with my application. I am using Visual Studio 6.0
>> on Windows 2000 and accessing the WaveAPI (winmm.lib). When I execute
>> my application from *within* the VC6.0 development environment,
>> everything behaves as intended, i.e., the audio programming appears to
>> function as expected. However, when I run the same executable outside
>> of the development environment, the audio fails miserably.
>>
>
> What do you mean by 'fails miserably'? It's hard to tell without more
> detail, but I'll guess anyway. If you're running within the VC
> envrionment, a different working directory is used than when you run it
> from the Debug or Release folders outside the VC6 environment. So the
> first thing I'd check is if the wav file you're loading is also in the
> Release or Debug directories.
>
>

Thanks to you and Scott for your help. First, the nature of the
application is a 'push to talk' type of audio that transmits audio from
one computer to another. There exists a "Talk" button for this purpose.
  When I am running in the VC environment and push the Talk button,
audio is recorded and transmitted until I push the Talk button a second
time. The second press concludes recording and transmission.

When I perform the same actions outside of the VC environment, the audio
is not transmitted, but never stops recording when I press the Talk
button the second time.

So, I am recording from a microphone and transmitting the recorded audio
over the network to a similar application that then receives the audio
and plays it back.

It is important to note as well that this is code that I've inherited,
so-to-speak, and it's a real mess. Some of the threading isn't
implemented correctly, the networking implementation is far from
stellar, and memory leaks abound.

More important, if that is possible, is that I cannot debug the
application in VC!! When attempting to use the debug build in the
debugger, the application doesn't get past the startup sequence without
tripping an assert. So, my debugging is limited to trial and error and
print statements to a log file when using the release build. Not a fun
way to go about doing things.

Regards,

Adam

Quantcast