Search the Community

IMGburn DOES NOT decrypt or "rip" anything its as its name implies its a burning program namely ISO's and with the release of the new version 2.0 it can also create an ISO from video files(unencrypted ) but it is not a replacement for DVDD. For legal reasons we dont discuss ripping or defeating copy protection here

I used DVD Shrink 3.2 to generate my ISO file, then using IMGBURN 2.0.0.0 tried to burn the image. The original came from a +R DL disk with 6,721,404,928 bytes. The compression settings were on Automatic. I used Write, not Build with ImgBurn The write completed successfully, and then the tray cycled to begin the verify and the device never recognized the DVD - Device Not Ready (Medium Not Present) See the following log. Log BENQ DVD LS DW1655 BCHB (ATA) Current Profile: DVD-R Disc Information: <! Before the burn > Status: Empty Erasable: No Free Sectors: 2,298,496 Free Space: 4,707,319,808 bytes Free Time: 510:48:46 (MM:SS:FF) Supported Write Speeds: 4x, 8x, 12x, 16x Pre-recorded Information: Manufacturer ID: RITEKF1 Physical Format Information (Last Recorded): Book Type: DVD-R Part Version: 5 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: 0 Last Physical Sector in Layer 0: 0 I 09:06:36 ImgBurn Version 2.0.0.0 started! I 09:06:36 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2) I 09:06:36 Initialising SPTI... I 09:06:36 Searching for SCSI / ATAPI devices... I 09:06:36 Found 1 CD-ROM and 1 DVD?RW! I 09:08:04 Operation Started! I 09:08:04 Source File: C:\Documents and Settings\My Documents\Data Files\DVD ISO FILES\_20K-On_Top.ISO I 09:08:04 Source File Sectors: 2,285,657 (MODE1/2048) I 09:08:04 Source File Size: 4,681,025,536 bytes I 09:08:04 Source File Volume Identifier: _20K_On_Top I 09:08:04 Source File Implementation Identifier: DVD Shrink I 09:08:04 Source File File System(s): ISO9660, UDF (1.02) I 09:08:04 Destination Device: [1:1:0] BENQ DVD LS DW1655 BCHB (E:) (ATA) I 09:08:04 Destination Media Type: DVD-R (Disc ID: RITEKF1) (Speeds: 4x, 8x, 12x, 16x) I 09:08:04 Destination Media Sectors: 2,298,496 I 09:08:04 Write Mode: DVD I 09:08:04 Write Type: DAO I 09:08:04 Write Speed: 16x I 09:08:04 Link Size: Auto I 09:08:04 Test Mode: No I 09:08:04 BURN-Proof: Enabled I 09:08:05 Filling Buffer... I 09:08:06 Writing LeadIn... I 09:08:21 Writing Image... I 09:19:20 Synchronising Cache... I 09:19:46 Image MD5: 45029dda5f8405459de998d0d995ad89 I 09:19:46 Operation Successfully Completed! - Duration: 00:11:41 I 09:19:46 Average Write Rate: 6,936 KB/s (5.0x) - Maximum Write Rate: 18,792 KB/s (13.6x) I 09:19:46 Cycling Tray before Verify... W 09:19:57 Waiting for device to become ready... Okay, I noticed the size of my source file was very large, so then I went back to DVD Shrink and recreated a new ISO file using a custom compression ratio of approximately 70%. This took much longer to create the ISO file of course. However, the result was the same, as you can see in the log. I 10:50:54 ImgBurn Version 2.0.0.0 started! I 10:50:54 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2) I 10:50:54 Initialising SPTI... I 10:50:54 Searching for SCSI / ATAPI devices... I 10:50:54 Found 1 CD-ROM and 1 DVD?RW! I 10:52:10 Operation Started! I 10:52:10 Source File: C:\Documents and Settings\My Documents\Data Files\DVD ISO FILES\_20K_On_Top.ISO I 10:52:10 Source File Sectors: 2,150,332 (MODE1/2048) I 10:52:10 Source File Size: 4,403,879,936 bytes I 10:52:10 Source File Volume Identifier: _20K_On_Top I 10:52:10 Source File Implementation Identifier: DVD Shrink I 10:52:10 Source File File System(s): ISO9660, UDF (1.02) I 10:52:10 Destination Device: [1:1:0] BENQ DVD LS DW1655 BCHB (E:) (ATA) I 10:52:10 Destination Media Type: DVD-R (Disc ID: RITEKF1) (Speeds: 4x, 8x, 12x, 16x) I 10:52:10 Destination Media Sectors: 2,298,496 I 10:52:10 Write Mode: DVD I 10:52:10 Write Type: DAO I 10:52:10 Write Speed: 16x I 10:52:10 Link Size: Auto I 10:52:10 Test Mode: No I 10:52:10 BURN-Proof: Enabled I 10:52:11 Filling Buffer... I 10:52:11 Writing LeadIn... I 10:52:35 Writing Image... I 11:01:37 Synchronising Cache... I 11:02:01 Image MD5: d7f9dab60eeee355896ed6c541605559 I 11:02:01 Operation Successfully Completed! - Duration: 00:09:51 I 11:02:01 Average Write Rate: 7,934 KB/s (5.7x) - Maximum Write Rate: 16,692 KB/s (12.1x) I 11:02:01 Cycling Tray before Verify... W 11:02:12 Waiting for device to become ready... Help, I only have 4 blanks left!! Any ideas of things to try to get this to work? Thanks.

