The Bug Genie
Better Explorer
previous_open_issue.png
Go to the previous open issue
previous_issue.png
Go to the previous issue (open or closed)
star_faded.png
Please log in to bookmark issues
bug_report_small.png
icon_project.png Better Explorer / Open Bug report BE-540 No eject USB drive thru BE command
next_issue.png
Go to the next issue (open or closed)
next_open_issue.png
Go to the next open issue
Issue basics
  • Type of issue
    Bug report
  • Category
    General
  • Targetted for
    Not determined
  • Status
    Postponed
  • Progress
  • Priority
    Normal
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (2)
People involved
Times and dates
  • Posted at
  • Last updated
  • Estimated time
    Not estimated
Issue details
  • Resolution
    Not determined
  • Reproducability
    Always
  • Severity
    Not determined
Attachments (0)
There is nothing attached to this issue
Commits (1)
 Admin (admin)
Oct 14, 2016 - 12:50
master
- Fix Fixed BE-540 - USB Eject not working
Duplicate issues (0)
This issue does not have any duplicates
Description
No eject USB drive thru BE command ==> file in use
via W10 file in use
via context-menu ( Right-Click on drive USB)==> Click Continue ==> ok

We need to stop BE to use eject thru standard W10

Steps to reproduce this issue
Insert an USB key
Add something on the key
Try to eject the key
Comments ()
#4
 Megaten (Megaten)
icon_reply.pngOct 18, 2016, in reply to comment #3
Better but not the best After inact automatique start ==> no Open Explorer ( Open: was my default automatic option ) Not raisonable to ask to the end user to inact that option?

Reboot system with key plugged: display BE OK Eject via the BE eject button OK<===========================good unplug and replug ==> BE stop working. I reproduce that at each try
#3
 Dimitar Tsenev (DimitarCC)
Oct 14, 2016
It should be fixed now.
Changes:
  •   The issue was closed
  •   Resolution changed: Not determined => FIXED
  •   Assignee changed to Not assigned
  •   User working on issue changed:  Dimitar Tsenev (DimitarCC) => Not determined
#1
 Megaten (Megaten)
Sep 27, 2016

Now BE crash on my two system, when I eject my USB key:
USB type: USB2.0 FlashDisk USB Device

System.OverflowException was unhandled
HResult=-2146233066
Message=L'opération arithmétique a provoqué un dépassement de capacité.
Source=mscorlib
StackTrace:
à System.IntPtr.ToInt32()
à BetterExplorer.UsbEject.DeviceClass..ctor(Guid classGuid, IntPtr hwndParent) dans D:\Visual Studio 2008\Projects\BetterExplorer-master\UsbEject\UsbEject\DeviceClass.cs:ligne 42
à BetterExplorer.UsbEject.DeviceClass..ctor(Guid classGuid) dans D:\Visual Studio 2008\Projects\BetterExplorer-master\UsbEject\UsbEject\DeviceClass.cs:ligne 23
à BetterExplorer.UsbEject.VolumeDeviceClass..ctor() dans D:\Visual Studio 2008\Projects\BetterExplorer-master\UsbEject\UsbEject\VolumeDeviceClass.cs:ligne 21
à BetterExplorer.MainWindow.<>c__DisplayClass161_0.<EjectDisk>b__0() dans D:\Visual Studio 2008\Projects\BetterExplorer-master\BExplorer\BetterExplorer\MainWindow.xaml.cs:ligne 930
à System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
à System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
à System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
à System.Threading.ThreadHelper.ThreadStart()
InnerException:

History