DeathStalker Posted October 11, 2011 Share Posted October 11, 2011 Reason: Not enough storage is available to process this command. Followed by - Failed to initialise FIFO Buffer (536,870,912 bytes) This ONLY happens when trying to burn files/folders, and not *every* time. I 15:07:32 ImgBurn Version 2.5.6.0 started! I 15:07:32 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7601 : Service Pack 1) I 15:07:32 Total Physical Memory: 8,387,052 KB - Available: 2,140,968 KB I 15:07:32 Initialising SPTI... I 15:07:32 Searching for SCSI / ATAPI devices... I 15:07:33 -> Drive 1 - Info: (ATA) I 15:07:33 -> Drive 2 - Info: (SCSI) I 15:07:33 Found 1 DVD±RW/RAM and 1 BD-ROM/HD DVD-ROM! I 15:09:53 Operation Started! I 15:09:53 Building Image Tree... I 15:09:53 Calculating Totals... I 15:09:53 Preparing Image... I 15:09:53 Contents: 12 Files, 2 Folders I 15:09:53 Content Type: DVD Video I 15:09:53 Data Type: MODE1/2048 I 15:09:53 File System(s): ISO9660, UDF (1.02) I 15:09:53 Volume Label: XXXXXXXX I 15:09:53 IFO/BUP 32K Padding: Enabled I 15:09:53 Region Code: 1, 2, 3, 4, 5, 6, 7, 8 I 15:09:53 TV System: NTSC I 15:09:53 Size: 3,117,830,144 bytes I 15:09:53 Sectors: 1,522,378 I 15:09:53 Image Size: 3,118,465,024 bytes I 15:09:53 Image Sectors: 1,522,688 I 15:09:54 Operation Successfully Completed! - Duration: 00:00:01 The popup for the Size appears, I click OK, then I get the VirtulAlloc, followed by the FIFO. There are NO problems *creating* an image, OR burning an image - only when burning files/folders - regardless of the type (Joliet/UDF) Thanks for any assistance. (It's getting quite annoying having to build an image for everything first). Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted October 11, 2011 Share Posted October 11, 2011 It's quite simple, just don't use such a big buffer if your machine can't handle it. Of course I already told you that here :- http://forum.imgburn.com/index.php?showtopic=18628 Link to comment Share on other sites More sharing options...
DeathStalker Posted October 11, 2011 Author Share Posted October 11, 2011 It's quite simple, just don't use such a big buffer if your machine can't handle it. Of course I already told you that here :- http://forum.imgburn.com/index.php?showtopic=18628 Yes, you said that, but you didn't *explain* it. I've got 8gb of RAM and a Dual Core 3.1 cpu. Please explain how my system can't handle a 512k buffer - AND why it only occurs when trying to burn files/folders but images are fine. Thank you. Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted October 11, 2011 Share Posted October 11, 2011 It's not down to me to explain why the VirtualAlloc function may or may not fail, I didn't write it - ask Microsoft. It's a 512MB buffer, not 512KB. You've probably set both buffers to 512MB yeah... so that means you're using 512MB for the reading side and another 512MB for the writing side - making 1GB in total. That's quite a bit when you've only got 2GB available and it's supposed to be contiguous memory. I've got 16GB of RAM and I still only use the default buffer settings. Ever heard the saying 'just because you can doesn't mean you should' ? Link to comment Share on other sites More sharing options...
DeathStalker Posted October 11, 2011 Author Share Posted October 11, 2011 Ok, that makes a bit more sense (my bad on the kb vs mb, lol). I thought the error was from ImgBurn, not Windows (kinda hard to tell if you're not a programmer Link to comment Share on other sites More sharing options...
Recommended Posts