Thanks for the help, I'm going to try and burn all the DL images clogging my drives this weekend, and since I don't have time to watch them all to check for errors, I'll rest a lot easier since I can't afford a stack of Expensive DL discs that will be useless because of some option I forgot to set. Most especially, thanks for this fantastic program, I couldn't live without it. I've always wondered why the best programs are always free, and what motivates someone to create them, take the time to make them better and better and then give them away for free. Out of all the programs out there the free ones are usually the ones that are worth paying for. I, for one, am very grateful for your work, I can't thank you enough, Roy Edit: I just noticed the donate button on the IMGBURN main page. I'm disabled and on a fixed income, but I'll be donating after the first of the month - I can't spare much, maybe $20 or a little more, but I guess it's better than nothing.

Mount the ISO in DAEMON Tools and then either copy the contents of the virtual drive to a folder on your hdd, or just use the virtual drive directly. Point ImgBurn's 'Build' mode at those files and have it create a new image. You then burn that to a double layer disc (or just burn on-the-fly as it builds) If that's no good for you (i.e. you want it on a single layer disc), you should go back to your AVI -> DVD program and tell it to make it a little smaller! That or run the DVD through any one of the million DVD compression programs available on the web. Get it to the right size and then burn it.

Now, this one has me worried... After shuffling off all desired data to kept from the partitions on the SATA drive to a USB drive, and barely managing to fit it all, I went in and attacked it from the POV of removing any FAT problems. Booted from a CD, ran FDISK /mbr, ran FDISK and deleted all the partitions, created a new C:, formatted it with a quick format, ran FDISK /mbr again, ran FDISK again to delete the partition to create all unallocated space, and rebooted with the system recovery CD in, with all USB devices and PCI cards disconnected, save for the monitor card. Only the absolutely required stuff was connected, save for the 2 DVD drives. Just the PS/2 keyboard, the USB mouse connected by the PS/2 bridge, the monitor card, and the two DVD drives. The recovery CD went to work, XP, the "2002 SP 1" update release that came with the default system was set up... and, to my surprise... the two DVD drives did NOT assume the drive letters D and E. Strangely... utterly in shock... they assumed the drive letters R and S which I ALWAYS used before! BUT, I have to set that MANUALLY! The drives SHOULD have assumed the first two available drive letters. With only C:, nothing else, they SHOULD have assumed D and E on a virgin install from the recovery CD. Like they have done before. SOMEHOW, they remembered and saved their drive letters from BEFORE, when I had changed them to R and S in my last Windows setup. WHY? More importantly... how?

I USED X PROGRAM TP RIP SOME DVDS TO MY HARD DRIVE NOW IM USING IMG BURN TO CREATE AN ISO SO I CAN BURN TO DVD.IM NEW AT THIS AND WAS WONDERING WILL THESE DISCS BE READ BY MY DAUGHTERS DVD PLAYER ON HER REGULAR TELEVISION?OR JUST A PC OPTICAL PLAYER.ALSO DO I USE THE ISO FILE OR THE MDS FILE TO BURN TO DVD MEDIA?

I am building a bootable image. I create the ISO image, then tried to write it to the CD. I get this error message: There is a problem with the El Torito configuration. Boot image: C:\bootcd.iso size 1,228,800 bytes Expected size: 1,474,560 bytes The boot image is the wrong size for the media type. I made a boot floppy for this laptop. I can boot from this floppy. Then I copied the files into a directory on the laptop. Then I used these files to build an ISO image. I appreciate all your knowledge and help. Thanks

