|
|
|
|
|
by ryandrake
940 days ago
|
|
I also briefly worked in Student IT support junior year of my university and "Winmodem" sent similar chills down my spine. An idea that never should have happened! You can boil a lot of tech changes down to either A: Let's take this problem that has been solved in hardware and move it to software! and B: Let's take this problem that has been implemented in software and bake it into hardware. Somehow, A is always a train wreck, and B usually pushes the abstraction stack upward and moves the industry forward. Yet, we as an industry keep trying A and expecting good results. |
|
In our case, we technically did not support your hardware - you had to show up with a working modem. But in practice, if you want to retain your customers, you need to support their hardware. At one point we used to have CDs full of known good drivers for all of the common softmodems that we'd send out if we couldn't figure out a configuration workaround. Even then, I had a handful of discussions with folks where I basically told them that their thing wasn't going to work - they either needed a different modem, of which we'd recommend a few that we knew some stores carried, or they needed to find a way to cut down their line noise. I'm one of those types that takes it a little bit personally when I spend a bunch of time on something and still can't solve it, so that always sucked. Maybe you could say that wasn't strictly the modem's fault, but even the cheapest hardware modems had better tolerance for line noise.