Jump to content

Sizzlechest

Members
  • Posts

    46
  • Joined

  • Last visited

Posts posted by Sizzlechest

  1. 18 minutes ago, dbminter said:

    Are you using the same WH16NS40's crossflashed to WH16NS58 on these new HP Elitebooks or are you using different drives that came with the HP's?  Those drives in the HP's may have drives that don't support DiscSpeed.

     

    BTW, I've not heard of the WH16NS58.  I have heard of the WH16NS40 and the WH16NS60, but never the NS58.

    Same drives. I'm beginning to wonder if Windows 10 might be another factor. I'm trying to remember if we upgraded the old PC from Windows 7 or not.

    The WH16NS58 is what Primera uses in their duplicators. The WH16NS40 used to be a different drive, but at some point they used the WH16NS58 drive and hobbled the firmware.

    EDIT: Okay, I found the problem. The registry entry for Blocked needs SOMETHING in there. It can't be blank. DOH!

  2. I have a bunch of LG HL-DT-ST BD-RE WH16NS40 drives cross-flashed to WH16NS58. Nero Discspeed can do quality scans on DVD and DVD-DL discs with these drives. We moved from desktop computers to HP Elitebooks and now Discspeed no longer seems to offer the quality tab. (Yes, I took out the "Blocked" string in the registry.) There's no way to play with the SATA settings in the BIOS. Other than try another kind of computer, does anyone have any suggestions for a workaround?

  3. PrimeraUser:

    I have a lot of experience with Primera duplicators. Your best bet is to use the PTPublisher or PTBurn. If you're looking to automate burning, PTBurn is the way to go. All you need to do is create a program to generate text files with all the information needed to create jobs.

    I'd suggest using something else to create ISO files and then pass those to PTBurn. If you want to do everything from the command line, get mkisofs under Cygwin or built for Windows to generate ISO files instead. I'm not sure if it supports HFS+, but it supports UDF, Joliet, and RockRidge.

  4. Also, why not just load the ISO in ImgBurn?  It should surely tell you if the ISO won't fit the DVD+R you have inserted into your drive.  It should either deny it or ask if you want to overburn it, which would tell you it won't fit on the DVD+R at its current size without overburn.  So, it's, at least, slightly larger than the DVD+R size.

     

    Because I am scripting a dvd robot handler and I want to check the iso so I can load the correct disc (DVD-R vs DVD+R DL) into the burner.

  5. Is there an algorithm I can use to determine if the contents of an ISO file will fit on a DVD+R? Checking the overall file size would be easy, but I do worry about edge cases where it's borderline. Are there any existing utilities that do this from the command line?

  6. Good to know. I just verified that I did use the new cable. It's a rare occurrence, so it's not easy to test a fix. The only two other options would be to try a different cable and/or upgrade the computer.

  7. I looked up the CORRECT model this time.  :wink:  I've used that drive for many years, with a few different copies of it over those years, since it needs replacing about every 11 months.  I never encountered a problem with DVD writing.  However, you mentioned a new USB cable, which implies you've put that model in an enclosure, since that's an internal drive.  Did you mean SATA cable, the internal connection for the internal drive internally?  Or did you mean a USB cable because that internal drive is an external enclosure connected by USB?

     

    Sorry, let me explain. There are two LG drives inside a Primera 4202 Blu-ray disc duplicator. The third drive in the log is the one that's inside the computer that operates the duplicator. It's an old computer that doesn't have USB 3.0 ports. That's why the log shows USB 2.0 even though the "enclosure" can support USB 3.0. It's a single USB cable for both drives. I have not attempted simultaneous burns yet. When I get a new computer with USB 3.0 capability, I will attempt it.

     

    Considering how rare this error is and that it might be related to a communications issue rather than an inability of the drive to read/write the disc, I suggested troubleshooting by changing out the USB cable. I might have re-used the USB 2.0 cable from the old duplicator rather than use a new USB 3.0 cable.

  8. I know. I googled first before posting. I'm beginning to wonder if the solution is to change the USB cable!

     

    FYI, when the error occurs, the retries fly by almost instantaneously. It's not like it's reading a bad disc where it has to re-seek. It usually happened early on in the burn, but this one was near the end.

  9. I've been periodically getting this kind of error on my new LG burner:

     

    I 11:47:56 ImgBurn Version 2.5.8.0 started!
    I 11:47:56 Microsoft Windows 7 Professional x64 Edition (6.1, Build 7601 : Service Pack 1)
    I 11:47:56 Total Physical Memory: 6,193,436 KiB  -  Available: 3,280,584 KiB
    I 11:47:56 Initialising SPTI...
    I 11:47:56 Searching for SCSI / ATAPI devices...
    I 11:47:56 -> Drive 1 - Info: HL-DT-ST DVDRAM GH70N UGA0-01 (E:) (ATAPI)
    I 11:47:57 -> Drive 2 - Info: HL-DT-ST BD-RE  WH16NS58 TST4 (F:) (USB 2.0)
    I 11:47:59 -> Drive 3 - Info: HL-DT-ST BD-RE  WH16NS58 TST4 (D:) (USB 2.0)
    I 11:47:59 Found 1 DVD±RW/RAM and 2 BD-RE XLs!
    I 11:48:09 Operation Started!
    I 11:48:09 Source File: U:\Disc Images\MPOE\MPOE 6.0.5.0B1\MPOE 6.0.5.0B1 - Disc 1 of 5 - RHEL 6.8 64-bit DVD.iso
    I 11:48:09 Source File Sectors: 1,924,219 (MODE1/2048)
    I 11:48:09 Source File Size: 3,940,800,512 bytes
    I 11:48:09 Source File Volume Identifier: RHEL 6.1
    I 11:48:09 Source File Application Identifier: GENISOIMAGE ISO 9660/HFS FILESYSTEM CREATOR © 1993 E.YOUNGDALE © 1997-2006 J.PEARSON/J.SCHILLING © 2006-2007 CDRKIT TEAM
    I 11:48:09 Source File File System(s): ISO9660 (Bootable), Joliet
    I 11:48:09 Destination Device: [0:0:0] HL-DT-ST BD-RE  WH16NS58 TST4 (F:) (USB)
    I 11:48:09 Destination Media Type: DVD+R (Disc ID: YUDEN000-T02-00)
    I 11:48:09 Destination Media Supported Write Speeds: 4x, 8x
    I 11:48:09 Destination Media Sectors: 2,295,104
    I 11:48:09 Write Mode: DVD
    I 11:48:09 Write Type: DAO
    I 11:48:09 Write Speed: MAX
    I 11:48:09 DVD+R Reserve Track: No
    I 11:48:09 Link Size: Auto
    I 11:48:09 Lock Volume: Yes
    I 11:48:09 Test Mode: No
    I 11:48:09 OPC: No
    I 11:48:09 BURN-Proof: Enabled
    I 11:48:09 Write Speed Successfully Set! - Effective: 11,080 KB/s (8x)
    I 11:48:09 Book Type Setting: N/A (Reason: Invalid Command Operation Code)
    I 11:48:10 Filling Buffer... (80 MiB)
    I 11:48:13 Writing LeadIn...
    I 11:48:22 Writing Session 1 of 1... (1 Track, LBA: 0 - 1924218)
    I 11:48:22 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 1924218)
    W 11:54:34 Failed to Write Sectors 1894432 - 1894463 - Reason: Data Phase Error
    W 11:54:34 Retrying (1 of 20)...
    W 11:54:53 Retry Failed - Reason: Invalid Address For Write
    W 11:54:53 Retrying (2 of 20)...
    W 11:54:54 Retry Failed - Reason: Invalid Address For Write
    W 11:54:54 Retrying (3 of 20)...
    W 11:54:54 Retry Failed - Reason: Invalid Address For Write
    W 11:54:54 Retrying (4 of 20)...
    W 11:54:54 Retry Failed - Reason: Invalid Address For Write
    W 11:54:54 Retrying (5 of 20)...
    W 11:54:54 Retry Failed - Reason: Invalid Address For Write
    W 11:54:54 Retrying (6 of 20)...
    W 11:54:54 Retry Failed - Reason: Invalid Address For Write
    W 11:54:54 Retrying (7 of 20)...
    W 11:54:54 Retry Failed - Reason: Invalid Address For Write
    W 11:54:54 Retrying (8 of 20)...
    W 11:54:54 Retry Failed - Reason: Invalid Address For Write
    W 11:54:54 Retrying (9 of 20)...
    W 11:54:54 Retry Failed - Reason: Invalid Address For Write
    W 11:54:54 Retrying (10 of 20)...
    W 11:54:54 Retry Failed - Reason: Invalid Address For Write
    W 11:54:54 Retrying (11 of 20)...
    W 11:54:54 Retry Failed - Reason: Invalid Address For Write
    W 11:54:54 Retrying (12 of 20)...
    W 11:54:54 Retry Failed - Reason: Invalid Address For Write
    W 11:54:54 Retrying (13 of 20)...
    W 11:54:54 Retry Failed - Reason: Invalid Address For Write
    W 11:54:54 Retrying (14 of 20)...
    W 11:54:54 Retry Failed - Reason: Invalid Address For Write
    W 11:54:54 Retrying (15 of 20)...
    W 11:54:54 Retry Failed - Reason: Invalid Address For Write
    W 11:54:54 Retrying (16 of 20)...
    W 11:54:54 Retry Failed - Reason: Invalid Address For Write
    W 11:54:54 Retrying (17 of 20)...
    W 11:54:54 Retry Failed - Reason: Invalid Address For Write
    W 11:54:54 Retrying (18 of 20)...
    W 11:54:54 Retry Failed - Reason: Invalid Address For Write
    W 11:54:54 Retrying (19 of 20)...
    W 11:54:54 Retry Failed - Reason: Invalid Address For Write
    W 11:54:54 Retrying (20 of 20)...
    W 11:54:54 Retry Failed - Reason: Invalid Address For Write
    E 11:55:08 Failed to Write Sectors 1894432 - 1894463 - Reason: Data Phase Error
    E 11:55:08 Next Writable Address: 1893472
    I 11:55:08 Synchronising Cache...
    W 11:55:11 User opted to skip the 'Close Track/Session/Disc' functions.
    E 11:55:11 Failed to Write Image!
    I 11:55:14 Exporting Graph Data...
    I 11:55:14 Graph Data File: C:\Users\Pvcsadmin\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_WH16NS58_TST4_THURSDAY-MAY-03-2018_11-48_AM_YUDEN000-T02-00_MAX.ibg
    I 11:55:14 Export Successfully Completed!
    E 11:55:14 Operation Failed! - Duration: 00:07:01
    I 11:55:14 Average Write Rate: 9,355 KiB/s (6.9x) - Maximum Write Rate: 10,972 KiB/s (8.1x)
    I 11:55:14 Close Request Acknowledged
    I 11:55:14 Closing Down...
    I 11:55:14 Shutting down SPTI...
    I 11:55:14 ImgBurn closed!

  10. I'd like a way to get information about a disc to verify there is only one session and has been finalized. I was able to accomplish this with IMGBurn using the following command:

     

    "C:\Program Files (x86)\ImgBurn\ImgBurn.exe" /INFO "test.txt" /CLOSEINFO /SRC 1:0:0 /MODE Discovery

     

    I can then parse the output to verify the disc meets my criteria. Is there a better way to do this?

  11. Opencandy is part of the installer, which is what people are complaining about. They want an installer that's free of it. Now, you can avoid Opencandy by running it from the command line using the /NOCANDY switch. The problem is that people like me use this in a corporate environment and when the company's antivirus picks up the installer as a virus, I have to explain how "it's no big deal." Even though we blocked the whole opencandy.com domain, which renders the issue moot, the fact it shows up in the scan is still a problem. By extracting all the files from the installer and using my batch file, VBS file, and REG file, you can use that to do an install and avoid opencandy completely.

     

    AFAIK, there is no Opencandy code in the APPLICATION itself, just the installer.

     

    EDIT: The download on Betanews says there's no Opencandy bundled:

     

    https://fileforum.betanews.com/detail/ImgBurn/1128426215/1

     

    Here are the hashes:

     

    CRC32: 1AF3CD36
    MD5: 4BF2B8F4B46385BFDA4D65E423CFB868
    SHA-1: 6A3D20796E1FCD4169D5D339AF6E491DCEA3367C
     

  12. Extract all the files from the installer using a program like 7Zip. Make an install.bat file using this:

    @echo off
    goto check_Permissions
    
    :check_Permissions
    echo Administrative permissions required. Detecting permissions...
    
    net session >nul 2>&1
    if %errorLevel% == 0 (
        echo Success: Administrative permissions confirmed.
    ) else (
        echo Failure: Current permissions inadequate.
        pause >nul
        exit 1
    )
    
    
    set prgf=%ProgramFiles%
    
    if "%PROCESSOR_ARCHITECTURE%"=="AMD64" set prgf=%ProgramFiles(x86)%
    if "%PROCESSOR_ARCHITEW6432%"=="AMD64" set prgf=%ProgramFiles(x86)%
    if "%PROCESSOR_ARCHITECTURE%"=="IA64" set prgf=%ProgramFiles(x86)%
    if "%PROCESSOR_ARCHITEW6432%"=="IA64" set prgf=%ProgramFiles(x86)%
    
    mkdir "%prgf%\ImgBurn\Sounds"
    copy "%~dp0\ImgBurn.exe" "%prgf%\ImgBurn\."
    copy "%~dp0\ImgBurnPreview.exe" "%prgf%\ImgBurn\."
    copy "%~dp0\ReadMe.txt" "%prgf%\ImgBurn\."
    copy "%~dp0\uninstall.exe" "%prgf%\ImgBurn\."
    copy "%~dp0\Sounds\Error.wav" "%prgf%\ImgBurn\Sounds\."
    copy "%~dp0\Sounds\Success.wav" "%prgf%\ImgBurn\Sounds\."
    
    mkdir "%USERPROFILE%\Start Menu\Programs\ImgBurn"
    cscript "%~dp0\createLink.vbs" "%USERPROFILE%\Start Menu\Programs\ImgBurn\ImgBurn.lnk" "%prgf%\ImgBurn\ImgBurn.exe"
    cscript "%~dp0\createLink.vbs" "%USERPROFILE%\Start Menu\Programs\ImgBurn\ImgBurn Read Me.lnk" "%prgf%\ImgBurn\ReadMe.txt"
    cscript "%~dp0\createLink.vbs" "%USERPROFILE%\Start Menu\Programs\ImgBurn\Uninstall.lnk" "%prgf%\ImgBurn\uninstall.exe"
    cscript "%~dp0\createLink.vbs" "%USERPROFILE%\Desktop\ImgBurn.lnk" "%prgf%\ImgBurn\ImgBurn.exe"
    
    reg import "%~dp0\EnableCDROM.reg"
    
    echo.
    echo Press any key to close installer.
    pause >nul
    

    Here's EnableCDROM.reg

    Windows Registry Editor Version 5.00
    
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\cdrom]
    "Start"=dword:00000001
    

    I don't remember if the createLink.vbs is part of IMGBurn or I got it from somewhere else, but here that is:

    set objWSHShell = CreateObject("WScript.Shell")
    set objFso = CreateObject("Scripting.FileSystemObject")
    
    ' command line arguments
    ' TODO: error checking
    sShortcut = objWSHShell.ExpandEnvironmentStrings(WScript.Arguments.Item(0))
    sTargetPath = objWSHShell.ExpandEnvironmentStrings(WScript.Arguments.Item(1))
    sWorkingDirectory = objFso.GetAbsolutePathName(sShortcut)
    
    set objSC = objWSHShell.CreateShortcut(sShortcut)
    
    objSC.TargetPath = sTargetPath
    objSC.WorkingDirectory = sWorkingDirectory
    
    objSC.Save
    
  13. I'm getting a dialog box at the end of a burn saying:

     

    CreateFile Failed! - Device: '\\?\usbstor#cdrom&ven_optiarc&prod_dvd_rw_ad-5280s&rev_1.z6#000000000000&0#{53f56308-b6bf-11d0-94f2-00a0c91efb8b}'

     

    I'm including the log of once such event. If I hit "retry" it will succeed after a couple attempts. The discs seems to burn fine. This just started happening and I can't think of anything that has changed recently other than perhaps a new Windows update. I'm running IMGBurn on Windows 7 Professional.

     

     

    ; //****************************************\\
    ;   ImgBurn Version 2.5.8.0 - Log
    ;   Tuesday, 17 May 2016, 17:23:27
    ; \\****************************************//
    ;
    ;
    I 16:59:50 ImgBurn Version 2.5.8.0 started!
    I 16:59:50 Microsoft Windows 7 Professional x64 Edition (6.1, Build 7601 : Service Pack 1)
    I 16:59:50 Total Physical Memory: 6,193,436 KiB  -  Available: 4,045,816 KiB
    I 16:59:50 Initialising SPTI...
    I 16:59:50 Searching for SCSI / ATAPI devices...
    I 16:59:52 -> Drive 1 - Info: Optiarc DVD RW AD-5280S 1.Z6 (D:) (USB 2.0)
    I 16:59:52 -> Drive 2 - Info: Optiarc DVD RW AD-5280S 1.Z6 (J:) (USB 2.0)
    I 16:59:52 Found 2 DVD±RWs!
    I 17:00:00 Operation Started!
    I 17:00:00 Source File: U:\Disc Images\ACB15 TI16\ACB15 TI16 CEI 1.0 ER1\ACB15 TI16 CEI 1.0 ER1 - Disc 1 of 1 - RHEL 7.1 x86-64 with ACB15 TI16 COTS DVD.iso
    I 17:00:00 Source File Sectors: 2,997,808 (MODE1/2048)
    I 17:00:00 Source File Size: 6,139,510,784 bytes
    I 17:00:00 Source File Volume Identifier: RHEL-7.1 Server.
    I 17:00:01 Source File Application Identifier: MKISOFS ISO 9660/HFS FILESYSTEM BUILDER & CDRECORD CD-R/DVD CREATOR © 1993 E.YOUNGDALE © 1997 J.PEARSON/J.SCHILLING
    I 17:00:01 Source File File System(s): ISO9660 (Bootable), Joliet
    I 17:00:01 Destination Device: [0:0:0] Optiarc DVD RW AD-5280S 1.Z6 (D:) (USB)
    I 17:00:01 Destination Media Type: DVD+R DL (Disc ID: MKM-003-00)
    I 17:00:01 Destination Media Supported Write Speeds: 4x, 6x, 8x
    I 17:00:01 Destination Media Sectors: 4,173,824
    I 17:00:01 Destination Media L0 Data Zone Capacity: 2,086,912 (Changeable: Yes)
    I 17:00:01 Write Mode: DVD
    I 17:00:01 Write Type: DAO
    I 17:00:01 Write Speed: MAX
    I 17:00:01 DVD+R DL Reserve Track: No
    I 17:00:01 Link Size: Auto
    I 17:00:01 Lock Volume: Yes
    I 17:00:01 Test Mode: No
    I 17:00:01 OPC: No
    I 17:00:01 BURN-Proof: Enabled
    I 17:00:01 Write Speed Successfully Set! - Effective: 11,080 KB/s (8x)
    I 17:00:01 Book Type Setting: DVD-ROM
    I 17:00:01 Optimal L0 Data Zone Capacity: 1,498,912
    I 17:00:01 Optimal L0 Data Zone Method: ECC Block Boundary
    I 17:00:07 Set L0 Data Zone Capacity Succeeded!
    I 17:00:07 L0 Data Zone Capacity - Effective: 1,498,912
    I 17:00:07 Filling Buffer... (80 MiB)
    I 17:00:08 Writing LeadIn...
    I 17:00:11 Writing Session 1 of 1... (1 Track, LBA: 0 - 2997807)
    I 17:00:11 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 2997807)
    I 17:00:11 Writing Layer 0... (LBA: 0 - 1498911)
    I 17:07:26 Writing Layer 1... (LBA: 1498912 - 2997807)
    I 17:14:48 Synchronising Cache...
    I 17:14:49 Closing Track...
    I 17:15:02 Finalising Disc...
    I 17:15:54 Exporting Graph Data...
    I 17:15:54 Graph Data File: C:\Users\Pvcsadmin\AppData\Roaming\ImgBurn\Graph Data Files\Optiarc_DVD_RW_AD-5280S_1.Z6_TUESDAY-MAY-17-2016_5-00_PM_MKM-003-00_MAX.ibg
    I 17:15:54 Export Successfully Completed!
    I 17:15:54 Operation Successfully Completed! - Duration: 00:15:53
    I 17:15:54 Average Write Rate: 6,844 KiB/s (5.1x) - Maximum Write Rate: 10,898 KiB/s (8.1x)
    I 17:15:54 Close Request Acknowledged
    I 17:15:54 Closing Down...
    E 17:23:27 CreateFile Failed! - Device: '\\?\usbstor#cdrom&ven_optiarc&prod_dvd_rw_ad-5280s&rev_1.z6#000000000000&0#{53f56308-b6bf-11d0-94f2-00a0c91efb8b}'
    E 17:23:27 Reason: The system cannot find the file specified.
    I 17:23:27 Shutting down SPTI...
    I 17:23:27 ImgBurn closed!

  14. I use IMGBurn differently in standalone mode and in a script differently. In standalone, I'd like IMGBurn to work with my duplicator to pick up and load the discs. Through the scripting, I handle all of the robot movements so I'd want that disabled.

     

    Also, it would be nice to program the bins for input and output. For example, Primera has three "bins:" Left, right, and reject. The default behavior is to grab a disc from the right and output to the left. Bad discs go to the reject output, which can also be a bin. I have mine with DVDs in the left, CDs in the right, and I output burned discs to the reject bin. Other duplicators have more than three bins. (This is part of the reason why I use scripting to handle the process. I also do disc label printing, too.)

×
×
  • Create New...

Important Information

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