Jump to content

All Activity

This stream auto-updates     

  1. Today
  2. MisoMaso

    I/O Error while varifying

    Thanks for the advice. So I converted the files to ISO, updated my drive to the latest firmware, and perhaps most importantly, tried Panasonic BD-RE DL this time. I successfully burned the movie to the disc and have no problem playing it on my Blu-ray player.
  3. Please post a new log from the current version of ImgBurn and a drive / media combo that should actually work
  4. Yesterday
  5. Sorry, I should have been clear. I have tried three drives. And yes, the last one, stupidly, is not a BD writer. My bad. It doesn't burn DVD's. i get that error. But it has been the same results with all drives. I am really unsure what gives. i am now pulling all cables and replacing them and taking a drive I know works 100% from my other system and transplanting it.
  6. That drive can't burn BD discs, only read them. It should be able to burn DVDs and CDs though. Also, you should update to the current release of ImgBurn.
  7. Hey all, I have a Shuttle XPC SZ77R5 that is baffling me. The internal LG drive can read DVD's and BD's just fine. But I am unable to burn anything. I have pretty much an immediate failure with error Invalid Operational Code. I have tried different burners, switching from SATA 2 to 3 to 4, all with no success. However, I can attach an external drive via USB 3.0 and burn just fine. The PC is running Windows 7 Ultimate retail upgrade 64 bit. All drivers seem updated. I am baffled and ready to wipe the drive and do a clean install, but wanted to post here first. I 14:29:22 ImgBurn Version 2.5.5.0 started! I 14:29:22 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7601 : Service Pack 1) I 14:29:22 Total Physical Memory: 16,741,052 KB - Available: 12,983,448 KB I 14:29:22 Initialising SPTI... I 14:29:22 Searching for SCSI / ATAPI devices... I 14:29:22 -> Drive 1 - Info: HL-DT-ST BDDVDRW UH12NS30 1.00 (D:) (ATAPI) I 14:29:22 Found 1 BD-ROM/DVD±RW! I 14:29:48 Operation Started! I 14:29:48 Building Image Tree... I 14:29:48 Calculating Totals... I 14:29:48 Preparing Image... I 14:29:48 Contents: 58 Files, 14 Folders I 14:29:48 Content Type: BD Video I 14:29:48 Data Type: MODE1/2048 I 14:29:48 File System(s): UDF (2.50) I 14:29:48 Volume Label: [Not Configured] I 14:29:48 Size: 24,021,816,669 bytes I 14:29:48 Sectors: 11,729,440 I 14:29:48 Image Size: 24,023,072,768 bytes I 14:29:48 Image Sectors: 11,730,016 I 14:29:48 Operation Successfully Completed! - Duration: 00:00:00 I 14:30:36 Operation Started! I 14:30:36 Building Image Tree... I 14:30:37 Calculating Totals... I 14:30:37 Preparing Image... I 14:30:37 Contents: 58 Files, 14 Folders I 14:30:37 Content Type: BD Video I 14:30:37 Data Type: MODE1/2048 I 14:30:37 File System(s): UDF (2.50) I 14:30:37 Volume Label: Space Adventure Cobra I 14:30:37 Size: 24,021,816,669 bytes I 14:30:37 Sectors: 11,729,440 I 14:30:37 Image Size: 24,023,072,768 bytes I 14:30:37 Image Sectors: 11,730,016 I 14:30:38 Operation Successfully Completed! - Duration: 00:00:02 I 14:30:38 Operation Started! I 14:30:38 Source File: -==/\/[BUILD IMAGE]\/\==- I 14:30:38 Source File Sectors: 11,730,016 (MODE1/2048) I 14:30:38 Source File Size: 24,023,072,768 bytes I 14:30:38 Source File Volume Identifier: Space Adventure Cobra I 14:30:38 Source File Volume Set Identifier: 4D8B73D200B2FBC0 I 14:30:38 Source File Application Identifier: ImgBurn v2.5.5.0 I 14:30:38 Source File Implementation Identifier: ImgBurn I 14:30:38 Source File File System(s): UDF (2.50) I 14:30:38 Destination Device: [0:1:0] HL-DT-ST BDDVDRW UH12NS30 1.00 (D:) (ATAPI) I 14:30:38 Destination Media Type: BD-R (Disc ID: OTCBDR-002-000) (Speeds: 40x, 48x) I 14:30:38 Destination Media Sectors: 12,219,392 I 14:30:38 Write Mode: BD I 14:30:38 Write Type: DAO I 14:30:38 Write Speed: 4x I 14:30:38 BD-R Verify Not Required: Yes I 14:30:38 Link Size: Auto I 14:30:38 Lock Volume: Yes I 14:30:38 Test Mode: No I 14:30:38 OPC: No I 14:30:38 BURN-Proof: Enabled W 14:30:38 Write Speed Miscompare! - Wanted: 17,983 KB/s (4x), Got: 48,768 KB/s (11.1x) I 14:30:39 Filling Buffer... (40 MB) I 14:30:39 Writing LeadIn... W 14:30:39 Failed to Write Sectors 0 - 31 - Reason: Invalid Command Operation Code W 14:30:39 Retrying (1 of 20)... W 14:30:39 Retry Failed - Reason: Invalid Command Operation Code W 14:30:39 Retrying (2 of 20)... W 14:30:39 Retry Failed - Reason: Invalid Command Operation Code W 14:30:39 Retrying (3 of 20)... W 14:30:39 Retry Failed - Reason: Invalid Command Operation Code W 14:30:39 Retrying (4 of 20)... W 14:30:39 Retry Failed - Reason: Invalid Command Operation Code W 14:30:39 Retrying (5 of 20)... W 14:30:39 Retry Failed - Reason: Invalid Command Operation Code W 14:30:39 Retrying (6 of 20)... W 14:30:39 Retry Failed - Reason: Invalid Command Operation Code W 14:30:39 Retrying (7 of 20)... W 14:30:39 Retry Failed - Reason: Invalid Command Operation Code W 14:30:39 Retrying (8 of 20)... W 14:30:39 Retry Failed - Reason: Invalid Command Operation Code W 14:30:39 Retrying (9 of 20)... W 14:30:39 Retry Failed - Reason: Invalid Command Operation Code W 14:30:39 Retrying (10 of 20)... W 14:30:39 Retry Failed - Reason: Invalid Command Operation Code W 14:30:39 Retrying (11 of 20)... W 14:30:39 Retry Failed - Reason: Invalid Command Operation Code W 14:30:39 Retrying (12 of 20)... W 14:30:39 Retry Failed - Reason: Invalid Command Operation Code W 14:30:39 Retrying (13 of 20)... W 14:30:39 Retry Failed - Reason: Invalid Command Operation Code W 14:30:39 Retrying (14 of 20)... W 14:30:40 Retry Failed - Reason: Invalid Command Operation Code W 14:30:40 Retrying (15 of 20)... W 14:30:40 Retry Failed - Reason: Invalid Command Operation Code W 14:30:40 Retrying (16 of 20)... W 14:30:40 Retry Failed - Reason: Invalid Command Operation Code W 14:30:40 Retrying (17 of 20)... W 14:30:40 Retry Failed - Reason: Invalid Command Operation Code W 14:30:40 Retrying (18 of 20)... W 14:30:40 Retry Failed - Reason: Invalid Command Operation Code W 14:30:40 Retrying (19 of 20)... W 14:30:40 Retry Failed - Reason: Invalid Command Operation Code W 14:30:40 Retrying (20 of 20)... W 14:30:40 Retry Failed - Reason: Invalid Command Operation Code W 14:31:47 Retrying (21)... W 14:31:47 Retry Failed - Reason: Invalid Command Operation Code E 14:31:49 Failed to Write Sectors 0 - 31 - Reason: Invalid Command Operation Code I 14:31:49 Synchronising Cache... W 14:31:49 Synchronise Cache Failed! - Reason: Invalid Command Operation Code W 14:31:49 Retrying (1 of 3)... W 14:31:49 Retry Failed - Reason: Invalid Command Operation Code W 14:31:49 Retrying (2 of 3)... W 14:31:49 Retry Failed - Reason: Invalid Command Operation Code W 14:31:49 Retrying (3 of 3)... W 14:31:49 Retry Failed - Reason: Invalid Command Operation Code E 14:31:53 Synchronise Cache Failed! - Reason: Invalid Command Operation Code W 14:31:58 User opted to skip the 'Close Track/Session/Disc' functions. E 14:31:58 Failed to Write Image! E 14:31:58 Operation Failed! - Duration: 00:01:19 I 14:31:58 Average Write Rate: N/A - Maximum Write Rate: N/A shit list.log
  8. Last week
  9. bulele79

    Spanish international 2.5.8.0

    Thank you so much.
  10. I hope you tried to recreate a disc before chucking them ! Iv'e found a little utility called floppyimage (floppyimage152.zip) . Works great and re-creates a bootable disc which tested OK.
  11. dbminter

    DVD+R DL help

    Eh, it happens. I was mostly being facetious. As I said before, before you proceed, you need to test that your source MKV plays okay and that the VIDEO_TS you're trying to burn is DVD Video compliant. Before going on, if they are corrupt somehow, no number of burns you make will make a difference. However, your new errors with a new drive are something entirely different, it seems.
  12. cholla

    DVD+R DL help

    Did you play the source file that you are creating the Video_TS folder from in a media player ? VLC or MPC-HC should be good for this. Did you test the Video_TS folder created in a media player to see if it will play before attempting to burn it ? Did you try DVDShrink as first suggested by dbminter to see if the Video_TS folder gave an error ? @ dbminter , I read a bit too fast & missed the DVDShrink in your earlier post.
  13. I always used WinImage to make images of my floppies, particularly bootable ones. So, why you can't get it to work is beyond me.
  14. Thanks for that info. I'll keep on looking for something to do the job If anyone has any other software suggestions then please let me know.
  15. CIRUCIAL

    DVD+R DL help

    Update: okay so I downloaded a new program called AVStoDVD after reading about how DVDflick hasnt been really updated in a long time and it's not the best for .MKV videos. After using this to get the VIDEO_TS file I now am having a writing sectors problem that ends up freezing and then crashing the computer. since opening this topic I got a new faster DVD recorder and I can't tell if it is bad or what. Several times it has vanished from Device Manager and to get it back into working condition I need to BIOS check for it and once I click it for boot device it comes back to working condition. So I have wasted 2 disc from it writing about 4% and 11% before it freezes.
  16. LIGHTNING UK!

    3.5" floppy read to file (then write to floppy)

    I’m sure winimage must be able to open its own images. It would be useless otherwise. When ImgBurn reads the floppy to an image, it’s a straight sector dump of the disk. There is no method of writing that back to a floppy disk within the program. It’s meant for use when building a bootable optical disc.
  17. I have tried winimage and get an error when trying to recreate disk - "current image format is not supported" As regards imgburn I was looking at the bottom of the comholio7 document - - http://forum.imgburn.com/index.php?/topic/1779-imgburn-build-mode/ "'Create Boot Image' can be used to read a bootable floppy disc to an image, or extract an existing boot image from a bootable CD. You just need to select the source drive and then click on the picture of the floppy disc. It'll ask you for a name for the image and then start creating it. It's is this type of image that the above mentioned 'Boot Image' option would point to."
  18. LIGHTNING UK!

    3.5" floppy read to file (then write to floppy)

    Try winimage, it’s what I always used to use.
  19. Imgburn has some capability for floppy discs. The main purpose is to take an archive and be able to recreate the disc if needed. There are very few windows programmes that are able to create an image archive. WinImage, MagicISO, etc, etc are all a bit flaky.
  20. LIGHTNING UK!

    3.5" floppy read to file (then write to floppy)

    ImgBurn is for optical drives and discs, not floppy drives / discs. Windows can copy a floppy disc.
  21. Hi . I've been looking for tips/hints as to how to read a bootable 3.5" floppy to a file using imgburn - Then recreating a bootable clone on a blank disk. Build mode seems to be the only way of getting some image files - a 1920kb ISO and a 5kb mds. To recreate the disk I'm assuming you have to use build mode again however you cant just select a:\ as destination (it needs a file or folder !!!) Also the make image bootable checkbox wants a boot image file . What do i Input in this field ? Any help useful. Thanks.
  22. dbminter

    DVD+R DL help

    I hope it's okay to recommend DVDShrink to test with in this case; I already did that earlier! I didn't think to ask. VLC would also work; I also recommended Media Player Classic Home Cinema since that's what I use.
  23. cholla

    DVD+R DL help

    I used DVDFlick way back & even then it was hit & miss. Try Open Files with DVDShrink with the VIDEO_TS folder you created. I've found DVDShrink a good tester . If it gives an error then that Video_TS probably won't write(burn) to disc. I hope it's OK to recommend this software here. Try AVStoDVD instead of DVDFlick. There is some learning curve on it but you should get a playable burnable file. One other thing to check: Will the file you are trying to convert with DVDFlick play in any media player ? VLC for example.
  24. dbminter

    DVD+R DL help

    You should still check the VIDEO_TS output and make sure it actually plays. There's no guarantee DVD Flick made the contents right. If the VIDEO_TS folder isn't DVD Video compliant, using Nero won't make a difference.
  25. CIRUCIAL

    DVD+R DL help

    I am using DVD flick so I guess ill use Nero since I did all the appropriate steps with flick Thanks for the help guys
  26. LIGHTNING UK!

    I/O Error while varifying

    There are firmware updates available for your drive. A newer one may perform better with the media you're trying to use. https://www.firmwarehq.com/Pioneer/BDR-206/files.html
  27. dbminter

    I/O Error while varifying

    I agree. Try something better than Riteks. I know on my PS3, Ritek BD media causes skips during playback. Verbatim BD-R don't. So, try some Verbatim BD-R and see if your drive likes those better.
  28. Ch3vr0n

    I/O Error while varifying

    From the log 20:44:33 Destination Media Type: BD-R (Disc ID: RITEK-DR3-000) Use better quality blanks Verstuurd vanaf mijn Nexus 6P met Tapatalk
  1. Load more activity
×

Important Information

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