Hi Andy.
Let's try to get this straight:
Which procedure did you follow until you got the "bad pump response"?
Here is the standard way to do the upgrade (for a MkII):
- Jumper your new drive to master drive without slave.
- Open your empeg
- Remove your old drive and set it aside
- Insert your new drive in the location of the old drive
- Apply the "builder-image" upgrade to your empeg
- Remove the new drive
- Jumper your old drive to master with slave
- Re-install your old drive at its old location
- Jumper your new drive to slave
- Re-install your new drive to the position that was previously empty
- Apply the current consumer or developer image to your empeg
- Check that emplode sees the full storage capacity
- Close the empeg
If you get any error at any stage of this, post here with an exact description of what type of error you got at which stage.
If you really care to go the hard way (partition the new disc yourself), this is how you could do it:
- Open your empeg
- remove the old drive and check that its jumper is set to master (with slave, if that is an option), then re-install it
- jumper the new drive to slave mode
- install the new drive next to the old one
- apply the developer image to your empeg (this could also be done beforehand)
- connect the serial port of the empeg to your PC and start a terminal emulation (e.g. HyperTerm)
- power on the empeg
- quit the player by pressing "q"+RETURN
- enter "fdisk /dev/hdc"
- delete any existing partitions ("p"+RETURN will show you the durrent partition scheme, "m"+RETURN shows a small help)
- create a new partition using "n"+RETURN, a primary partition ("p"+RETURN), partition number 4 ("4"+RETURN), starting and ending at the default cylinders (two times RETURN)
- exit fdisk writing the partition table to the disc (press "w"+RETURN)
- create a file system on that partition: "mke2fs /dev/hdc4"+RETURN
- "mount -n -o rw /dev/hdc4 /drive1"+RETURN
- "mkdir /drive1/fids; mkdir /drive1/var"+RETURN
NOTE: Using this procedure, you are
never able to use the new drive as your first drive, because it does not contain the scratch and program partitions. Though the current software (as of 1.03) does not use the additional partitions the second drive usually contains, SonicBLUE/empeg reserves the right to do so in later software versions. However, you gain some megabytes (about 100) of music storage using this procedure (for now). If empeg ever decides to use the second drives scratch partition (or any other of the additional partitions on the second disc), you will need to re-initialize the second disc (and thereby loose all the data on it).
cu,
Sven
proud MkII owner (12GB blue/green/smoked, was #080000113 is #090001010)