NIC for win98

jeneric.DeleteThis@iquest.net wrote:

> Hey Brodick,
>
> Any comments on my installation in the other thread?
>
> Thanks...
>
> brodick.DeleteThis@thehouse.com wrote:
> > Confirming ability to post/

I'm not able to 'reply' to that post. Maybe here.

You should be just about ready to go.
Add TCP/IP to your NIC, fill in the "Identity" applet w/ 'workgroup'
under Workgroup and after Rebooting try to ping via <Computername>.
By way of testing this ping capability I just unplugged another PC
from my network and tried it. Worked for me.

No entry will show up w/ winipcfg until you are connected via your
NIC.

Good luck or check back.
Order the DSL. You need all the pieces to put any puzzle together.
 >> Stay informed about: NIC for win98 

Thanks Brodick. Not to sound too dense, but could you give me a more
step-by-step translation of the suggestions you offer below? I used to
know how to do quite a few computer things "back in the day", but have
regressed to a simple user the last few years. I don't quite know how
to execute the stuff you mention.

Thanks!


brodick RemoveThis @thehouse.com wrote:
> jeneric RemoveThis @iquest.net wrote:
>
> > Hey Brodick,
> >
> > Any comments on my installation in the other thread?
> >
> > Thanks...
> >
> > brodick RemoveThis @thehouse.com wrote:
> > > Confirming ability to post/
>
> I'm not able to 'reply' to that post. Maybe here.
>
> You should be just about ready to go.
> Add TCP/IP to your NIC, fill in the "Identity" applet w/ 'workgroup'
> under Workgroup and after Rebooting try to ping via <Computername>.
> By way of testing this ping capability I just unplugged another PC
> from my network and tried it. Worked for me.
>
> No entry will show up w/ winipcfg until you are connected via your
> NIC.
>
> Good luck or check back.
> Order the DSL. You need all the pieces to put any puzzle together.
 >> Stay informed about: NIC for win98 

OK everybody, the update:

On the gamble that the NIC was installed correctly, we went ahead and
ordered the DSL. Today was the day that the service went live, so I
hooked up the DSL modem and started with the installation CD.

I got stopped right out of the gate when the installer told me that it
could not continue since I did not have version 5.5 or higher of IE
installed. I don't use IE at all, and never saw this requirement
mentioned on any web sites or in any documentation, so I called tech
support to see if there was a workaround.

She tried to walk me through a bunch of stuff, and came to the
conclusion finally that while the DSL modem seemed to be talking to the
DSL service, the computer didn't seem to be talking to the NIC. So I
was back to working with the NIC drivers.

I tried to refresh the driver several times, using both the "search for
best driver" method and the "list the devices" method. One method ended
up asking for my WIN98SE cd, which is loaned out at the moment, and I
had to skip several files to get through that part. I'll have that cd
back tomorrow, so I can try that again.

Through my fiddling, I seem to have made a change, because now the
D-link NIC appears in the pull-down menu in the winipcfg dialog box.
When I pick it, the following parameters are displayed:

Adapter Addy: 00-00-00-00-00-00
IP Autoconfiguration Addy: 169.254.118.185
Subnet Mask: 255.255.0.0

Now, when I restart windows, I get lots of ugly text screens before
Windows starts up, telling me that the registry or the system.ini file
is referring to specific devices that it can't find, namely:

vnetsup.vxd
vredir.vxd
dfs.vxd

Then, on the start of Windows, but before the icons appear, a Windows
Networking dialog appears, telling me that it can not locate a
msnp32.dll file, and that Microsoft Network is not available.

So, I'm still not done. Please, any and all suggestions are
appreciated.

Thanks,
Eric



