SCOUG-HELP Mailing List Archives

<< Previous Message << >> Next Message >>

Date:	Thu, 9 Jan 2003 19:44:54 PST8
From:	Michael Rakijas <mrakijas@oco.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help <scoug-help@scoug.com >
Subject:	SCOUG-Help: PUSH onto PROBLEM STACK

=====================================================
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.
=====================================================

** Reply to message from "Steven Levine" on Sun, 5 Jan
2003 23:21:49 PST8

> In <200301052144743.SM01228@host-66-81-181-174.rev.o1.com>, on 01/05/03
> at 09:41 PM, Michael Rakijas said:
>
> >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.
>
> http://pws.prserv.net/mckinnis/nicpak/index.html

Although I am happy that this site offers another version of the driver for the
D-Link card, I found the REXX utilities offered for network card installation
assistance mostly unhelpful. It essentially told me something I already knew -
that I had a Realtek 8139 based network card. I followed the directions at the
web site and also tried the directions in the readme and couldn't get it to do
much of anything including update the niccard list in MPTS. I started to read
the REXX file to try and trace the logic but lost patience since I pretty much
knew that I just needed to add the drivers provided in the realtek.zip file.

The good news is that the driver provided was different than the one I was
using and it loads! The one I was using is the same one as the one in the
machine I am trying to debug. Of course, it loads in the machine I am trying to
debug, but it got me thinking: Could this be the cause of the trouble on the
existing machine? What I would ask is this: when I do test this hypothesis,
can I simply copy over the DLKRTS.NIF and DLKRTS.OS2 (backing up the existing
ones) that represent the new driver or should I go the conventional path via
MPTS?

There is one last question. While working this problem, I tried removing and
reinstalling MPTS. I don't remember exactly what I did to effect the reinstall
but I think I tried Selective Install for Networking. That didn't work
(something like "Couldn't create response file") but I found NPCONFIG.EXE (on CD
#2?) and that worked. Now MPTS looks considerably different than it did before.
The one that was there at initial install had a kind of Java look to it with
fine pitch fonts kind of like the newer TCP/IP configuration notebook. After
reinstall, it looked more like the classic MPTS interface with its blockier
looking fonts (kind of like the original TCP/IP configuration notebook). It
looks like the same functionality exists in both and they work similarly, but I
assume the change was done for a reason. Am I missing anything and how do I
change back to the original interface?

Thanks again for all the help.

> Steven

-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".

=====================================================

Return to [ 09 | January | 2003 ]

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.