Even I wonder why I still use Win ME. Do you think my DELL Dimension XPST500 with 256MB can run XP? BOOT SUCCESS. I found rawread.exe and rawrite.exe on the net. I used rawread.exe to create RAWBOOT.IMG from my floppy I then used imgburn to create the boot image. Reboot and success. I have my DOS CD and access to C: You mentioned another file is needed. Can you explain in more detail. Thanks. Also, what inspired all of this was an article by Fred Langa about booting a DOS system on a CD. He said that I could have floppy emulation as A: plus files on the CD as device D: That is, write the CD with the floppy image RAWBOOT.IMG and add another directory say TEST. Additional programs go in this directory. Such as disktest, memory test, etc. Here is the reference to the article>>> http://www.informationweek.com/story/showA...icleID=10818064 Have you seen this done? Do you have any suggestions?

Ah Win Me....that's a shame Yes, you'll have to search the net for a tool that can create a raw image of a floppy disc. It'll end up being a file of 1.44mb in size. 'WinImage' is one tool I know of that can do it. Once you have that bootable image, yes you can use that as the 'bootable image' in ImgBurn. You will need to add at least 1 file/folder to the compilation before you can burn the disc though. Simply specifying the bootable image part is not sufficient.

Since I do not have Win NT (I have Win ME) can I make a raw image on my hard drive from my floppy using one of the utilities I see on the internet? Can I use the Raw image to create the ISO file?

Every disc that I have burned had not been able to play on any stand alone player, although the back ups play fine on my 3 computers and my son's Play Station2. We have 2 stand alone players in the house and last night I sent a burn to a friends house to see if the disc would play on his play. NO it didnt. I have used Nero CD speed to test the quality of the burn all on the 90"s good burns, I used Verbatim, TY and Princo discs. I have used Shrink to create the ISO - still no go on the playback. I have been told that you can burn stright from the Video_TS folder with this new version of IMGburn yet I am having no luck figuring that out. I have gone through the guides and it look like the "Build may be what I need?" not sure. First question is how do I burn from the Video_TS folder without it being an .ISO file. Thank you, Again I am not sure what the problem here is if it is a problem with ripit4me or shrink or imgburn. Oh ya the movie is RV region 1

LOL!!!! If I copy files from a magazine coverdisk to my HD with Windows Explorer, that?s OK. If I copy the same files to my HD in ISO format using ImgBurn, it means ImgBurn is a ripper? You truly are an idiot. I think you're getting the point. Creating ISOs and burning files makes it able to "rip" things. Ripping doesn't have anything to do with removing protection. They are separate issues. People tend to confuse them. What a load of crap. The only one confused here is you. You?ve no concept of what the term ?ripping? means. ?Ripping? infers the extraction of multimedia content from a file or disk. Creating an ISO from unprotected files has nothing to do with ripping. Windows Explorer can't create ISOs or burn DVDs. So get a clue before you hurt yourself. You've given an analogy that doens't even hold up. I repeat. Nothing you have said in any way refutes what I said. It wouldn?t matter what I say. You are too egocentric to listen and too stupid to learn. Your foray into the world of computers would be best served by buying a PS2. It?s obvious you have neither the brains nor the wit to operate a piece of equipment as complex as a personal computer.

You need a RAW image of the bootable floppy disc. Copying files + sticking them in a folder + making an image is not enough. Put the disc in the floppy drive and use the 'Create Boot Image' option to do a raw read. This will only be available in NT based OS's though. If it works, you'll end up with a file 1,474,560 bytes in size.

I don't understand this. You have a very weird way of thinking calweycn. You can't call something a 'ripper' because it can create an ISO file, that's just plain ridiculous.

Horseshit. That's about the most stupid and ridiculous statement I've had the misfortune of reading. Is Nero a ripper? What about UltraISO? MusicMatch Jukebox? Do any of these programs remove Macrovision? What about ARccoSS? Doh! The word "ripping" applies to copying discs, whether they are protected or not. People "ripped" CDs when they had no protection at all. Removing protection and "ripping" are two different things. ImgBurn can rip "non css dvds." It's a ripper, whether or not you want it to be. Words have meanings. You can't say it's not a ripper, when it can create ISOs and burn files. It doesn't defeat any copy protection, but it can and does RIP discs. I stand by what I said. Nothing you have said in any way refutes what I said. I think you're getting the point. Creating ISOs and burning files makes it ableto "rip" things. Ripping doesn't have anything to do with removing protection. They are separate issues. People tend to confuse them. Windows Explorer can't create ISOs or burn DVDs. So get a clue before you hurt yourself. You've given an analogy that doens't even hold up. I repeat. Nothing you have said in any way refutes what I said.

