Re: Question

[Aaron Gage <agage@riemann.mines.edu>]

> I assume that the first character on each line printed by pktwatch is a 'S',
> and there is no line with a 'R' in the first column, right?

Correct.  When I copied down that line, I forgot to show the beginning:
S 00403325FDE2  (which is just a send flag with the hardware address).

> The line above
> looks correct for a sent packet. If you don't get any other lines than these,
> it is very likely that your packet driver didn't receive any packets. I've
> heard about this problem in the past with some cheap NE2000 cards: packets
> get sent out correctly, but the packet driver doesn't receive anything, and
> therefore can't pass anything on to the bootrom.

This is basically the conclusion I came to from the information on the web.

> I assume that the packet
> driver you are using is not fully compatible with your network card for
> some reason (very likely it has something to do with hardware interrupt
> handling). Does your network card come with it's own packet driver? If
> yes, you should try to use that.

This could be part of the problem.  It is possible that this card was
repackaged with the wrong disk of drivers.  Even if the drivers were
correct, I may have chosen the wrong one for this application.  Actually,
here's the full story -- I bought two of these cards, and the included
disk for one was bad, so I used the other.  However, I believe that these
cards are identical.

The included drivers are:

Netware ODI
Netware IPX
Netware 2.2 server
Netware 3.11 server
Microsoft LAN Manager
Microsoft MS Windows for Workgroups
FTP PC/TCP

I tried using the FTP PC/TCP, which did not produce any new results.  I'll have
a look at the others.

> Otherwise, take a look at the FTP or Web
> servers of the card manufacturer. Sometimes, you can find working drivers
> even from manufacturers of those cheap cards.

I'll try this anyway -- if I can figure out who makes the PN-16 card.  I
knew I should have just bought Linksys ;)

> If you are still unlucky,
> try to use the packet driver under plain DOS and check that it really works,
> for example when using PC/TCP or some other DOS TCP/IP stack. It is especially
> important with the Crynwr packet drivers (those provided with netboot) that
> you specify a correct hardware interrupt number.

I'll keep trying.  If all else fails, I'll just shelve these cheap cards
and buy something with at least a brand name.

> gero.

Thanks for the help.

--Aaron