Oracle Forms

First ... we are using Forms6i developed in client-server mode with developer licenses, and then we run these forms / reports / etc. via runtime on a Terminal Server. Oracle does not technically support this, but I can state for a fact that it runs justfine_ and has for last 6 years, and 6 years before that via WinNT. Forms6i is so brilliantly stable, it's hard to think of giving it up ... but that's another story.

Duncan Mills??? Grant Roland??? y'all lurking??? (please don't hate me!!)

We have a form that runs just fine, queries data, creates a list.
It had a double-click (dc) on a key field to go to child record, users could review, edit, save, close, return to list, dc to next rec in select. Handy, because user didn't lose select set and could work at will.

New Requirement ... user wants to open several of those child records at once and arrange at will on screen, close at will, etc.

So ... we figured out how to do this with RUN_PRODUCT (Forms, etc. parameters) yippee!
(RUN_PRODUCT Is woefully searched / documented, except for run reports and, of course, deprecated in 10g, but I digress).

So ... now we deploy our test form on our production Terminal Server (we have a way to do this), an old trooper, a Windows 2000 Terminal Server. It runs just fine, does what we want. Good. Now we put it on our VIRTUAL Terminal Server (VTS), and test again. It all works, lovely, users can open 100+ sessions and VTS does not blink, all to the good (in real time, users will open maybe 5 of these sub-sessions at a time, and we will limit them to 15 via Oracle Profile.

Here's the problem:
On the old TS, it does exactly what we want.
On the new VTS, it beeps 3 times when a child rec is DC'd to.
This will drive the users batty. They need no more noise in a noisy environment.

We have tried the following ...

(a) Quiet Mode (seems to otherwise work, but not with this).

(b) an environment variable ... "QUIET=YES" ... no effect.

(c) turning off server's speaker ... no effect.

(d) changing the settings in the mysterious CONFIG.NT and AUTOEXEC.NT files that still exist in the System32 folder (this was the secret of working with WinNT servers!!!)

(e) looking for a setting in the secretive CAGPREFS.ORA file or the registry ... no luck here so far.

(f) looking thru forms help ... but this is woefully non-descript on beep behavior.

===>>> Does anyone have other ideas or an actual solution?

Is there something peculiar to using Windows 2008 R2 Terminal Server (virtual or not)??

Is there some mystic operating system setting that should be set and is new to us?

Kind regards all, thanks in advance for any clues, especially if you've read this far.

Suzanne Michelle