Then I don't think that you are showing the proper settings in the Volume Specifications.
They are shown enabled for that volume, but you are saying that they really aren't.
Search found 36 matches
- Sat Sep 17, 2022 8:03 pm
- Forum: Report Bugs
- Topic: Volume Specifications do not match the default
- Replies: 3
- Views: 15245
- Fri Sep 16, 2022 11:46 pm
- Forum: Report Bugs
- Topic: Volume Specifications do not match the default
- Replies: 3
- Views: 15245
Volume Specifications do not match the default
Windows OS: Win10 Hardware Information [tab]CPU: Ryzen 5700X [tab]Main Board: ASRock B550M Pro4 [tab]Memory: 32 GB [tab]Hard Drives: 500 GB SSD PrimoCache Version: 4.2.0 Screenshot(s) of your PrimoCache's main dialog showing cache configuration and statistics: Problem Description: In the Volume Spe...
- Wed Jan 02, 2019 1:53 am
- Forum: Report Bugs
- Topic: Install conflict with Samsung Magician
- Replies: 14
- Views: 16428
Re: Install conflict with Samsung Magician
It's interesting to hear about junction points on Ramdisk however. Support may have feedback on that one. I uninstalled Samsung Magician, and re-installed Primo Ramdisk Pro 6.3. Everything worked fine this time, and all the junction points were created/transferred properly. So it appears that Samsu...
- Mon Dec 31, 2018 10:32 pm
- Forum: Report Bugs
- Topic: Install conflict with Samsung Magician
- Replies: 14
- Views: 16428
Re: Install conflict with Samsung Magician
Maybe this explains the problem I had yesterday with Primo Ramdisk Pro 6.1 (if it is similar to PrimoCache). I installed it on a Win10 (1809) new install that also had Samsung Magician 5.2.1 installed, and Rapid Mode cache enabled. I found that the junction points I created did not work with my BOIN...
- Thu Aug 03, 2017 11:31 am
- Forum: Technical Support
- Topic: Renew beta license?
- Replies: 2
- Views: 2547
Renew beta license?
I have only four days left on the license for the test of Beta 3.0.0.0. Can this be renewed?
Also, I have a license for 2.7.0. What will the upgrade policy be?
Also, I have a license for 2.7.0. What will the upgrade policy be?
- Tue Mar 14, 2017 1:57 pm
- Forum: Technical Support
- Topic: CHKDSK fails
- Replies: 6
- Views: 6314
Re: CHKDSK fails
I tried 5.6.0, but it has the same problem, and CHKDSK fails. I guess I did not see it before because I never had to use CHKDSK during the time I was using it. But thanks for sending the link to try it.
- Mon Mar 13, 2017 10:04 pm
- Forum: Technical Support
- Topic: CHKDSK fails
- Replies: 6
- Views: 6314
Re: CHKDSK fails
I was unable to isolate the cause by disabling applications, services and unplugging USB ports. I even uninstalled my anti-virus. So I will have to uninstall 5.7.0 for now. Thanks for checking, it may not happen again on another installation.
- Mon Mar 13, 2017 6:24 pm
- Forum: Technical Support
- Topic: CHKDSK fails
- Replies: 6
- Views: 6314
Re: CHKDSK fails
I don't think that it ever happened with Primo Ramdisk 5.6. I would try 5.6 again, but I don't have a copy. Is there a way to download it? But it happens 100% of the time with 5.7. Fortunately, I am past the frequent crashes (due to bad disks, cables and even video cards), so I don't have to use CHK...
- Sat Mar 11, 2017 2:45 pm
- Forum: Technical Support
- Topic: CHKDSK fails
- Replies: 6
- Views: 6314
Re: CHKDSK fails
Also, when CHKDSK fails, I usually (but not always) get Event ID 137 error report in the Event Viewer: Log Name: System Source: Ntfs Date: 3/11/2017 9:26:54 AM Event ID: 137 Task Category: (2) Level: Error Keywords: Classic User: N/A Computer: Jim-PC Description: The default transaction resource man...
- Mon Mar 06, 2017 9:43 pm
- Forum: Technical Support
- Topic: CHKDSK fails
- Replies: 6
- Views: 6314
CHKDSK fails
With Primo Ramdisk 5.7.0, I am not able to run a CHKDSK on my Win7 64-bit machine after a ramdisk is created. I get an error message upon reboot to the effect that autocheck has failed because of some newly-installed software. When I remove the ramdisk volume, the problem goes away and I can run CHK...