Old School wrote:Hi all,
I recently bought an Addonics Adsaide ide to sata adapter. Addonics says this adapter can:
Convert any Serial ATA hard drive or Serial ATA storage device into IDE hard drive or ATAPI devices
Support ATA 33/66/100/133
48 bits LBA. Support large hard drives of 137 GB or larger with one partition
Mount directly to the back of SATA hard drive
Bootable
Simple plug and play, no drivers required
Compatible with any OS (Windows, DOS, Mac, Linux, UNIX..) that supports IDE or ATAPI storage devices
Supports Spread Spectrum in receiver
Compliant with ATA specifications
Input: combo SATA 15-pin power and 7-pin data connector (direct attach to SATA hard drive)
Output: 40-pin IDE male connector (work with standard IDE connecting cable). They advertise that this adapter can break the 137GB HDD limit for older equipment.
Currently we can recognize HDD's bigger than this, but only use up to 137GB of the drive, the rest is wasted space.
I cloned my internal ide drive to a 500GB sata hard drive and installed it using this adapter. The HDR recognizes the sata drive, but as having only 137GB, and boots all almost all the way before it hangs after checking DMI.
I think the device may not be working because plug and play is not enabled in the bios, but I'm afraid to try enabling it for fear it may reallocate irq resources and overwrite the new configuration to the bios possibly ruining my machine. But I'm out of my element here and not sure if any of what I am saying is correct. If any of you have any ideas I would be eternally grateful.
Have a blessed day,
Mike W.
Hey Mike (and
Funk, too)... trust all is well...
That's probably gonna be a '
Show-Stopper', man... supporting larger drives is an issue that's reliant upon the operating system (
Windows 95 - i.e. the Mackie OS) at the kernel level for starters. Windows 95 does not properly support drives larger than 32GB without a high probability for data corruption... that's BIOS related as well. They work together, but ultimately it's the BIOS that sets it up (
hardware n BIOS code) and then Windows will manage
what's there as reported by BIOS. Mackie addressed this to the current limitations (
at the time) of the hardware with the 1.4 OS release and subsequent BIOS chip firmware upgrade. This is all due to the addressing system employed and bit depth support therein (
28-bit vs 48-bit for LBA). It's a hard limitation at the issue core, one that doesn't appear to be resolvable. The BIOS code, operating system drivers and the Windows Registry are all part of what would be in play here. and there's also no avenue to resolve this without the BIOS and operating system source code base. The Mackie engineers don't provide a terminal for any hope of getting access to an MS-DOS prompt for driver installation and/or Registry issue mitigation either. It's quite messy, and giving me a headache even thinking about what's theoretically involved (LOL)...
The hardware will '
work', but only within the limitations of the driver, firmware and operating system code... albeit
not supporting all the hardware specifications per se. Sadly, none of this exists within the 'User-Land', only to the developers. If y'all can get things working, I tip my hat to ya... I personally just don't see how - just a lot a frustration...
But again, you knew this was coming, so...
[Standard Mgmt Disclaimer] - "Your actual mileage may vary..."
All the best with this, I'd be interested in the result of your experience...
Peace \m/