SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 17 | February | 2003 ]

<< Previous Message << >> Next Message >>


Date: Mon, 17 Feb 2003 12:54:34 PST8
From: Peter Skye <pskye@peterskye.com >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: speaker pid log ?

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

Steven Levine wrote:
>
> Dani's driver will beep if it detects drive errors.

Thanks, I didn't know that. I just went through her danis506.add docs
and she does issue low, medium and high beeps for various errors, so
it's possible that the three-tone ascending sequence I'm hearing is all
three beep codes occuring at the same time. I've emailed her to ask.

I did run her DiskInfo utility (which apparently queries her driver for
totals) and the response screen shows no errors, but it doesn't say that
it includes the three error categories she beeps on so I've asked her
about that too.

> >Is there a utility I can run that will monitor the cpu speaker
> >and tell me which program/PID/driver is using the thing?
>
> If you have a working OS/2 trace setup, you can trace
> both the DosBeep and the DevHlp beep. This will be
> most useful if the beep is from an application.

Hmm. I load Theseus on bootup -- is that what you mean? I have this
line in my CONFIG.SYS (I'm using W4 FP10):

DEVICE=H:\apps\Theseus\THESEUS5.SYS

Or did you want me to hook up a debug machine through COM2? I don't
know if I have the FP10 debug kernel or not.

- Peter

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================


<< Previous Message << >> Next Message >>

Return to [ 17 | February | 2003 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.