-
Posts
30,514 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by LIGHTNING UK!
-
Thanks for the confirmation
-
I'd be interested to see a PIPO scan of that media if you have one handy! Just wondering if the 716 is anything like the 708 (I tested them with the 716 in the 'media' forum)
-
Hmm that's most odd then. The only thing I changed that could have caused this issue is the amount of data I read at a time from the hdd. As you're saying the 'Buffer' is always full, that means it's reading from the hdd just fine. The problem is then sending it to the burner. Just humour us and follow the DMA/slow burning related post in the FAQ. i.e. uninstall your ide controller and reboot. EDIT: ok, just looked at the IBG files, it's not a dma problem. 1.2.0.0 is burning fine and then it looks like plextors WOPC is kicking in - or something else is using the bus/channel and stopping it burning at full speed. You'll then notice it jumps back to 4x for the 2nd half of the disc, before then messing up again.
-
Which buffer is at 0% (or near it) when you burn?
-
It should delete if it's not used / called elsewhere in the queue. I will double check though... program logic became a little complicated in the end and I may have fixed one thing and broken something else.... i.e. this! Thanks Oh and once in the queue, the option you set in the queue is the one that gets used. i.e. when you add an image, it will auto check the delete box IF that settings one is checked. After that, the delete option in the settings is never looked at.
-
Oh well monteca820ce, I tried! Maybe your machine just doesn't support the command or something. It is valid and I couldn't improve it now if I tried! (It's very basic!)
-
Clarification of 1.2.0.0 verify behavior
LIGHTNING UK! replied to fordman's topic in ImgBurn Support
Indeed, I do have FS/IFO parsing I guess... but it's much easier to treat the image as a whole rather than something made up of lots of little files! And as you said, doing it sector by sector, I can check non file/user data too. -
Clarification of 1.2.0.0 verify behavior
LIGHTNING UK! replied to fordman's topic in ImgBurn Support
You're spot on shamus ImgBurn 1.0.0.0 and all version of DVD Decrypter ONLY checked the physical disc for read error (by reading every sector). ImgBurn 1.1.0.0+ compares what's read from the media against the image file itself. So in order to get a proper byte by byte verify, you just need to leave the settings on their default values. i.e. 'Verify against image file' should be ticked. You're burning an ISO file, so that's what it's compared against. I do not deal with things on an 'individual file within image' level. -
A bug to myself! lol BDS2006 exe's that are then compressed with UPX are crashing under this OS. I guess it would also effect 95 and possibly Windows Me. As ImgBurn.exe is compressed by UPX, you need to decompress it. You can get v1.25 from http://upx.sourceforge.net/ Extract the upx.exe to the same folder as ImgBurn.exe and run the following CLI. Upx -d ImgBurn.exe All will be well in the world once you've done that. The next release will not use UPX - I'll probably use PECompact instead (I've tested that and it works ok).
-
Test wode actually writing on disc! (v1.2.0.0)
LIGHTNING UK! replied to r0lZ's topic in ImgBurn Bugs
Ok, it's almost 1am but I've had a quick look around the code and I think I've now added all the extra 'if' statements I need to in order to properly check/allow for the /TESMODE cli switch. I'll do some proper testing in the morning. -
Test wode actually writing on disc! (v1.2.0.0)
LIGHTNING UK! replied to r0lZ's topic in ImgBurn Bugs
Damn it! This is all due to where I'm acknowledging that testmode has been enabled via CLI. It's kicking in after the normal checks for media type etc because I didn't want the CLI parameter to actually change the checkbox in the main GUI. All boils down to a lack of testing in this area. CLI is not something I generally concern myself with - as I never use it! -
Test wode actually writing on disc! (v1.2.0.0)
LIGHTNING UK! replied to r0lZ's topic in ImgBurn Bugs
No, there is no way to do a test and then a write. As for actually burning in test mode...well you are using DVD+R there and I'm sure you know the DVD+R format doesn't support the test/simulation feature However, it should have displayed an error to that effect... will have to check why you didn't get it! (if you're saying you didn't ?) -
The layerbreak position ImgBurn has picked up looks ok to me. Ignore what scenarist is saying for the LBA... however it's doing its calculation, it's the same as ImgBurn's one. btw, the discs we buy are all OTP. No point building a PTP image.
-
Details, downloads etc on the main website. http://www.imgburn.com
-
Looks like your drive doesn't fully support those discs. Try updating your drives firmware to the 1.20 version, you're way behind. http://forum.rpc1.org/dl_firmware.php?download_id=1898
-
Well, as this program only deals with burning images, you tell whatever program you're using to output to an ISO and then burn that. Sorry but I (we) cannot help you with the 'ripping' part, you'll need to look elsewhere for that info.
-
Quite simple, you don't. ImgBurn burns images in the same way DVD Decrypter used to. Nothing more - well, apart from additional burning features of course.
-
LiteOn 8xx series... dunno, probably not!
-
Just started using ImgBurn and it won't work, PLEASE HELP.
LIGHTNING UK! replied to Brian002100's topic in ImgBurn Support
Update your drives firmware with the PDS7 version. http://forum.rpc1.org/dl_firmware.php?download_id=1965 -
Because one is a DVDROM and the other is a writable disc. That's just the way it is.
-
BENQ DVD LS DW1655 BCDB (ATA) Media Information: BENQ DVD LS DW1655 BCDB (ATA) Current Profile: DVD+R Disc Information: Status: Empty Erasable: No Free Sectors: 2,295,104 Free Space: 4,700,372,992 bytes Free Time: 510:03:29 (MM:SS:FF) Supported Write Speeds: 2.4x, 4x Physical Format Information (ADIP): Disc ID: RICOHJPN-R01-02 Book Type: DVD+R Part Version: 1 Disc Size: 120mm Maximum Read Rate: Not Specified Number of Layers: 1 Track Path: Parallel Track Path (PTP) Linear Density: 0.267 um/bit Track Density: 0.74 um/track First Physical Sector of Data Area: 196,608 Last Physical Sector of Data Area: 2,491,711 Last Physical Sector in Layer 0: 0 Results: I 12:40:12 ImgBurn Version 1.1.0.8 Beta started! I 12:40:12 Microsoft Windows Server 2003, Standard Edition (5.2, Build 3790 : Service Pack 1) I 12:40:12 Initialising SPTI... I 12:40:12 Searching for SCSI / ATAPI devices... I 12:40:13 Found 3 DVD-ROMs, 2 DVD?RWs and 2 DVD?RW/RAMs! I 12:40:23 Operation Started! I 12:40:23 Source File: -==/\/[DISCOVERY IMAGE]\/\==- I 12:40:23 Source File Sectors: 2,295,104 (MODE1/2048) I 12:40:23 Source File Size: 4,700,372,992 bytes I 12:40:23 Destination Device: [2:0:0] BENQ DVD LS DW1655 BCDB (J:) (ATA) I 12:40:23 Destination Media Type: DVD+R (Disc ID: RICOHJPN-R01-02) (Speeds: 2.4x, 4x) I 12:40:23 Destination Media Sectors: 2,295,104 I 12:40:23 Write Mode: DVD I 12:40:23 Write Type: DAO I 12:40:23 Write Speed: MAX I 12:40:23 Link Size: Auto I 12:40:23 Test Mode: No I 12:40:23 BURN-Proof: Enabled I 12:40:23 Filling Buffer... I 12:40:23 Writing LeadIn... I 12:40:37 Writing Image... I 12:55:16 Synchronising Cache... I 12:55:17 Closing Track... I 12:55:26 Finalising Disc... I 12:55:52 Exporting Graph Data... I 12:55:52 Graph Data File: C:\IBG\BENQ_DVD_LS_DW1655_BCDB_19-FEBRUARY-2006_12-40_RICOHJPN-R01-02_MAX.ibg I 12:55:52 Export Successfully Completed! I 12:55:52 Operation Successfully Completed! - Duration: 00:15:27 I 12:55:52 Average Write Rate: 5,222 KB/s (3.8x) - Maximum Write Rate: 5,583 KB/s (4.0x) I 12:55:52 Cycling Tray before Verify... W 12:56:01 Waiting for device to become ready... I 12:56:09 Device Ready! I 12:56:09 Operation Started! I 12:56:09 Source Device: [2:0:0] BENQ DVD LS DW1655 BCDB (J:) (ATA) I 12:56:09 Source Media Type: DVD+R (Book Type: DVD-ROM) (Disc ID: RICOHJPN-R01-02) (Speeds: 2.4x, 4x) I 12:56:09 Image File: -==/\/[DISCOVERY IMAGE]\/\==- I 12:56:09 Image File Sectors: 2,295,104 (MODE1/2048) I 12:56:09 Image File Size: 4,700,372,992 bytes I 12:56:09 Verifying Sectors... I 13:01:11 Exporting Graph Data... I 13:01:11 Graph Data File: C:\IBG\BENQ_DVD_LS_DW1655_BCDB_19-FEBRUARY-2006_12-40_RICOHJPN-R01-02_MAX.ibg I 13:01:11 Export Successfully Completed! I 13:01:11 Operation Successfully Completed! - Duration: 00:05:02 I 13:01:11 Average Verify Rate: 15,249 KB/s (11.0x) - Maximum Verify Rate: 22,377 KB/s (16.2x)
-
Bug with Layer Break Flag setting on ISO burns
LIGHTNING UK! replied to fordman's topic in ImgBurn Bugs
Sorry, I tend to just remember the post I'm replying to rather than all the details mentioned earlier! My brain runs out of space otherwise It's stupid of CloneDVD to go to the trouble of building a nice DL ISO and then not inserting the layerbreak flag in the IFO - hence it was probably just a fluke that a cell landed on a nice LBA. On the other hand, if CloneDVD really does do it nicely, you should have a word with Olli and get him to change how it works. -
Booktype not being set to -ROM instead of +R DL
LIGHTNING UK! replied to HiBob's topic in ImgBurn Support
ImgBurn doesn't touch the booktype stuff unless you specifically sit there and do it yourself. If they're not burning as DVDROM, I would guess another program has reset that setting on your burner. Just do it again. -
Bug with Layer Break Flag setting on ISO burns
LIGHTNING UK! replied to fordman's topic in ImgBurn Bugs
Your best bet is to just rebuild the ISO using PgcEdit and have it pass the correct layerbreak LBA to ImgBurn. An ISO without a layerbreak flag in the IFO is unlikely to have a cell in the right place for ImgBurn to add one. I don't recall seeing a PM, no. That said, I cannot really help beyond Paypal or Nochex anyway. I appreciated the offer though -
Bug with Layer Break Flag setting on ISO burns
LIGHTNING UK! replied to fordman's topic in ImgBurn Bugs
If you're manually setting the layerbreak position, ImgBurn will behave the same way as DVD Dec and the maths overflow problem doesn't even come into play. I'm hoping to release 1.2.0.0 tomorrow.