Jump to content

LIGHTNING UK!

Admin
  • Content Count

    30,088
  • Joined

  • Last visited

Everything posted by LIGHTNING UK!

  1. This is a bit of an impossible problem to fix (nicely). Your drive is returning some bogus info as the program tries to detect the real start of the track (what would be knowns as Index 0 / the pregap). D 18:52:11 Sub-Channel - LBA: 146991 (32:41:66), Raw Data: 01 16 02 04 4E B2 00 64 82 CC 00 00 00 00 00 00 D 18:52:11 Sub-Channel - Original: 146991 (32:41:66), Wanted: 146991 (32:41:66), Got: 294132 (65:23:57) D 18:52:11 Sub-Channel - LBA: 146991 (32:41:66), Raw Data: 01 06 02 04 4E B2 00 64 82 CC 00 00 00 00 00 00 D 18:52:11 Sub-Channel - Original: 146991 (32:41:66), Wanted: 146991 (32:41:66), Got: 294132 (65:23:57) D 18:52:11 Sub-Channel - Bogus response data! D 18:52:11 Sub-Channel - LBA: 146992 (32:41:67), Raw Data: 82 02 02 C0 01 74 00 32 41 67 54 0C 00 00 00 80 D 18:52:11 Sub-Channel - Wrong Type! D 18:52:11 Sub-Channel - LBA: 146993 (32:41:68), Raw Data: 01 04 00 00 01 73 00 32 41 68 00 00 00 00 00 00 D 18:52:11 Sub-Channel - Original: 146991 (32:41:66), Wanted: 146993 (32:41:68), Got: 146993 (32:41:68) D 18:52:11 Sub-Channel - LBA: 146993 (32:41:68), Raw Data: 01 04 00 00 01 73 00 32 41 68 00 00 00 00 00 00 D 18:52:11 Sub-Channel - Original: 146991 (32:41:66), Wanted: 146993 (32:41:68), Got: 146993 (32:41:68) D 18:52:11 Sub-Channel - LBA: 146993 (32:41:68), Raw Data: 01 04 00 00 01 73 00 32 41 68 00 00 00 00 00 00 Your drive is returning invalid subchannel info for sectors 146991 and 146992 and that info is causing the program to loop as it attempts to find the real start of track 4 by applying an offset based on what the drive is reporting. For example, the '16' in the top line's 'Raw Data' is supposed to be the track number. Well... there aren't even 16 tracks on the disc! It also then magically changes it to 6 and yet everything else is the same. (6 is still wrong) That bit of code that is responsible for 'Analysing Tracks' is actually quite a complicated due to the fact that some drives have to be told to return info on sector X to get info on sector Y. It isn't just a case of trying sector Y and if you don't get the info, moving on. You have to work out what it's given you after your initial request and then apply an offset to what you ask it for the 2nd time. Some also jump around, so you'll ask for X and it'll give you Y+10. Then you'll ask again and it'll give you Y-5. It's a real pain in the a***. The best thing I can probably do in this situation (and what I've now done) is to implement a timeout whereby if no progress is made into narrowing down the true start of a track (and therefore end of previous track) within 30 seconds, it times out and moves onto the next one. I can see the current code narrowed yours down to just being left with those 2 problems sectors pretty quickly (around 3 seconds), and if the pregap is out by 2 frames (2/75th of a second) due to those issues, so be it. It's better it moves on (using what it has successfully figured out) than gets stuck for all eternity trying to perfect it. D 18:51:57 Session 1 -> Track 4 -> ISRC -> None Found! D 18:51:57 Sub-Channel - Previous Track End LBA: 0 (00:02:00), Current Track Start LBA: 147142 (32:43:67) D 18:51:57 Sub-Channel - LBA: 147141 (32:43:66), Raw Data: 01 04 00 00 00 00 00 32 43 66 00 00 00 00 00 00 D 18:51:57 Sub-Channel - Original: 147141 (32:43:66), Wanted: 147141 (32:43:66), Got: 147141 (32:43:66) D 18:51:57 Sub-Channel - New Current Track Start LBA: 147141 (32:43:66) ... D 18:52:00 Sub-Channel - Previous Track End LBA: 146990 (32:41:65), Current Track Start LBA: 146993 (32:41:68)
  2. LIGHTNING UK!

    Enable remote SPTI access

    That setup option just manipulates a few reg keys. Reinstalling over the top and enabling the option is fine. You won't lose your settings. You could follow this instead if you prefer... https://www.tenforums.com/tutorials/156422-enable-remote-access-removable-storage-devices-windows.html
  3. Sorry to be a pain... can I get 1 more log please?! Load the program and go into Read mode. Press the F6 key to enable Program Debug Mode (you'll notice a log entry) and then start the read again. *do not enable I/O debug mode (F8)* You don't need to leave it repeating the same thing over and over when it gets to track 4, just long enough to capture whatever it's looping on. I'll need the complete log of that session please. Don't crop it as I want to follow the program logic right from the start. Thank you!
  4. Thank you. Can you now go into Read mode and copy + paste all of the info from the box on the right when that disc is in the drive please.
  5. LIGHTNING UK!

    Mismatching ISO files from same DVD video disc

    It errors out like that because it predates UAC and used to be able to write to HKLM in the registry. Now it can’t. Run as admin and you won’t get the errors.... or ignore them as you have been doing. iFO RC is IFO file region code. It’s just a byte in the file where you can set which region the disc is for. That’s in addition to the regional code the disc itself might have.
  6. That doesn’t sound right. Lba out of range means it’s beyond the end of the disc. Can you provide a log showing that stuff at all please?
  7. LIGHTNING UK!

    Installer Fail...

    I don’t know what you’ve downloaded there, but it certainly isn’t the ImgBurn setup program (installer). What exactly did you click on when over at the digital digest website? Screenshot that site for me please and show me what you clicked on.
  8. I wonder when the discs were manufactured? Maybe they’ve deteriorated and the drive can’t reliably burn them now. You could try enabling the ‘perform opc before write’ option in the settings and see if that makes a difference.
  9. That info is beyond the 2048 bytes of user data in a CD sector and therefore not included in an ISO. As for making the drive burn as-is (errors and all), that's where RAW mode burning would come in - which ImgBurn doesn't support.
  10. LIGHTNING UK!

    Two instances of ImgBurn running?

    Yes, a properly connected ssd would be fine.
  11. The success one was too loud (it used to scare people), so I’m pretty sure I adjusted it down slightly.
  12. They could be important if the game checks for bits that are intentionally wrong. If your drive corrects them, it’s actually made them ‘wrong’ - and then the game may not play correctly. It could also just mean your image isn’t great in the first place.
  13. LIGHTNING UK!

    Two instances of ImgBurn running?

    Well... there’s only ever 1 active drive in the program at any time, so you can only burn to 1 drive at a time. Different instances can burn to different drives simultaneously, but your storage device(s) would need to be fast enough to support it.
  14. LIGHTNING UK!

    Mismatching ISO files from same DVD video disc

    The other two could still be modifying the contents of the disc as it’s being read. ImgBurn won’t be. You’d have to do a file comparison and see what's different between the two (three).
  15. LIGHTNING UK!

    Miscompare versus Read Error

    Correct
  16. LIGHTNING UK!

    Two instances of ImgBurn running?

    Yes
  17. LIGHTNING UK!

    Scrambled sector or bad sector?

    The file system on that disc was made by Toast on an Apple machine. It has nothing to do with the machines you’re using and that info doesn’t change if you ‘copy’ the disc. From best to worst, udf->Joliet->iso9660
  18. Some memory is probably being overwritten - bad! Go for restart rather than continue.
  19. LIGHTNING UK!

    Request. Convert bin/cue to .img

    BIN and CUE works fine with DAEMON Tools. I do not really think of 'IMG' as a format. To me, it's just a raw dump of the disc... equivalent to the BIN file (which is pretty useless without the CUE).
  20. LIGHTNING UK!

    ASCQ 0x90 errors, but disk appears to be good?

    Possibly. Posting the log would help.
  21. LIGHTNING UK!

    ImgBurn v2.5.8.0 Released!

    As usual, you can download it and view the changelog by visiting the main website. http://www.imgburn.com/ Special 'Thanks' to all the beta testers, translators and donors!
  22. LIGHTNING UK!

    Scrambled sector or bad sector?

    It might be getting the 'CubaseSX3Level1' name from an autorun file. It's correctly showing 'My Disc' when you look at the properties (matching what ImgBurn shows). ImgBurn displays the volume label from the (best) file system. It doesn't look at the autorun file. You can hover your mouse over where it says the volume label and it'll show you info from some other fields in the file system descriptors too.
  23. LIGHTNING UK!

    Scrambled sector or bad sector?

    I figured you’d be using the same versions on both machines, so anything that may or may not feature in the changelog for 2.5.8.0 wouldn’t come into it. Obviously I do not remember what I did when, it was years ago!
  24. LIGHTNING UK!

    Scrambled sector or bad sector?

    LRA is last recorded address. If you’ve got the track size, it isn’t overly required. Some drives don’t bother returning that info. The addition of ADIP info might be down to the date of the firmware in the LG drive. The adip info doesn’t change, even once you’ve burnt the disc. So the book type field will show the real type of disc. The last recorded info can be changed as a result of burning, and that’s where you’d then see a disc have its book type changed to dvdrom for compatibility reasons. As for the commas, that’s down to your regional settings. The program uses what your OS is configured for.
  25. LIGHTNING UK!

    Scrambled sector or bad sector?

    Are you able to try your Samsung drive in that other machine? It's quite a specific error and seems weird a drive would return it when reading a normal DVD-RW disc. Maybe you've some software on your PC that's messing with the error codes? There's nothing that can be done software wise to work around this issue. If that's really what the drive thinks the problem is, you just have to live with it. The firmware update might fix it, but you'd have to try and find a changelog for SB01 somewhere. FirmwareHQ is fine, we helped collect all the firmware and build it.
×

Important Information

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