Dibs on 2

I'll take two please.

Could we look into shipping a mass order to someone in the US and then distributing from there to save on shipping? Possibly to someone in the States who could also offer installs?

I might too. I've got to finish up some other stuff first though.

You can count me in for 1 please

Definately 1, possibly 2...

Wow. It amazes me that so many of us are willing to spend close to 200 bucks on a small RAM upgrade. Maybe i'm missing the huge benefit here, but that's a chunk of change. Someone fill me in... why? Surely it can't be to save drive spinups for wear and tear... a new drive costs less.

Oh, and standard disclaimer applies... i'm not dissing the product since well... as we all know Patrick is THE MAN. Just trying to grok it. I want it but i don't know why. heheh.

Quoting famous Jeep motto:
It's a GEEK thing, you wouldn't understand...

Disclamer: no pun intended

I'm going to run an internet web server from it.. need the extra memory for NFS/Apache.

Cheers

Don't know. But he'll put it back together in 2 hours

But you don't have to justify it, just buy it

pca

Don't worry, I'm not all that protective. I do after all have a MK2A motherboard here on the desk being used as a power supply

Neatly, of course...

pca

What are the advantages of this method?

Primarily, reliability. In an automotive application, vibration will remove patch wires eventually, unless you use a LOT of glue. Plus it will be quicker to assemble and if necessary debug.

pca

Could we look into shipping a mass order to someone in the US and then distributing from there to save on shipping?

I'm planning on arranging to have a local 'distributor' to do exactly this, on various continents. It will make a lot of things much simpler. I just haven't had a chance to contact the various suspects yet.

pca

We have a full shipping facility here. UPS and FedEx make daily pickups.

Could we use the memory we already have for the empeg? cause I already have a bunch of memory chips for my empeg. But am very interested in this either way.

Sign me up!

Yep, count me in for 2.

My own plan is to get one of these upgrade boards from Patrick, and then find some willing bloke to send me their player so I can install it and test Hijack on it -- making any Hijack changes as required to get it all nicely supported. And then to return the upgraded player to whomever loaned it. They pay for the parts, but not for the actual installation.

For my own players, I'm sticking with one set (16MB) of stacked add-on memory. I'm not wealthy enough to actually install the 64MB kits onto all of my own players!

Cheers

I understand the reliability side... but no one (save for Mark and his webserver) has really justified why you'd need more RAM in the first place. Help me out folks, i'm trying to justify the cost to myself here!

I'm up for one kit.

And Loren, more memory also allows use of larger music databases. Think of it this way, in theory, a 100 gig player filled with typical music would have a database 5 times larger then a 20 gig player. Thus, less cache. Bu upgrading to 32, or 64, you return the player to a state where it has plenty of cache room, and also has enough memory to do the database rebuilds. It was discussed at the meet that database rebuilds don't currently enable swap, leading to some of the crash issues in 3.0 alpha on database rebuilds, due to the memory overhead of the player app running.

Well, once units with 32MB or more become common, I fully intend on adding some major new functionality to the hijack kernels. The kinds of stuff I've held off in the past due to memory consumption.

You know.. like vertical playlist menus.. NFS server (just a kernel config option), etc..

Cheers

I volunteer my unit if you want Mark. It's been out of my car recently and sitting in the house. Need to tighten up the mounting a little but much too busy at the moment. It has Ver 2 software but if you want to use it feel free to install any version you want. Just let me know what you want to do. (This means I'm in for one board )

If I play my root playlist on my Rio, it won't remember it between reboots. My empeg (mk2) won't even play the root playlist in the first place. I'm hoping that more RAM will help this. Either way, database rebuilds are painful. Mark has mentioned the web server stuff will be faster, and I've been getting more use out of that as well.

Hard drives are cheaper, but data is priceless.

Isn't the can't remember the playlist problem to do with lack of space in the dynamic data partition? The space reserved for the current playlist has a hard limit. Extra RAM won't help in this case. You'll need to get the empeg guys to see about modifying the format of the dynamic data partition.

Need any more response? I want one!