|
Don't forget that even though the IBM SDLC/MPCA cards may only show up as using IRQ 3, they actually use IRQ 3 AND IRQ 4. Neil Palmer AS/400~~~~~ NxTrend Technology - Canada ____________ ___ ~ Thornhill, Ontario, Canada |OOOOOOOOOO| ________ o|__||= Phone: (905) 731-9000 x238 |__________|_|______|_|______) Cell.: (416) 565-1682 x238 oo oo oo oo OOOo=o\ Fax: (905) 731-9202 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ mailto:NPalmer@NxTrend.com AS/400 The Ultimate Business Server http://www.NxTrend.com > -----Original Message----- > From: pault@praim.com [SMTP:pault@praim.com] > Sent: Tuesday, June 09, 1998 11:13 PM > To: 'midrange-l@midrange.com' > Subject: Re: SDLC Help (again) > > Vincent LeVeque wrote to midrange-l: > > Against better advice, I've purchased an IBM brand SDLC card (used), > to enable dial-in to a local AS/400 through the ECS port. > The SDLC card came with no documentation or configuration software. I > can't seem to get Windows NT or CA/400 to "see" it. > Any suggestions? Besides "buy a Hayes Autosync", which I probably > should have done in the first place. > I understand there might be a diagnostic diskette available for this > card. > If so, does anyone know where I can get it? > > Dear Vincent, > > The setup file you need is named IBMSDLC.INF and is shipped as part of > Client Access for 95/NT. If you look at the file, you will see that it > offers only one configuration choice for an SDLC card. The adapter's > IRQ must be 3 and its I/O address must be 380. The hardware of the > IBM card is able to support more IRQ's and I/O address ranges than the > values listed in the Client Access information file. > Some months ago I had a conflict between a sound card that was > hardwired to use only I/O address 380 and an IBM MPCA adapter. Since > the documentation with the card listed support for alternative I/O > addresses, I contacted IBM to ask whether the SDLC driver built into > Client Access could work with the card set to a different I/O address > than 380. > The response that I received from IBM was that the driver built into > Client Access can only work with the adapter at the settings listed in > the IBMSDLC.INF file. It is not possible to use the adapter at any > other setting with the Client Access driver (if you attempt to > experiment, you will usually receive an adapter not found message). > You should use your resource managing tools on your Win NT machine to > verify that the required I/O Address and IRQ are available. You should > also verify that any hardware configuration options that might exist > on the card itself ( ie dip switch settings) have been set to request > the proper resources. > The IBM web site for Client Access includes a setup document for SDLC > connections that provides step by step instructions on configuring > your Netsoft Router correctly. > Hope this helps, > /Paul > - -- > Paul Tykodi, Technical Director E-mail: > pault@praim.com > Praim Inc. Tel: 603-431-0606 > 140 Congress St., #2 Fax: 603-436-6432 > Portsmouth, NH 03801-4019 > > +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.