-
Posts
30,522 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by LIGHTNING UK!
-
That's better Ok so the PdhAddCounter(\PhysicalDisk(_Total)\Avg. Disk Queue Length) function is getting stuck and not returning control to the program. You may find it's logged something in Event Viewer (Control Panel -> Administrative Tools). Anyway, now load up 'Performance' - again, Control Panel -> Administrator Tools. See which counters are automatically loaded when it starts. If you right click the big graph area a menu should appear. Click 'Add Counters'. Change 'Performance Object' to 'PhysicalDisk'. Select 'Avg. Disk Queue Length' in the 'Counter' box and '_Total' in the 'Instances' box. Then click ok. Let me know if all of that is possible / works ok.
-
It's not a problem. Just a little odd you didn't notice that window pop up after you clicked 'Calculate'.
-
What does it say when you try to open it? It already had an ex_ extension, it just needed to be changed to exe. If your system isn't configured to show file extensions, that could be where the confusion is coming from.
-
That 'Create Layer Break Position' window is waiting for your input. If you don't know what you're doing, read the guides - that's what they're there for! This one applies to you/what you're doing. http://forum.imgburn.com/index.php?showtopic=4643
-
Ok, email sent. It should be with you in 5 - 10 mins. Don't forget to check your spam/junk folder for it.
-
Can you get a me a screenshot of the entire screen? Or just enough to show all of ImgBurn's windows.
-
Right, I'm going to have to send you an updated version of ImgBurn so you can repeat the process with that. Is it ok to use your forum email address? Can you not kill ImgBurn's process via Task Manager rather than rebooting?
-
oh damn, I forgot about that You'll have to find a single layer (4GB) image to test with. And that log shows you missed pressing F6!
-
Ok cool, here's what you do... Load the program Make sure buffer recovery is enabled in the settings (if you haven't touched it then don't worry about checking it) Click the write image file to disc button Load your ISO (use the same one that failed to burn before, don't worry that it won't fit on a DVD-R disc) insert DVD-R disc make sure the 'Test Mode' box is ticked. Press the F6 key - you should see a log entry saying debug has been enabled. *this is very important* Start the burn. At this point you'll have to just accept the message about it not fitting on the disc. Once it's burning, fire up defrag quickly and set it going on the same drive as where your source ISO image is located (i.e. C:\ drive) What we're aiming for is being able to swamp the hdd with multiple requests so it can't provide ImgBurn with enough data - thus forcing buffer recovery to kick (and get stuck). If just running defrag alongside the burn isn't enough to kill the buffer levels in ImgBurn, try starting a full virus scan on the drive too or something. Once you get the 'Waiting for buffers to recover' message in ImgBurn's log window, let them recover (stop defrag/virus scan etc) and see what happens next. It'll either remain stuck on that message as per the reason for this thread, or it'll work properly and get back to 'writing sectors' - where you'll then have to do it all again and hope it gets stuck!
-
Ok, before we get into the technical stuff, I need to know something... Do you have any rewritable, CD-R or DVD-R discs? (otherwise these tests will cost you a disc each time and I don't like doing that to people)
-
Your options are mentioned here - http://forum.imgburn.com/index.php?showtopic=8000
-
Still no good in what way? I thought you were just going to disable buffer recovery and ignore the problem? Have you reproduced the issue when burning a rewritable disc / DVD-R with test mode enabled?
-
Ok so just switch the 'Data Type' option to 'MODE2/FORM1/2352' and the 'File System' option to 'ISO9660'. Burn and see if it works. If that doesn't work, try with the 'File System' option set to 'ISO9660 + Joliet'. With the right combination of options, there's no reason we shouldn't be able to get ImgBurn producing a working disc. Once we've figured it out, I can make the program detect a firmware disc build and automate setting the correct options (to make it easier for others / you in the future).
-
Yes. Try not to use your machine too much when burning, even just downloading etc - anything that uses the hdd will kill the sequential transfer rate and that will empty out the buffers if it goes too low. Turning buffer recovery off won't stop the buffers running out - you just won't be told about the issue when it's off. When they run out, the device buffer will be all over the place. When that happens, drive has to keep turning the laser on/off and basically 'pausing' the burn - and that's something you want to try and avoid. The idea behind buffer recovery is that the drive only has to do that once.
-
Ah, if it does it every time, we could do some digging and work out exactly where it's getting stuck and try to fix it properly. Buffer recovery kicks in when your hard drive isn't providing data quickly enough - so you could semi force the situation by doing something like running defrag whilst trying to burn. You could be burning to a rewritable disc or a DVD-R with Test Mode enabled so as to not waste any discs. If you're not interested in getting to the bottom of it then you can take the easy way out... If you disable buffer recovery, that whole chunk of code will no longer get called/run. If it's not called/run, it can't get stuck.
-
It's impossible to say exactly where it's stuck based on the info you've provided. It looks like the program has run into difficulty somewhere between filling up the buffer and checking the disc activity level. Does it get stuck like that *every* time the program mentions 'waiting for buffers to recover' ? I expect ImgBurn is just waiting for a Windows API function to complete processing. Disabling 'Buffer Recovery' would get around the problem but ideally you'd figure out why your system gets stuck in the first place - obviously it's not meant to!
-
Nothing is jumping out at me as being obviously wrong. It burnt and verified ok so ImgBurn did its job. It could be an issue with the source files or that the PS3 doesn't like media you're using - I honestly couldn't tell you. Have a look at some more 'generic' forums (i.e. Doom9) - you'll probably find a lot more people on them doing what you're trying to do.
-
It's highly unlikely.
-
Try it with Mode2/Form1/2352 instead.
-
Like I said, read the thread. http://forum.imgburn.com/index.php?showtopic=8000
-
Oooooh, if it's a small image (less than 1GB in size), DT will emulate a CD-ROM rather than a DVD-ROM. Mount the MDS that ImgBurn created rather than the ISO and you'll be ok. It'll force DT to emulate a DVD-ROM.
-
Playing the VOB isn't the same as playing the IFO. The region checks will only take place when playing the DVD Video disc properly (i.e. via the IFO). Your virtual drive might be emulating a region 1 device and the decoder might be set for region 2 (or vice-versa). Make sure the virtual drive is set for region 2. (you can do it via DT's system tray tool)
-
There's no such thing. Try playing the disc (mounted image) in the likes of 'Media Player Classic - Home Cinema' instead.
-
Change the I/O interface back to SPTI. There's no reason and you don't want to be using Patin-Couffin. Read this: http://forum.imgburn.com/index.php?showtopic=8000
-
If those screenshots are accurate (and round the right way), stick to burning the Maxell (RITEKF1) discs at 16x. Your drive does a better job of burning them at 16x than it does at 6x or 8x.