S
smidgie
New member
What kind of tweaks can i do to windows 2000 pro to get n-track to work at it's highest performance? i've already set the cache size to twice my ram and made the min and max the same. what else can i do?
Slackmaster2K
Gone
Nothing really. n-Track runs great on Windows 2000 without any goofy optimization.
Are you having any particular problems? To record effectively on Windows 2000, it helps to have more than 128MB of RAM and a processor of at least 500Mhz.
Slackmaster 2000
Are you having any particular problems? To record effectively on Windows 2000, it helps to have more than 128MB of RAM and a processor of at least 500Mhz.
Slackmaster 2000
R
Rusty K
New member
Smidgie,
Hey I'm no expert but I'll pass along something I heard through a friend on the internet that turned out to help me out.
He said that a friend of his that worked for intel had a chance to preview ME and 2000 before it went on the market and claimed that both versions were tremendous resource hogs and required 256M of RAM to operate smootly.
I was having quirky problems with my system, 700hz, 128M, ME and N-track. After hearing this story I added another 128M and my system has settled down quite a bit.
I would be carefull of some of the optimization schemes that are out there. They may help if you're way short on RAM but otherwise I don't know.
Rusty K
Hey I'm no expert but I'll pass along something I heard through a friend on the internet that turned out to help me out.
He said that a friend of his that worked for intel had a chance to preview ME and 2000 before it went on the market and claimed that both versions were tremendous resource hogs and required 256M of RAM to operate smootly.
I was having quirky problems with my system, 700hz, 128M, ME and N-track. After hearing this story I added another 128M and my system has settled down quite a bit.
I would be carefull of some of the optimization schemes that are out there. They may help if you're way short on RAM but otherwise I don't know.
Rusty K
S
smidgie
New member
thanks. i only have 128 megs of ram so i guess i'll be a little limited in what i can do with n-track. now i need more money for more ram. darn
R
Rusty K
New member
Hey smidgie,
I told you I wasn't an expert so take what I said with a grain of salt. I'm really not sure that ME wasn't the problem. I've seen many post from those with 2000 who swear by it.
Have you been having trouble? N-track tends to crash on it's own occasionally. I've learned to "save" my work often so's not to loose it. N-track will work fine for a long time then something sets it off. It's best just to save and close then reopen. This will often clear it up. It's usually a plugin causing some kind of problem but sometimes I cause the problem by say switching presets in some plugs during playback. Most plugs are ok but some........
Rusty K
I told you I wasn't an expert so take what I said with a grain of salt. I'm really not sure that ME wasn't the problem. I've seen many post from those with 2000 who swear by it.
Have you been having trouble? N-track tends to crash on it's own occasionally. I've learned to "save" my work often so's not to loose it. N-track will work fine for a long time then something sets it off. It's best just to save and close then reopen. This will often clear it up. It's usually a plugin causing some kind of problem but sometimes I cause the problem by say switching presets in some plugs during playback. Most plugs are ok but some........
Rusty K
S
smidgie
New member
Windows ME is incredibly slow. I was running it before and i was doing some mixing with only about 7 tracks with plug-ins...only one reverb and i kept getting the blue screen and it kept crashing and crashing. it was terrible. ME took about 5 minutes to start up too. Hopefully 2000 will be better. I just installed it so i haven't done anything big on it yet. But i think it should work out just fine. thanks