Jump to content

LIGHTNING UK!

Admin
  • Posts

    30,514
  • Joined

  • Last visited

Everything posted by LIGHTNING UK!

  1. calweycn, The reason everyone denies these claims is that no burning program has control over the 'quality' of the burn. There's not some magical setting you can adjust to raise / lower PI/PO error rates. You take a chunk of data from a file, send it to the drive via the 'Write (10)' command, then repeat the process again until you've sent all the data. With that in mind, I don't see how using *ANY* program could have a direct impact on burn quality.
  2. Your player might not like those discs. It might like them slightly better if you could booktype them to DVDROM rather than leaving them on DVD+R. Can't remember if the NEC 2510 actually supports that though.
  3. 'Sectors To Load' should be on 4. Incase that makes a difference! I hope you're testing this stuff on CD-RW's
  4. Is it really slow dragging windows too? Sounds like your graphics card isn't accellerating things properly. Is the performance slider (in display properties) right upto the max level? Could also be that you're on a bad driver. Take a look and see if there's a newer one.
  5. What emulation type did you use? I believe it needs to be on 'None (Custom)'. It would be easier (and better) to just get your mate to copy the entire cd for you. I don't think there is anything wrong in doing that, the license sticker / bit of paper is what you've paid for. Obviously it'll have to be the same version as the one you did have - i.e. Professional OR Home edition.
  6. db, Get us a screenshot from the 'Disk Management' mmc snapin.
  7. Your post had words / sequences of characters that the server checks for and doesn't allow. It's a security thing and is nothing to do with me or this forum.
  8. I would be totally amazed if Roxio could burn to that media. Your drive can't initialise it and so NO program would even know there's a disc in the drive. If says 'Medium Not Present' in the statusbar because that's the error message being returned by the drive when ImgBurn queries it to see if it's 'Ready'. ImgBurn cannot display any info about the drive in that panel on the right (normally it would put a lot more than 2 lines in there) because the drive doesn't support the media you're using. When it's like that, the box is disabled too - hence why you can't copy / paste the 2 lines that it DOES say. The firmware update may help if it add support for the media you're using. Personally I would try to buy some 8x DVD+R as you stand a better chance of that working. You need some discs that have been around for a while!
  9. lol the real v2.1 should be out today / tomorrow if testing doesn't throw up any problems. I released (what I hope is) the last beta in this series last night to the testers.
  10. If I can find some, I'll get some.
  11. There is an option for that already in the settings. It's on the 'General' tab.
  12. Do you mean 'Build' rather than 'Burn' ? You can save / load projects that can store folder selections etc. It's possible to pass the project file via the CLI. So you could make a batch file and stick it in your scheduled tasks folder.
  13. btw, I'm sure all that stuff is explained in the guide. I knew there was a reason we (well ok, Corny!) made those things!
  14. Just make sure you get the DVD+R / DVD+RW type! Your drive doesn't seem to support DVD-R or DVD-RW.
  15. Have a go burning some MCC (typically Verbatim) or TY (Taiyo Yuden) discs instead. Basically your drive is having problems writing to (the outer edge?) of those discs. I believe your firmware is up-to-date so that only leaves 'try different media' on the 'things to do' list.
  16. Regardless, burning something and you not getting sound is nothing to do with the software you used. Your problem is with whatever made those files, or of course with whatever you're trying to play the disc on. Either way, it's not support for ImgBurn that you require and so this isn't the best place to find your solution.
  17. There was a specific reason I couldn't make the queue behave in that way. It's because the 'Information' box always shows the settings for the FIRST selected item. Events get called when boxes are ticked etc and they run even when you (the user) are just selecting an item - and hence ImgBurn populates the controls with your current settings for that image. So basically, if I made a 'tick' of a box apply to all selected images, by simply selecting the image (without any manual 'ticking'), the images would all have that option ticked. Also, if images have different settings, how do I show a combination based on ALL the selected images values? I'd need some overriding checkbox to say 'Right, apply this setting to all selected images'. That would probably best be done in a different screen. That's all very complicated to try and explain... but basically I had my reasons for doing it how it's done and not how we'd both like it to be! So basically just remember that the options apply to the single image who's name is also specified in the 'Information' box. That image is the top one in the selection. I guess I could make it so that if multiple items are selected the options can't be changed. At least others wouldn't then fall into the same trap you have. That of course then limits the functionality behind the 'copy settings' stuff on the context menu. You'd have to deselect all but one image in order to make changes, before you can then apply them to others having reselected them. I've noticed the focus issue too myself and have fixed that already for v2.1. It does it because when you tick a checkbox, it jumps you into the combobox associated with it. Because selecting an item in the list also causes the box to 'tick' itself (if that option is enabled for said image), it also runs the event that then jumps focus over to the combobox. As you've seen yourself, it doesn't matter if you use the keyboard or the mouse to change select different images, the focusing problem remains.
  18. lol especially when you're the same person that created that other thread! You do realise we weren't born yesterday yeah? 10/10 for effort though
  19. Well just make sure you have the full thing there in the first place! Nobody ever said you could take the main files of anything and play them as if it were a complete dvd - you can't!
  20. Hmm you've actually brought another problem to my attention now with this thread. If DVD+R discs pad out to a full ECC block, that then mean 'my' last sector on the disc (so far as 'build' mode is concerned) is no longer the actual last sector - it's potentially 15 sectors before it. That basically means my UDF backup Anchor point is wrong because it's supposed to be in the last sector on the disc. The backup one is only used if the first (sector 256) is unreadble so it's not exactly a major issue, but I still had to fix it So now I pad the images I make after all the filesystem data and before the UDF backup anchor point, ensuring the last sector of the image lands on the last sector of an ECC block. This will also have the effect of the image + device MD5 hashes being equal even when burnt to DVD+R - because I'm doing the padding rather than the drive. I'll still leave the 'Device (Padded) MD5: xxxxxxx' value in the log though for times when you're burning images that don't align to ECC blocks properly and so the drive DOES have to do its own padding.
  21. Geez... still can't find it?! Were you even looking for it?! lol
  22. Sorry davidw89, you're not going to change my mind! The answer remains at 'No'. The 'smart' thing would be for LG to make the bitsetting stuff persistent between reboots/power cycles in the same was all the other manufacturers do.
  23. Well I (we) can't comment on your stuff with DVD Dec. If the source files are ok (or source image), the burnt disc should be fine too.
  24. Didn't you just say you'd done the original again with DVD Shrink and burnt it with ImgBurn.... and that plays ok? If so, I'm not sure I understand what the problem is now exactly.
  25. The MD5 is calculated by passing the data (every sector / byte) read from the disc (or image file) to some API microsoft provides. Once you've given that API all the data, you run another API command to calculate the MD5 (or any other type of value you want) from it. As I don't read the extra padding sectors from the DVD+R, there's no way to append that to a second MD5 calculation. I'm also not sure if I can get the MD5 and then add more data before calculating it a second time. EDIT: Ok, I can't add data after I've calculated the value. What I can do though is duplicate the hash before I calculate it, then add data to the duplicate before calculating that one. I will add a 'padded' MD5 value to the log for DVD+R discs.
×
×
  • Create New...

Important Information

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