VOGONS

Windows 98 Networking - Installing a NIC

Topic actions

First post, by PSYDUCK

Posted on 
User metadata
Rank Newbie
Rank
Newbie

I Cut my teeth on Windows 95/98 when I started fiddling with computers when I was 12 but I didn't touch networking until XP - for the fun of it I want to add a NIC to one of my retro machines to use a locally hosted FTP Server and to mess around with a few old BBS's. I've setup a new VLAN on my Firewall and it's basically ready to go - except now I've gotta get Windows 98 to play nice with a NIC.

I've dug through my shed, found a suitable NIC and Installed it - however I'm just getting the below error:

The attachment Screenshot 2023-09-24 102311.png is no longer available

IIRC 1F6 (The error code) is the Range of memory it wants to use however I've found my IDE Controller is using that range - this is my theory for why I'm getting the error message:

The attachment 2.png is no longer available

To confirm I've tried a few driver versions with no dice. Any tips on getting this to work or should I try another NIC?

Reply 1 of 7, by darry

Posted on 
User metadata
Rank l33t++
Rank
l33t++

Try unchecking "use automatic setting" and use a different a preset that uses a different memory range.

Otherwise, you might be able to change the default range using the card's configuration utility (usually a DOS executable bundled with the drivers).

Reply 3 of 7, by PSYDUCK

Posted on 
User metadata
Rank Newbie
Rank
Newbie

Disabling of 'use automatic setting' and using a non-conflicting range allowed me to enable the NIC, Windows was saying it was working OK but Could not get any Driver details - I forced updated the driver and rebooted and now I am getting a message on the below popup:

The attachment 4.png is no longer available

Checking with winipcfg and it's not too happy.

The attachment 5.png is no longer available

I checked the stack to make sure TCP/IP is installed

The attachment 6.png is no longer available

Lastly, Can't ping 127.0.0.1:

The attachment 7.png is no longer available

I uninstalled all Communications components, restarted, reinstalled, restarted same problem. Last ditch effort Windows reinstall, the drivers I was using did not include an application to modify the memory range and at this stage, I only have transport of files via Floppy disk as my ext cd burner has gone walkabout. If the windows reinstall does not work, then I'll find a cd burner to use the package giantclam linked.

I Appreciate everyones help and I'll report back.

Reply 4 of 7, by PSYDUCK

Posted on 
User metadata
Rank Newbie
Rank
Newbie

Reinstall accomplished nothing - burnt basically every driver pack I could find and went through them on by one, cannot find any reference to a tool that can change the working memory range. Also found an Intel Install that basically says to disable PnP and Manually configure, however my BIOS is fairly basic - whilst I can disable PnP there isn't too much I can do about manually configuring the card.

The attachment Screenshot 2023-09-26 183728.png is no longer available

Reply 5 of 7, by giantclam

Posted on 
User metadata
Rank Member
Rank
Member

What did PROset.exe report?

Reply 6 of 7, by PSYDUCK

Posted on 
User metadata
Rank Newbie
Rank
Newbie

The only PROSet application I found was a Windows application for reporting on the state of the NIC - It never actually detected it. I did find a Diag DOS Executable which DID detect the NIC but said it could not be loaded due to a memory conflict.

Reply 7 of 7, by darry

Posted on 
User metadata
Rank l33t++
Rank
l33t++

Maybe try disabling what what you suspect is the conflicting hardware and remove/disabling as much of the hw as posdible. Thentry running the proset util from a bootable floppy to set the range you want . Then reenable everything.

Go to top of page Go to top of page
Back to Software
Close window
Close window