goldenfingaz Posted July 28, 2008 Posted July 28, 2008 Hi, i found something i think its a bug. When i set on the I/O tab the Buffer size to more than 330MB i get 2 error messages. I added 2 sceenshots as attachment.
mmalves Posted July 28, 2008 Posted July 28, 2008 It's not a bug: that happened because you didn't have enough available memory for a 512 MB buffer. When you start ImgBurn, the 3rd line from the Log window tells you how much available memory there was when ImgBurn was started.
goldenfingaz Posted July 28, 2008 Author Posted July 28, 2008 (edited) It's not a bug: that happened because you didn't have enough available memory for a 512 MB buffer. When you start ImgBurn, the 3rd line from the Log window tells you how much available memory there was when ImgBurn was started. Nice Avatar pal. There is enough free. I 15:16:49 ImgBurn Version 2.4.2.0 started! I 15:16:49 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 3) I 15:16:49 Total Physical Memory: 3.144.104 KB - Available: 2.502.420 KB I 15:16:49 Initialising SPTI... I 15:16:49 Searching for SCSI / ATAPI devices... I 15:16:49 Found 3 DVD-ROMs and 2 DVD Edited July 28, 2008 by goldenfingaz
LIGHTNING UK! Posted July 28, 2008 Posted July 28, 2008 What does that error say in english? The API call is failing, it's nothing to do with ImgBurn.
goldenfingaz Posted July 28, 2008 Author Posted July 28, 2008 (edited) Reason: For this command is not enough ram available. But there is enough. I 18:54:39 ImgBurn Version 2.4.2.0 started! I 18:54:39 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 3) I 18:54:39 Total Physical Memory: 3.144.104 KB - Available: 2.457.224 KB I 18:54:39 Initialising SPTI... I 18:54:39 Searching for SCSI / ATAPI devices... I 18:54:40 Found 3 DVD-ROMs and 2 DVD Edited July 28, 2008 by goldenfingaz
LIGHTNING UK! Posted July 28, 2008 Posted July 28, 2008 Sorry, it's just a Windows API function that I call with the specified size. It's failing and that's the reason Windows is reporting.
goldenfingaz Posted July 28, 2008 Author Posted July 28, 2008 Sorry, it's just a Windows API function that I call with the specified size. It's failing and that's the reason Windows is reporting. Ok, thanks for reply and for ImgBurn too.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now