There is no disk in drive error messages with Windows gtk3 builds

[t-o-d-d]

Currently: Windows RawTherapee-64-release-gtk3-bugfix-4.2.1425
AboutThisBuild-RawTherapee-64-release-gtk3-bugfix-4.2.1425.txt

I've attached a screenshot of my Windows 10 info:

Exact steps: Launch RT, and these errors start popping up like crazy:

It cycles through about five of my drive letters with this error message about ten times before loading RT. This time I actually wiped everything RT related out of my OS drive and reinstalled RT, and had gaaned92's Windows 'RawTherapee-64-release-gtk3-bugfix-4.2.1412' installed since yesterday and used it off and on all day without experiencing this problem. Launched it again tonight and started having the problem. So uninstalled RawTherapee-64-release-gtk3-bugfix-4.2.1425 and deleted program files then installed gaaned92's Windows RawTherapee-64-release-gtk3-bugfix-4.2.1425 build but continued to get the error messages.

I then reinstalled Squyaders 'RawTherapee_WinVista_64_Gtk3_Release_4.2.1375' and do not have this issue with this build.

Lastly, I installed gaaned92's RawTherapee_WinVista_64_debug_gtk3-bugfix_4.2.1425, which also generates the 'no disk' error messages o'plenty.
AboutThisBuild.txt
***I followed the Windows debug steps twice but each time the log file was empty at the end of the run. I copied the command prompt info into a text file manually and have attached here so you can see that I did try. I don't know if the info helps any though...
debug-attempt.txt

***I also have two more of gaaned92's Windows builds installed that do not have the no disk problem:
RawTherapee-64-release-locallab-4.2.1265 and
RawTherapee-64-release-pixelshift-4.2.1241.

So the problem seems isolated to the gtk3 builds. I thought I might try thoroughly wiping everything out again entirely then reinstalling, but figured I'd submit this bug report first to see if we can isolate the problem in some better way...

More background info:
First experienced this 'No Disk' issue in gaaned92's Windows 'RawTherapee-64-release-gtk3-bugfix-4.2.1396' build. See this post.

At the time I had Sguyader's Windows 4.2.1291 build installed which didn't have this issue, as none of his builds have ever had this problem. I didn't have the problem with gaaned92's build until I'd been using it for a day or two.... I figured the issue was due to my modified options file conflicting with gaaned92's build but didn't want to mess with my working Sguyader install... Finally just some days ago decided to thoroughly uninstall Squyaders latest working 'RawTherapee_WinVista_64_Gtk3_Release_4.2.1375' including the appdata stuff and try the latest gaaned92 Windows 'RawTherapee-64-release-gtk3-bugfix-4.2.1412' build and was happy to not see the no disk error messages..

[Partha1b]

This is an old gtk bug whereby when you build on a disk that is not available on the user's system but the disk drive is available (in this case the N-drive), it will do this.

Typically, the C-drive is available on everyone's system and so you don't see this. Best to build on a drive not likely to be available on the user's system (like I do on my Z-drive) or on the C-drive.

It's harmless but annoying.

[Beep6581]

Ping @gaaned92 @sguyader

[gaaned92]

@Partha1b : sorry but I don't really understand your first sentence. Could you elaborate.

I build on D-drive. And as I don't want to build in the C-drive, my only solution would be to create a partition somewhere and give it the letter Z: in order to safely build RT!

[t-o-d-d]

@gaaned92 @Partha1b I certainly have a D: drive and the drives that get the No Disk message are only certain drives, the USB drives in my screenshot here...

***Also, I shutdown my PC at night and I just ran 'RawTherapee-64-release-gtk3-bugfix-4.2.1425' to verify which exact drives get the No Disk error and now I am not getting the problem today... I will try to remember what was running last night... Maybe another app triggers this condition...

[t-o-d-d]

@Partha1b @gaaned92 Ok found it... I remembered that I had my SD Card in the drive last night (L: above)

I inserted the card and then the No Disk errors started.. It cycled through the N: M: and K: drives with the error a bunch of times, but not the L: drive.... Then I closed out RT and took the SD card out and then the No Disk errors started going through all four USB drives (N: M: L: K:).

One last thing I tried was clearing out my temp folders but RT still took me through all the No Disk errors after that... I guess there is no way to reset except to shutdown/reboot... Good thing though is there is a workaround going forward which is to make sure there is never an SD card in the drive when I launch RT...

[Partha1b]

@gaaned92 What I mean is the following: I have found that if you are using (say) Drive D to build RT and the user does not have a disk in drive D, it will give that error. I didn't think this error existed anymore and you can find references to it from 2006-2007.

I do my builds on drive Z which is unlikely to be on a user's system though of course it's possible. I think there are some registry cures for this though I have not encountered the error my to bother.

Finally the error is harmless and you can click cancel to continue. But it is annoying to the user of course.

Hope I am being clear?

[t-o-d-d]

Finally the error is harmless and you can click cancel to continue. But it is annoying to the user of course.

And to be clear, in my case I have to click cancel about 20 or more times, so it definitely is annoying. And there are times when the error messages come up when clicking on various tools in RT while editing, so there can be additional rounds of 20+ cancel clicks at random times...

[Partha1b]

@t-o-d-d Are you sure you haven't processed images from those drives with RT?

[t-o-d-d]

@Partha1b 100% positive that I haven't.

[gaaned92]

@Partha1b Thank you. I will set up a Z: partition to overcome the problem.
What is mysterious is how and where in the build, the build drive is encoded? perhaps in the innosetup install files and written in the registry RT uninstall key?
@t-o-d-d when you have multiple versions installed with innosetup, if you want to delete or uninstall a RT version, the easiest and safest way is to run the unins000.exe that is inside the directory.

[t-o-d-d]

@gaaned92
Don't know if you've switched to Z: yet but just tried your 'RawTherapee_WinVista_64_release_gtk3-bugfix_4.2.1445' and the problem remains... Also, I've found that I get the same No Disk behavior if any USB flash drives are plugged in to my computer...

[gaaned92]

@t-o-d-d not yet switched to Z: . First I have to build a new partition in existing disk or install a new disk.

@Floessie @heckflosse could you have a look on this issue?

[heckflosse]

@gaaned92 @t-o-d-d I always have a USB flash drive plugged into my computer but never had this issue (Win7/64)

@gaaned92
you don't need to build a new partition.
subst z: C:\rt_folder

[Partha1b]

@heckflosse Correct. The point is if you have a drive plugged in then you won't have the issue. :)