I please if possible need your help to mod the Marvell mv63-64xx drivers (x64). I own a motherboard with a 88SE6440 chip that controls two SAS/SATA port.
The last official Marvell release is tagged version 3.1.0.2408 (attached to that post). There is a semi-official release (non WHQL) tagged 4.0.0.1200 (also attached to that post).
Version 4.0.0.1200 has been release for SuperMicro AOC-SASLP-MV8 owner to allow >2TB hard drives (unfortunately 3.1.0.2408 doesn’t support them). The problem with drivers version 4.0.0.1200 is that the “Safe Eject” feature has been removed.
I plan to use one of those SAS/SATA port with hard drives grater than 2TB and I will use it as eSATA and I would prefer enable safe eject for it.
The safe eject works perfectly with drivers version 3.1.0.2408. My guess it that the file MvCoInst.dll present in that version is in charge of the safe eject feature.
After numerous attempts I don’t find a way to make the safe eject working with drivers version 4.0.0.1200 (I have try a lot of soft modding things : edit the inf, replace sys files… nothing works). My guess is only an hard modding in the file mv64xx.sys can make it working. Unfortunately I haven’t any knowledge and I can’t do it by myself.
If someone have an idea of how I need to proceed, or if someone can make the modding, help is more than welcome.
I doubt, that you will find anyone, who is able and willing to modify any .sys file for you, but I have another idea: Download the free tool named HotSwap! from >here<, install it and choose the disk, which you want to get "safely removed".
Many thanks for your reply and also for your hint.
To be honest I have test a lot of configurations to try to be able making the safe eject working (I even manage to display the safe eject tab in the drivers but unfortunately nonfunctional). The problem is that my knowledge is very limited and I have only tried low level modifications. If I wrote that modding the sys file could be the solution it’s only because I don’t think about another way to make it functional. But someone more aware might think about something I don’t even imagine and that’s why I decided to post here and asked you.
By the way, if you think that it’s relevant, you can use and add the attached drivers to your library for people who want the latest version with >2TB support because it’s not very easy to locate them (and also the previous one with safe eject support).