<https://lh3.googleusercontent.com/-ICfTjsfCSWA/V1GzC1j01rI/AAAAAAAAAB0/nmj6pX1I7xU7IY0qskMS49Ky3eKTWJU7gCLcB/s1600/JALLIB-SDC-WIN10_error-2.jpg>
<https://lh3.googleusercontent.com/-dhHcpeEV7rU/V1GzEtst5GI/AAAAAAAAAB8/icwzZBk_0IEULtucKdOzabVv6fK6LS-6gCLcB/s1600/JALLIB-SDC-WIN10_error-3.jpg> <https://lh3.googleusercontent.com/-bSPy5bNXs98/V1GzAF6-xHI/AAAAAAAAABs/ZVF0Ah2UwEQBWXW8mztJtSZX8Qr9XzEDQCLcB/s1600/JALLIB-SDC-WIN10_error-1.jpg> OK, tried a completely new 18F26J50 board (a custom SMD application I made a while ago), and using SPI2 I get *almost *the same result: - When externally powered the SD card is recognized and the directory is read correctly. - When connected to the USB the generic Mass Storage Device is recognized and added to the Device Manager, but the associated drive letter is never assigned. FYI, if no card is inserted, the Mass Storage Device is *not *added to the Device Manager, so it's not an issue of card detection or having a valid card present (it passes that test when present). Something odd is going on in how Windows interacts with the MSD library. I've attached Windows 10 screenshots of the errors that *both *boards produced, with completely different set-ups. Has anyone categorically got Mass Storage working with any of the USB-enabled 18F PICs? -- You received this message because you are subscribed to the Google Groups "jallib" group. To unsubscribe from this group and stop receiving emails from it, send an email to jallib+unsubscr...@googlegroups.com. To post to this group, send email to jallib@googlegroups.com. Visit this group at https://groups.google.com/group/jallib. For more options, visit https://groups.google.com/d/optout.
