Jump to content

LIGHTNING UK!

Admin
  • Posts

    30,521
  • Joined

  • Last visited

Everything posted by LIGHTNING UK!

  1. Always burn at 4x in that drive. The 2.4x write strategy seems a bit dodgy... in fact, even 4x is a bit hit and miss (well, with my drive anyway). Hopefully the next firmware update will resolve these issues.
  2. Start your own thread please Mohammad Atfan Iqbal.
  3. ImgBurn see's my hddvd just fine, the issue here is that I perhaps don't detect HDDVD capabilities properly in 2.3.2.0. This is purely cosmetic and it should still work fine. The drive will only show up in Read / Verify modes as it's just a reader and not a burner.
  4. You can't see the file system stuff, all you see is actual file data and that's not what I was talking about. The LBA of the file data is not important at all for the type of data the OP is burning. The (current version of the) program burns the actual files in alphabetical order within their respective folders. It does this one level at a time. i.e. root\1 root\2 root\3 root\1\1 root\1\2 root\2\1 root\3\1 root\3\2 root\1\1\1
  5. It doesn't matter who the discs are branded by. If the dye they're using is rubbish then they'll still be rubbish.
  6. The drive isn't showing any supported write speeds so I doubt it can handle them at all. If a firmware update doesn't fix it (or isn't available) then you're stuck. Buy Verbatims in future.
  7. Look at the 'supported write speeds' text in the info panel on the right. It doesn't matter what you tell the program to write at, the drive will only ever write at those speeds. The program doesn't control the actual speed, the writer does. Please stop it with the abuse towards other member or I'll make sure the door slams behind you on your way out.
  8. This doesn't sound like it's anything to do with ImgBurn, try another forum.
  9. lol yeah that's a lame suggestion Jason
  10. That is very odd then as it's only the same messagebox function that's being called.
  11. Don't burn at 4x, new drives are optimised for speed, especially with decent media. Go for 8x at least (12x would be fine). How did you solve the FSCTL_LOCK_VOLUME error? Hopefully not by just turning off the 'exclusive access' option! It's very unusual to get the 'Invalid Address For Write' as the first error. Normally it occurs after a write error but your log doesn't show anything like that.
  12. lol what exactly did I fix?! Just looks like it's not reporting the correct size for the disc and that's your drives problem really. If you compare image sizes, the drive says: I 10:37:20 Source Media Sectors: 53,442 Yet the RN one said I 10:52:30 Image File Sectors: 53,440 (MODE1/2048) That's 2 sectors different. As I go by what the drive reports in response to being issued the 'Get Capacity' command, I can only assume the info it provides via the 'Read TOC' one is different (again, this is a drive problem). Copy + paste the info from the right panel in ImgBurn (with the dodgy disc in the drive) and we'll know for sure.
  13. Basically, at the moment your drive is producing really bad (low quality) burns on the media you're using. So bad in fact that it then can't read back what it's just written (that's what the 'Verify' stage checks for). If you use decent quality media in your drive then the burn quality will improve and your problems will go away.
  14. How truncated exactly? Your player would probably support ISO9660 and Joliet file systems. Maybe you've switched it to ISO9660 + UDF within ImgBurn, hence your player is stuck using ISO9660 which is limited to file names of 8.3 characters long (i.e. xxxxxxxx.yyy). Make sure the 'file system' option is set to ISO9660 + Joliet + UDF (or just ISO9660 + Joliet) and try again.
  15. You should probably slow the scan speed to 4x too.
  16. Put a disc in your drive and read it from the info panel on the right. Drives do seem to jump between 1 of 2 numbers when they initialise the discs though - and of course DVD+R is different to DVD-R.
  17. Try again with decent Verbatim / Taiyo Yuden media. You might also like to consider crossflashing to the real firmware as that drive is an OEM Lite On SOHW-1653S.
  18. How does your player display the file names? Are they truncated or still the same as when they're on your hdd?
  19. lol I'd love it if he did. I'd certainly be more interested in watching TV about politics! Clarkson rules!
  20. Yup, they appear to be.
  21. Don't pay over the odds for the Plextor, I'm pretty sure it's just a rebranded Pioneer 112/212.
  22. The order wouldn't be anything to do with me, surely that's down to your player.... or rather *you* pressing play on the right file?! They're stored in alphabetical order within the file system (as is required by the specs).
  23. Yup and then you can just press the green down arrow with the red 'x' int it (on the toolbar) to move between the untranslated strings.
×
×
  • Create New...

Important Information

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