Community
cancel
Showing results for 
Search instead for 
Did you mean: 
DMRtech
Beginner
837 Views

Req: Intel RST and Windows 10: RST driver source codebase unification to include HM77 Express Mobile Chipset C216 hub and "older"

Dear,

 

I should write this to Intel directly, alas,

 

RST drivers 12-14.. for PCe/mSATA SSD and C216/HM77 express chipset are working BAD in windows 10. Like, REALLY bad, meaning BSODing on production machines.

 

Reasonaby, considering that the chipset is old enough - in one solution model - is for source to be published and maintained by community or private repo and Intel dev API keys to preventbeing behind zillion rolling releases of windows 10 kernel.Should not be problematic from any standpoint.

 

Could you please push the driver source somewhere, privately or public alikes of GitHub, in order that we, the owners of the laptop/chipset we invested money into, can have a very important production feature (it was chosen for that - it was $900 per unit back then).

 

No, I reject the answer "just install SSD". No - technologically - what we want is caching of sectors to be done by SSD, and long-term retention of data to be done by HDD. Effectively making a hugely efficient SSHD and not a "burning" liability of a huge SSD. At least, until Microdumbsoft make a vital change: that we can safely make separate partitions for User, AppData, Program Files, connect them via junctions (mount points), and for that to work across OS upgrade as they still say no that is not supported as someone is lazy to mod an install check routine. Partitions are for a reason that Chkdsk.exe /f C: of one huge 800GB partition takes more than 20 minutes for just few RST BSODs when the inconsistencies in filesys have to be checked. Talk about downtime :-(

 

 

 

As for totally corect solution -idealy;

 

 

-all features across branches of the software should be diff/ unified and made available for the next ver of driver

 

 

-fix a situation where current v16 driver on HM77express actually recognise C216 as RSTe (in reality, it is originally designated as RST hub, NOT RSTe -> and also in connection to that, the GUI for v16 has a non-functional PCIe mSATA SSD support for RST RAID0 - that should be revamped again. It is not so hard at all to do that, and there is a significant base of users still running their machinery on Intel core 7 CPU/HM77 express chipset

 

 

-Furthermore, RST command line too should be revamped again for the latest ver of RST - to give users with deeper mind some advanced feats for their system.

 

-RST for C216 should receive a support to accelerate more disks than only first HDD via internal code backport from highest version of RST which supposedly do accelerate multiple drives

 

Yeah, it sounds a lot to write in one thoughtful article - but in a coding world not too much to correct. The codebase source is already there (non-public)

 

 Wishing something put us users back on productivity track, as this situation hamper our productivity and our 900$ per unit investment Intel chipset/CPU arrangement

 

Best,

 

 

 

 

0 Kudos
2 Replies
Esteban_C_Intel
Employee
475 Views

Hello DMRtech,

 

Thank you for posting on the Intel® communities.

 

Our best recommendation for you is to roll back to a version of Windows 10/8 or 7 which works better for you as a bug fix unless its security issue is highly unlikely.

Also, we would recommend you to check with your motherboard manufacturer on the best Intel® RST driver available for your system.

We will close this inquiry; but, if you need further assistance, please post a new question.

 

Esteban Ch.

Intel Customer Support Technician

A Contingent Worker at Intel

DMRtech
Beginner
475 Views

Dear EstebanCH_Intel,

 

it is too ineffective for the scenario we are running.

 

Windows 10 is here to stay. Windows 7/8.8.1 is effectively phased out by Microsoft and anyone else.

 

Fully obvious, manufacturer support is therefore outdated in the driver supply chain, as the original chipset maker still does not have working Windows 10 driver set for Intel Core 3rd gen / Ivy Bridge.

 

Therefore, we are completely alright to skip consumer-level "fixes", and collab on this product support defect at engineer/coder/management level.

 

 

Best,

Reply