Jump to content

LIGHTNING UK!

Admin
  • Posts

    30,521
  • Joined

  • Last visited

Everything posted by LIGHTNING UK!

  1. For whatever reason, if it's still saying it can't create an ISO of a multi track disc, the '/MODE BUILD' parameter can't be reaching the program and it's still stuck in Read mode.
  2. Yes, you should be able to just point build mode at the drive letter and have it make an ISO of everything on the disc as Explorer sees it. If you're having trouble with that, post the command line you're using.
  3. Ok, sticking with 4x, try enabling 'Perform OPC before write' in the settings and giving it another go. If that still doesn't work, you'll have to try some other discs to see if the drive is just faulty.
  4. Not really, it just takes an image of the entire disc. Use EAC or something like that.
  5. It would appear the drive is no good at burning those MKM-003-00 discs at 8x. Try burning at 4x instead.
  6. The error was from the OS (or filter/codec), not ImgBurn. The OS doesn't normally like paths over 256 (ish) characters. It'll usually start using the short names for folders when that starts happening (notice the path and '~' shown in mediainfo's info) but in this situation, I guess that couldn't happen. I could potentially do something in my code to help it along.
  7. I guess at this point I could do with trying the flac file for myself. Can you upload it somewhere, email it or whatever? You may have other filters that are being pulled into the graph and messing things up... it's hard to say without checking everything. All I know is that madFlac normally works just fine. It's what I'm using for such things and I have the same Win 7 SP1 x64 setup. Just one thing though, if you use ImgBurn to create your CUE file using the 'Create CUE' tool, can you screenshot the error box that pops up please when you add a flac file to the source box? The error message you've mentioned in your previous posts doesn't fit with what I seem to recall the OS saying when no suitable filters were installed. You may like to uninstall madflac, capture the error, install it and capture it again. Maybe you could also use something like InstalledCodec to create a report on your codecs. You can create an 'All Items' HTML report using the View menu and let me compare it to mine. http://www.nirsoft.net/utils/installed_codec.html
  8. Can you post the MediaInfo details of one of the Flac files please? Also, which OS are you running?
  9. It's not the CUE file. Take off K-Lite and just use the recommended madFlac one. Make sure it's installing itself properly as having things like UAC enabled etc can complicate things. Double check there's nothing funny about your Flac file too. Check their details using something like MediaInfo.
  10. My guess is the filter isn't installed properly or your files are in a format it can't decode.
  11. Why can't you copy and paste? Are you getting an error? It's no good just saying you can't. I don't want you to burn anything, just provide exactly what I've asked for. Of course I've looked through what you've posted. There's nothing you're doing wrong, your drive (or more likely, your machine) is just messing up. That's why I've asked for additional 'family tree' info.
  12. The cue is fine. You have a different file for each track, that's why its time doesn't change... You're always reading from the start of the file. Post the log from the burn please.
  13. Go into write mode, right click the drive selection box and pick 'family tree'. Close the box that comes up and copy + paste everything from the log window straight into your reply. There's no need for wordpad.
  14. The drive's OPC is nothing to do with ImgBurn, so uninstalling / reinstalling doesn't touch it. There's no reason for your drive to behave differently in your new machine. It's a piece of hardware and should be no more / less capable of burning discs now than it was before. If your old PC is still usable, put the drive back in it and try it again. Do not clear OPC each time, it's there so the drive can 'learn' how to burn. I said to do it once so it cleared out anything weird, after that you shouldn't touch it again.
  15. Did you clear the drive's OPC history like I told you to in my previous post? Please do a kprobe scan on that disc @ 4x and post a screenshot of the final graph (not just the results/numbers/figures). Maybe your drive needs cleaning or you've got a bad batch of discs.
  16. Please just copy + paste the *full* log from the Log window (or full session log from log file if you've closed the app down). You can access the auto-saved log via the 'Help' menu.
  17. This stuff is easy to Google. Read up on what m-disc actually is. http://www.mdisc.com
  18. 1. yes 2. I've no idea. If you want really durable media, buy some M-Disc discs.
  19. Sorry but you're going to need to update your version of ImgBurn for us to even begin tying to help you. 2.5.8.0 is the current one.
  20. You can't go far wrong with Taiyo Yuden CDs and Verbatim / Taiyo Yuden DVDs.
  21. It has settings but you don't need to touch them, it works just fine with the default ones.
  22. I very much doubt that other application even attempted to zero the sectors. Zeroing is effectively the same as burning data to the disc (just with zeros rather than actual data) and your drive seems unable to do that... so you should expect a real write operation with real to fail too.
  23. It doesn't contain malware. It contains a plugin that offers you 3rd party software. That can offer various different things (from a wide range - toolbars, browsers, other apps etc) but you're free to opt out of installing them. 2.5.7.0 (and a good few versions before that) was bundled with the ask.com browser toolbar and you had to opt out of that too if you didn't want it. So recommending one over the other is daft. You want the latest one so you have the new and improved features / bug fixes.
  24. Same problem without the port multiplier? I.e. Just one drive at a time. It's erroring out after about 10 seconds so that's probably just something the controller card or multiplier is doing. The program sets a much longer timeout as optical drives need that - it's being ignored. Maybe a firmware or driver update for the card would help?
  25. Same problem at the other supported write speeds? Try another spindle of discs and perhaps cleaning the drive with a cleaning disc.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.