jeneric.RemoveThis@iquest.net wrote:
> Thanks Brodick. Not to sound too dense, but could you give me a more
> step-by-step translation of the suggestions you offer below? I used to
> know how to do quite a few computer things "back in the day", but have
> regressed to a simple user the last few years. I don't quite know how
> to execute the stuff you mention.
>
> Thanks!
>
>
> brodick.RemoveThis@thehouse.com wrote:
> > jeneric.RemoveThis@iquest.net wrote:
> >
> > > Hey Brodick,
> > >
> > > Any comments on my installation in the other thread?
> > >
> > > Thanks...
> > >
> > > brodick.RemoveThis@thehouse.com wrote:
> > > > Confirming ability to post/
> >
> > I'm not able to 'reply' to that post. Maybe here.
> >
> > You should be just about ready to go.
> > Add TCP/IP to your NIC, fill in the "Identity" applet w/ 'workgroup'
> > under Workgroup and after Rebooting try to ping via <Computername>.
> > By way of testing this ping capability I just unplugged another PC
> > from my network and tried it. Worked for me.
> >
> > No entry will show up w/ winipcfg until you are connected via your
> > NIC.
> >
> > Good luck or check back.
> > Order the DSL. You need all the pieces to put any puzzle together.
 >> Stay informed about: NIC for win98 

Oh, I forgot one last thing: I got a couple of error codes during my
various attempts to refresh the NIC driver last night. The codes were
1F6 and 137. Any know what these mean? Thanks.
 >> Stay informed about: NIC for win98 

You need to get that Win98SE installation disk and finish the job properly.
Even if the files are already on your system, that part of the procedure
involves Registry edits, and I'm fairly certain the instructions for at
least some those are found on the Windows CD. It is typical for drivers
developers to use Windows standard files and procedures whenever possible,
instead of supplying them.

Those error codes simply indicate failure to successfully complete this or
that sub-procedure, probably because of the need for the Windows
installation files, though it *might* be you have the wrong drivers set, or
the NIC itself might even be bad. Try the Windows CD first.

--

Gary S. Terhune
MS-MVP Shell/User
http://grystmill.com/articles/cleanboot.htm
http://grystmill.com/articles/security.htm

<jeneric.DeleteThis@iquest.net> wrote in message
news:1161778440.841256.19380@f16g2000cwb.googlegroups.com...
> Oh, I forgot one last thing: I got a couple of error codes during my
> various attempts to refresh the NIC driver last night. The codes were
> 1F6 and 137. Any know what these mean? Thanks.
>
 >> Stay informed about: NIC for win98 

I got my Windows CD back last night, and tried again. Strangely, even
though I perrformed the same driver refresh tasks that I thought I was
doing the night before, I never got to a point where the wizard asked
for the Windows CD again. So, I didn't get to use it.

However, this morning I located the .cab files on the Windows CD that
contain the four files that my system now can't find. I suppose I'll
try extracting those to windows/system tonight and see if that gets me
any closer to home. Bad idea?

Thanks...


Gary S. Terhune wrote:
> You need to get that Win98SE installation disk and finish the job properly.
> Even if the files are already on your system, that part of the procedure
> involves Registry edits, and I'm fairly certain the instructions for at
> least some those are found on the Windows CD. It is typical for drivers
> developers to use Windows standard files and procedures whenever possible,
> instead of supplying them.
>
> Those error codes simply indicate failure to successfully complete this or
> that sub-procedure, probably because of the need for the Windows
> installation files, though it *might* be you have the wrong drivers set, or
> the NIC itself might even be bad. Try the Windows CD first.
 >> Stay informed about: NIC for win98 

Possibly.

Have you determined that in fact the files that are being looked for aren't
on the system? (Make sure you have "Show All Files" enabled in Folder
Options.) If that turns out to be the case, then I would want to determine
whether the files from the installation CD are the proper versions and
haven't been superceded by versions contained in Critical Updates. I do this
by using the MSKB to search on the filenames. Generally the info comes up.

--

Gary S. Terhune
MS-MVP Shell/User
http://grystmill.com/articles/cleanboot.htm
http://grystmill.com/articles/security.htm

<jeneric DeleteThis @iquest.net> wrote in message
news:1161869609.288201.114990@f16g2000cwb.googlegroups.com...
>I got my Windows CD back last night, and tried again. Strangely, even
> though I perrformed the same driver refresh tasks that I thought I was
> doing the night before, I never got to a point where the wizard asked
> for the Windows CD again. So, I didn't get to use it.
>
> However, this morning I located the .cab files on the Windows CD that
> contain the four files that my system now can't find. I suppose I'll
> try extracting those to windows/system tonight and see if that gets me
> any closer to home. Bad idea?
>
> Thanks...
>
>
> Gary S. Terhune wrote:
>> You need to get that Win98SE installation disk and finish the job
>> properly.
>> Even if the files are already on your system, that part of the procedure
>> involves Registry edits, and I'm fairly certain the instructions for at
>> least some those are found on the Windows CD. It is typical for drivers
>> developers to use Windows standard files and procedures whenever
>> possible,
>> instead of supplying them.
>>
>> Those error codes simply indicate failure to successfully complete this
>> or
>> that sub-procedure, probably because of the need for the Windows
>> installation files, though it *might* be you have the wrong drivers set,
>> or
>> the NIC itself might even be bad. Try the Windows CD first.
>
 >> Stay informed about: NIC for win98 

