davexnet Posted August 11, 2009 Posted August 11, 2009 Hello - I'm using the latest Imgburn in XP Sp3. After a successful write to a DVD, I close the program by clicking in the upper right corner, when a message box appears. It says: Access violation at address 77422912 in module comctl32.dll Read of address 00000000. It seems to be associated with Imgburn since Imgburn remains in the Taskbar until I click OK on the above message. Here's the relevant log. ; //****************************************\\ ; ImgBurn Version 2.5.0.0 - Log ; Tuesday, 11 August 2009, 00:08:48 ; \\****************************************// ; ; I 23:53:17 ImgBurn Version 2.5.0.0 started! I 23:53:17 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 3) I 23:53:17 Total Physical Memory: 2,030,044 KB - Available: 1,387,784 KB I 23:53:17 Initialising SPTI... I 23:53:17 Searching for SCSI / ATAPI devices... I 23:53:18 Found 1 CD-RW and 1 DVD
Cynthia Posted September 19, 2009 Posted September 19, 2009 Curious. Did you find a solution to your issue?
davexnet Posted May 18, 2010 Author Posted May 18, 2010 No it's still doing it in XP SP3 even after the more recent version of Imgburn. I had a situaltion today (and I sent in the generated diagnostic info ) Where I was writing a data disk (files and folders). I was using the disk layout editor screen. Files were added, I wrote the disk, then re-opened the layout editor. Deleted the files, added some new files and wrote a 2nd disk. Repeated this a couple of more times, each time, simply simply redoing the layout editor before writing the next disk. Then I received about 4 or 5 of the crashes in comctl32 one after the other. Is the problem related to the layout editor? Second question. Assume I have added a compilation of files to the layout editor. Instead of burning the disk, I save the project with the intent of burning it later. But before I burned the project some of the source files were accidentally deleted or moved. When the project is reopened, the layout editor (or anything else for that matter) does not indicate that some of the files are unavailable. Shouldn't it tell you?
Recommended Posts