2000Pro / 2000Server dualprocessor seem screw up winmodems
This is a discussion about 2000Pro / 2000Server dualprocessor seem screw up winmodems in the Everything New Technology category; Hi all, I'm new here. I just have come to the conclusion that winmodems like SM56 or Intel 536EP cannot run on a dualprocessor system in a W2k environment. I'm facing this trouble for at least two months with no positive result.
Hi all, I'm new here.
I just have come to the conclusion that winmodems like SM56 or Intel 536EP cannot run on a dualprocessor system in a W2k environment. I'm facing this trouble for at least two months with no positive result. I've found weak signals on the net about like behaviour, but no cure. This is the issue: if you try to connect using such a modem, even from a clean new OS installation, your connection fails or freezes in a couple of minutes. you can well tamper with connection speed, protocols, data compression: the only result is to delay the fault. I tested it in five dualprocessor computers equipped with SuperMicro and Asus Xeon boards with the same result. Opposedly all works plain on single processor P4 boards. I suppose it's a w2k bug, as it sounds very unlikey to me that two distinct brand modems running from two distinct drivers on two distinct moments, each being the one installed on test, can have an identical bug. Please, does anyone know a remedy?
Best regards
I just have come to the conclusion that winmodems like SM56 or Intel 536EP cannot run on a dualprocessor system in a W2k environment. I'm facing this trouble for at least two months with no positive result. I've found weak signals on the net about like behaviour, but no cure. This is the issue: if you try to connect using such a modem, even from a clean new OS installation, your connection fails or freezes in a couple of minutes. you can well tamper with connection speed, protocols, data compression: the only result is to delay the fault. I tested it in five dualprocessor computers equipped with SuperMicro and Asus Xeon boards with the same result. Opposedly all works plain on single processor P4 boards. I suppose it's a w2k bug, as it sounds very unlikey to me that two distinct brand modems running from two distinct drivers on two distinct moments, each being the one installed on test, can have an identical bug. Please, does anyone know a remedy?
Best regards
Participate in our website and join the conversation
This subject has been archived. New comments and votes cannot be submitted.
Oct 17
Oct 21
0
1 minute
Responses to this topic
Use an external modem rather than winmodems.
