New
#150
Right .......at some point it's all a younger man's game anyway and I cant believe the age of two unfavorable candidates for POTUS, given the rigors of the job outside of Reagan and Ike ....it's absurd at least with the conveniently or really forgetful and confused woman for obvious reasons and the other one ain't far behind without a teleprompter and some minders ...
I have 14915 on an SDD and the 14393 AU on metal in this PC in my specs or I can use one of the other windows 10 AU PC or my HP EliteBook here on the AU or the Andoid Chrome browser with a KB and mouse and voice search or Youtube etc. in my 4K HDR Sony Android TV in here like I did while this one in my specs shipped for 4 days recently after my 6 yr old 6 core test mule flamed a mainboard nearly 2 wks ago to the day and this new one is way faster anyway :).
OTOH If I were at one PC and one NTFS HDD volume I would be on the AU and not dual booting these betas with the AU .
I keep 3 or 4 ESD of these win betas on another HDD in rotation in case a new one is terribly bad or I need a re install or clean install with media (which has all occurred ) but 14905 is getting rotated onto the recycle bin straight away if I haven't done it already .
I had the 14905 stuck on slow ring branch issue and had to score a reliable 14915 ESD off the web last night for a clean install on this SSD.
Those are only bench marks, in normal day to day use, with RAPID turned off(or Magician in-installed), there is no perceivable difference, specially on a multi disk system, as RAPID can only be turned on for one disk(usually the C partition).
Only exception I found, is, full AV scans(as opposed to Quick scans) will be sped up, because of the scan goes deeper into the system, hence more files are scanned. And a full scan is only need if you think you have already been infected, so there is no real use for RAPID on a day to day basis., it just adds to startup programs.
The below are just my observations of RAPID & Windows 10
- It caused problems with live tiles updating.
- It also caused problems running a Hypervisor, both VMWare, and later Hyper-V when, I switched it 10 Pro.
- Together with Fast Startup turned on, it really caused problems, with PendingFileRename operations getting done, causing serious stability problems.
- And it does the same thing as prefetch does anyhow.
Samsung Magician 4.5 RAPID Mode - Evaluated With Demonstrated Speed Increase | The SSD ReviewRAPID mode is a RAM caching feature. Samsung’s RAPID white paper states that RAPID works by analyzing “system traffic and leverages spare system resources (DRAM and CPU) to deliver read acceleration through intelligent caching of hot data and write optimization through tight coordination with the SSD.”
Basically, it takes hot files and frequently accessed files such as a Microsoft Outlook email database or commonly used parts of files and stores them into the system RAM for future requests. And on top of that, it optimizes writes to the SSD for the fastest performance. Pretty sweet, eh?
There is a catch, however, and that is that there will always be a risk of data loss when caching files in the RAM. To minimize this risk, Samsung created RAPID to strictly adhere to the Window’s flush commands. This results in a data loss risk that is identical to that of Windows OS cache or HDD cache. Furthermore, it uses up to 25% of system RAM and RAPID 2.0 increased the maximum limit up to 4GB, well above that of RAPIDs first release. Because it was designed to only make use of excess system resources though, it will scale back resource usage and turn back to a pass-through mode if the system is working on higher priority tasks.
Once again Cliff you have outdone yourself. Thank you for this thoughtful and hugely benefical explanation for what I perceived to be a huge problem, but thanks to the Tenforums community and others, I have now realized my mistaken way of thinking and I will not worry too much about this "loss of a feature," essentially.
I would like to posit that I did just now clean install the RTM build of Windows 10 (build 10240) and tested it out with the latest version of Samsung Magician (v. 4.9.7) and found that the AHCI detection problem disappears. This means that the AU build of Windows 10 and later have some bug in their code that interferes with the correct detection of the AHCI mode of the SSD (when you clean install the AU or later builds) and which the Windows team should fix. Here is the proof:
Damn, "gonna have to stop ducking," this stuff just keeps going over my head. . .
- finally managed to get the 480's settled in using the 16.8.3 hotfix driver..
- wasn't easy, had to scrub everything and start again from the bottom up..
- lookin' good so far - crossfire is behaving..
- was a bit worried there, for a while..
PS - just downloaded B-52's album.. Really lovin' Groove Music so-ooo much..!!
It's interesting that there hasn't been lots of dialog about this build. Does this mean it's dull or everyone is satisfied with it?
- sort of a no-news-is-good-news thing..
- have to agree, magilla, mighty quiet round here..
- the 950XL mobile is working well with this build..
- continuum is running smoothly - noticed that it now has the red x in top-right corner, to close screen..
- all is well..
- so far...
- however, I'm about to inject a King Edward
- who knows what might happen..
- dan, dan, dan..