Gareth Jones

To cut a long story short, I’ve sent the D-Link 655 that I got just over a week ago back to the retailer which, coincidentally, cost me £13.85 because I had to send it back to bloody France! Nope, I seriously won’t be buying from PIXmania again.

The reason for sending the unit back is simple; though actually diagnosing the problem was far from it. Having hooked the D-Link up to my Netgear DGN2000 which was now running in modem-only mode, my internet download speed dropped from 20mbit to 10mbit. Because it wasn’t actually the D-Link that was dialling up, this unit wouldn’t give me any connection details other than “connected” (which was far from helpful) so I had to disconnect that and connect to the Netgear directly in order to access its webmin and check the details on there. The Netgear reported a 20mbit connection, and yet whenever I downloaded anything on any of the computers, I was getting 250kb/sec max.

It turns out that the D-Link was establishing a mere 10mbit connection to the Netgear (the D-Link being a gigabit unit and the Netgear being a 100mbit unit), so no matter how fast my internet connection was I was only ever going to get 10mbit from it. I set the D-Link to force a 100mb connection and when that didn’t work I tried the gigabit option, which also didn’t do anything. Hardly performance that you’d call “Xtreme”, is it, D-Link? There was no such option on the Netgear. I disabled QoS, packet shaping, UPnP and everything else that was there to be disabled but no, nothing made any difference so I logged into PIXmania, found my order and requested an RMA number. I wrapped the D-Link back up in its French SKU box and prepared it for posting. I then did what I now wish I had done at the beginning and ordered a gigabit switch, which I’d use to connect everything to the router and get the best of both worlds – a gigabit internal network and a 20mbit internet connection.

I connected everything back up to the Netgear for now and put that back in modem/router mode, only to find that this was now playing up and refusing to issue a DHCP IP address to one of my computers. Also, one of its ports refused to work with any device. I’d had another Netgear router do this to me 18 months ago – the DG834G – which was what I’d replaced with the DGN2000. Really angry at this point, I binned the Netgear, vowed never to buy any of their crap again and hooked up the old Thompson router that we got from O2 a year ago. Everything connected to that without any problems.

The gigabit switch arrived a few days ago and so far everything with the internal network is fine, though there is an issue with O2′s router which I’m hoping a replacement router from O2 will fix, but I’ll write about this separately as it appears that a number of others are experiencing the same thing.

Hassle, hassle and yet more hassle!

After my banning from the MDM support forums for pointing out that Zinc V3 is a load of rubbish, MDM pruned the forums of multiple posts that had anything negative to say about the software and closed down the bug reporting page:

We have currently suspended new Bug Submissions whilst we compile and validate existing entries. Thank you for your patience.

Evidently, the only way MDM is able to reduce their bug count is to prevent people from being able to report them in the first place. Likewise, the only way they’re able to have a forum of satisfied customers is to delete every negative post as it comes in. Let this serve as a warning to anyone thinking about buying anything from MDM.

On the positive side, the entire conversation was saved before it was deleted by Gambini and is provided here for posterity: Page 1, Page 2.

As you can see, Gambini seems to be of the opinion that if a large organisation has been sucked in by his false advertising, the ridiculous bug level of his software is irrelevant. He also seems to believe that unless you have a multi-million selling product that your opinion on software that you’ve paid good money for is worthless. Furthermore, should you dare to ask questions about this, you will be banned.

Is this is a company that you want to support?

I’ve just managed to get myself banned from the MDM forums for stating that their Zinc V3 software is a load of rubbish. Released about two years ago, the software currently has a whopping 70 open bugs – many of which date back to the beginning of 2008!

I first started using Zinc around 6 years ago, back when it was called Flash Studio Pro (1.9.x). The software was pretty flaky but was good enough for the small projects that I was working on at the time. Soon after though, support for the software vanished as MDM released a new product called Zinc V2 which provided a new GUI and a load of new commands. I upgraded like most of MDM’s users, only to find that Zinc V2 had just as many bugs as FSP and that MDM was just as slow to fix them.

