I just noticed today that while Blender runtimes are active, Windows can’t read a newly inserted disk. This is a big problem for me since my software requires the disk in to run. When the disk isn’t in, it prompts the user to insert it, but thats not a lot of use if they have to restart my program to read the disk. I’ve replicated the issue on XP too.
I didn’t notice the bug earlier because I’ve always used ISO’s on my development computer. For some reason, ISO’s do get picked up and read while the runtimes are active.
I’m using Blender 2.45 on Vista Business and XP Pro. Does anyone know what might be causing this or how I could fix it?
I’m positive it’s not the CD drive being broken because the CD becomes readable the moment I close the runtime. That and it did it on another computer too.
I’ve posted before about weird errors (that make no difference to the way it runs) testing Blender sims while the CD drive was burning, I’m wondering if its related.
If anyone using 2.49 could try running a runtime, then try inserting a disk and being able to read it while the runtime is still running then please tell me, it could well be the last straw that forces us to update.