X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
From: "Lawrence Rust" <nospam AT NOsoftsystemSPA DOT coM DOT uk>
Newsgroups: comp.os.msdos.djgpp
References: <4468AAA9 DOT 29630 DOT ECAC73 AT gerritvn DOT gpvno DOT co DOT za>
Subject: Re: SwsVpkt
Date: Mon, 15 May 2006 17:03:43 +0200
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1807
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807
Lines: 23
Message-ID: <44689859$0$20160$8fcfb975@news.wanadoo.fr>
Organization: les newsgroups par Wanadoo
NNTP-Posting-Date: 15 May 2006 17:03:54 CEST
NNTP-Posting-Host: 86.207.184.243
X-Trace: 1147705434 news.wanadoo.fr 20160 86.207.184.243:2448
X-Complaints-To: abuse AT wanadoo DOT fr
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

"Gerrit van Niekerk" <gerritvn AT gpvno DOT co DOT za> wrote in message
news:4468AAA9 DOT 29630 DOT ECAC73 AT gerritvn DOT gpvno DOT co DOT za...
[snip]

> Thanks Lawrence, changing the hardware interrupt to 9 fixed the problem.
> For clarification: Interrupt 9 is the real h/w interrupt used by my NIC.
Should
> one always specify that correctly for SwsVpkt?

No, any available unused interrupt (in the VDM) is OK.

> Isn't the interrupt just a way
> for the realmode stub to communicate with the win32 driver?

You're right; the interrupt is only used as a signal to the 16-bit real mode
stub, typically to get it execute a section of 16-bit code.

Normally the default interrupt 7 used by SwsVpkt works fine.  It's possible
that your system has this interrupt in use by another driver.

-- Lawrence Rust, Software Systems, www.softsystem.co.uk