roberto21

Of course, this may be possible. However, with 2.5.5.0, after the error was detected by Verify, the disk appeared indeed "empty", as if nothing had been written on it (I was trying with an ISO bootable image, 25 minutes of processing). With 2.5.1.0, no error detected, disk full and working. Anyhow, I'll reload the new version and, if the error occurs again, I'll try to post a log. Thanks for your attention and patience. Roberso

I don't know why I cannot reply to this existing topic, maybe administrators can set things straight moving this post to the correct place. I just wanted to add my personal experience: using an ASUS laptop, win7 64bit, with two dvd drives (IDE\CdRomHL-DT-ST_DVDRAM_GT30N and an ASUS_SDRW-08D1S-U1 USB), I have been using imgburn without particular problems until I switched to the last version 2.5.5.0. At this point, I was not able to write any disk without getting the "session mismatch" error on both drives; after trying more or less everything (short of updating the chipset drivers, that are already up-to-dated, according to ASUS site), I decided to switch back to 2.5.1.0, and magically the problem disappeared. Now everything is fine again. If somebody can make any sense of this, please let everybody know... Robergt