dbminter

Well, I summoned up the blood and just worked through the fatigue to swap out the latest USB HDD for the one that used to work, restored Windows 10 1909 back to when it used to work, restored the live data partition back when it used to work, booted into Windows, did nothing else, and waited for 60 minutes. On cue, the Start menu wouldn't open! So, it's a problem with the PC. Not a BIOS issue! Not a security issue! Not a software issue! Funny enough, a BIOS update had been released since this all began. I applied that, knowing full well it wouldn't address the problem, and it didn't. So, there's no escaping it. I have to get a 2nd new PC is under 2 years!

I am still suffering with whatever it is I have, though I doubt it's stomach flu anymore, unless stomach flu lasts more than 7 days. I still need to perform one last test to rule out it's not the new USB HDD, but I can't do it until I get enough strength to be able to lift the one out of place and put an old one in. Then, restore known good images of Windows 10 1909 and live data partition on the old device, start Windows, and wait an hour. Also, last things I needed right now to happen all at the same time: 1.) needing a new PC 2.) 2 ER visits 3.) 2 primary care physician visits 4.) my waterbed sprung a leak 5.) one of the few Christmas gifts to me under the tree this year that isn't To me From me arrived from a friend from Amazon.com damaged! It was an 11 disc DVD set where 6 of them were packaged out of order and one was disconnected from its peg, floating around inside the packaging, getting scratched beyond play.

It's half a year past its warranty under Dell. Plus, to replicate the issue, I'd have to send in one of my USB HDD's along with it, which means sending in my live data, which is too important. Plus, it would have be configured to load the Desktop folder from F:\.

Well, not that I'm defending Freemake Video Converter, because it has a lot of problems, it is converting from one video container format to another. That's where the long time comes in, particularly on the so called "free" version. Which watermarks the video so how useful is it? ImgBurn just burns what you feed it. It does no, and cannot do, any video conversion.

It's NOT a security issue! It happens on 2 different drives that were working fine before. It doesn't do this on my old PC. So, the problem is with the PC. It's not solved by deleting everything and start from scratch. Tried that. 7.0.0.69 is the last Gold release of CXD. And I spent all afternoon into the evening in the emergency room with apparent stomach flu. Really hit me first hard yesterday, but today, my first attempt to eat something, caused uncontrollable shaking. Last thing I need right now.

Try something other than MediaRange BD-R DL. Like Verbatim BD-R DL. When using dual layer media, the only reliable stuff used to be made by Verbatim. CMC bought up Verbatim so it's hard to say much anymore. Near as I can remember, MediaRange is a no name manufacturer so their discs are cheap. Cheap media often times aren't recognized by players.

By engrave, do you mean burning a BD-R? By lounge, do you mean a Blu-Ray player? If so, ImgBurn should automatically finalize discs for you. If a Blu-Ray player isn't playing your BD-R movie disc, it could be a variety of things. Either non-compliant BDMV and CERTIFICATE folders made by the program that made them or your player doesn't like the BD-R's you're using and doesn't recognize they've been inserted.

There's no way around it. My PC's still not working right and the tech guys find nothing wrong. I connected this USB HDD to my old PC and it doesn't do what it does on my newest PC. Any time any contents are accessed from this drive in any way, Windows locks up fatally after an hour and won't restart, ever. It's not the USB HDD because it works fine on my old PC. So, there's no way around it. The problem is with this PC that's only a year and a half old. Well, Dell goes on my list now. Also on my list is Pioneer. Now the BDR-212 won't write to BD-R! It ALWAYS returns Medium Corrupted when trying to write to them now! Before, I'd get that error and just retry the burn and it would work. I put the SAME disc the 212 returns the Medium Corrupted error on in my LG WH16NS60 and it burns fine. I will see if I can still take up Pioneer on that refund offer.

Did you find my VRO input post on the VSO CXD forum?

When I bought my CXD license, I got the lifetime version. Don't know if they still offer that anymore. Why offer that when they can make you pay infinitely? I used to use Partition Wizard but the last time I tried a resize operation, all it did was hide the partition and didn't do anything else. Stayed at 0%. Tried to get tech support to help, but I knew, from looking at the log, they'd find nothing wrong because nothing was being done. And, of course, they couldn't help. So, I switched to AEOMI Partition Assistant. It has its own bugs, but they're not nearly as fatal. And their tech support stinks, too. They keep asking me to describe the SAME thing over and over again! Yes, free versions of True Image used to come with my My Books. I never used it because True Image kept borking the recovery media. It would recognize external source devices for recovery images, but it would then FORGET they were there... but only after, conveniently, DELETING the target partition for restore! So, from chevr0n's suggestion, I tried and switched over to Macrium Reflect.

