VOGONS


First post, by keenmaster486

User metadata
Rank l33t
Rank
l33t

I have this Socket 5 machine, and I'm trying to get network cards to work in it.

So far I've tried a D-Link card and a 3C905TX. Both of the cards' drivers claim that the cards are "not installed" or "not present", but I know for a fact that yes, they are installed. I checked the BIOS PCI settings, but the only option there that was of any consequence was the triggering (set to level).

I can enter the 3Com card's BIOS after the machine POSTs, so I know it's working.

I also ran two hardware info programs, and they both could see the card and told me exactly what the bus, dev, irq, etc. settings were (thus I know that the card is indeed present and working). I set those manually in NET.CFG, but still no dice.

What am I doing wrong? I could post screenshots of the BIOS and the driver output if needed.

World's foremost 486 enjoyer.

Reply 3 of 15, by keenmaster486

User metadata
Rank l33t
Rank
l33t
h-a-l-9000 wrote:

Maybe not the correct drivers?

Well, I don't think so... For the Dlink card I know for a fact the drivers are correct; for the 3com card I'm using the Etherdisk for 3C90x cards; maybe that's wrong.

mrau wrote:

chipset drivers? this is early pci, it may be quirky

Chipset drivers for DOS? Would I find those on vogonsdrivers if I found out what my chipset is? (Sorry, forgot to mention this is in pure DOS)

World's foremost 486 enjoyer.

Reply 5 of 15, by keenmaster486

User metadata
Rank l33t
Rank
l33t

OK, now I've given up on PCI and have moved to using a 3C509 ISA NIC. I load LSL, 3C5X9(the driver), and IPXODI, which all load perfectly with no errors, but when I connect it to a known working IPX-networked machine and try to start NetKeen, it acts as if the cable is unplugged. I tried a different, known working, cable but it still doesn't work. Any thoughts? I will look for that network guide, maybe it will have some info that will help me.

World's foremost 486 enjoyer.

Reply 6 of 15, by jheronimus

User metadata
Rank Oldbie
Rank
Oldbie
mrau wrote:

sry, i was kinda sure we were talking windows...
you did try the dos network guide somewhere here on these forums? i really dont remember what the title was...

Just a shot in the dark. A while ago I tried to get a 3COM card to work under 6.22. It modified the autoexec (or maybe config.sys) and worked, but then I realised how much of a hassle getting TCP up would be, and decided to install Windows 95 on that machine. Then I installed the Win drivers, but it also gave me the yellow exclamation mark error. Turns out, Windows copies all the configuration from DOS 6.22 if you're doing an upgrade. And DOS initialization of the card conflicted with the drivers. Once I deleted those lines from the config files, everything worked smoothly.

Could that be your issue?

MR BIOS catalog
Unicore catalog

Reply 7 of 15, by keenmaster486

User metadata
Rank l33t
Rank
l33t

Well, this 3C509 card only modifies the AUTOEXEC.BAT file, not CONFIG.SYS. I tried letting those run at startup and they don't work. So I commented them out, and ran the commands manually the same way I always do (LSL, driver, IPXODI) and it still doesn't work.

I've also run the diagnostic program and all the tests it runs turn out OK.

World's foremost 486 enjoyer.

Reply 8 of 15, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author

You have to make sure both sides use the same FRAME format - IIRC this was done through the net.cfg.

    File Name:          NET.CFG
----------
Sample of configuration file:
-----------------------------

...
LINK DRIVER FETODI
FRAME ETHERNET_802.2

Link driver must match your file. The choices were ETHERNET_802.2 and ETHERNET_802.3.

1+1=10

Reply 10 of 15, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Did you select the correct interface in the config program? Some of those cards have AUI, BNC and TP, you have to choose the correct one. Do you connect through a hub or directly? Are there LEDs that indicate link activity? How is the other machine known working?

1+1=10

Reply 11 of 15, by keenmaster486

User metadata
Rank l33t
Rank
l33t
h-a-l-9000 wrote:

Did you select the correct interface in the config program? Some of those cards have AUI, BNC and TP, you have to choose the correct one.

I tried to do that and it (the config program) gave me an angry window stating that there is only one option (TP).

h-a-l-9000 wrote:

Do you connect through a hub or directly?

Directly. I've tried two different cables.

h-a-l-9000 wrote:

Are there LEDs that indicate link activity?

Haven't looked at those, I'll try that next.

h-a-l-9000 wrote:

How is the other machine known working?

I've played NetKeen, Descent, and Doom between it and a modern computer running DOSBox Megabuild 6.

World's foremost 486 enjoyer.

Reply 12 of 15, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author

> Directly. I've tried two different cables.

That's a problem. Not all cards are capable of switching into crossover mode. You either need to use a hub or a https://en.wikipedia.org/wiki/Ethernet_crossover_cable .

1+1=10

Reply 13 of 15, by keenmaster486

User metadata
Rank l33t
Rank
l33t

Ooh, I have a crossover cable. I'll try that next, thanks!
Edit: wait a minute, would using a hub or a router work? I have a plethera of modern hubs and routers; but I'm not so sure I can find my crossover cable.

World's foremost 486 enjoyer.

Reply 14 of 15, by Jorpho

User metadata
Rank l33t++
Rank
l33t++
keenmaster486 wrote:

Edit: wait a minute, would using a hub or a router work?

Probably, but then you'd have to start worrying about whether your hub or router is properly configured.

Reply 15 of 15, by keenmaster486

User metadata
Rank l33t
Rank
l33t

Hey, I hooked up a hub and now it works perfectly! Thanks a million, I don't think I would have realized that on my own 😀

World's foremost 486 enjoyer.