Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.mobile.android > #37168
| From | nospam <nospam@nospam.invalid> |
|---|---|
| Newsgroups | comp.mobile.android |
| Subject | Re: Android 6 |
| Date | 2017-01-02 08:51 -0500 |
| Organization | A noiseless patient Spider |
| Message-ID | <020120170851415117%nospam@nospam.invalid> (permalink) |
| References | (6 earlier) <291220161202474716%nospam@nospam.invalid> <a9d5f932-7b61-0ec9-6954-ac9f7f27c7bb@arnowelzel.de> <VA.00000c22.00519969@me.invalid> <lMAnGZ1HXFaYFw+B@end.of.the.universe> <77u3dhr8hkrv.jdtu6ks2qz3d$.dlg@40tude.net> |
In article <77u3dhr8hkrv.jdtu6ks2qz3d$.dlg@40tude.net>, tlvp <mPiOsUcB.EtLlLvEp@att.net> wrote: > > As the OP and as this has gone slightly OT, what is the reason why it is > > often recommended that SD cards in dashcams be regularly formatted in > > the dashcam? > > > > In my case, the new 64GB and 128GB SD cards showed in W7 as being > > formatted FAT32.They weren't initially recognised in the cam. > > > > Formatted in the cam and they were recognised and work well. > > > > When W7 displays their properties, they are both still shown as > > formatted FAT32. > > When I format a *SD card with the help of a Windows system, there's no file > or folder to be found on the freshly formatted card. > > When I use a particular non-Windows device to format the card, there's > often one (or several) specifically named folder(s) on the freshly > formatted card. For example, if it's a camera (or a phone with camera) > doing the formatting, there's often a DCIM folder created, along with a > Camera (or similarly named) subfolder, purpose-built for the use of the > device doing the formatting. > > It might be (but no guarantees here) that, without those idiosyncratic > folders, the device won't recognize the card. HTH. Cheers, -- tlvp cameras will write a dcim folder if there isn't one already there.
Back to comp.mobile.android | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Android 6 Bill <Billaboard@gmail.com> - 2016-12-22 17:21 +0000
Re: Android 6 The Real Bev <bashley101@gmail.com> - 2016-12-22 10:00 -0800
Re: Android 6 Bill <Billaboard@gmail.com> - 2016-12-23 00:23 +0000
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-22 19:30 -0500
Re: Android 6 Bill <Billaboard@gmail.com> - 2016-12-23 12:42 +0000
Re: Android 6 tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2016-12-23 11:58 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2016-12-29 13:43 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2016-12-30 15:34 +0000
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2016-12-30 22:33 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2016-12-31 13:27 +0000
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-04 08:59 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-04 13:40 +0000
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-11 09:00 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-15 18:23 +0000
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-15 21:20 +0100
Re: Android 6 AL <45364747@invalid.com> - 2017-01-04 10:06 -0700
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-11 09:00 +0100
Re: Android 6 tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2017-01-05 01:34 -0500
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-07 14:14 +0000
Re: Android 6 tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2017-01-07 13:09 -0500
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-08 18:18 +0000
Re: Android 6 tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2017-01-08 15:42 -0500
Re: Android 6 The Real Bev <bashley101@gmail.com> - 2017-01-08 17:11 -0800
Re: Android 6 nospam <nospam@nospam.invalid> - 2017-01-08 20:19 -0500
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-09 23:55 +0000
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-11 18:07 +0100
Re: Android 6 Frank Slootweg <this@ddress.is.invalid> - 2017-01-08 21:34 +0000
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-09 23:55 +0000
Re: Android 6 Joerg Lorenz <hugybear@gmx.ch> - 2016-12-24 10:49 +0100
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2016-12-22 23:55 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-22 19:15 -0500
Re: Android 6 Joerg Lorenz <hugybear@gmx.ch> - 2016-12-23 05:46 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-23 00:15 -0500
Re: Android 6 Dave Higton <dave@davehigton.me.uk> - 2016-12-23 17:11 +0000
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-23 12:43 -0500
Re: Android 6 Dave Higton <dave@davehigton.me.uk> - 2016-12-23 21:22 +0000
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-24 14:29 -0500
Re: Android 6 Dave Higton <dave@davehigton.me.uk> - 2016-12-25 11:10 +0000
Re: Android 6 Piet <www.godfatherof.nl/@opt-in.invalid> - 2016-12-25 12:37 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-25 11:18 -0500
Re: Android 6 Dave Higton <dave@davehigton.me.uk> - 2016-12-25 20:28 +0000
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-29 12:02 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2016-12-29 23:45 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-29 18:02 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2016-12-30 22:24 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-31 11:55 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-04 09:04 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2017-01-04 10:14 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-11 18:11 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2017-01-11 13:05 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-13 17:23 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2017-01-16 15:35 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-17 05:39 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2016-12-30 15:34 +0000
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2016-12-30 22:26 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2016-12-31 13:27 +0000
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-31 11:55 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-04 09:11 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-04 13:40 +0000
Re: Android 6 nospam <nospam@nospam.invalid> - 2017-01-04 10:14 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-11 18:12 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2017-01-11 13:05 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-13 17:24 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-15 18:23 +0000
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-15 21:30 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-16 15:42 +0000
Re: Android 6 nospam <nospam@nospam.invalid> - 2017-01-16 15:35 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-17 05:44 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-17 17:47 +0000
Re: Android 6 Bill <Billaboard@gmail.com> - 2017-01-01 01:05 +0000
Re: Android 6 tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2017-01-02 02:08 -0500
Re: Android 6 David Taylor <david-taylor@blueyonder.co.uk.invalid> - 2017-01-02 08:01 +0000
Re: Android 6 nospam <nospam@nospam.invalid> - 2017-01-02 08:51 -0500
Re: Android 6 Bill <Billaboard@gmail.com> - 2017-01-02 20:41 +0000
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-04 09:18 +0100
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-04 09:14 +0100
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2016-12-29 14:05 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-29 12:02 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2016-12-29 23:46 +0100
Re: Android 6 Dave Higton <dave@davehigton.me.uk> - 2016-12-31 20:18 +0000
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2016-12-29 13:47 +0100
csiph-web