dr, I saw your post about your Explorer issue on the VSO CXD forum.

I think I sussed the problem out by attaching the USB HDD in question to an older PC running an older Windows 10 version. I got a new error this time, but this error was more indicative of what was probably going on. It appears to be NEITHER a hardware or a software issue! It appears a partition on the drive had been turned entirely read only somehow. When connecting that drive to my old PC, I couldn't open anything for editing. I couldn't even create new files in the root directory of the partition. That partition had one thing in common in all tests: contents were being accessed from it. My Desktop folder and my Waterfox web browser profile folder were on that partition. Desktop gets accessed every time Windows starts. On the 1809 image restore, the problem only appeared when Waterfox accessed its contents, creating corrupted contents where Waterfox wouldn't even load. So, I restored the partition image made back when it was working and the contents were no longer in read only mode. Now, WHY Windows WOULD work for 45 to 60 minutes BEFORE crashing if the contents were read only makes no sense. Should have happened immediately. WHY connecting the other working HDD did the same thing makes no sense either. I won't know if this fixes the issue until I get the PC back from the shop to test it. Plus, it doesn't explain WHAT set the entire partition read only. And, frankly, HOW. It could STILL be a hardware issue in my live PC that is causing this. Or could be a hardware error in the USB HDD. What also isn't explained is why Windows would lock up on subsequent restarts, even with the drive disconnected.

It's not a BIOS problem. Besides, there isn't a new BIOS update. I updated Windows 10 1903 to 1909 twice just fine for 2 weeks with no problem. It's not a BIOS issue. VSO basically said my VRO problem wasn't something they cared about right now. They said they're too busy doing the 64 bit version to worry about my piddling problem. I did more tests and Wondershare Filmora processes the VRO just fine, so it's a CXD issue.

It's not a BIOS issue. BIOS settings just don't change themselves and I haven't updated the BIOS in months. Otherwise, I'd have have suspected a borked BIOS. It's not a Device Manager issue as even restoring all images where Windows was working fine before it does this. It doesn't do this unless a USB HDD is plugged in and contents are accessed from it. All images were working fine until the 21st. Regardless of device, when 2 working ones I had before, one for over a year, do this. So, the problem has to be an internal hardware error. After explaining the issue to the shop I went in and detailed my 3 days of debugging, he agrees with me it's either the mobo, the RAM, the CPU, or the BIOS controller on the mobo. I forgot to run MemTest86 and did so last night. No problems there so it's most likely not the RAM. If the mobo needs to be replaced, might as well get a whole new PC. Replacing the mobo might void my Windows license.

The bottom line is you get one image per disc. So, you can't burn more than one image to a disc.

They're neither matted or shiny. They're inkjet printable. As for the board behavior, it's just the server acting up, most likely. Give it a few hours/a day, and it should resolve. I had no problem posting this just now. It's a hardware issue. It can't be software related because it's happened on 2 1909 images that were working fine, on my 1903 that was working fine, and on my 1809 factory default installation which was working fine. It only happens when ANY external USB hard drive is connected. Regardless of what drive, what USB port, what USB cable, and what power supply, it happens. It didn't do this until the 21st, so, since it happened out of the clear blue, judging from all the other I've been debugging with dozens of restores and testing combinations, it's a hardware error inside the PC. I disconnected ALL peripherals, except a mouse, keyboard, and external HD's. I connected different mice and keyboards via different means, from wireless to wired on different ports, so it's not those peripherals. When Explorer.exe/the Start menu crash, turning off the connected USB HDD and restarting makes the problem go away. Reconnect the device, and Explorer.exe/the Start menu crash. Since it happens regardless of the drive I connected, it's not one particular drive. It's not the particular USB port because I tried two on the back and one on the front. Since it happens on 2 different USB HDD's, both from WD but different models and capacities, it has to be a hardware error inside the PC. Either the motherboard, the RAM, the CPU, or the USB controller. Can't be the ports because regardless of port, regardless of whether they're front or back, it occurs. I've exhausted everything I can do at this point. After 3 days of testing, it will have to go to Best Buy for them to examine... who won't find anything wrong! I've been down this road before. It's a god problem. After jumping through hoops, spending money, there's no logical reason and no fix. God problems have no fixes. Beyond what Best Buy can do, which is nothing, I'll have to get another PC. Just a cheap one, though, as I'm still paying off one the I got in 2018!

