emusonacid!

So I got another EMU and tried to take a harddrive out of my old one to fit in the new EMU (same model), but for some reason even though the system can see the drive, it is not working, no banks on it, no data about it (0 bites) etc...
I vaguely remember that SCSI devices had to have ID's in order to be recognised, I have forgotten, do harddrives need them too?
Any info would be much appreciated.

I take it the HD is SCSI, so.....

Q. Are both Emus running EOS4.7?
If the original one is running 4.7 but the newer one is on an earlier EOS this is probably your problem!
You may be experiencing this problem because the drive is formatted in FAT32.
If this is the case update the new Emu to EOS4.7. Then it should read the FAT32 HD.

Q. Do both Emus have the same SCSI ID settings?
If not ensure the settings in the new one are changed to match those in the first, then do a drive mount.



Hopefully this will sort it out.

If it fails to show up then reinstall the HD back into the first Emu, just to check that the HD has not failed during the transplant.

It will probably be the first solution!

Whatever you do don't reformat the drive unless you have all the data backed up.

"If the original one is running 4.7 but the newer one is on an earlier EOS this is probably your problem!
You may be experiencing this problem because the drive is formatted in FAT32.
If this is the case update the new Emu to EOS4.7. Then it should read the FAT32 HD."

This is probably it!! Will try this tomorrow.. if only I could find a disk with 4.7 .... I used to have 20 of them because I was selling them on Ebay.. meeeeh

Re EOS4.7 floppy
Create your own from the machine that's running 4.7

The floppy disc has to be formatted in EMU-format, not DOS-format.
IF you use a DOS-formatted floppy disc, EOS will try to write to the floppy disc but will abort the operation with an error-message.

Got it sorted, one interesting thing, the OS was extremely slow upon connecting the floppy drive and I rectified it by changing the direction of the floppy cable on the mobo, however by using the same direction of the cable in the new machine the OS was slow again, which was rectified again by changing the direction yet again. It seems these two EMU 5000 Ultras have different layouts of the floppy connector, I checked and rechecked it all twice, Wierd. One is manufactured in 99 and the other in 2001..

You always have to look for PIN #1 of the connector and the red stripe of the ribbon cable has always be connected to PIN #1.

An alternative solution is to put the FLASH-module you want to update into the E4 Ultra where the floppy drive is working and install EOS 4.70.
It doesn't matter if you swap the FLASH-modules again. Don't forget to execute InitEE and recalibrate the volume and data wheels.

I updated an e6400 Ultra of a forum member this way as his floppy drive did not work, although correctly installed.
The floppy controller chip seemed to be broken.

Aaaah, thats another solution!
Yes, I was trying to align the red stripe to pin 1 and on both models the pin 1 is towards the front of the unit, but for some reason the floppy cable worked properly on pin 36 or whatever in one of the machines.. strange!

Now.. anyone wants to buy my old floppy drive? :D