SCOUG-HELP Mailing List Archives
Return to [ 05 | 
January | 
2003 ]
<< Previous Message << 
 >> Next Message >>
 
 
 
Content Type:   text/plain 
=====================================================  
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.  
=====================================================  
 
Rocky:  
 
Do you have the correct driver for the D-Link card?  You might want to try the NICPak   
page (http://pws.prserv.net/mckinnis/nicpak/.  Other than that I can't help you.  
 
On Sun, 5 Jan 2003 21:41:23 PST8, Michael Rakijas wrote:  
 
>=====================================================  
>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.  
>=====================================================  
>  
>Hi folks,  
>  
>Well, I'm finally getting back to trying to squash the TCP/IP bug with my home  
>network and the one eCS machine on it.  My current strategy was to set up  
>another dummy eCS machine.  Unfortunately, setup problems that occur get pushed  
>onto, and need to get popped off the problem stack before I can address my  
>objective.  In short, I can't get the eCS machine to recognize, and load the  
>driver for the network card, a D-Link 530TX+ 10/100 adapter.  
>  
>I've tried all the obvious stuff.  I've swapped out cards and I'm pretty sure  
>it's not hardware because I can run the DOS-based diagnostics in a DOS session  
>and it sees the card fine.  The diagnostics themselves look good.  I deinstalled  
>and reinstalled MPTS with the driver for the card with no change in behavior.  
>The objective machine that I am trying to debug uses the card and loads the  
>driver with no difficulty.  I confirmed no corruption with the driver files  
>(DLKRTS.NIF, DLKRTS.OS2 and PROTOCOL.INI).  When booting this dummy   
machine, the  
>driver states that no netcards were found and a serious error is reported.  The  
>driver, loaded soon after the UDF driver banner, refuses to load.  
>  
>The only remaining thing I could think of was a BIOS conflict.  I updated the  
>BIOS (a Dell XPS R450) to the most recent available and the IRQ reported by the  
>diagnostics (IRQ11) is set to available in the BIOS resource settings.  The  
>address reported by the diagnostics is 1000H but I see nowhere in the BIOS where  
>I can make sure that that address is available.  Does anyone have any  
>suggestions that I might try?  Thanks in advance.  
>  
>-Rocky  
>  
>=====================================================  
>  
>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".  
>  
>=====================================================  
>  
>  
>  
 
 
 
=====================================================  
 
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".  
 
=====================================================  
 
  
<< Previous Message << 
 >> Next Message >>
Return to [ 05 | 
January | 
2003 ] 
  
  
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.
 
 |