emendelson Posted Tuesday at 01:34 PM Share Posted Tuesday at 01:34 PM I have a script that runs the vDos.exe DOS emulator. This works perfectly on Intel machines, but on ARM systems, vDos.exe needs to have "Strict compatibility" set in its Compatibility options, available from the Properties dialog. Is there a way to set the compatibility options from an AutoIt script? I've searched the forums without finding anything. Link to comment Share on other sites More sharing options...
Developers Jos Posted Tuesday at 02:03 PM Developers Share Posted Tuesday at 02:03 PM (edited) How does the command line look that shells vDos? Edited Tuesday at 02:03 PM by Jos SciTE4AutoIt3 Full installer Download page - Beta files Read before posting How to post scriptsource Forum etiquette Forum Rules Live for the present, Dream of the future, Learn from the past. Link to comment Share on other sites More sharing options...
emendelson Posted Tuesday at 02:21 PM Author Share Posted Tuesday at 02:21 PM (edited) Like this: FileInstall("d:\dropbox\vdosinst\AutoItScripts\vdosbase.exe", $temp & "\vdos.exe", 1) If @error = 1 Then ShowError(51) $vDosTmp = ($temp & "\vdos.exe") RunWait($vDosTmp, $temp, @SW_MINIMIZE) $temp is a folder in the user's %TEMP% folder. ShowError() is a function that displays the error number. Edited Tuesday at 02:22 PM by emendelson Link to comment Share on other sites More sharing options...
emendelson Posted yesterday at 12:06 AM Author Share Posted yesterday at 12:06 AM I think the answer to my question is something as simple as this: RegWrite("HKCU\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers", "C:\path\to\vdos.exe", "REG_SZ", "~ ARM64VERYSTRICTEXECUTION") Not tested in a script, but this is what I found in the Registry. Link to comment Share on other sites More sharing options...
Andreik Posted yesterday at 09:25 AM Share Posted yesterday at 09:25 AM (edited) Did you tried this? FileInstall("d:\dropbox\vdosinst\AutoItScripts\vdosbase.exe", $temp & "\vdos.exe", 1) If @error = 1 Then ShowError(51) $vDosTmp = ($temp & "\vdos.exe") RunWait($vDosTmp & ' ~ ARM64VERYSTRICTEXECUTION', $temp, @SW_MINIMIZE) Edited yesterday at 09:25 AM by Andreik When the words fail... music speaks. Link to comment Share on other sites More sharing options...
emendelson Posted yesterday at 12:45 PM Author Share Posted yesterday at 12:45 PM (edited) Thank you for this. I didn't know it was even possible. It didn't work, possibly because RunWait doesn't seem to use parameters. So I tried: RunWait(@ComSpec & " /C " & $vDosTmp & ' ~ ARM64VERYSTRICTEXECUTION', $temp, @SW_MINIMIZE) But that didn't work either. The least bad thing I can think of is to write the registry entry and then delete it after running the command, in order not to clutter up the registry, but your method would be better if I could figure out how to make it work. EDIT: As far as I can tell from online sources, the command-line parameter won't have any effect. The only way to make this work seems to be through the Registry. Of course I could be wrong about this, and any information will be welcome. Edited 16 hours ago by emendelson Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now