A security researcher with expertise in rootkits has built a working prototype of new technology that is capable of creating malware that remains "100 percent undetectable," even on Windows Vista x64 systems. Joanna Rutkowska, a stealth malware researcher at Singapore-based IT security firm COSEINC, says the new Blue Pill concept uses AMD's SVM/Pacifica virtualization technology to create an ultra-thin hypervisor that takes complete control of the underlying operating system. Rutkowska plans to discuss the idea and demonstrate a working prototype for Windows Vista x64 at the SyScan Conference in Singapore on July 21 and at the Black Hat Briefings in Las Vegas on Aug. 3. The Black Hat presentation will occur on the same day Microsoft is scheduled to show off some of the key security features and functionality being fitted into Vista. Rutkowska said the presentation will deal with a "generic method" of inserting arbitrary code into the Vista Beta 2 kernel (x64 edition) without relying on any implementation bug. he technique effectively bypasses a crucial anti-rootkit policy change coming in Windows Vista that requires kernel-mode software to have a digital signature to load on x64-based systems. The idea of a virtual machine rootkit isn't entirely new. Researchers at Microsoft Research and the University of Michigan have created a VM-based rootkit called "SubVirt" that is nearly impossible to detect because its state cannot be accessed by security software running in the target system. Now, Rutkowska is pushing the envelope even more, arguing that the only way Blue Pill can be detected is if AMD's Pacifica technology is flawed. "The strength of the Blue Pill is based on the SVM technology," Rutkowska explained on her Invisible Things blog. She contends that if generic detection could be written for the virtual machine technology, then Blue Pill can be detected, but it also means that Pacifica is "buggy." PointerRead more here about Microsoft's moves to hardens Vista against kernel-mode malware. "On the other hand?if you would not be able to come up with a general detection technique for SVM based virtual machine, then you should assume, that you would also not be able to detect Blue Pill," she added. "The idea behind Blue Pill is simple: your operating system swallows the Blue Pill and it awakes inside the Matrix controlled by the ultra thin Blue Pill hypervisor. This all happens on-the-fly (i.e. without restarting the system) and there is no performance penalty and all the devices," she explained. Rutkowska stressed that the Blue Pill technology does not rely on any bug of the underlying operating system. "I have implemented a working prototype for Vista x64, but I see no reasons why it should not be possible to port it to other operating systems, like Linux or BSD which can be run on x64 platform," she added. Blue Pill is being developed exclusively for COSEINC Research and will not be available for download. However, Rutkowska said the company is planning to organize trainings about Blue Pill and other technologies where the source code would be made available. Rutkowska has previously done work on Red Pill, which can be used to detect whether code is being executed under a VMM (virtual machine monitor) or under a real environment.

But they also comment that effectiveness of the "blue pill" may have something to do with Pacifica design flaws, right? I infered that Intel chips might not be as susceptible. Or may be they are. The article could have used better editing. If you are talking about the part that states; "AMD's SVM/Pacifica virtualization technology to create an ultra-thin hypervisor that takes complete control of the underlying operating system." I didn't take that as it not affecting Intel systems. I took it as they are using a technology developed by AMD to make this piece of malware.

I'm having a very strange problem. When I create a DATA dvd with imgburn I can only read the DVD from the drive I burned it with. The DVD is not readable on any other PC. The DVD is not readable even on the SAME PC (different drive) It is only readable on the drive it was burned with. Its a very strange problem. However, I don't have this problem with vSO CopyToDVD. I'd love to get his fixed in imgburn.. I've been waiting so long for this feature

If you are talking about the part that states; "AMD's SVM/Pacifica virtualization technology to create an ultra-thin hypervisor that takes complete control of the underlying operating system." I didn't take that as it not affecting Intel systems. I took it as they are using a technology developed by AMD to make this piece of malware.

