3Com Driver for Win3.11

[sp1d3rb1t3]

Hello all,
I am trying to install a 3Com EtherLink III 3c509B-C into a Soyo SY-7VBA133U Motherboard using Win 3.11.  I have done a clean install of DOS 6.22 and Windows 3.11, but I am unable to install my NIC's drivers.  For some reason when I attempt to execute 3c5x9cfg.exe NIC configuration utility from DOS, I get this error:  Run-Time Error r6003 - integer divide by 0.  I have ran the pnpdsabl from the driver disk, disabled virus check and pnp os support in the BIOS, as well as set all IRQ and DMA settings to legacy ISA.  If anyone has any knowledge of this old stuff, please help!   

[recovering space - attachment deleted by admin]

[Aegis]

Are there options to choose which DMA channel and IRQ you want to use?

Are you sure you want to disable plug and play support?  It's been a long time since I've set IRQ's and DMA's -- I think you'll have to do it manually.

Welcome to the Forum!

[sp1d3rb1t3]

Thanks!  No, I can't choose which channels to use, I can only switch from PnP to legacy ISA (which is what the NIC is).  I'm pretty sure I have to disable PnP; I don't think Win 3.11 supports PnP.  But I've tried installing the driver both ways - no luck

[Aegis]

Oh, yes, that's right ... Win 3.11 -- no plug and play, as I remember.

[patio]

DOS Drivers

Unsupported Drivers
Any driver listed below is for your convienence ONLY
3Com does not provide Technical Support for these drivers. 
File Name: dosdrver.exe Size: 56865 Date: 11/10/00
Dos drivers for the faster Pentium machines for where you might experience divide overflow errors.

4th one on the page.....i believe this is the error you are getting so try this one.
You will still have to set up the IRQ's for Win 3.11 to get it to work but it should.

[Spoiler]

Ok....many moons ago 3Com used a tool you had to down load and run from DOS. This tool would look though the ISA slots and find the card and let you pick a IRQ. After you programed the Eprom on the card you would boot the machine in Win3.11 and load the drivers.

Normally you would put the tool onto a floppy and boot the machine off the floppy to program the card.

I don't know where to get the eprom loader tool. 3Com may still have it on there site.

http://www.3com.com/products/en_US/result.jsp?selected=all&sort=effdt&order=desc&sku=3C509B-COMBO

If I remember right the defualt IRQ was set to 5 on the 3Com stuff.....

[patio]

A sharper memory than me, Spoiler.....Kudos.

[Spoiler]

Thanks! Patio...

(takes a bow) 

[sp1d3rb1t3]

Thank you for the input gentlemen,
I will try both these suggestions, hopefully with success.  I'll keep you posted!
Curt

[sp1d3rb1t3]

In case anyone is curious as to why I am playing with this antiquated stuff, I am an ATC maintainer with a sad equipment modernization program.  Our voice recorder cpu went down and unfortunately the FAA has strick guidlines as to which hardware/software combinations are allowed, and the voice logger version I have only allows for Win 3.11 at the workstation.  I am attempting to use the old CPU from our voice switch (actually fairly modern) as a replacement, it's just very stubborn.  Anyway, I really appreciate you all for taking the time to help me.
Curt

[sp1d3rb1t3]

Spoiler:
I think the program you are referring to is 3c5x9cfg.exe, which is the configuration and diagnostic program for the NIC.  If so, I am unable to get to this step, because I cannot even install the packet drivers (I'm guessing because the Mobo isn't recognizing the NIC)

[Spoiler]

I would try another NIC myself but the program I was talking about was a Eprom programer. You had to make a DOS boot disk and at the A: prompt you typed the name of the program and it was almost like flashing the BIOS but it was for the NIC.

Let me look around and see if I can find it.

For now I know that the old 3Com stuff used 5 and 7 for the IRQs. I would try to manually set it to each of these in windows and reboot to see it it kicks in.

[sp1d3rb1t3]

Thanks Spoiler, I will try that.  Where in Win 3.11 can I set the IRQs?  I think the Mobo isn't even recognizing/communicating the NIC, which I can only assume is why I cannot install the packet drivers.