Mail Archives: opendos/2005/01/10/03:29:45
Sigh!
Over the holidays I've started (contemplating;-) experimenting with
networking two (or more;-) of my PC's. DR-DOS 7.XX comes with
PNW, so this seemed like an obvious choice to use.
Firstly, I established what I/O and IRQ resources were available
on these PC's, selecting I/O address 300h and IRQ 5 or IRQ 10
as suitable for use by a network card.
Secondly, I tried to identify what network cards I had and what
resouces they required (or could be configured to use). Initially,
I settled on a pair of SMC 8013EPC cards, until I realized they
would use up a 16K memory window, whereas I tend to make full
use of my UMB space for various DOS drivers and for EMS. Next,
I tried to identify a pair of old 8 bit Novell cards and a pair of (also
old) 16 bit Novell cards - AFAICT, these are NE1000 and NE2000
cards, respectively (well, they don't have a recognizable model
number, but the NE1000 and NE2000 packet drivers are happy to
load with them and report their MAC address correctly). Although
these cards only support IRQ 2 through 5 (I'd have preferred to
use IRQ 10), they don't require a RAM window, so are ideal for
a DOS environment. Since I expect the 16 bit cards will have
better performance over the 8 bit cards, I settled for the (AFAICT)
NE2000 cards.
Alas, when I tried to load the VLM ODI drivers (NE2000.COM is
1996/04/01 vintage), I got the error message :
"The hardware configuration conflicts"
The same vintage NE1000.COM driver, using the same hardware
configuration (different card of course, same settings), loads
without any such error message.
Next, I tried installing the Client32 for DOS (version 2.71) drivers
with the NE2000 cards. Seemed OK, no such error message.
Well, it seems very strange to me that Novell's VLM ODI NE2000
driver isn't compatible with their own NE2000 card, yet that's what
the above suggests to me! :-(
Since the Client32 NE2000 driver seems happy with the 16 bit
Novell cards, I though perhaps this would be a suitable (actually,
preferred, because it loads in XMS, leaving more free conventional
memory) driver to use with PNW. However, the posting below,
and other stuff I can find on the Internet, suggests these are not
compatible (also, I don't know if the Client32 stuff can perform
server-type functions for peer-to-peer networking). :-(
So,
1) Can anyone confirm (or otherwise) that Novell's VLM ODI NE2000
driver is broken, when using an original (early 90's) Novell card?
2) Have I correctly interpreted Ben's posting, which to me says that
the Client32 drivers are incompatible with PNW?
Joe.
> -----Original Message-----
> From: Ben A L Jemmett [SMTP:ben DOT jemmett AT ukonline DOT co DOT uk]
> Sent: Sunday, February 01, 2004 1:34 PM
> To: opendos AT delorie DOT com
> Subject: Re: File transfer util in DR-DOS? [PNW vs Netware]
>
---------- snip ----------
> > I not in a position to do any heroic hardware upgrades on the machines,
> but
> > I do have an old 10-T hub which also has a coax port, and I was going to
> > plug the network cable from one of the computers into this, along with a
> > laptop. I'm hoping that will get me on the network. Once I am, will a
> > Netware client on the laptop be able to see the Personal Netware server
> and
> > log on for file sharing?
>
> The old VLM client for DOS is the only one that will access a Personal
> NetWare
> server. At a protocol level, PNW and NetWare itself are incompatible, so
> the
> other Novell clients won't talk to PNW. I'm not sure if the Macintosh
> client
> will talk to PNW, since that's nothing to do with Novell these days, but I
> doubt it'll work. At a transport level, Personal NetWare uses IPX.
>
> Regards,
> Ben A L Jemmett.
> (http://web.ukonline.co.uk/ben.jemmett/, http://www.deltasoft.com/)
-------------------------------------------------------------------------------------------------------
This email (including any attachment) is confidential. If you are not the intended recipient,
you must not disclose or use this email or the information contained herein for any purpose.
If you have received this email in error, please immediately advise us by reply and delete this email.
This email may not be altered, forwarded or re-issued without our consent. AMPY Email Metering is
not responsible for any changes made to this email or the effect of any changes on the email’s meaning.
It is the responsibility of the recipient to scan this email for viruses and faults prior to processing.
AMPY Email Metering shall not be liable for any loss or damage caused by this email from transmission,
viruses, faults or the use of data accompanying this message. AMPY Email Metering reserves all its
rights, including copyright,in this email.
- Raw text -