NIC for win98

Confirming ability to post/

Hey Brodick,

Any comments on my installation in the other thread?

Thanks...


(E-Mail Removed) wrote:
> Confirming ability to post/

(E-Mail Removed) wrote:

> Hey Brodick,
>
> Any comments on my installation in the other thread?
>
> Thanks...
>
> (E-Mail Removed) 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.

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!


(E-Mail Removed) wrote:
> (E-Mail Removed) wrote:
>
> > Hey Brodick,
> >
> > Any comments on my installation in the other thread?
> >
> > Thanks...
> >
> > (E-Mail Removed) 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.

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



(E-Mail Removed) 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!
>
>
> (E-Mail Removed) wrote:
> > (E-Mail Removed) wrote:
> >
> > > Hey Brodick,
> > >
> > > Any comments on my installation in the other thread?
> > >
> > > Thanks...
> > >
> > > (E-Mail Removed) 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.

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.

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

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.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.
>

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.

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

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.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.
>

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.