r0cker22 Looks like Creaky got you there. Though your RAM is near borderline the memory allocation error didn't occur with the new install of Nero. Firmware covers write strategies and media supported. It's obvious why that should be kept updated if problems are encountered. Using good media is important. That's why you see people with problems asked what they're using. Be aware brands sell media by different manufacturers. That's why I asked earlier for the manufacturer code from an app such as DVD Identifier. With the Nero, your log identifies the media manufacturer. That's why Creaky was inquiring about what you were using and suggesting the "good stuff". Software updates solve problems encountered with the software (bugs) as well as adds new function. Those in the know sometimes give you the solution without a complete explanation of the cause. Some users of the earlier Nero 7 encountered memory allocation problems. Sound familiar? In the future keep a copy of your old Nero installation files you know to be stable. That way you know you have a stable version in case the new update malfunctions. If you encounter problems with the update, revert to the known stable version to see if that solves the problem and wait till a new release comes out if necessary. A lot of people needed to do this recently. The early 7 had problems and the release before 7.0.8.2 wouldn't work properly for a lot of users. Glad to see you got a good burn. BTW, 7.0.8.2 appears to be stable and the best of the Nero 7 so far. Creaky had good reason to suggest you update to the latest version of the software.
Good on ya , creaky. Heres a FULL extract from my NERO BIBLE Not enough memory Error code: 8:23:18 AM #2 Phase 114 File APIProgress.cpp, Line 263 DVD-Video files reallocation completed (no file modified) 8:23:19 AM #3 Phase 111 File APIProgress.cpp, Line 263 DVD-Video files sorted 8:23:19 AM #4 Text 0 File ThreadedTransfer.cpp, Line 505 Tried to get 48128 KB of memory 8:23:19 AM #5 TRANSFER -5 File ThreadedTransfer.cpp, Line 506 Error: not enough memory 8:23:19 AM #6 NEROAPI 7 File Burncd.cpp, Line 2975 Error:\nCannot connect TRF. 8:23:19 AM #7 Text 0 File AudioCompilationImpl.cpp, Line 828 DRM: DRM burn session terminated. 8:23:19 AM #8 Text 0 File AudioCompilationImpl.cpp, Line 857 DRM: Closing entire DRM handling. Bye. Existing drivers: Registry Keys: HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinLogon\AllocateCDROMs : 0 (Security Option) Solution: You have a basic problem with your Windows swap file - it's to low. How much free disk space do you have on your hard disk? Try these two things: 1. Reboot - can free up some space in your memory or swap file - you could have too much applications running at the same time. 2. Add some swap space. How to do: right clic on desktop --> properties --> advanced --> performances --> advanced --> modify --> choose a memory size x1.5 than the RAM size (e.G i choose 512 for initial and 512 for max). Last edited by cynthia : 2 Mar 2005 at 01:49 PM.
Gwendolin That doesn't work with XP to access the swap file. That enters "Display Properties" and there is no "advanced" or path to the swap file. From the Nero log r0cker22 is using XP. [bold]How to access and change swap file in Windows XP.[/bold] Start --> My Computer In the left hand column click View System Information. In the next System Properties window that opens click on the Advanced tab. In the first box called Performance click on Settings. In the next pop-up window click the Advanced tab. In the bottom box where it's labeled "Virtual Memory", you've guessed it, click on Change. In the new Virtual Memory window it should show you all incidences of paging files on your system. Highlight the one you want to get rid of and select the "no paging file" check box and then press set. If you want to customise the size of the swap file you want to keep, highlight it and then select the Custom size check box. I wonder about that. I have 2GB (2048MB) RAM and the initial size is 1536MB and the maximum is set to 3072MB and the system works great. In my case the ratio is x0.75 initial and x1.5 maximum. Unless there's a real need, I suggest leaving it where the system set it. According to the log there is 1022MB physical memory for rOck22's system. According to that the initial size may be in the range of 768MB and the maximum near 1536MB. Is that a personal compilation? Creaky supplied a recommendation on your rule 1 when he mentioned programs and the low amount of usable RAM and the need for more. As for swap files, you may want to add some of this info to your "bible", including the above instructions on how to access it in XP. It's material anyone can access from Windows support or Microsoft. Normally the swap file isn't a problem unless something out of the ordinary happens to corrupt the system. Then there are warnings other than just Nero having a memory problem. [bold]Note for novices on DVD backups: (commonly accepted and provided once again by Brobear) As a rule of thumb, you should have twice the size of your source files in free space on the hard drive before attempting a backup with most backup apps.[/bold] [bold]How Windows Determines the Recommended Maximum Swap File Size[/bold] [bold]Temporary Swap File[/bold] • Q. What is the temporary swap file recommended maximum size? A. [bold]It is four times the physical RAM in the computer, rounded to the next 4 megabytes (MB). For example, if you have 3 MB of free XMS memory, you can create 16 MB of virtual memory ([3 MB * 4] + 4MB = 16 MB). Four is the default value for the SYSTEM.INI [386Enh] switch "PageOverCommit=". The recommended maximum size is also limited by the "50 percent free hard drive space" rule (that is, a swap file cannot take more than 50 percent of the available, usable hard drive space [compressed or stacked hard drive space is not considered usable]).[/bold] Whichever limit is reached first establishes the maximum size. • Q. When I set a temporary swap file to a size larger than the maximum recommended size, the following error message is displayed. What does this message mean? Windows will not use more than the virtual memory specified by the Recommended Size. Are you sure you want to create a larger swap file? A. WIN386.EXE creates the temporary swap file at run time, and the file grows as necessary; the swap-file functionality only controls the maximum size allowable. You can never exceed 50 percent of the free hard disk space or four times the amount of physical RAM. [bold]Permanent Swap File[/bold] • Q. When I set a permanent swap file to a size larger than the recommended maximum size, Windows forces the setting back to the recommended maximum size, even when plenty of free hard drive space exists. When this occurs, the following message is displayed. What does this message mean? The number you specified is too large. The number currently displayed is the largest you can specify. A. When Windows sets up a permanent swap file, free and contiguous hard drive space limits the recommended maximum size. A permanent swap file must be located on unfragmented space; therefore, even if there is plenty of disk space, the swap file is limited by file fragmentation. If you have an disk-optimization program, such as Speedisk by Norton Utilities or Compress by PC Tools, you can use it to make more of the free hard drive space contiguous and usable for a permanent swap file. [bold]NOTE: The maximum size limitations described in the first answer apply in addition to the required unfragmented disk space.[/bold] NOTE: These utilities should not be run from Windows and should not be run if you are using a disk cache. For more information, consult the manual for the utility you are using. KBCategory: kbusage KBSubcategory: wfw win31 wfwg ==================================================== [bold]How Windows Handles Bad Permanent Swap Files[/bold] SUMMARY This article explains the process Windows follows to find or re-create an existing permanent swap file if a swap file problem is detected. The swap file is an element of the memory management services Windows provides. It is used to swap application code and data that is not being used from RAM to the hard disk. In this manner, Windows can provide more memory to your applications than is physically installed on your computer. MORE INFORMATION After you type win at the MS-DOS prompt, Windows reads the SYSTEM.INI file for various startup information, including the size, type and whereabouts of the swap file. If Windows finds a reference to a swap file, it looks for it (386SPART.PAR) on the hard disk. If 386SPART.PAR is the wrong size (zero bytes, for example), Windows (WIN386.EXE) deletes and recreates 386SPART.PAR. If 386SPART.PAR does not exist at all, the following error message is displayed on a blue screen: Corrupt Swap-File Warning This error message asks if you would like to delete the corrupted swap file. If you choose No, Windows does not attempt to correct the bad permanent swap file, and starts normally. Until you choose Yes, every time you start Windows, you will receive this error message. If you choose Yes, the next time you start Windows, CPWIN386.CPL (the 386 Enhanced portion of Control Panel) is used to create a new swap file. If the permanent swap file is created successfully, no further problems occur and all the settings in your Windows configuration should be the same as they were before you had swap file problems. If Windows cannot find CPWIN386.CPL or if there is a problem with the file, the following error message is displayed: The CPWIN386.CPL utility could not be run. Either CPWIN386.CPL could not be found, an access error occurred on the file, or there was insufficient memory to run the utility. The permanent swap file can not be set up. If you receive this error message, make sure the file, CPWIN386.CPL, is in your SYSTEM subdirectory. If CPWIN386.CPL loads successfully but fails to create a permanent swap file, the following error message is displayed: The CPWIN386 utility was not able to set up the permanent swap file. This error message could be caused by insufficient disk space or other problems that normally prevent permanent swap file creation.
