Defenestration

EMET 4 detects SimExecFlow mitigation on ImgBurn shutdown. Happens with both UPX and non-UPX versions of ImgBurn. Workaround: Disable SimExecFlow detection for ImgBurn.

OK thanks.

As you can see from the log, the "Synchronising Cache..." stage takes a long time. I'm sure IB 2.3.2.0 didn't take this long. Is 3 minutes 18 seconds normal ? I will post some more logs if needed from the previous version of ImgBurn, and from different media and drive. I 04:18:33 ImgBurn Version 2.4.0.0 started! I 04:18:33 Microsoft Windows XP Professional x64 Edition (5.2, Build 3790 : Service Pack 2) I 04:18:33 Total Physical Memory: 4,193,120 KB - Available: 2,867,704 KB W 04:18:33 Drive F:\ (FAT32) does not support single files > 4 GB in size. W 04:18:33 Drive G:\ (FAT) does not support single files > 4 GB in size. I 04:18:33 Initialising SPTI... I 04:18:33 Searching for SCSI / ATAPI devices... I 04:18:54 Found 2 DVD±RW/RAMs! I 04:19:10 Operation Started! I 04:19:10 Device: [0:0:0] TSSTcorp CD/DVDW SH-S182M SB05 (S:) (USB) I 04:19:10 Media Type: DVD-RW (Disc ID: MKM 01RW6X01) (Speeds: 4x, 6x) I 04:19:10 Quick Erase: Yes I 04:19:10 Erasing Disc... I 04:19:40 Operation Successfully Completed! - Duration: 00:00:29 I 04:19:40 Operation Started! I 04:19:40 Source File: B:\Backup\Essential_Software\Possible\MemTest86+\memtest86+-2.01.iso I 04:19:40 Source File Sectors: 898 (MODE1/2048) I 04:19:40 Source File Size: 1,839,104 bytes I 04:19:40 Source File Volume Identifier: MT201 I 04:19:40 Source File Application Identifier: MKISOFS 1.1.2 I 04:19:40 Source File File System(s): ISO9660 (Bootable) I 04:19:40 Destination Device: [0:0:0] TSSTcorp CD/DVDW SH-S182M SB05 (S:) (USB) I 04:19:40 Destination Media Type: DVD-RW (Disc ID: MKM 01RW6X01) (Speeds: 4x, 6x) I 04:19:40 Destination Media Sectors: 2,298,496 I 04:19:40 Write Mode: DVD I 04:19:40 Write Type: DAO I 04:19:40 Write Speed: MAX I 04:19:40 Link Size: Auto I 04:19:40 Test Mode: No I 04:19:40 OPC: Yes I 04:19:40 BURN-Proof: Enabled I 04:19:41 Filling Buffer... (40 MB) I 04:19:41 Writing LeadIn... I 04:19:47 Writing Session 1 of 1... (1 Track, LBA: 0 - 897) I 04:19:47 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 897) I 04:19:47 Synchronising Cache... I 04:23:05 Image MD5: 9fae22f2666369968a76ef59e9a81ced

I created an image of a data CD (my XP installation disc) using ImgBurn, and then created two more images of the same disc with IsoBuster (one User Data, the other RAW). Both User Data ISO's were exactly the same (ie. 591MB and same MD5), but the RAW image was a fair bit larger (ie. 678MB). Why does ImgBurn create ISO's from User Data instead of RAW, or does it depend on the source disc (ie. sometimes it will use User Data, other times RAW) ?

Thanks LUK! BTW, I wasn't using the CLI mode.

I just backed up the ImgBurn.ini file, and after re-installing ImgBurn I just copy the .ini file to the IB program folder before starting IB. The setting is remembered by IB (ie. Settings->Graph Data->Default Folder is set to custom with the path as "D:\ImgBurn_Graph_Data\").

After re-installing Windows, I used my previous ImgBurn settings which I had backed up. The original Graph Data folder no longer existed and when I burned an image, the graph data file was placed in the root folder, instead of the folder being automatically created. To reproduce, 1) Create a folder (eg. D:\ImgBurn_Graph_Data) 2) Go into ImgBurn and set this location as the graph data folder 3) Delete the folder created in (1) 4) Burn an image The graph data will be placed in D:\, and not D:\ImgBurn_Graph_Data\

As this option also applies to the Build mode, then I think it would be more suited under the Verify tab of the settings dialog.

Build->Don't Prompt VIDEO_TS Content->Answer No does not work. It always answers Yes.

Fair enough. You don't ask.... I'm actually in the process of building a new Desktop which should solve a lot of the "slow" issues I'm having with my laptop. To keep the case nice and tidy on the inside, I'm hoping to get some SATA DVD writer's for it. I read in another thread that you mentioned that there should be no problems as long as you use the SATA connections provided by the motherboard chipset, as opposed to third party chipsets. This is OK for starters (I'm using Asus P5B Deluxe which offers 6 + 2 SATA-II ports) but later on I may want to add further SATA ports. Do you have any recommendations for good (ie. reliable and compatible) PCI or PCIe SATA-II cards ?

Loving the new version 2.2! Great work as always LUK! The new Automatic Write Speed is very useful, and could be even more so IMO. I can usually burn at a faster speed when the source files are on my internal hard drive, compared to when the source files are on an external hard drive. With this in mind it would be very handy if source drive letters could also be specified, allowing a different write speed to be automatically used with the same media when different hard drives are used for the source media. If the source files are on multiple drives, the minimum speed is used. One other thing, the log shows the Write Speed specified under the Device tab, instead of having a line like "Automatic Write Speed engaged: MCC-004-000 BENQ DVD LS DW1655 E:" which could be useful.

Thanks for the heads-up polo. I missed his other post.

I have an NEC AD-7173A which is the same as the Sony AWG170A (NEC and Sony merged their optical drive departments to create a new company called "Optiarc") and don't have any problems burning with it in an external enclosure. It's a great drive. First off, what media are you using (in particular the media ID code) ? If you are using good quality media like Taiyo Yuden or Verbatim (Mitsubishi CC), then I would get a replacement drive. However, post the log here so we can see what's going wrong.

I've got myself a licence for IPB and want to set up a forum with it. I did a test installation, and noticed that the username you enter for the administrative account during installation ends up being added to the "Root Admin" group which is highlighted with a red colour. I noticed on the ImgBurn forum that LUK! is a member of the "Admin" group which is also highlighted with a red colour. I'm wondering whether it's good practice to have one username which is used solely for root administrative tasks, and then have another username which is used for general purposes including normal admin tasks ? I'm thinking that this way a hacker would have to guess both the username and the password to get root admin access, since you would mainly only be logged on with the admin user and not the root admin user. Is this what you have done LUK!, or have you just changed the name of the "Root Admin" group to just "Admin", and so have single username with root admin access ? Any advice would be appreciated.

Have you considered "Need For Speed"? I did but decided against it on the following review/rating: http://uk.gamespot.com/search.html?type=11...amp;x=0&y=0 Part of me went for GT because that's what I'm familiar with. I had considered (and may still get him) Burnout 3: Takedown due to it's great review at the same site above, and preferential reviews compared to Revenge. Who am I kidding..... I'm getting these games for myself!