Effects issue

[bitSync]

the drive on the old D8b needs to be
imaged to your pc

the image then needs to be put on your new D8b drive.

those saves on the floppy will not contain ALL the needed nfo to merge smoothly to another console. ur gonna need a ide adapter.
if you were only going to do a clean reinstall then your floppy method would be okay, but to transfer any type of fx settings the new d8b needs those subparameters that are written to the drive while your actively performing edits, fx, etc.

Goonkalonyn is correct about needing to image the drives to transfer the entirety of the drive data. I wrote up a procedure here describing how to do it for both a HDD and a Compact Flash as a target -

http://www.sonido-7.com/d8b/files/userguides/Mackie-d8b-Macrium.pdf

Hope this helps. It's super easy and should resolve your drive imaging issues.

I don't mean to alarm you, but is or was the second d8b OS 5.0/5.1 ever bootable from its own CPU HDD image and do you have that HDD image available to you? The installation of OS 5.0 or 5.1 requires the availability of the ESN and unlock code for the value stored on a chip in the d8b console brain board. If you are trying to boot a new d8b from a drive image from a 'foreign' d8b, that will not work; you will not be able the authorize the software. Please see this thread for more information on the subject -

http://www.d8bforum.com/phpBB3/viewtopic.php?f=2&t=928

Please let us know how you make out.

[Phil.c]

Thanks for your help and info!

The v5.1 codes for both d8b's were bought from Mackie and I still have them so I don't think there's an issue there.

The d8b I am now using works fine with new projects, it's only when I open older ones which have been reloaded via floppy from the original that things are not quite right but your method should put that right.

Phil

PS. If the bug is in my original HD's 5.1 OS can this OS be bypassed when copying to the new HD?

[goonkalonkyn]

if the bug is in your firmware or bios.

what build is your 5.1?

[bitSync]

Thanks for your help and info!

The v5.1 codes for both d8b's were bought from Mackie and I still have them so I don't think there's an issue there.

The d8b I am now using works fine with new projects, it's only when I open older ones which have been reloaded via floppy from the original that things are not quite right but your method should put that right.

Phil

PS. If the bug is in my original HD's 5.1 OS can this OS be bypassed when copying to the new HD?

Hi Phil,

If you are confident that there is a bug in the OEM d8b executable then I'd think that would present itself whether you imaged from an OS 5.0/5.1 HDD or if you built the OS drive from scratch from the 5.1 floppies. If you think the d8b executable you're imaging from has been damaged somehow then imaging from that drive will certainly transfer the damaged OS to your new media. Do you have the 5.1 floppies you can build from?

Is it possible you have a hardware/firmware fault somewhere in the original d8b system?

[Phil.c]

I've been using 5.1 for twelve or more years, everything ok until a few months ago, I have the two v5.1 floppy's but have not used them for twelve years!

I don't know if the bug is hardware related, I have done a ribbon connector clean/reseat on the d8b but not on the cpu.

[bitSync]

I've been using 5.1 for twelve or more years, everything ok until a few months ago, I have the two v5.1 floppy's but have not used them for twelve years!

I don't know if the bug is hardware related, I have done a ribbon connector clean/reseat on the d8b but not on the cpu.

It would be pretty weird for the OS executable to just 'go bad', so to speak. If you have the OS on the Mackie floppies you can do an MD5 hash checksum on both the HDD-resident version of the OS and the floppy-resident version of the OS. If they're the same checksum then the OS on your HDD is the same as it was when distributed by Mackie on the floppies.

At that point I would be suspicious of a hardware issue.

[Phil.c]

I forgot to mention that besides the Locator and Automation not working, two of the Mackie plugins don't open and cause the d8b to crash, they are both unlocked.

[bitSync]

I forgot to mention that besides the Locator and Automation not working, two of the Mackie plugins don't open and cause the d8b to crash, they are both unlocked.

Well, I'm sorry to say I'm out of my depth here. This sounds too complicated for long distance troubleshooting, but I'm suspecting you have some hardware issues. Hopefully, someone else here can offer some assistance.