OK, I think I'm really close now. I extracted new copies of the four
files mentioned above, as well as msnet32.dll, and all the startup
errors are now gone.

Then I did a driver refresh on the NIC, and this time it asked for the
98SE CD, and pulled some stuff from there as well. I got a clean
install, with no error codes! I've got a "Network Neighborhood" icon on
my desktop now, and the NIC is listed as an installed network component
under Control Panel -> Network -> Configuration.

I've got good driver information at Device Manager, and the NIC still
appears in the winipcfg pull-down menu. I also have two green lights on
the NIC card, and all the proper lights on the DSL modem.

So, what's left to do to get data flying through this thing when I pull
up a web browser?



Gary S. Terhune wrote:
> Possibly.
>
> Have you determined that in fact the files that are being looked for aren't
> on the system? (Make sure you have "Show All Files" enabled in Folder
> Options.) If that turns out to be the case, then I would want to determine
> whether the files from the installation CD are the proper versions and
> haven't been superceded by versions contained in Critical Updates. I do this
> by using the MSKB to search on the filenames. Generally the info comes up.
 >> Stay informed about: NIC for win98 

You've already done "Release All" followed by "Renew All" in winipcfg? What
are the results (IP address, etc.)?

--

Gary S. Terhune
MS-MVP Shell/User
http://grystmill.com/articles/cleanboot.htm
http://grystmill.com/articles/security.htm

<jeneric.RemoveThis@iquest.net> wrote in message
news:1161916900.207161.320340@e3g2000cwe.googlegroups.com...
> OK, I think I'm really close now. I extracted new copies of the four
> files mentioned above, as well as msnet32.dll, and all the startup
> errors are now gone.
>
> Then I did a driver refresh on the NIC, and this time it asked for the
> 98SE CD, and pulled some stuff from there as well. I got a clean
> install, with no error codes! I've got a "Network Neighborhood" icon on
> my desktop now, and the NIC is listed as an installed network component
> under Control Panel -> Network -> Configuration.
>
> I've got good driver information at Device Manager, and the NIC still
> appears in the winipcfg pull-down menu. I also have two green lights on
> the NIC card, and all the proper lights on the DSL modem.
>
> So, what's left to do to get data flying through this thing when I pull
> up a web browser?
>
>
>
> Gary S. Terhune wrote:
>> Possibly.
>>
>> Have you determined that in fact the files that are being looked for
>> aren't
>> on the system? (Make sure you have "Show All Files" enabled in Folder
>> Options.) If that turns out to be the case, then I would want to
>> determine
>> whether the files from the installation CD are the proper versions and
>> haven't been superceded by versions contained in Critical Updates. I do
>> this
>> by using the MSKB to search on the filenames. Generally the info comes
>> up.
>
 >> Stay informed about: NIC for win98 

No, I hadn't done that. This is my first time around the block with
these devices on my home machine, and I'm very much groping around in
the dark.

I would appear that I'm not out of the woods yet. "Release All" was
fine, but on clicking "Revew All", the machine thought for some time
(with the hourglass), and then returned an IP Configuration box that
read ' Error. DHCP Server Unavailable: Renewing Adapter "" '

The values for the NIC when I first pull up winipcfg are:

Adapter Addy: 00-15-E9-F9-B8-A8
IP Autoconfiguration Addy: 169.254.52.163
Subnet Mask: 255.255.0.0

These do not change after I click out of the IP Configuration error
message.

Also, an addendum from last night: Windows now does not Restart or Shut
Down correctly. It goes all the way to the "Windows in shutting down"
screen, and then hangs. I can hard reset the machine with the "reset"
button on the case, but I can't power down the computer at all (well, I
assume pulling the power cord would do it).

