Clipper - fast NT and TONE()

Author

fast NT and TONE()

Chen Kedem

2004-11-22, 3:55 am

The following code freeze on my client PC:

FUNCTION test()
? "Start"
WAIT
TONE( 800, 10 )
? "End"
WAIT
RETURN NIL

Compiled with Clipper 5.2e and Blinker (forgot what version, don't
have it here)

clipper test /n
blinker fi test

On my NT4.0 WS (1.8Gh) all is working,
on my client NT4.0 WS (IBM 2.8Gh) the program freeze and the CPU is 99%
when it try to do the TONE()

From a thread a few w

s ago, I think this a problem with NT, but
until the MS support would returned to me, is it a known issue?
is there a patch available somewhere I can try?

My original problem is with a Clip4Win 3.0 application, but
plain Clipper show the same result.

The soundcard play just fine with Win32 applications, and typing
a ^G on the command prompt sound the internal beeper.

Thanks for any help

Chen.

Mel Smith

2004-11-22, 3:55 am

Chen,

I had the same problem:

I was provided a Win NT machine on my customer's network (but in my separate
office). One of my client's 'techies' installed it and passed it to me for my
use.

Later, when I placed my executable on it and tried to run it, my program quit
and left me at the Command Prompt. After mystifying hours, I finally nailed
down that it was my app sending a 'tone' to the user (actually just ??chr(7) )
that caused my app to quit). however, the 'tone' never was heard so it was
difficult to pin down why this was happening.

Later the 'techie' arrived and insisted that it was my program that was at
fault, so I brought up an old copy of FoxBase at its Dot Prompt and entered the
following command:

Fox+>? CHR(7)

.... and immediately FoxBase quit and sent me back to the Dot Prompt !!

Even then the 'techie' didn't believe me, but later he replaced the machine
with an older Win 2000 machine and the fault did not re-occur.

Strange thing is that none of the later Win XP machines had this problem.

Go figure !!

-Mel Smith

Chen Kedem

2004-11-22, 8:55 pm

Applying Microsoft hotfix Q320694 for NT Workstation
solved the problem!

As NT is no longer officially supported, yoy need to
contact Microsoft support in your region and ask them
for this fix (note that the Server and Workstation use
different files, make sure you ask for the right one).
Our company have some kind of support agreement for MS
product so we did not have to pay extra for this fix,
I'm not sure if this is always the case.

The fix replace NTVDM.EXE and WOW32.DLL

Chen.

Sponsored Links