Some time later, support for V2 again dropped off the face of the earth as the company excitedly announced the release of Zinc V3 – a cross-platform application that was built from the ground up, no less. MDM made lots of noise about it being the most stable version of the software yet, thoroughly tested and that it would only be released when it was absolutely bomb-proof thanks to an extensive beta phase. Another thing that I remember from this time was disgruntled customers who had just bought Zinc V2 being told that their product was no longer supported and that if they wanted to move to V3, they’d have to pay an upgrade charge. The V2 forums were also locked, making it difficult for people who didn’t want to “upgrade” to V3 discuss and resolve issues collaboratively. So much for looking after your customers.

Anyway, fast forward two years and here we are. The bugs that are to be fixed in the next version (the 17th for those keeping count) include fixes for such basic functionality as being able to export JPEGs, read and write to the Windows registry, resetting event handlers, broken AS3 support, broken MAC mask support and a load of other things that should have been resolved before launch let alone before the software’s 2nd birthday. There are even bugs on there that were once fixed but have since been re-introduced in later “updates” thanks to the poor level of testing they do over there. A full list of the open bugs is helpfully available on their website here.

I never upgraded to V3 myself. Having seen first-hand how painful it was to come up with workarounds to V2′s bugs after jumping from V1, I decided to sit out the next ride and wait for the inevitable bugs and other issues to be resolved before taking the plunge – yep, despite MDM’s bullish claims of QA this time around. I also didn’t see any major benefits in V3 seeing as I hardly ever need to develop for Macs or Linux-based PCs (just as well as the support for these two OSs is patchy and inconsistent), so I was in fact more than happy to watch from the side-lines until the dust settled. The problem was that the dust never did settle and two years on V3 users are still having to put up with an insane bug count. V2 was bad sometimes, but nowhere near as bad as V3.

Despite not having taken the plunge for V3 myself, I would still visit the forums occasionally, sometimes helping out a newbie or two with some Flash/Zinc related questions and sometimes just watching in amazement as the bug reports continued to come in thick and fast – bug reports for standard functions that showed quite clearly that were was next to no testing going on at MDM between releases. As the bug count continued to rise and MDM continued to clumsily release hit-and-miss updates, I thanked my lucky stars for not having given them any more of my hard-earned cash.

Finally it was the 2nd of December 2009 and I took another look at the forums – hoping that by some miracle V3 was in a usable state by now. What I found in Gambini’s post (that they were “aiming” to fix some of the bugs but couldn’t make any guarantees) just floored me and so I started asking awkward questions and suggested that perhaps a 2-year-old application that had over 70 known bugs is actually a load of rubbish and that hey really needed to sort themselves out. Other users agreed but stopped short of venting their own frustrations as openly as I – surprising really since they had paid good money for V3 while I had not. MDM responded by offering some pretty lame excuses (we’re a small team, there’s lots to do, we’ve had lots of things go wrong this year, blah blah) and totally failed to explain why 2-year-old software that they charge good money for should still be on the shelves with over 70 known bugs.

Rather than admit Zinc’s problems, Gambini (or Jaspal Sohal to give his real name) tried all kinds of tactics to divert attention from the software by – among other things – accusing me of not caring about MDM and being there only to start arguments. While I don’t really care for MDM either way (why would I? And why is that even relevant?), I do care about having access to good software and I do dislike it when honest, hard-working people are ripped off when buying faulty goods.

Anyway, for making my thoughts known, I was banned. I haven’t logged back in to see what they did with my posts, but I was there long enough to see that they deleted some other posts that didn’t reflect too kindly on themselves or their products.

In short, anyone who owns Zinc V3 and is unimpressed with its bugs should be prepared to be banned from the forums if they dare raise their concerns with the administrators. Anyone who is looking to buy some decent (i.e. working) software on the other hand would be wise to seek out some alternatives! The one that I’ve recently started using again is Northcode’s SWF Studio. I had used SWF Studio in the past but was never 100% happy with the script language, but having been forced to search for an alternative to Zinc due to V3′s ridiculous bug count, I found that the latest version of the software (SWF Studio 3) has a brand new scripting language that is much more intuitive – but most importantly it actually works!