3Com Isdn Pro Ta Drivers

When using this ISDN modem, I contacted 3Com Tech Support about this very problem. Here was their response:'Thank you for contacting 3COM Online Support. I understand that you are having problems installing the ISDN TA on Windows 2000. The Windows 2000 drivers for the TA come with Windows 2000. The INF file name is mdm3cusb.inf and should be located in the Winnt folder where Windowswas installed. The file mdm3cusb.in which is a compressed file should be located in the I386 folder on the Windows 2000 CD.'

Remember, the 3.2 Control Center software (e.g.Win98) does not work with Win2k. Only a USB (connection & W2K drivers) will result in a full bandwidth 128K connection. (Serial gets a max of 90K)The process requires a manual install of the USB drivers, not plug & play. I found this thread, I saved it to hard drive back on 12-29-00 and finally found it.

I hope it helps. This was posted by another user.'

USR Pro TA and Windows 2000After fiddling with the Pro TA under W2K, I think I have figured out thequirks of the USB connection, hope this might help someone:- Do NOT install the 3Com software or INF files. Instead, plug the Pro TAand let it come up as an 'unknown device' in the device manager. Thenmanually upgrade the driver to the MS-supplied one (under 3Com) called '3ComU.S. Robotics USB ISDN TA'. Careful, do NOT select '3Com U.S.

Robotics USBISDN.Pro. TA', that's the Euro-ISDN version (that driver won't let youselect National ISDN for a switch type).- Once installed, fill in your SPIDs under the 'ISDN' tab on modemproperties. Make sure the SPIDs appear in the same order the TA hasconfigured itself for. The driver seems to re-program the TA the first timeit talks to it, if the SPIDs in the software are wrong, it won't work, evenif you have manually programmed the TA using AT commands.- Do NOT unplug the TA while the PC is running.

For some reason, anyestablished Dialup networking entries will revert to a maximum baud rate of115K (the 230K item will disappear from the list). The only way to fix it,as far as I know, is to delete and re-create the dialup networking entries.- Occasionaly, the dialup will fail with the 'Error in connecting device'message. The only cure seems to be to reboot. Annoying, but infrequent.USR says the official W2K driver should be available by the end of thisweek, hopefuly some of these quirks will go away.Martin.To be honest, I am not entirely convinced the baud rate means anything forthe USB connection, I have been able to download an uncompressed 8 meg PDFfile (the Pro TA manual, ironically) at 50-55KB/sec through an ISP (i.e.using hardware compression only). 230K should have gotten me a max ofapprox 23K, so I think the MS-supplied USB/serial driver (usbser.sys) movesthe data at the full 1.5 or 12MB all the time, regardless of the softwaresettings under 'Modems'. I had the same ISDN modem, and all I had to do was plug the USB cable in and it automatically installed the drivers and worked.

3com Isdn Pro Ta Drivers.com 7

The drivers that come with it aren't meant for win2k, and 3Com's web site is useless.I could rant for days about how much I loathed that setup though. If you unplug the USB cable (or just the modem's power), Win2k will lose the configurations settings for all the connections associated with it. Win2k also had a nasty habit of not letting me dial out from time to time, requiring a complete system reboot.

Dialing was something I had to do often, since everything was 'on the clock!' The whole 'auto-decide-between 64 and 128k' thing didn't work at all, so I had to create two connection icons.

3com Isdn Pro Ta Drivers.com For Sale

I ended up using 64 most of the time because I didn't want to waste those precious minutes.I have a cablemodem now, I'm still contemplating taking this thing up to the local firing range, and basking in the enjoyment of watching it be blown up to tiny bits and peices.