DisplayServer 2b2 and v2.0 beta

Just had a go at reanimating DisplayServer on my empeg after upgrading to the 2.0 beta and found it is actually very easy! (well if you had installed DS on one of the music partions anyway). All I had to do was:
* mount the drives rw (& rwm of course)
* backup the old profile
* use zmodem to load the new profile into /etc
* correct desplayserver.conf and use zmodem to load it into /etc
(actually I created it from scratch - was easier :-) )
* create a symbolic link to the DS install location (/drive0/opt in my case).
* ro and rom everything and reboot
and since I wanted VolAdj back too ..
* flash mlords VolAdj kernel using Tonys kernel flash util in LogoEdit

See, piece of cake

(list 6284, Mk1 S/N 00299 4GB blue [for sale]. Mk2 S/N 080000094 26GB blue)

Okay it may be easy to you but me be computiong dunce give us a step by step guide for those of hard of thinking

Okay, so I managed to get displayserver up and running with v2beta3 (I had to opt for the manual route) however, I have some problems.

DS runs fine but I can't use any of the playlist features. It lets me get as far as the Playlist page but any of the options from there cause DS to core dump. I opted to install the custom kernel, could this be the problem?

I realise that this post might be a little light on detail but any tips appreciated.

--
D.

--
Dean

Greetings!

Is anyone else having trouble with DS2b2 and memory when running 2.0b3? I find that with the player off, I can do everything, but with the player running, I cannot get a track listing from some of my longer playlists. I have tried the reservecache option (set up to 24) with limited success.

Paul G.
SN# 090000587 (96GB Smoke)
SN# 030103046 (10GB Blue - Emergency Spare)

Aye, I'm having a little bit of trouble here. Just following the instructions at the top of the README, I'm unable to add the tgz-masquerading-as-mp3 in through emplode. I'm told the MP3 format is not supported.

If I ZMODEM the mp3 in, rename to .tgz, and unwind it, I get an install.sh and install.tar, but the install.sh appears to be writing to the empeg display. Well, I'm in shell. Clue, please? :-)

UPDATE: Found elsewhere on this BBS a series of posts that suggests a downgrade to the 1.03 kernel first, then a few other steps after that. OK, but what if one enjoys making things a bit more challenging? I know I have this install.tar sitting here and I know I could go ro and just unwind it from root, but ... not sure if that's a wise move just yet.

If I ZMODEM the mp3 in, rename to .tgz, and unwind it, I get an install.sh and install.tar, but the install.sh appears to be writing to the empeg display. Well, I'm in shell. Clue, please? :-)


You shouldn't rename and unpack the mp3/tar-file
type the following after zmodeming the file to /tmp :

# export ARCHIVE=/tmp/ds2b2.mp3

# tar xzfO $ARCHIVE empackager/install.sh | /bin/bash

this should start the install script and find the right data file...

Oh, um, of course! Right. I saw the # signs and thought those were previously commented out and that I should skip them.

OK, everyone, stop laughing. Cut it out. (laughs)

I'm not laughing. I need the Displayserver For Dummies guide. Does anyone have one of these laying around anywhere?

I couldn't find anymore discussion on the topic of installing display server while running v2.03.
Is this just a dead topic because empload checks files more carefully now?
It was such a clever installation method. Now I have to resort to a slow xmodem transfer of the file.

Or you can downgrade to 1.03, upload displayserver, upgrade back to 2.0b3, and run the displayserver installation.

If I am running 2.00Beta3, should I still accept the installation of the modified 1.03 kernal during the displayserver install? It only seems to work if I do.... but will this have any adverse effects on the player operation?

You should not use a 1.03 kernel against a 2.0x player.

Displayserver will still work without the special kernel, you just won't get the remote control with the java applet.