Jump to content
Sign in to follow this  
goldenfingaz

I/O Buffer trouble when higher than 330MB on 2.4.2.0

Recommended Posts

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.

post-13306-1217247073_thumb.png

post-13306-1217247077_thumb.png

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites
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. :thumbup:

There is enough free. :whistling:

 

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 by goldenfingaz

Share this post


Link to post
Share on other sites

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 by goldenfingaz

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites
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. :)

Share this post


Link to post
Share on other sites
Sign in to follow this  

×

Important Information

By using this site, you agree to our Terms of Use.