glad you found it but put the swap file back to the size you had it 3 times the ram. just make the min one less then the max that will befine.
am glad it was not the extra stacks being needed as i could not find any way of telling you how to add them in xp? just the tweak program.
steegy if the system has multiple hd's on a raid card the ram does not really matter for the amount of swap file.
it needs to set up to work with dividing the amount for each hd. i don't know the forumla but i just put it one 3rd the size of the drive its on.
and i try to make that the fastest hd to help it's speed. but by putting the requirement size for each hd on the one it gets rather big.
but that allows more room on the other hd's for file storage.
but i'm just glad he did not have all that trouble.
roving cowboy / keith hall. My skinshttp://www.mediamonkey.com/forum/viewto ... =9&t=16724 for some help check on Monkey's helpful messages at http://www.mediamonkey.com/forum/viewto ... 4008#44008MY SYSTEMS.1.Jukebox WinXp pro sp 3 version 3.5 gigabyte mb. 281 GHz amd athlon x2 240 built by me.) 2.WinXP pro sp3, vers 2.5.5 and vers 3.5 backup storage, shuttle 32a mb,734 MHz amd athlon put together by me.) 3.Dell demension, winxp pro sp3, mm3.5 spare jukebox.) 4.WinXp pro sp3, vers 3.5, dad's computer bought from computer store. )5. Samsung Galaxy A51 5G Android ) 6. amd a8-5600 apu 3.60ghz mm version 4 windows 7 pro bought from computer store.
Page file size only depends on how large your RAM is, and how you use your computer (mainly as server, or mainly as client). If you have multiple hard drives, you can split this page file over the drives, so each drive has a smaller "disk size loss". Obviously it's best to put the page file on the fastest hard drive you have, and if possible (if you have a fixed 2nd drive) not on the primary one (it's best to offload it as much as possible). -- I don't want to be nitpicking, I just won't accept wrong information --
Back to the point of this thread:
@cmx: If you've found a specific file that causes issues with MediaMonkey (during scanning, tagging, playback, ...) while it normally should work fine, you can send it to the support at mediamonkey (file size as small as possible, or using something like YouSendIt) with enough information.
@cmx do not wait for a dev response to send the logs, the support email is there to accept such things always any time you have a problem and can log/reproduce it.
You can reference this thread in your email, that way if they do have a response on your logs/problems or the problem in general then they can post here if they desire.
Page file size only depends on how large your RAM is, and how you use your computer (mainly as server, or mainly as client). If you have multiple hard drives, you can split this page file over the drives, so each drive has a smaller "disk size loss". Obviously it's best to put the page file on the fastest hard drive you have, and if possible (if you have a fixed 2nd drive) not on the primary one (it's best to offload it as much as possible). -- I don't want to be nitpicking, I just won't accept wrong information --
Back to the point of this thread:
@cmx: If you've found a specific file that causes issues with MediaMonkey (during scanning, tagging, playback, ...) while it normally should work fine, you can send it to the support at mediamonkey (file size as small as possible, or using something like YouSendIt) with enough information.
steegy why can't you read the same thing different ways?
you said what i said only differently.? split it up if you want too and put it on the faster hd. same thing i said. only the ram does not really matter, proof is in my systems i use and or take care of. it was one of my systems that 3d game asked for more swap file and i have the large one on there with 500+ mbs of ram so the ram did not matter it wanted more swap file. if i say something its because I've more then likely have done it.
you should know that by now.
as i said before I'm just glad he did not have all that mess to fix and he got it working.
cmx make sure you do a couple logs to double the chance it finds the error.
Last.FM Node
