Solved the Logic 1Gig+ RAM problem! (error 108)
#1
Posted 21 May 2004 - 05:05 AM
I have found a workaround for the problem of Logic interpreting RAM in excess of 1Gig as 'negative' memory and thus producing the notorious 'out of memory' message when you try to glue audio and import midi.
The answer is: you can limit the amount of memory that Windows (and all applications) "sees". This requires a reboot but can be easily switched back to full RAM with another reboot.
First, make sure your system is set to allow Windows to manage the swap file. (in Control Panel > System > Advanced > Settings)
Then go to Start -> Run, type "msconfig".
Click the boot.ini tab.
Click 'Advanced Options'.
Tick 'MaxMem', and in the box type "1024" (no quotes).
When you click Ok to leave msconfig you will be prompted to reboot.
This is described here:
http://support.micro...kb;EN-US;181966
When the PC restarts (at least, when _mine_ restarts -- lol!) I am able to finally use Logic without the ridiculous memory problem.
You can verify that the amount of memory 'seen' by the system is only 1gig by going to control panel > system.
It is still a shame that this requires you limit the available memory, even if only temporarily; however many of you have dual boot music PCs anyway, so it would be simple enough to make the music installation permanently 'see' only 1gig of RAM.
I do hope this helps everyone. I think it's shameful that emagic won't update their Windows program now that they are owned by Apple, but am glad to at least not have to take the RAM physically out of my machine!
Iain
#3
Posted 21 May 2004 - 11:56 AM
I have subsequently found that the most efficient way of switching between setups is to add an extra line to the boot.ini file (I'd only recommend this for advanced users, I don't want to risk messing up anyone's PC!):
Under '[operating systems]' in boot.ini, I now have:
'multi(0)disk(0)rdisk(0)partition(1)WINDOWS="Microsoft Windows XP Home Edition" /fastdetect' (no quotes)
This is the normal setup with 2Gig RAM.
But the next line is:
'multi(0)disk(0)rdisk(0)partition(1)WINDOWS="Microsoft Windows XP for Logic" /fastdetect /maxmem=1024'
The 'maxmem' part is added automatically by msconfig. But by having *both* lines in boot.ini, you are given a choice when you boot between the full RAM system (for general apps) and the limited 1Gig one (for logic).
I'll be interested to hear how this works for people -- please ask if anything's unclear.
Regards
Iain
#4
Posted 29 August 2004 - 02:06 AM
Anyway, I'm still interested to hear about how it works for everyone else...
#5
Posted 05 October 2004 - 08:43 AM
Anyway, I'm still interested to hear about how it works for everyone else...
Hi Ian,
My name is Dan and i am a Logic user,
are you sure that Logic works only at 1Gigabyte
because a friend of mine have 1.5 gigas and no problems with glue tool and
out of memory messages...
Me have same problem because 2 gigs of memory on Xp pro...
Best to you...
#6
Posted 05 October 2004 - 09:01 PM
because a friend of mine have 1.5 gigas and no problems with glue tool
I, myself, using 1.5 gigs, could glue some combinations of regions, across different tracks, stereo only, but sequential regions in the same track, and or mono tracks, as well as other various incidences, would not glue. Can't say why or why not. Have not tried the "fool Windows" trick, but it sure seems to be worth a try. (I have been using samplitude for most of my audio editing, and so only for that reason have I not.)
Z
#8
Posted 02 November 2004 - 08:24 AM
How can i do the RAM trick in WINDOWS 2000.
When i startup Logic, it takes 450 from my RAM and with 8 track and 8 plugins i am on 800mb!!
I can not work!!
Antonis
I don't think, from what you say, that your issues are related at all to the topic being discussed here.
You have already posted a question relating to this, in it's own thread here. Why don't you follow up on that ?
#9
Posted 08 July 2005 - 08:35 AM
I discovered this 1 gig limitation error the hard way, AFTER i bought a 2 gig dualchannel set for my new mobo/music pc.
Well, i tried that little neat trick that was suggested in the top of this topic, BUT, if the mobo is "native" dualchannel, and detects the 2 gig at startup, Windows craches with a bsod at startup. Since i guess that running in dualchannel, kinda configures the ram as 1 block, and not 2. ??
Just for info. Hope it can help someone.
Dr. A-Funz
#10
Posted 10 July 2005 - 08:02 PM
hello , i didn't find the window with the swap file thing.
and when i click "advanced option" in the "boot.ini" window i get a crash message.
[AMD 3.8 64bit , 2GB RAM , XP , Logic 5.5.1]
This post has been edited by hitphy: 10 July 2005 - 08:05 PM
#12
Posted 27 July 2007 - 05:20 AM
I posted this the other day, I just wanted to add to it.
Hi All
I tried reducing the amount of memory that windows sees. That worked ok but limited my RAM, thus limited the amount of samples I could use.
I reset to the full amount in my system 2048mb and installed Cacheman 5.50 by chance, I don't know what it does or how it does it, but the memory problem is almost gone or i get one error warning message when I really push the system.
http://www.download....4-10216523.html
This really worked on my machine so I hope it works for you.
It is not a total fix, as the issue does appear when you go over 1.5gb memory usage. If you do get the memory error at that point you need to delete undo history to prevent loss of data and song problems.
Before i installed the cacheman songs would corrupt and not open, when the error appeared the undo would not work plus hanging for long periods. But after cacheman I dont see it to that extent anymore.
Keep Logic on the PC alive!!!!!!!!
#13
Posted 07 March 2008 - 11:57 AM
I have found a workaround for the problem of Logic interpreting RAM in excess of 1Gig as 'negative' memory and thus producing the notorious 'out of memory' message when you try to glue audio and import midi.
The answer is: you can limit the amount of memory that Windows (and all applications) "sees". This requires a reboot but can be easily switched back to full RAM with another reboot.
First, make sure your system is set to allow Windows to manage the swap file. (in Control Panel > System > Advanced > Settings)
Then go to Start -> Run, type "msconfig".
Click the boot.ini tab.
Click 'Advanced Options'.
Tick 'MaxMem', and in the box type "1024" (no quotes).
When you click Ok to leave msconfig you will be prompted to reboot.
This is described here:
http://support.micro...kb;EN-US;181966
When the PC restarts (at least, when _mine_ restarts -- lol!) I am able to finally use Logic without the ridiculous memory problem.
You can verify that the amount of memory 'seen' by the system is only 1gig by going to control panel > system.
It is still a shame that this requires you limit the available memory, even if only temporarily; however many of you have dual boot music PCs anyway, so it would be simple enough to make the music installation permanently 'see' only 1gig of RAM.
I do hope this helps everyone. I think it's shameful that emagic won't update their Windows program now that they are owned by Apple, but am glad to at least not have to take the RAM physically out of my machine!
Iain
Hello mate! This trick has helped me, I'm on core 2 quad, 2gb ram. I've limit my ram, but I work with video too and I decide to make dual boot xp system, one for Logic + audio and other for video. But now I can't limit my ram

Sign In
Register
Help

MultiQuote
