DSLRUsers.com

http://nikoneurope-en.custhelp.com/cgi- ... _topview=1

http://www.digicamnews.net/archives/200 ... ts_ed.html

And use your camera to format the CF card.

Birddog, I think you need to be introduced to http://tinyurl.com/


Gordon

The problem with Tinyurl is that it conceals where the link leads. And since it's easy to go
{url="...long link..."}page at nikon.com{/url} Birdy could make it look shorter if he wanted to.
I'd prefer that, as what we see is pushing the page width right out.


As for the problem, I suspect it's caused by Nikon not actually following the EXIF standards,
in order to cram extra stuff in there, and getting caught out. I bet Microsoft fix the problem

The format problem is likely to be that XP by default formats things with NTFS and
cameras generally only read FAT or FAT32. Not really Nikons fault, but interesting
to explain to users. I bet they got people going "Nikon broke my memory card" or "my
crappy Nikon can't read my 4GB memory card but it works fine in my Canon", when in
fact it was "I didn't read the instructions".

... but more to the point (since it happens only if you do stuff in XP via windows Explorer) is WTF don't people manipulate their shots using a decent image viewer.

No, Windows XP does not default to NTFS. It checks the volume size then determines what file system to use from there. Try it on a card (you can just cancel the format) and you'll notice it defaults to FAT32. The reason is that all OS'es have their quirks. A volume formatted in FAT32 on a MAC will not be readable on a PC. FAT32 just means a 32-bit "File Allocation Table" is created allowing 2^32 unique file names before one is repeated. FAT is 16-bit and allows 2^16. NTFS (New Technology File System) is Microsoft's solution to the unwieldy sector size when using FAT32 on today's uber large HDD's.

Nikon's warning against formatting in Windows likely has more to do with Microsoft trying to charge Nikon some amount for access to code or something so D70's (and others) could read Microsoft FAT32. Personally, kind of glad Nikon opted not to

As for the NEF issues, this is news to me (and glad to know it). It's likely a result of poor coding on Nikon's part as opposed to something Microsoft has done...