Like a new model of car, best give Vista at least a year before installing it. By then most of the major fuck ups should be fixed (which'll create new ones, natch). By then the security companies will surely have developed ways to detect and defeat this "Blue Pill" rootkit. The article isn't clear--or maybe I just don't know enough--but it seems to imply that Intel-based systems wouldn't be effected Did I read it incorrectly?

Thanks DVDFAB Video Manager creator works great. Would have been great to have it all in one tool tho. Perhaps we can still persuade LUK to still consider it as a requirement to create ISOs

We at Doom9 forums are looking into a experimental layer break format (IE seamless) similar to the way that Superbit DVDs do their layer breaks. What essentially it looks like it does is causes the buffer to remain full enough so when a layer break occurs that there will be no pause or skip as occurs with most layer breaks and most home DVD players. Rolz the developer of PGCedit has added to a beta of his code to make layer breaks seamless with a option set. Using decrypter to burn with manually adding where the layer break occurs (calculated from the sector id used in PGCedit to create the ISO) I have burned several dual layer disks. They all seem to work flawlessly on playback on my home DVD players with no pauses at the breaks. Using IMGburn or Decrypter for that matter and a regular non seamless break (flag 0 or 2 depending on if it is at the start of a vob or not) I would get a slight pause at the break (as expected from any dual layer). This is exciting stuff and I have some questions on IMGburn. First if I use imgburn to burn with the seamless flag on it seems to give a error saying incorrect format. If I set the manual break sector lba (as I do in Decrypter) would it work the same as decrypter and burn anyways and leave the seamless flag set? In any case maybe you could get with Rolz and discuss a way to be able to start imgburn and have it ignore that the break is seamless (like a runtime parameter that would also accept the layer break position)? Now I only have tested several titles due to the expense of dual layer disks, but so far every one burned with the seamless flag set works great in all of my players (no pausing at layer break). Discussion link: http://forum.doom9.org/showthread.php?t=110426 To the rest of the forum: This is purely experimental and may produce coasters for some of your home DVD players (mainly older ones I would guess) so be warned. Thanks, Jamos

Consider the free version of DVDFab 0.17.0, which can create a basic video manager from a VTS. www.mrbass.org/dvdfab Regards

Hi! This is the first time I use the brand new "build" option of ImgBurn to create an ISO image. When I try to burn the image via the MDS file I got the following log, where it warns about a "L0 Data Zone Capacity Miscompare", even if the process finalilzes succesfully. Should I worry about this error? the dvd+r that I got seems to be correct. Thanks and congratulations for this software. Best regards, Errupin. I 13:02:51 ImgBurn Version 2.0.0.0 started! I 13:02:51 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2) I 13:02:51 Initialising SPTI... I 13:02:51 Searching for SCSI / ATAPI devices... I 13:02:51 Found 2 DVD?RWs! I 13:03:35 Operation Started! I 13:03:35 Source File: D:\DVD\WILLOW\WILLOW.MDS I 13:03:35 Source File Sectors: 3.887.536 (MODE1/2048) I 13:03:35 Source File Size: 7.961.673.728 bytes I 13:03:35 Source File Volume Identifier: WILLOW I 13:03:35 Source File Application Identifier: IMGBURN - THE ULTIMATE IMAGE BURNER! © 2006 LIGHTNING UK! I 13:03:35 Source File Implementation Identifier: ImgBurn I 13:03:35 Source File File System(s): ISO9660; UDF (1,02) I 13:03:35 Destination Device: [0:0:0] PIONEER DVD-RW DVR-111D 1.06 (E:) (ATA) I 13:03:35 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) (Speeds: 2,4x; 4x; 6x; 8x) I 13:03:35 Destination Media Sectors: 4.173.824 I 13:03:35 Write Mode: DVD I 13:03:35 Write Type: DAO I 13:03:35 Write Speed: 2x I 13:03:35 Link Size: Auto I 13:03:35 Test Mode: No I 13:03:35 BURN-Proof: Enabled I 13:03:35 Optimal L0 Data Zone Capacity: 1.943.775 I 13:03:35 Optimal L0 Data Zone Method: Copied From Original Disc W 13:03:59 L0 Data Zone Capacity Miscompare! W 13:03:59 Wanted: 1943775, Got: 1943776 I 13:04:08 Filling Buffer... I 13:04:09 Writing LeadIn... I 13:04:10 Writing Image... I 13:04:10 Writing Layer 0... (LBA: 0 - 1943774) I 13:24:26 Writing Layer 1... (LBA: 1943775 - 3887535) I 13:44:50 Synchronising Cache... I 13:44:51 Closing Track... I 13:44:52 Finalising Disc... I 13:45:52 Image MD5: cd2fe5e8c7e434520260ecd66b9c7794 I 13:45:52 Operation Successfully Completed! - Duration: 00:42:16 I 13:45:52 Average Write Rate: 3.187 KB/s (2.3x) - Maximum Write Rate: 3.385 KB/s (2.4x)

Do you still have the files you built the ISO from? If so, are they DVD Video files? i.e. IFO/BUP/VOB ones. During the initial build did you get a 'Create Layer Break Position' dialog box come up? If you did, can you please get it up on the screen again and take a screenshot of the window - perhaps with the same option selected that you selected when you actually built the image. Basically the MDS file is wrong and that probably means the padding for the layer break is wrong too. (Since v2 was released I've fixed a couple of bugs to do with 32k padding on certain sets of dvd video files. One of these bugs could indeed cause this padding problem.)