-
Posts
47 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Sizzlechest
-
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.)
-
The optiarc is the drive in the duplicator. I doubt they locked out the USB ports since the drives are still appearing. I'll check the Device Manager. EDIT: Opening the Device Manager threw up a message about being security restricted, but I was still able to see the devices in there. I didn't find the duplicator. but I don't see it as an administraotr either. What does it show up as on your side?
-
I'm using IMGBurn with the drives in an actual duplicator, but I didn't enable the SDK. IMGBurn isn't configured to manipulate the robot.
-
I have some more information that might be relevant... I found this thread here talking about differences in the bootcode of a Sony Optiarc AD-5260S sold retail vs. the firmware found in a Primera duplicator, which is what I'm using. http://club.myce.com/f86/ad-5260s-bootcode-mismatch-322268/ Someome made a comment that the Primera firmware contained "extended tray eject capabilities." This is the first I've ever heard of it. Does this sound familiar to you?
-
No, that's expected. This is occuring at the end of the verify when the program closes itself. The drive tray ejects, which isn't being done by IMGBurn, so IMGBurn must have exited at that point. Sometimes, the drive tray then closes. There's nothing out of ordinary in the IMGBurn log.
-
I have been running IMGBurn via the command-line in a 2 year old script that I use to automate the burning of discs. Here's the command I use: MODE WRITE /SRC filename.iso /DEST F: /COPIES 1 /VERIFY YES /SPEED AUTO /TESTMODE NO /DELETEIMAGE NO /EJECT NO /WAITFORMEDIA /START /CLOSE /NOSAVESETTINGS Notice that I do not tell IMGBurn to eject the disc. I eject the disc myself through another command after IMGBurn is complete. (I did this to ensure the script would work if I ever had to switch to another burning program that dodn't support ejecting the tray on completion.) Ever since upgrading to 2.5.7.0, I noticed that sometimes the drive ejects, but then the tray closes soon after. The only thing that has changed recently is IMGBurn. Has the behavior of IMGBurn changed? Does it attempt to close the drive tray when it gets shutdown? This doesn't happen consistently. I suspect there may be a timing issue where perhaps under some conditions, the command to close the tray is happening after the command to open the tray, although I honestly can't see how that could be happening since IMGBurn should be closed by then. I'm assuming the response is that nothing changed in the way discs are handled or how they're verified. But like I mentioned, this is a new bug on an old script.
-
Oh, I didn't know you could do that. I assume this would be the list of possible options: CD-R CD-RW DVD-R DVD+R DVD-RW DVD+RW I don't need bluray settings, but I assume there would be something applicable. BTW, the readme says: /SPEED <Write Speed> Used to change the value of the 'Write Speed' drop down list. The parameter must match the value within the drop down list exactly. Examples: /SPEED MAX /SPEED 1x /SPEED 2.4x (or 2,4x depending on regional settings) I'd like to ensure I override any settings and force AWS from the command line. Is "/SPEED AWS" or "/SPEED AUTO" the correct way to do it?
-
Yes, that will be fine. I'll test it tomorrow morning. Have you sent it yet? I checked my Junk Mail, too.
-
Yes, that will be fine. I'll test it tomorrow morning.
-
Sounds good. Whenever you're ready.
-
I would if I could, but it's on a PC that's not accessible from Internet.
-
Sure. No problem. I'll be you guinea pig.
-
Yes. All burning software has access to the Pioneer drive. I can burn discs, open the tray, and close the tray just fine, but the robot doesn't load/unload or print, obviously.
-
Ah. Thanks anyway. I would have loved to use IMGBurn instead of the crappy software that comes with my duplicator.
-
I saw the new options in 2.5.1.0 for robots and media changers, so I thought I'd try it out with my Primera Bravo II Disc Publisher. I enabled the checkboxes in the I/O section, but I got the following errors: I 10:08:08 Initialising BS_Robots... E 10:08:08 Unable to initialise BS_Robots! - BSRobots20.dll E 10:08:08 Reason: The specified module could not be found. I 10:08:09 Initialising SPTI... I 10:08:09 Searching for Auto Loader devices... I 10:08:09 Found 0 Auto Loaders! I 10:08:09 Searching for Medium Changer devices... I 10:08:09 Found 0 Medium Changers! I 10:08:09 Searching for SCSI / ATAPI devices... I 10:08:09 -> Drive 1 - Info: HL-DT-ST CD-ROM GCR-8480B 1.00 (D:) (ATA) I 10:08:09 -> Drive 2 - Info: PIONEER DVD-RW DVR-108 9.18 (E:) (USB) I 10:08:09 Found 1 CD-ROM and 1 DVD±RW! FYI, the Pioneer is the drive in the duplicator. Where do I get the BSRobots20.dll file?