Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Attempting to access missing drive #360

Closed
fire-eggs opened this issue Jun 15, 2018 · 6 comments
Closed

Attempting to access missing drive #360

fire-eggs opened this issue Jun 15, 2018 · 6 comments

Comments

@fire-eggs
Copy link
Collaborator

System information:

  • Windows OS version: Windows 7
  • ImageGlass version: V5.1+

Describe the bug:

"ImageGlass.exe - No Disk" dialog box appears repeatedly.

IG will bang on a dismounted drive. May require problem images which IG won't load.

Expected behavior:

Once a disk has been dismounted, IG should fail to find it silently.

To Reproduce

Steps to reproduce the behavior:

  1. Have a dismount-able drive mounted, e.g. a DVD in drive.
  2. Run IG. View images. May require 'error' images.
  3. Dismount drive (e.g. eject DVD).
  4. Try to view images. Said dialog box (trying to access drive D:) appears repeatedly.

Most noticeable when thumbnails are viewed: appears to attempt to access drive D: twice for each failed thumbnail image. App freezes while dialog box is shown.

Seems to happen even if IG is shut down after dismounting drive D:. Running again, attempts to access drive D:.

Is "disk watch" not being intelligent about missing devices?

Screenshots:

Dialog references drive D: but note no drive D: active in Explorer.
image

Additional context:

@fire-eggs
Copy link
Collaborator Author

Confirmed with ImageGlass-Moon 6.0.0.0

image

@fire-eggs
Copy link
Collaborator Author

This is happening only intermittently right now - currently for the toolbar icons ?!?

Should this issue occur repeatedly for others, Google-sensei suggests that making the following call in Main() should solve the problem:

SetErrorMode(ErrorModes.SEM_FAILCRITICALERRORS);

@kristiker
Copy link

Still happens it's annoying.

@fire-eggs
Copy link
Collaborator Author

Yup, it certainly is annoying! Thank you for the comment - I'll integrate the change.

fire-eggs added a commit that referenced this issue Apr 8, 2019
@d2phap
Copy link
Owner

d2phap commented Apr 14, 2019

Available in the latest IG Moon https://imageglass.org/moon

@d2phap d2phap added this to the Issues 6.0.12.29 milestone May 25, 2019
@d2phap d2phap closed this as completed May 26, 2019
fire-eggs added a commit that referenced this issue Nov 27, 2019
fire-eggs added a commit that referenced this issue Dec 1, 2019
@fire-eggs
Copy link
Collaborator Author

As far as I've been able to determine, this is a system configuration issue and not caused by something IG is doing "wrong". But the fix is still necessary as the system configuration issue may be difficult to diagnose or fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants