I bough the Meike MK-910 fro Ebay recently. I did have the MK900 but found it odd in some ways. It appeared to not fire the flash every so often. It would fire the TTL but then nothing. Seemed it was confused with the metering I believe. Forcing the camera (a d7100) out of auto-iso seems to make it work.
Anyway, the 910 does none of these things. It’s much better. The HSS Works well too. It works as a remote in Manual mode which I believe people had issues with on the MK-900. Not used it a great deal however, but all in all I’m pretty pleased. They seemed to have fixed the battery drain the 900 had too. This one doesnt instanlty drop to two bars the moment you put batteries in!
Crashing lsass.exe on your shiny 2012r2 DC? It’s a known bug according to PSS. You have three choices. a) use a different DC to rename things. b) turn of all auditing on the DC (seriously) c) apply a hotfix that you can only get from PSS.
Personally, I’ve gone for option “a”. We need the auditing and option c had a number of “it’s your fault if it breaks” warning attached to it that scared me a little. I’ll await the real patch which apparently will be “soon”. THough that’s in Microsoft Minutes so don’ hold your breath….
I’ve had this flash for some time now, and whilst initially impressed I’m getting slowly more disappointed with it. It seems to consistantly underexpose photos. I’ve no idea why. There are certain combinations of having the cameras ISO on auto and matrix metering enabled where the flash will fire but it always seems to be at 1/128. Changing the iso to manaul (and keeping all the settings the same) fixes it. How does that make a difference? Another fix is to enable spot metering. I’m very confused. It seems most problematioc in contrasty areas or when I focus on something that is black. I can’t recommend this flash unfortunately. I’m now looking for another. I seem to keep spending £100 or so on flashes that arent perfect. MAybe I should bite the bullet and just get the sb910…
Had the issue recently where the DFM would stop reporting statistics on all of our volumes on some controllers. After spending an eternity digging around it seems that if you enable debug logging on the dfm you will see an error returned by the controller that it has run out of memory. You can increase it but please check this burt first http://support.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=472940
To increase the memory from the default of 262144 do “options perf.dblade_zapi.buf_limit and select a higher number (in bytes). Try 307200 (300k) first then slowly increase it if you have no joy.
“vmdk is larger than the maximum size supported by datastore”
[SnapDrive Error]: Please specify valid VMFS datastore name. (SnapDrive Error Code: 0xc0041033)
Have a read of this:
Create a new vmfs5 datastore and then add the key listed in the article. No need to restart snapdrive. snapdrive will then use that as the file to back the RDM when it does a verification.