by doktor1360 » Tue Dec 28, 2021 2:32 am
If you get past the steps of cleaning inside the console, and still have everything freezing up on ya... I'm gonna stick my neck out and posit that most likely it's gonna be some sort of anomaly in the serial communications between the console and host unit (DB25 data cable conduit). I've had this happen to me personally, just recently during a boondoggle of my own.
Ultimately, I just backed up to Square One... blanked the install media (the hard disk, or compact flash card in my case) w FDISK, and installed the drive back into the D8B host cpu. I then placed the USB media containing the install into the emulator and booted up. I proceeded to install the Mackie OS v5.1 operating system, reboot to install the Plugin Service Pack 3 release and rebooted again. When the interface finally came up and displayed, I got a "one moment please..." message in the fluoro-display and then FROZE... HARD. I simply turned off the D8B for a few moments, rebooted and it came right back up again... this time requesting authorization. At which time, I shut things down, removed the compact flash card and loaded it (mounted it) in my Linux workstation with a usb 6-in-1 media card reader. At this point, I brought the file system up in Dolphin (file manager app), deleted the 'MackieOS.EXE' and replaced it with the forked file that mitigates all the authorization function subset. I then placed the cf card back into the reader in the cpu host, booted the hardware and up came the D8B v5.1 operating system, fully authorized and ready to play ball...
Personally, I think your desk and cpu host (hardware) are not the issue... as this operating system can, and has, proven to be somewhat problematic at times. One thing, I think, that most here either forget or really don't have any reference to is that this is Windows 95 SP1 at the kernel... and Micro$oft'$ first implementation of the dreaded Windows Registry. If you know anything about that system management layer, you just shivered in fear a little. I'm not about to start into a discussion on the Registry, but ONE BYTE in an operating system key:value pair deep in an arcane system dependent hive somewhere within can send the whole OS tumbling... like dominoes. The Mackie operating system is then really no exception, for obvious reasons. I know this because I was a large system client/server developer on the platform for many years... and Micro$oft would break our code every 6-18 months with a new release of their DotNET garbage... but I digress...
Review your installation process, and if all else fails... just blank the disk and reinstall the os & service pack... rinse/repeat...
As always, for transparency, here it is:
[Standard Mgmt Disclaimer] - "Your actual mileage may vary..."
--
Dok
"Too many guitars is just about right..." - [Anonymous Player]