SD memory Card Reader/ Slot is not working on Windows 10. SD card and was able to access it when i had windows 7, but when i upgraded to windows 10 and inserted the memory card reader in the slot it stopped detecting, their is no action and i am not able to access it. Method 2: Install latest drivers for the USB device and check.
Thank all of you for informations. But I'm afraid, I'm not able to use any of them: 1) New I-IMAQ driver v8.5 still doesn support Coreco PC-CamLink (or maybe I m not able to find method to install property drivers in MAX) 2) Alliancedrivers are to expensive and as Kaccie wrote, doesn't work correctly. 3)Thirth method should be the best way, but I'm not able to handle with dll compilation (low experience in C/dll programing) So, I would like you Kaccie please for help, should you be so kind and send me your CamLink driver (and if it is possible an example) to email dejmek(at)kte.zcu.cz. Hi all, I think interfacing a framegrabber with LabVIEW can be much harder than Kaccie said. You will need to have a good knowledge of C/C, in order to develop a dll which takes care of many things, and especially of image pixels transfer. This means handling correctly the image border, different pixel depths, memory alignment, etc.
(the image in memory may not be stored in the same way in the IFC driver and in LabVIEW and you will have to take care of that). This is the job we have done at my company: Alliance Vision. Our driver supports all Coreco framegrabbers, and it has been tested with many differents cameras (Analog, RGB,camera Link.). Our driver is well documented, and we also provide free technical support. You can purchase it from our company , and from our United States partner which is Graftek Imaging Best Regards. Jean-Chrisotphe BENOIT Alliance Vision.
George, Not a problem. I have a PC-dig grabber running a dalsa camera. I can give you the c file that compiles into a dll (done in MS visual studio 6.0) and a VI that puts a while loop around this dll, grabbing an image each time. Do you have an email address? By the way, I'm pretty confident that Alliance vision 'drivers' work great. The only problem is that they are expensive and they wouldn't provide me with a demo to gurantee that it works.
So it was hard to persuade my advisor to purchase it.
I'm having problems with my external SanDisk cardreader on my new Windows 7 64-bit PC and I wonder if anyone has experienced similar problems or if there are any suggestions. When I plug the cardreader into either a USB2 or USB3 port (I have choice of 4 USB3, or 6 USB2) I can see the 'Removable Disk' listed in a Windows Explore window but when I insert a CF card and attempt to open the device I get a popup that says 'Please insert a disk into the Removeable Disk'. If I look at the device in Disk Management (of Computer Management) I can see the partition as 'Healthy (Active, Primary Partition)'. If I leave the CF card in the reader and reboot the PC I can now read the card and all the contents. These CF cards were formated in my D70.
I also have a D7000 which uses SD cards, so I bought a new SanDisk reader that support both SD and CF cards. It behaves the same as the above with both types of cards. I have to insert a card and reboot the PC before I can read the contents. Once the PC is rebooted I can use ViewNX2 and Nikon Transfer 2 to move the pictures to my PC. PC is a custom build: ASUS P8P67 Deluxe mother board i7-2600K CPU 16 GB ram 4 WD 1 TB disks 1 external WD MyBook 1 TB drive for backups Photoshop CS5 64-bit CaptureNX2 Canon Pro9000 printer Canon 9000F scanner Any suggestions would be appreciated. It's a pain to have to reboot evert time I want to change cards.
Thanks, Peter. I'm no technical whizz-kid so am just stabbing in the dark a bit.
But I wonder if the fact that your computer is a Custom Build just might have something to do with it. Certainly on the Win7 laptop which I bought as stand-by replacement just a short while ago (a Samsung) gives me no similar problems with plug-in USB type drives. I've used quite a few different small ones in recent weeks in order to move such as installation programs etc from a copy on my current computer to the new one.via such as a plug-in USB thumb-drive.quite varied types but all have been taken onboard by the Samsung readily enough. You say that yours will not seem to recognise a drive when you are switched on and plug it in, but it works OK if you do a fresh boot-up when it does recognise a USB drive. Is this maybe due to the fact that when you are switched on and plug one in.it then normally has to look for a suitable driver to use with that 'new' plug-in drive.
But it is not finding one. Yet from a fresh boot-up with the USB plugged in.it does find something. So is it only finding a driver for it when it HAS to do so at boot-up time.to use all the drives it then has to try to identify and hand over to you.when actually switched on and a USB drive inserted it is then NOT finding one. That seems surely to be the problem.
But as it is a Custom Build.this failure to find a NEW driver for a NEWLY added drive. Must it seems be related to the build?? It's not happened on my Win7 but on the old XP system if I plugged in anything which it did not recognise I invariably got a screen telling me so and asking in effect if I wanted to let it search further, or indicate somewhere it could look.and I often then tried first to tell it to look in a Windows/INF folder or something,where a lot of things seem to be. Do you get any such screen as that when it cannot find anything.on your Win7 that is? What happens if you leave the card reader plugged in and just use eject when you want to remove a card (look under 'Computer', right click on the icon for the reader, then click on Eject)? IOW, plug in the reader, and reboot.
Then, insert a card after it's finished booting (don't put it in before you boot). Then, use Eject when you want to remove it and/or insert a different card (leaving the reader plugged in all the time). As already mentioned, it could be trying to find drivers when you first plug it in. Windows behavior can be odd in that area, especially if you switch USB ports (where it may try to reinstall the driver again for the other port).
So, I'd try leaving the reader plugged into the same USB port all the time. I'd plug it in (without any card in it), reboot and then see if it recognizes a card when you plug one into it. If so, see if you can use the 'Eject' feature (right click on it under Computer and select Eject), so you can insert and remove different cards without rebooting. Or, see if you have a 'Safely Remove' icon in your system tray (that should do the same thing), which may be hidden (look at hidden icons if you don't see it). You can't 'eject' the card in a USB card reader. If you do, it disconnects the card reader itself and you won't be able to use it again until you either (a) reboot, or (b) unplug and replug the card reader. When you're finished using the card in a USB card reader, wait to make sure the activity light is no longer blinking and then just pull the card out.
The same is true of most 'internal' card readers because they are almost always connected to a USB header on the motherboard. The big problem with them is that there's no way to unplug/replug the card reader if you 'eject' it short of opening up the case and finding the right wires to pull, so the only recourse is to reboot.
Sean Nelson wrote: You can't 'eject' the card in a USB card reader. If you do, it disconnects the card reader itself and you won't be able to use it again until you either (a) reboot, or (b) unplug and replug the card reader.
When you're finished using the card in a USB card reader, wait to make sure the activity light is no longer blinking and then just pull the card out. The same is true of most 'internal' card readers because they are almost always connected to a USB header on the motherboard. The big problem with them is that there's no way to unplug/replug the card reader if you 'eject' it short of opening up the case and finding the right wires to pull, so the only recourse is to reboot. Sorry Sean, My Acer with build in card readers (5 slots for a total of 11 card formats) works fine and sees all my CF and SD and SDHC cards and neatly ejects them under win7 and also did so under Vista.
![]()
Your observation might be machine dependant. Snap snap - click click. Also note that Windows may treat a reader differently if a card is inserted at the time you boot. Boot into Windows with the reader plugged in, without a card inserted. Then, see if you can plug in a card and it's recognized and copy files from it. Then, see if you can use the eject feature (or safely remove if an icon appears for it in your system tray), and insert a different card after using Eject to see if it's recognized as a new card. I've got more than one USB attached card reader, and that's the way they work in Win 7.
The 'trick' is to make sure you don't have card inserted when you boot into Windows. Then, Windows treats the reader differently. You have quite a number of hard drives. When you reboot, and the computer then detects the USB drive, do all those hard drives and their partitions, if any, retain their previous drive letter designations, or is there a change in one or more of them? I ask this because the fact that the plugged-in card shows up in the disk management console suggests that its assigned drive letter may already be in use by one of those HDDs. I've heard conflicting explanations of how and why, but Windows has a known tendency to do that. If you Google 'Article ID: 297694,' you'll find Microsoft's recent discussion (Sept.
23, 2011) and a 'hotfix,' but be warned that MS has supposedly been trying to fix this bug since before SP3 was issued for Windows XP. The quick fix when this issue does arise is to right-click on the unrecognized drive in the disk management console, and assign an unused drive letter manually, via the entry on the context menu that will appear. Jim Cockfield wrote: Also note that Windows may treat a reader differently if a card is inserted at the time you boot. Boot into Windows with the reader plugged in, without a card inserted. Then, see if you can plug in a card and it's recognized and copy files from it. Then, see if you can use the eject feature (or safely remove if an icon appears for it in your system tray), and insert a different card after using Eject to see if it's recognized as a new card.
I've got more than one USB attached card reader, and that's the way they work in Win 7. The 'trick' is to make sure you don't have card inserted when you boot into Windows.
Then, Windows treats the reader differently. Jim- I suspect that the trouble/misunderstanding here is that you are using the word 'Eject' which others are perhaps thinking of a full ejection of the whole thing.whereas I suspect that you don't actually mean it that way. I see nothing at all wrong with what you say.I've not done it that way.I just click on a Zentimo taskbar icon that then lets me specify the plug-in drive to eject.or rather 'STOP'- which is actually what is required.
Doing that, you certainly can then 'eject' (pull out) the card FROM the reader (leaving the latter inserted as it is then 'dead' of course.) then later just plug in a card to the inserted reader when it will come 'alive'again. I don't myself usually leave the card-reader plugged in.but I see no reason why not.as it will be inactive.UNTIL a card is again inserted of course. Sean Nelson wrote: You can't 'eject' the card in a USB card reader.
If you do, it disconnects the card reader itself and you won't be able to use it again until you either (a) reboot, or (b) unplug and replug the card reader. Fotonut wrote: My Acer with build in card readers (5 slots for a total of 11 card formats) works fine and sees all my CF and SD and SDHC cards and neatly ejects them under win7 and also did so under Vista. Just to be perfectly clear, when I say 'eject' I'm not talking about just removing the card, I'm talking about clicking the 'Safely Remove Hardware' icon (in the notifcation area that's normally at the right end of the task bar) and selecting 'Eject device name '.
If that doesn't disable your USB-connected card reader then there's something interesting going on there that I'd like to know more about. Fotonut wrote: My Acer with build in card readers (5 slots for a total of 11 card formats) works fine and sees all my CF and SD and SDHC cards and neatly ejects them under win7 and also did so under Vista. Just to be perfectly clear, when I say 'eject' I'm not talking about just removing the card, I'm talking about clicking the 'Safely Remove Hardware' icon (in the notifcation area that's normally at the right end of the task bar) and selecting 'Eject device name '. If that doesn't disable your USB-connected card reader then there's something interesting going on there that I'd like to know more about.
Now, I must be confused. My chassis-mounted card reader works the same as Fotonut's. So did the one it replaced. And so does my Sandisk multi-card reader. If I use 'safely remove' in the sys-tray, I get the message that I can now safely remove the card, but the slots remain visible as lettered drives in Windows Explorer, along with the optical drives in the section for drives with removable storage.
If I click on them when no card is present, I get a message to insert media in the drive. I can plug the card or a different one right back into the same slot of the reader. At no time am I compelled to unplug the reader, and I often leave the Sandisk plugged in for weeks at a time, and use the CF, SD and MS slots dozens of times.
I can't imagine why people would bother buying and installing these readers, especially the chassis-mounts, if they did not behave this way. Fotonut wrote: My Acer with build in card readers (5 slots for a total of 11 card formats) works fine and sees all my CF and SD and SDHC cards and neatly ejects them under win7 and also did so under Vista. Sean Nelson wrote: Just to be perfectly clear, when I say 'eject' I'm not talking about just removing the card, I'm talking about clicking the 'Safely Remove Hardware' icon (in the notifcation area that's normally at the right end of the task bar) and selecting 'Eject device name '. Lyle Aldridge wrote: Now, I must be confused.
My chassis-mounted card reader works the same as Fotonut's. So did the one it replaced. And so does my Sandisk multi-card reader. If I use 'safely remove' in the sys-tray, I get the message that I can now safely remove the card, but the slots remain visible as lettered drives in Windows Explorer, along with the optical drives in the section for drives with removable storage.
Curiouser and curiouser. I've done a bunch of Googling and haven't found anything definitive, but it did lead me to discover that there are other options than using the icon in the taskbar notification area. Here's what I found (each of these starts with a card plugged into the drive and the volume name visible in Windows Explorer):. clicking the 'Safely Remove Hardware' icon in the Taskbar notification area, then clicking 'Eject device-name ' causes the entire drive to disappear and requires it to be unplugged/replugged in order to be used again. (Note - the context menu actually shows an entry for the device and for the volume mounted on the device, but the volume is grayed out and only the device is clickable). opening the 'computer' view of Windows Explorer, right-clicking on the device and selecting 'Eject' dismounts the card and leaves the device available.
It can be reused simply by plugging the card back into the drive. This is the way I'd expect it to work. Opening the 'Devices and Printers' view of Explorer (which you can do by clicking the 'Safely Remove Hardware' Icon in the Taskbar and selecting 'Open Devices and Printers'), then right-clicking on the card reader and selecting 'Eject' causes the entire drive to disappear and requires it to be unplugged/replugged in order to be used again. The behaviour was the same whether the policies for the device were configured as 'Quick Removal' (which disables write caching) or 'Better Performance' (which requires you to use 'Safely Remove Hardware' to prevent corruption).
I'm using an external USB 2.0 SanDisk ImageMate card reader that has only one slot for SD/SDHC cards. I'm wondering if the device attribute bits are slightly different for some readers and this accounts for the differences in behaviour.
Sean Nelson wrote: Sean Nelson wrote: You can't 'eject' the card in a USB card reader. If you do, it disconnects the card reader itself and you won't be able to use it again until you either (a) reboot, or (b) unplug and replug the card reader. Fotonut wrote: My Acer with build in card readers (5 slots for a total of 11 card formats) works fine and sees all my CF and SD and SDHC cards and neatly ejects them under win7 and also did so under Vista. Just to be perfectly clear, when I say 'eject' I'm not talking about just removing the card, I'm talking about clicking the 'Safely Remove Hardware' icon (in the notifcation area that's normally at the right end of the task bar) and selecting 'Eject device name '. If that doesn't disable your USB-connected card reader then there's something interesting going on there that I'd like to know more about.
You are referring here to USB connected readers, but you also stated this, which i was referring to. The same is true of most 'internal' card readers because they are almost always connected to a USB header on the motherboard. The big problem with them is that there's no way to unplug/replug the card reader if you 'eject' it short of opening up the case and finding the right wires to pull, so the only recourse is to reboot. I did mean the same eject process (safely remove hardware).
In win7 it even shows the type of card, in vista it just showed drives, so it was always a guess if i ejected the right card. The same is true for any USB stcks i connect, in win7 it shows the make of the stick, in vista it did not just showed drive letters, making removal a guess. It was too easy to remove the wrong reader or stick making going back a restore point necessary.
Hope i explained it correctly. Snap snap - click click. Lyle Aldridge wrote: Fotonut wrote: My Acer with build in card readers (5 slots for a total of 11 card formats) works fine and sees all my CF and SD and SDHC cards and neatly ejects them under win7 and also did so under Vista. Just to be perfectly clear, when I say 'eject' I'm not talking about just removing the card, I'm talking about clicking the 'Safely Remove Hardware' icon (in the notifcation area that's normally at the right end of the task bar) and selecting 'Eject device name '. If that doesn't disable your USB-connected card reader then there's something interesting going on there that I'd like to know more about. Now, I must be confused.
My chassis-mounted card reader works the same as Fotonut's. So did the one it replaced. And so does my Sandisk multi-card reader. If I use 'safely remove' in the sys-tray, I get the message that I can now safely remove the card, but the slots remain visible as lettered drives in Windows Explorer, along with the optical drives in the section for drives with removable storage. If I click on them when no card is present, I get a message to insert media in the drive.
I can plug the card or a different one right back into the same slot of the reader. At no time am I compelled to unplug the reader, and I often leave the Sandisk plugged in for weeks at a time, and use the CF, SD and MS slots dozens of times. I can't imagine why people would bother buying and installing these readers, especially the chassis-mounts, if they did not behave this way. Hmmm, my readers do not show up in windows explorer unless there is a card in it. Running win7 ultimate 32 bit. So it may be a setting in windows to get the readers to show. Snap snap - click click.
Sean Nelson wrote: Fotonut wrote: My Acer with build in card readers (5 slots for a total of 11 card formats) works fine and sees all my CF and SD and SDHC cards and neatly ejects them under win7 and also did so under Vista. Sean Nelson wrote: Just to be perfectly clear, when I say 'eject' I'm not talking about just removing the card, I'm talking about clicking the 'Safely Remove Hardware' icon (in the notifcation area that's normally at the right end of the task bar) and selecting 'Eject device name '. Lyle Aldridge wrote: Now, I must be confused. My chassis-mounted card reader works the same as Fotonut's.
So did the one it replaced. And so does my Sandisk multi-card reader. If I use 'safely remove' in the sys-tray, I get the message that I can now safely remove the card, but the slots remain visible as lettered drives in Windows Explorer, along with the optical drives in the section for drives with removable storage.
Curiouser and curiouser. I've done a bunch of Googling and haven't found anything definitive, but it did lead me to discover that there are other options than using the icon in the taskbar notification area. Here's what I found (each of these starts with a card plugged into the drive and the volume name visible in Windows Explorer):. clicking the 'Safely Remove Hardware' icon in the Taskbar notification area, then clicking 'Eject device-name ' causes the entire drive to disappear and requires it to be unplugged/replugged in order to be used again.
(Note - the context menu actually shows an entry for the device and for the volume mounted on the device, but the volume is grayed out and only the device is clickable). In vista this its how it worked for me. Often all the volumes/drives would show in the save to remove hardware list making it easy to eject the wrong one. I do have to note, that if the volume was grayed out then it had no card in it. And Safely remove hardware of a grayed out volume/drive would remove the volume/drive even from Device Manager. Going back a restore point would place it back in Device manager and make it available for use again.
In win7 ultimate 32 bit just the volume/drive that has a card in it will show in the save to remove hardware list. (this is for build in cardreaders, i've never had an external cardreader). opening the 'computer' view of Windows Explorer, right-clicking on the device and selecting 'Eject' dismounts the card and leaves the device available. It can be reused simply by plugging the card back into the drive. This is the way I'd expect it to work. Opening the 'Devices and Printers' view of Explorer (which you can do by clicking the 'Safely Remove Hardware' Icon in the Taskbar and selecting 'Open Devices and Printers'), then right-clicking on the card reader and selecting 'Eject' causes the entire drive to disappear and requires it to be unplugged/replugged in order to be used again.
The behaviour was the same whether the policies for the device were configured as 'Quick Removal' (which disables write caching) or 'Better Performance' (which requires you to use 'Safely Remove Hardware' to prevent corruption). I'm using an external USB 2.0 SanDisk ImageMate card reader that has only one slot for SD/SDHC cards. I'm wondering if the device attribute bits are slightly different for some readers and this accounts for the differences in behaviour.
Snap snap - click click.
Comments are closed.
|
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |