I'm wondering if anyone has reconsidered the pesky memory problem of player 2.01 on 64meg modified boards. The problem was that the cache was working so hard to fill 64 meg that it choked other processes and caused audio skips.

WIth the discussion of larger drives and huge music collections, is it possible to revisit this to take advantage of the larger memory for the database and cache without hurting the player?

I know the player software source code is gone for good, no fooling this time, but is there any way to patch it? Maybe tell the player that 32 meg is for cache and 32 meg is for applications? Maybe 32 meg alone would provide the database size to handle these massive collections?

Not a demand, just a curiousity.

You can use the reservecache setting to tell the cache to use less RAM (which leaves more free for applications). Do a search and you should find more about this.

Hugo

I was never able to find a setting that worked. My player with 16MB out performs my player with 64MB hands down. The upgrade board was a total waste to me and, unless a workaround can be found, is only useful for people that stick with 2.00 and plan on a lot of 3rd party software that might need it.

Link.

Not even setting it at 32meg via dip switches? Maybe a reservecache setting would work then. Hm, maybe I should get mine installed and try it myself....

I didn't know about dip switches... that'd be worth a try. I just got the player back from Eutronix for another issue, so I could test it. I'm assuming a search on "dip switch" should find something.

The dip-switches are on the memoryboard, and is used to disable the different banks of memory. Each switch disables 16Mb, but I think you have to disable from the top of the memoryrange.

Stig

Don't even *think* about trying to play with those dip switches, Brad. Accessing them requires dismantling the entire (*everything*) player, and doing so would disturb the attachment points of the memory board itself. This is a *very* fragile installation, and is best left alone rather than fiddled with. You will *break* your player if you try this.

-ml

If it is giving you a lot of trouble, I would recommend reloading 2.00. All 2.01 has over the 2.00 is the memory enable code. If you revert to 2.00, the player software will not be able to get to the extra memory. But the kernel and any utilities would. This might be your best option.

He could easily cut the RA3 jumper wire that is pulled from the SA1100, eliminating the fourth bank of memory. This wire wraps around the edge of the empeg's circuit board, and is easily accessible. Should speed things up a bit.

Since my memory board isn't installed yet, I could switch it to 32 and have Eutronix install it. Ultimately, just leave it at 32. I could test the reservecache settings to see if it could work with 2.01. Worth it, or no?