player v3a5 vs. hijaack

Hi guys.

How do i install the V3a5 software and hijaack ? - can i use the "normal" pre-compiled hijaack thingy for the V2 software or what? - if not, how do i do it (easyly)

The same Hijack works equally well for the 2.0 final software or for the 3.0 alpha software. As long as it's a fairly recent version.

Remember that the 3.0 alpha software has problems with its database rebuilds, has bugs, and is not recommended for daily use yet. It's called "Alpha" for a reason. Most folks should stick with 2.0 until 3.0 is more stable.

The same "normal" Hijack is appropriate for both v2 and v3 player software.

And if you have not yet discovered "upgrader", then do a quick BBS search for it. It can save you a ton of time switching between various v2/v3 versions of player software, without wiping out Hijack each time.

-ml

Thanks guys, ... found the upgeader too, any notes on how to use that?

./upgrader target_empeg_ip_address car2-developer-blahblah.upgrade

(or upgrader.exe for mswin).

Cool, now i just can't fint the windows verison of upgrader (must be blind)

I've just now made it somewhat easier.

The Hijack site (link at top of BBS screens) has a compressed tar file with Linux, Windows, and (older version) MacOSX versions of upgrader within.

-ml

Mark, you're (as usual) the greatest!

I didn't think there was any reason to rebuild the MacOS upgrader; Is there? The images you can spit out won't be mountable on a Mac.

I can build it if you want a newer one.

Yeah, no need for a new OSX version. For that matter, you may be the only OSX user anyways!

Cheers

you may be the only OSX user anyways

He isn't I have used the OS X version a few times. Comes in quite handy.
-Mike

Well, my wife would use it if her solution wasn't "here, upgrade my player"... but there probably aren't more than a dozen or so, I'm guessing.

mmm... I see to be having some problems. I'm using a windows machine with cygwin and when I try and run the upgrader I found on your website I get some errors. I've attached a screenshot.

Ahh.. The package does not include the ncftpput and gunzip binaries, which as you can read (from the top of the output you attached) are also needed.

I had those here once, but have lost them. I suspect the person who originally sent them still has them though.. time for a BBS search.

Cheers

Ahh.. found them..

The gunzip.exe and ncftpput.exe binaries are now included in the upgrader.tgz package from the Hiack site. Refetch it.

-ml

mmm... Still got the same error... I decompressed the files into my home directory in cygwin... any ideas why it wouldn't be able to see it?

No idea. I don't use Windows. But you should probably put all three .exe files into the same directory, then open a command window, CD to that directory, and run the command from there.

Or switch to Linux.

My suggestion: If this is a full-blown Cygwin install. Just run the setup.exe program again and add the 'gzip' and 'ncftp' packages to your install. They'll be installed in your PATH correctly.

...as seen here (I just tried it).

How do i add 'gzip' and 'ncftp' packages to the install? I don't see an option for that when I run setup.exe...

When you get to the "Select Packages" screen, click on the "View" button until it says "full".



Then scroll down the list until "gzip" is visible in the "Package" column, and click on the swirly arrow thing in the "New" column once. The version number of gzip should appear. Do the same for "ncftp".

Then click "Next" until it's done.

(Note that mine says "Keep" where the version number would appear, because I've already got gzip installed).

Okay, I just tried this (for the first time ever) in VMware.
(And just how ironic is that!)

To get upgrader to work, with ncftpput.exe and gunzip.exe in the working directory, I first had to do this: export PATH=".:$PATH"

Worked like a charm first try after that. This is from within the cygwin bash shell, not a dos prompt.

Cheers

I don't have ncftp in my list...

Just use the files I provided -- see my latest post above, and do this command first within the Cygwin window:

export PATH=".:$PATH"

I don't have ncftp in my list...

Which mirror are you connecting to? If I connect to ftp.mirror.ac.uk, I get ncftp in my list.

mmmkay... Well... It claims it worked, however it still says I've got Alpha 3... Was I doing something wrong?

This is what I typed at the commandline

upgrader-cygwin.exe 10.0.3.130 car2-developer-v3.0-alpha5.upgrade

(Note: My username and password are both blank because there isn't one)

Any error messages in the output?

nope. just said "Upgrade complete, rebooting... ALTHOUGH... I just noticed for KERNEL it said:

/proc/empeg_kernel, size=475832 bytes
--> SKIPPED

I also got a skipped for "DRIVE"...


I take it that might be my problem?

Nope, those are normal.

Did the player reboot afterwards? If not, reboot it!

yep, it rebooted... Still saying Alpha 3 though...

*Sigh*

Here's the output from when I ran it -- attached.

mmmyeah... With the exception that the upgrade file I am trying to use is Alpha 5, it looks EXACTLY the same... Down to the letter...

Post the output from the cygwin window.

Okay, I'll try v3a5 and see what it says.. maybe rob forgot to change the version number on the display. Where are you seeing "alpha3", exactly?

-ml

Here ya be

Looks alright. It should take about one minute or so to complete, not instantaneously. Right?

Where are you seeing "alpha3" ?

I just redid it here with v3a5 and it worked just fine.
Gotta switch it back again now!

Cheers

Yep, it's about a minute... And yes, it says "alpha 3" when it boots up... One thing i did notice though, is that it goes directly into "standby" mode when it turns on...

I was thinking the same thing about rob not changing the label. Is the standby thing a distinguishing feature of Alpha 5?

No, mine says alpha5 on the little text screen during player startup.

The standby is merely due to the upgrader having put the player into standby before applying the upgrade. After reboot, the player simply returns to standby the first time because that's what it was doing before the reboot.

-ml

Mmm... Well, for whatever reason mine seems to not want to get out of Alpha 3 and move on up to Alpha 5...

Maybe I'll try re-downloading alpha 5 and seeing if that helps (doubts it...)

No need. Your alpha5 file is fine, otherwise upgrader would have complained (there's a CRC or checksum or something that it validates).

Try running it again?

Try v2final?

Weird. Windows folks have all the fun.

Ah faaak... Now I tried using the consumer image (was this a bad thing?) and I got a "broken pipe" error... When I tried to re-apply the developer one (which, if you recall, didn't give me any errors - just didn't acctually upgrade it), I get the broken pipe error again...

Arrg....

The only reasons for a broken pipe are if the gunzip/ncftpput executables are not found in the PATH. Did you remember to (re)do the "export PATH=".:$PATH" bit again?

Cheers

Now this is just silly...

I applied the v2.00-final upgrade file and I got NO ERRORS... It booted up, and "lo and behold" it says ALPHA 3 AGAIN!


*Is All Out Of Logical Ideas*

Err.. your player DOES have Hijack installed, right?

Yes. v361

Thanks for asking though

Is there another player on the LAN?

I wish... Got an extra?

(BTW - I've busted out the serial cable and am doing this the long way... We'll see what happens in a few minutes..)

Do this in the cygwin window:

./upgrader --extract car2-whatever.upgrade

Then do this:

ftp your.empeg.ip.addr


pas
cd /dev
put _dev_hda5 hda5
quit

And then reboot the empeg.

I'll give that a shot. It's in the middle of the serial upgrade (I'll make sure to reinstall hijack as soon as it's done) but I'll give that a shot afterwards

Mmm... Well, the whole "serial" upgrade worked like a charm... *Sigh* looks like it's the slow lane for me... Unless you can think of what the problem would have been...

(BTW - I'll try the commands you wanted me to try to see if that helps at all... I guess I'll try downgrading to alpha 3 in that test)

Nothing... Still says (now) Alpha 5... Seems like serial is the way to go for us winblows users

For you, anyway. Others have been using this for some time now.

Cheers