AlbertEinstein Posted February 26, 2018 Posted February 26, 2018 (edited) I just burned a 25GB BD-R. I went to make a cup of coffee while I let the BD-R finish burning. I came back and my screen had gone black. I have my screen set to turn off after 10 minutes. The system is set to go to sleep in 30 minutes. But I know I wasn't away from my computer that long. I had to enter my password to get back to the Windows desktop. It looks like the burn was 98% finished. The software put up some weird error on the screen about a streaming error or something. It asked me if I wanted it to try and close the session. So, I said yes. The BD-R drive moaned and groaned for a good 3 or 4 minutes before I got tired of it and just rebooted Windows to save the BD-R motor from burning up. When I got back into Windows 10 I checked the disc and it is readable so it's not a complete loss. I think at the moment my screen turned off the burn got messed up somehow. Or it got messed up from me just hitting "enter" on the keyboard to wake up the screen and enter my Windows log on pasword. Can you please confirm anything I have said here? I honestly think this messed up burn @ 99% finish is wholly related to the screen shutting down and then being woken back up by me. Maybe if I had just waited until I heard my BD-R drive stop spinning everything would have been okay? Obviously, in the future, I'm going to try and not be away from the keyboard so long so I don't take any chances. But what are you thoughts on this issue? Thanks for reading! Edited February 26, 2018 by AlbertEinstein
LIGHTNING UK! Posted February 26, 2018 Posted February 26, 2018 Post the log please. The issue was probably completely unrelated. Screensavers shouldn't make a difference. So long as the drive isn't physically powered off or reset somehow, you can pretty much pause the burn and resume it without an issue - note, this is not something a screensaver would do anyway!
AlbertEinstein Posted February 27, 2018 Author Posted February 27, 2018 (edited) Post the log please. The issue was probably completely unrelated. Screensavers shouldn't make a difference. So long as the drive isn't physically powered off or reset somehow, you can pretty much pause the burn and resume it without an issue - note, this is not something a screensaver would do anyway! I'm sorry I don't see any data related to the failed burn in the log. I think you've stated in the past when the application exits the wrong way that the log data is not written? Your application tried to "close the session", I think, and the drive tried but never would stop growling. So, I had to do things the hard way. So, that's what happened. I'm going to wise up and start using my screen capturing utilities like GreenShot and ShareX or even just the Windows print screen function. Because there are Windows that pop up with the specific error messages in them. I just never can remember exactly what they say. The last one was something about a stream or streaming error. There was no power loss. New question for you: I'm working on a new project to burn and your software complained about filenames being the same in a folder on my hard drive. And they actually are the same, except for casing in the file extension. I have a lot of images that have the same filenames but the extensions are .jpg and .JPG. That is enough for Windows 10 NTFS to "allow" the duplicate filenames I guess. Since they exists that way. Your application detects them as the same and offers to rename them. Your hands may be tied on this issue but I was just curious if this is something you could fix in a future version. No big deal for me to just give each set of files their own folder to avoid all of the brouhaha. Edited February 27, 2018 by AlbertEinstein
Recommended Posts