The first step

Hi there all.
I have a new Mark II on its way as we speak(very excited).
I just want to know whats the first step with software etc.
I have seen posts saying the vesion 2.011 sux and screws up alot so i just want to know what i should d'load and install and in the right order. Links to the page would be nice too.

Thanks

You will probably get a lot of answers. Here's mine:

Install v2.00beta11 immediately, and THEN upload your music.

Install Hijack either before or after the music upload (before is good), and immediately go into the Hijack menu (press and hold knob until it appears) and DISABLE periodic filesystem checking. Otherwise, your music uploads may take even longer.

This is the inverse of more common advice, but the music uploads take forever, and are much slower with v1.03 or v1.03 than with v2.00beta11.

ok thnx mlord

Then the next question i have is its only a 12 gig HD in it(lol like 2500 songs isnt enough) but i have 24 gigs of tunes on my home comp. So do i try to install a 2nd HD myself(maybe buy off ebay and which kind of HD does any1 reccomend) or send it back to rio to do it(have no idea how much that costs or long it takes so info there would be kewl too)??

o yeah and it has to be at least a 20 gig or higher to fit all the tunes i have now.

You can do either. Click on "RioCar.Org" at the top of this web page, and look for the Drive-Upgrade FAQ there.

Cheers

I think that David (the guy at empeg who would be dealing with your drive upgrade) has said that they aren't really intending to do any more drive upgrades there (not that, apparently, they did many anyway), but that you could get them to do it, but it would cost you an arm and a leg. Probably better/easier to do it yourself. Make sure to read the Drive Upgrade FAQ, though, like Mark suggested.

its a pretty easy process.. if u can install a harddrive in your home computer you can do it in the empeg

I have seen posts saying the vesion 2.011 sux and screws up alot

It's nice to see the well-rounded impression we give people on here.

Rob
(using Beta 11 for weeks, no crashes, no lock ups, about 1,000,000 extra features than 1.03)

>using Beta 11 for weeks, no crashes, no lock ups

Don't you just hate it when that happens during beta testing?

Actually, apart from the messed-up INFO modes, which Hijack now takes care of nicely, beta11 is working very well here for me as well.

Ooops.. except for the infinitely-growing config.ini file problem, which could easily be the cause of many other reported issues: once config.ini grows beyond 4096 bytes in size, the player only reads the tail end of the file, modulo 4096 bytes. That could REALLY mess up a number of things.

The growth (for those who missed it) is due to the "favourite visuals" feature in Emplode.

Cheers

The fsck disable option of Hijack still does absolutely nothing for me. Emplode will still do a filesystem check once its counter gets up to whatever value it thinks a check is due at.

Otherwise, might as well go directly to the new stuff. It's what everyone's talking about anyway, so it's easier to get caught up on problems and get advice.

Bruno

>The fsck disable option of Hijack still does absolutely nothing
>for me. Emplode will still do a filesystem check once its counter
>gets up to whatever value it thinks a check is due at.

Gee, that's too bad. Works for me.

I haven't had this problem... For me, the only time fsck happens on sync is if there's a real good reason, like if I had a drive mounted and lost power (that doesn't happen much.) The periodic checks are gone.

I thought I had this problem when my player decided to do a disk check RIGHT AFTER I installed HiJack. When I installed HiJack, the first thing I did was disable the disk check. A few minutes later, I did a sync and a disk check started. At first, I said "what the heck?" until I remembered that the instruction to perform a disc check was made during my PREVIOUS sync BEFORE I installed Hijack.

IIRC, when the player (or emplode?) decides a sync is needed because of a certain amount of time or a certain number of consecutive syncs, it doesn't happen right away. Instead, it sets itself up so that upon the NEXT sync, a disc check is performed.

I can say that after I received my 60GB unit, I immediately installed v2.00b11, and attempted to upload about 5gb worth of songs. On that synchronization, and all of the several attempts since, all the songs will upload but the unit will lock up when it goes to restart itself. I always wake up to a timeout on Emplode, and the Rio is locked up (despite the cycling blue LED) and requires hard power removal to reset it.

I've never seen it act any other way during a synchronization. I've never uploaded under 1.03, so I don't know if I have a bad unit. Now that I think about it, I guess they don't all do this under v2.00b11 or people would be complaining, eh?

- Chris

If the empeg is playing when I start a synch it will always quit at the restarting player point but if I power it off first it only does that once in a while. But the songs always upload so it is no big deal. I believe it is a known little bug and nothing to worry about so no you don't have a bad unit.

The "hang after sync" has been "normal" for all of the public betas thus far.. an annoyance, but that's all.

Use JEmplode instead of Emplode, and the occurance rate drops significantly.

Cheers

-ml

..I have lockups, but its due to the player, not the kernel..
Also on 2.00b11, and after playing with the installed 1.3, am greatly glad I'm ON 2.00b11. :>

Yes I certainly agree, There are no reasons not to run the latest version and many to run it. It's a win win.

There are no reasons not to run the latest version

Yeah but that wasn't the case until pretty recently though... There were certainly some, shall we say, limitations and hidden features in the 2.0 series, but I'd say it's damn near final.

Speaking of which, where *IS* 2.0 final?