Also, an observation: When I use my regular dial-up modem to access my
ISP while the DSL modem is turned on, it dials into and logs on to my
ISP service just fine. But when I pull up a browser, it can't find any
URLs, like when a lookup table is down. When I turn off the DSL modem,
then refresh the browser, it works fine. I don't have to re-dial-in to
the ISP to get it to work.

Anyway, thanks very much for the continued suggestions. I'll start
Googling for DHCP and Windows shut-down problems now. [sigh]



Gary S. Terhune wrote:
> You've already done "Release All" followed by "Renew All" in winipcfg? What
> are the results (IP address, etc.)?
 >> Stay informed about: NIC for win98 

What ISP and what brand/model modem do you have? The info would help greatly
in figuring out what's up.

Note that even if there's only one computer attached, you'd be *very* wise
to add a router to the mix in order to include NAT. NAT = Network Address
Translation. Using NAT, your machine would have a local network address
instead of the one assigned by your ISP. Makes it much more difficult for
unwanted outside entities to get to your machine. Also tends to make setup
easier, since the router includes its own DHCP server that you can get to.
Much easier t-shooting than trying to deal directly with your ISP's DHCP.

In any case, the fact that your NIC can't seem to update its address from
the DHCP server is cause for concern. All I can think of at the moment is to
completely remove *everything* from the Network applet and restart the
system. The NIC should prompt a hardware installation routine, and with any
luck it will complete the task properly this time. You will, of course, need
to reinstall the Dial-up Adapter, too, in the Network applet. Click
Add>Adapter. Everything else the DUN needs (TCP/IP, Client) will already
have been installed by the NIC installation.

Oh, and the last part about the DUN now not working for IE now... In
Internet Options, check the Connections tab. Try "Dial whenever a network
connection is not present" first, and if that doesn't do it, try "Always
dial my default connection." If that still doesn't work, post back.

--

Gary S. Terhune
MS-MVP Shell/User
http://grystmill.com/articles/cleanboot.htm
http://grystmill.com/articles/security.htm


<jeneric RemoveThis @iquest.net> wrote in message
news:1161943532.366158.128810@k70g2000cwa.googlegroups.com...
> No, I hadn't done that. This is my first time around the block with
> these devices on my home machine, and I'm very much groping around in
> the dark.
>
> I would appear that I'm not out of the woods yet. "Release All" was
> fine, but on clicking "Revew All", the machine thought for some time
> (with the hourglass), and then returned an IP Configuration box that
> read ' Error. DHCP Server Unavailable: Renewing Adapter "" '
>
> The values for the NIC when I first pull up winipcfg are:
>
> Adapter Addy: 00-15-E9-F9-B8-A8
> IP Autoconfiguration Addy: 169.254.52.163
> Subnet Mask: 255.255.0.0
>
> These do not change after I click out of the IP Configuration error
> message.
>
> Also, an addendum from last night: Windows now does not Restart or Shut
> Down correctly. It goes all the way to the "Windows in shutting down"
> screen, and then hangs. I can hard reset the machine with the "reset"
> button on the case, but I can't power down the computer at all (well, I
> assume pulling the power cord would do it).
>
> Also, an observation: When I use my regular dial-up modem to access my
> ISP while the DSL modem is turned on, it dials into and logs on to my
> ISP service just fine. But when I pull up a browser, it can't find any
> URLs, like when a lookup table is down. When I turn off the DSL modem,
> then refresh the browser, it works fine. I don't have to re-dial-in to
> the ISP to get it to work.
>
> Anyway, thanks very much for the continued suggestions. I'll start
> Googling for DHCP and Windows shut-down problems now. [sigh]
>
>
>
> Gary S. Terhune wrote:
>> You've already done "Release All" followed by "Renew All" in winipcfg?
>> What
>> are the results (IP address, etc.)?
>
 >> Stay informed about: NIC for win98 

Thanks very much for all the help and suggestions, folks. In the end, I
updgraded that machine to WIN XP, and everything plays as it should
now. Thanks again.
 >> Stay informed about: NIC for win98 

Thanks very much for all the help and suggestions, folks. In the end, I
updgraded that machine to WIN XP, and everything plays as it should
now. Thanks again.
 >> Stay informed about: NIC for win98