ImgBurn doesn't do any image conversion at all. It just burns what you feed it. It can create images, but not convert between types. And, I don't think Mac is supported, so ImgBurn couldn't create those images, anyway, even if you did feed it a bunch of files to make it bootable.

Got and tested my DVD-R's. The good news is the WH16NS60 STILL likes those. At least the ones I got for now, but who knows if they're still quality MCC or if CMC made them. So, I can swap in my NS60 for the BDR-212 again. The bad news: now, I've got a serious bug that is not behaving to any logical behavioral pattern. After 45 to 60 minutes of being logged in, Explorer.exe/the Start menu "crash." Nothing runs and Windows cannot be restarted, forcing a power off. When Windows starts on ALL subsequent attempts, Explorer.exe/the Start menu "crash," rendering the system useless. What is so problematic is it does this on Windows 10 1909 images where it wasn't before. On two different 1909's. And on 1903 as well. The only image it's not doing on is the factory default image: Windows 10 1809. So, I may have to end up reinstalling everything! At least, though, doing that may be able to isolate the problem and I can fix my regular image installations. So far, I've upped 1809 to 1909 without an apparent manifestation of the problem. What's so annoying is the ONLY way to test this is after each debugging step to do NOTHING for an hour to see if it happens!

My DVD-R's should arrive tomorrow. New ConvertXToDVD gold version released! 7.0.0.69 - 0013736: [Bug] [VSORep] disabled emails appears on the pre-filled box - 0013764: [Bug] [VSORep] closed ticket if we cannot retrieve the status - 0013772: [Bug] Subtitles issue -> red subtitle with green border - 0013788: [Suggestion] [HELP MENU] Change "Report a bug" to "Support Center" + icon

Actually, turns out the problem was with that particular .VRO as I cannot recreate the issue by creating new multiple stream recorded VRO. So, the entire problematic4 GB VRO must be sent to VSO for analysis. I've already submitted another bug report with the files attached, but because of its size, it's awaiting pending approval for sending to VSO. Got an Amazon.com order just shipped today of some new Verbatim DataLife Plus inkjet printable MCC DVD-R's. I'll swap in the WH16NS60 for testing these DVD-R's and see if they work. If they do, then, the BDR-212 goes out of cycle and the NS60 is cycled back in as my primary use device.

Discovered a pretty fatal bug in ConvertXToDVD that goes back at least a year. If you import a VRO file that is made up of multiple recordings on a Panasonic DVD Video recorder, regardless of the contents running time, ConvertXToDVD only imports/converts 1 minute of contents. I regressed from 7.0.0.68 to 64 and it does it then, too. Even on 69 Beta. I know VRO works because this failing VRO is just under 2 hours and I had an over 2 hour VRO that converted in 64 a few months ago. The only difference was that VRO was one recorded stream, whereas this failing VRO is made up of 4 separate recordings. I submitted both a bug report and on the VSO forums.

There are command line switches to ImgBurn, but I've never used them before. You could create a .BAT file calling ImgBurn.exe with these parameters to automate the process. Then, all you'd have to do is create 10 different .BAT files because each one would have a different input/output name. Just double click on the .BAT file and it executes. However, someone else will have to tell you about the command line parameters, as I've never used them before, sorry.

Have you used this software before and it didn't do this? Because it seems to be the default behavior of the output of this software. To reload the video at the end of playback. However, since this appears to be BD Video related, I know next to nothing about how that behaves.

Funny, the exact same thing happened again on the first disc from a different stack of BD-R's! Medium corrupt error but a 2nd attempt to burn it starts. Weird. So, it must be something going wrong with this Pioneer crap. It seems the reason the 2nd attempt works is because no actual data was written before the failure. It says 0 KB written when I cancel the operation.

As he said, the problem is the authoring software you're using to create VIDEO_TS folders for DVD Video is starting automatic playback of the title when you play the disc. Now, if you mean automatic play means when you insert the disc it starts playing the Blu-Ray on your player, that's a problem with your Blu-Ray player.