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 [ 02 | January | 2002 ]

>> Next Message >>


Date: Wed, 2 Jan 2002 01:14:38 PST7
From: "Steven Levine" <steve53@earthlink.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: SBLive setup

=====================================================
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.
=====================================================

In <3C32B0DD.2DE6@peterskye.com>, on 01/01/02
at 11:06 PM, Peter Skye said:

>The drivers are chained. Typically the first driver asks its hardware if
>it needs service; if the hardware does want service then the driver
>INs/OUTs the necessary ports. The driver can then either pass the
>interrupt down the chain to any other driver which might want it, or
>return without passing the interrupt. If the driver doesn't attempt to

In general, this is a reasonable explanation of how it works in DOS. The
OS/2 device driver implementation is quite different and most of your
statements don't apply.

>while but as I recall there's a bit in the driver header which the driver
>programmer can set to choose either type of behavior.

>*Therefore*, you can either disassemble the drivers to see how the
>headers are set up *or* you can play with the sequence of the drivers
>until you find a sequence that works. :)

You're thinking of the shared access bit. This has nothing to do with IRQ
sharing. IRQ sharing is determined when the IRQ is allocated via a DevHlp
call.

Steven

--
----------------------------------------------------------------
"Steven Levine" MR2/ICE 2.30a #10183 Warp4/FP15
www.scoug.com irc.webbnet.org #scoug (Wed 7pm PST)
----------------------------------------------------------------

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

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".

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


>> Next Message >>

Return to [ 02 | January | 2002 ]



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.