marcinez Posted April 11, 2007 Posted April 11, 2007 I have problem with version 2.3.1.0. My english is bad so I show you screen. This is new version LOG: I 19:39:09 ImgBurn Version 2.3.1.0 started! I 19:39:09 Microsoft Windows 2000 Professional (5.0, Build 2195 : Service Pack 4) I 19:39:09 Total Physical Memory: 523 752 KB - Available: 213 884 KB W 19:39:09 Drive C:\ (FAT32) does not support single files > 4 GB in size. I 19:39:09 Initialising SPTI... I 19:39:09 Searching for SCSI / ATAPI devices... I 19:39:09 Found 3 DVD?RWs and 1 DVD?RW/RAM! And problem is: In version 2.3.0.0 no problem: LOG: I 19:48:33 ImgBurn Version 2.3.0.0 started! I 19:48:33 Microsoft Windows 2000 Professional (5.0, Build 2195 : Service Pack 4) I 19:48:33 Total Physical Memory: 523 752 KB - Available: 227 788 KB W 19:48:33 Drive C:\ (FAT32) does not support single files > 4 GB in size. I 19:48:33 Initialising SPTI... I 19:48:33 Searching for SCSI / ATAPI devices... I 19:48:33 Found 3 DVD?RWs and 1 DVD?RW/RAM! And screen: Version 2.3.1.0 can't read good large of file.
LIGHTNING UK! Posted April 11, 2007 Posted April 11, 2007 Hmm ok, I've seen a similar report about an image being found as 2336 elsewhere so I will look into this asap. Thanks for reporting it.
marcinez Posted April 11, 2007 Author Posted April 11, 2007 Next when I want to write dvd program convert this mode 2336 into 2048 but dvd is bad, and I can't read this writed dvd.
LIGHTNING UK! Posted April 11, 2007 Posted April 11, 2007 Damnit, it was because of the new FAT16/FAT32 detection code. On some images of certain sizes, it could get the sector size wrong by matching a signature code earlier than it should have been. I guess I'll be releasing 2.3.2.0 VERY soon then!
marcinez Posted April 11, 2007 Author Posted April 11, 2007 I guess I'll be releasing 2.3.2.0 VERY soon then! I'll be wait. Now I returned to 2.3.0.0 version
LIGHTNING UK! Posted April 11, 2007 Posted April 11, 2007 That's fine, I might even release it tonight!
steom Posted April 11, 2007 Posted April 11, 2007 In this new version the Lock Volume for Exclusive access of the drive doesn't work anymore. at least in my system. The 2.3.0.0. work flawless.
LIGHTNING UK! Posted April 11, 2007 Posted April 11, 2007 Doesn't work in what way? I don't remember touching it! The only thing I might have done is fail silently when specific error codes are returned - but of course if it doesn't error out in the first place, that doesn't come into it.
LIGHTNING UK! Posted April 11, 2007 Posted April 11, 2007 Nope, I dunno what you mean. I just opened up 2 instances of ImgBurn, both pointing to the same drive and then tried to burn something with one of them. I got the 'unable to lock....' error as expected.
Recommended Posts