Quote:
Originally Posted by TeknoKid
Ok.. so today.. I tried the original 2GB card with the original data.. Same "No Memory Card Found" message I had with the other 2 memory cards.. When I would reset the device it did take quite a while before the message would appear.. I started wondering if it wasn’t a software issue rather than a hardware issue so I copied the system folder from the 0603 firmware (2.0 RC1) onto the original 2GB card.. inserted it in the reader and reset.. it did the standard reset then went through the installing firmware cycle.. Aah Ha! So it can read the card after all.. when the cycle finished now I can use the device again.. I copied the 0603 firmware back on to my 8GB card (the one with all my books on it) and did the whole reset cycle again.. it all worked fine and now the reader is working again..
|
I replied to this on the iRex forum, but just wanted to echo it on here for those that don't follow both.
I had the exact same thing happen with the 0408 firmware. I wasn't smart enough to think of re-installing the firmware, I was assuming it was a hardware problem with the card slot. After contacting tech support, that's the first thing they suggested, IE reinstall the firmware, which solved the problem for me too.
I suspect what happened is that there was some condition/error while the PC was disconnecting from the DR800 that caused corruption of a file/setting/etc. I know that the DR800 has some code in it to prevent the PC and the DR800 from both accessing the filesystem on the card at the same time. Maybe it flags the card as unavailable while it's connected to the PC, and something happens that it doesn't set it as available again... etc. Just a guess.
I don't know if this is something new in the beta firmware, or if the problem has been there all along and it's just rare enough that not many people have run across it. iRex has said on here before that there is a difference between "Eject" and "Safely Remove" and that they recommend one of them and not the other. I can't remember exactly which is which, but it's in an older thread on here. Maybe using the wrong one has a small chance of getting the DR800 "stuck" in the mode where it doesn't think it's allowed to access the filesystem on the card anymore.
Just so you know, I'm still running the beta firmware (RC2 now) and have not had any more instances of this happening. I wouldn't let it stop you from running RC2. Now we know how to resolve it, if it happens again. But it seems pretty rare.