Quote:
Originally Posted by Nick_1964
Yes.. but in the release notes, nowhere stands that the "ejection" (hmm.. hope I don't say 18+ things here) is only for Calibre.
It is announced as a feature, then I think it is a feature that works in my o.s.
|
What release notes? Or are referring to my post with a list of changes? The post that has disclaimer about them being things that I noticed while testing the betas? And that I state they mainly cover functions of the firmware that I use and are probably incomplete? I'll remember to put the disclaimer in bold next time. Or do I need flashing red as well?
Quote:
If there was: When u eject the device from within Calibre, it will start again, I wasn't "complaining" because that works (never saw that button but more things are hidden in my language,or not exactly clear because everyone is speaking english here and then I have to search for what the function is in English.)
|
I think that's based on another off-hand comment of mine. Yes, I have an eject button in the toolbar. You probably don't as I use a plugin called "Smart Eject" so that I can have an easy way to eject the device.
Quote:
Everyone says, it works for me in Calibre, but this is not a Calibre topic.
So if i see: If u eject the device,it starts again without disconnecting the usb cable,and it is not in a Calibre topic, I think it is a feature that works in windows 7,which it doesn't with the safe eject function.
Windows doesn't give a warning like "another program is using this device so you can't eject it" it just does, the device drive (usually J) disappears,and I can't use the eject button again since I already eject it.
So yes it works from Calibre, but that is not what the feature list says.
|
And I have no idea whether it works with Mac or a Linux box. Actually, I do know for CentOS6. The eject that it's explorer equivalent has, will disconnect the device so that it restarts.
Quote:
I don't think there is something wrong with 3 computers, but I now think... did I tried it with the Aura HD or the Glo.. from the Glo it doesn't work, for the Aura HD I gonna test it.
All the deviced are hooked up on a 14 port USB hub..so I gonna see if that is the bottleneck.
/edit tried it on a direct USB port,not on the hub with both Aura HD and Glo, didn't work so I think the function called in the Changelist for this firmware,must have something like ("works from Calibre").
Attachment 130340 The menu shows the device.
Attachment 130341 The menu shows the device is ejected (with the sound that belongs there)
Attachment 130342 Device stays in this modus.
|
So, I was lax in my testing. I did notice that it didn't always work. But, that hadn't happened enough for me to look for a pattern. But, I made the assumption it was a combination of what I did while the device was connected. Pre-3.11.0, I had occasions where the device didn't restart after disconnecting, or took a long time to, so I assumed it was related to that. But, I have done some testing. Much to my surprise, ejecting from the "Safely remove device" menu is not the same as ejecting from explorer or calibre. From explorer, it's the same as from calibre. The device will disconnect fully and restart. From the safely remove menu, it doesn't. To my mind, that's unexpected and bad. This should be the safest way to disconnect the device. After all, that is what the menu says. But, it leaves the device in a partial state that could be a problem.
And just to be explicit:
- I did most of my testing with Windows 7, 32bit and all the latest fixes on an aging ASUS laptop
- Ejecting from calibre, will let the device restart without disconnecting.
- Using "Eject" from explorer, will let the device restart without disconnecting.
- Using "Eject eReader 3.11.0" from the "Safely remove device" icon in the system tray will not let the device restart without disconnecting.
- Using "Eject" on the icon in the "Devices and Printer" folder will not let the device restart without disconnecting.
- This is with a Glo and a N905 Touch
- I have not tested in any other version of Windows
- I have not tested in a Mac
- I have tested with a CentOS6 machine (some sort of AMD) and it did let the device restart without disconnecting.