Re: AMD Mem Tweak - Read/modify mem timings on the fly - [Vega Friendly] [Win/Linux]
Hello all,
I noted in an earlier post issue running the CLI via a batch file, sadly I have the same issue - has anyone come across this (seemingly basic Windows/Authentication issue) before? in that post the admin rights were applied to a batch file that would then run the batch file with correct access privs.
Batch File Usage Issue
Problem - unable to launch the CLI via batch file via a simple batch file in the start-up folder (current up to date patched Win 10 build)
Workaround - manually launching the batch file works, settings applied and CLI/GUI work as expected. I am able to use CMD to edit/tweak/test and run the batch file manually but not the start-up - all other miners/use of start-up has never failed until now
Straps Issue
Straps when viewed from a Polaris BIOS are displayed correctly/setup and strap working correctly it would seem but less 200 H/s GUI displays the default settings (even under load/running the miner) stumped by this as when I manually re-apply the same settings on the strap and re-run the CLI/GUI tool the correct settings are applied (over the BIOS strap defaults) - very strange - strap when viewed in R_ encoded and re-added - again same issue. (straps on the bios have the edited tweaks but are not working unless the GUI tool/CLI tool re-adds them - stumped lol
So GUI not reporting the settings as they are on the strap on the modded BIOS (just the default) not on all Polaris, but on a mining 470 (tried all 4 BIOS switches - same) otherwise when I edit the strap, apply - they work / as expected
Thanks all
I noted in an earlier post issue running the CLI via a batch file, sadly I have the same issue - has anyone come across this (seemingly basic Windows/Authentication issue) before? in that post the admin rights were applied to a batch file that would then run the batch file with correct access privs.
Batch File Usage Issue
Problem - unable to launch the CLI via batch file via a simple batch file in the start-up folder (current up to date patched Win 10 build)
Workaround - manually launching the batch file works, settings applied and CLI/GUI work as expected. I am able to use CMD to edit/tweak/test and run the batch file manually but not the start-up - all other miners/use of start-up has never failed until now
Straps Issue
Straps when viewed from a Polaris BIOS are displayed correctly/setup and strap working correctly it would seem but less 200 H/s GUI displays the default settings (even under load/running the miner) stumped by this as when I manually re-apply the same settings on the strap and re-run the CLI/GUI tool the correct settings are applied (over the BIOS strap defaults) - very strange - strap when viewed in R_ encoded and re-added - again same issue. (straps on the bios have the edited tweaks but are not working unless the GUI tool/CLI tool re-adds them - stumped lol
So GUI not reporting the settings as they are on the strap on the modded BIOS (just the default) not on all Polaris, but on a mining 470 (tried all 4 BIOS switches - same) otherwise when I edit the strap, apply - they work / as expected
Thanks all
For your first issue, right click the .exe, go to properties, compatibility, tick the "always run as admin". You still need to disable UAC I guess, alternatively you could use task scheduler to run as admin at logon or each boot.
Can't help much with your second issue I'm afraid, hopefully someone else will though.