• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Just ordered a MX300 2TB...

biostud said:
...for the very nice price of ~$316 (Danish store)

Goodbye slow HDD, you are no longer needed 🙂
Click to expand...
Nope indeed. I went with two 1TB SSDs back in 2013 when I built my current rig and they is no way I'm going back to HDD myself if I can help it.
 
I got one (2TB MX300) at a price $200 USD more. It was more than I needed -- I could've been fine with a 1TB -- but we make judgments like that all the time.

However. While we're discussing Crucial SSDs, has anyone noticed a behavior of the Crucial Executive software which I"ve seen over the span of MX100 . . . BX[x00] . . MX300? It seems to show itself this way.

If you install Executive for a newly-added Crucial drive, it seems to work just fine. If you move a Crucial drive to another machine, whether Executive is already there or you install it fresh -- it doesn't see or allow access to the newly added drive.

I've seen this happen about 5 times on various systems I own. And -- that's OK -- if you can get your SSD information from CrystalDiskInfo or some other tool. But it just doesn't make sense for a lot of reasons.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top