I see a coupla guys already handled that (thanks!).
Actually they did not. I'd like to hear your specific examples of 'conflicting messages'.
It would also help if your sales reps would become acquainted with what they were selling - maybe have them use (and troubleshoot) a few e220s themselves.
Agree 100%. Training is always an issue.
Little patronising for a myBB rep, hmm? We obviously haven't met, so I'll disregard that comment.
So you make a statement without substantiating it and when I ask you to do so, I'm being patronising? Nope, rather I need to understand why you make such statements (like you did in this thread), so I can help you understand whatever it is you don't.
On this point, I've seen this often here on myBB. Forumites are so used to be able to come here and post whatever they like and then they're taken aback when actually asked to substantiate it. For example here you made a few distinct statements without actually providing any facts to back them up. And when asked to provide the underlying facts, your best response is that the question is patronising?
VMC is a convenience interface, nothing more. I've used the same modem across three operating systems with no software installations beyond the drivers on the modem itself (and that was only on Windows) - so the problem can't really lie with the software, can it?
VMC is an interface. Just like any other dash. What problem with the software?
If you code something that breaks when you upgrade something else, then there's a flaw in your original design. I'm sure you must realise by now that the average PC user does not actively seek updates for software, and why should they need to, when it's a dialup modem?
Had you done the job right on the first version of VMC, chances are you wouldn't have had to upgrade past that, not for 10 years at least. Future-proof, as we developers call it.
I've long realised that only people on this forum write perfect software that have all the features ever needed in version 1.0, support all upcoming hardware, even that not designed yet, and have zero bugs.
The rest of the world unfortunately write software that sometimes have bugs and needs upgrades to support new features. All you perfect *developers* should really go and sort out Microsoft, Linux, IBM, Sun, Oracle, Cisco and all the other big boys who keep on releasing software that's not perfect. I'm sure they'll pay handsomely for someone who can "future-proof" their software for 10 years.
This might not happen to you, but I've had instances where the signal just completely dies. Towers go offline without warning, they drop the 3G signal for no apparent reason, and there are times (used to be at least once every 36 hours) where international sites become inaccessible for hours at a time. I've even had the internet become completely unavailable despite the modem reporting it being connected - there is no possible way the problem here lay on my side.
I'd really suggest you read up a bit about how cellular communications work. Specifically UMTS. It's a complex environment and prone to problems. It's just the nature of the beast.
Won't you pass me some reports where showing where international sites become inaccessible for hours, every 36 hours. I'd like to pass them to the engineering guys as this does not at all relate to the management reports I get every day.
Then there is the speed. Granted, we're talking wireless (and thus fluctuating), but the speed sometimes drops to sub-gprs levels, even though I'm clearly on a 3G line. I've also never achieved the maximum throughput Vodacom advertises. I'm lucky to get 1mbps for about 3 seconds a week - and I live within 3km of a 3G-enabled tower.
Then the latency. Don't get me started on the latency.
See above on learning about UMTS. Will really help you. For example; 3Km is way outside the spec. and probably explains why you see cell-breathing.
Won't you point me to the throughput Vodacom advertises? I've not seen these ads. Where did you see them, on TV? In the press?
Then there are the times when it just fails to establish a connection. The modem works, the software's there, hell, it gets to the "Registering your computer on the network" part, but just craps out from there with arcane error codes and no explanations.
As you said yourself, the OS only sees the 3G device as a modem. So those 'arcane error codes without explanations' are coming from your OS. You should take it up with the OS authors.
Your 155 helpdesk told me to reset. Guess how much that helped?
My 3G modem never moved from its spot, so I'd expect the quality of service to be constant at least 80% of the time, but every day was a hassle.
So yes, in summary, I'd say there's a fair amount of work that needs to happen with your infrastructure. Also, get your developers to code something that doesn't crash every hour (memory overflow, if I recall), and ship it embedded on the modem.
Read a bit on cell technology, might explain a few things. Or ask, if you're not sure.
So, in summary, please learn a bit about cellular comms and don't be shy to ask. Myself (and many others here) are willing to help as much as we can for you to understand the technology. And the fact that unlike your coding, it's just not perfect.
In other words, if you're not sure, please ask. But please don't make statements you don't have any underlying facts to back it up. And if you do have facts to back it up, please share it with us. We can then use it to make the network better for every one.
but please don't post unsubstantiated views or opinions as facts. It's an honest request, BTW. Not trying to be 'patronising'.
BTW, I was always under the impression the dash is embedded in the modem?
it's slow. it's ugly. it's unstable and it takes forever to load for such a basic frontend.