> There was a bug in nvapeek/poke (it was using the wrong address space by > default), can you update your pull and try again? [That explains why you saw > 'S' in the output.]
Of course - here you are:
The version I used is from the "Download ZIP" button in GitHub: https://github.com/envytools/envytools/archive/master.zip
[aloew@aloew-lap nva]$ sudo ./nvapeek 10200c ... [aloew@aloew-lap nva]$ sudo ./nvapoke 10200c 10 [aloew@aloew-lap nva]$ sudo ./nvapeek 10200c ...
Maybe now another bug, as we don't seem to get any hex address and/or value output?
Please advise if we need to pass any additional parameters to get hex ouput...
BR, Andreas
> There was a bug in nvapeek/poke (it was using the wrong address space by
> default), can you update your pull and try again? [That explains why you saw
> 'S' in the output.]
Of course - here you are:
The version I used is from the "Download ZIP" button in GitHub: /github. com/envytools/ envytools/ archive/ master. zip
https:/
[aloew@aloew-lap nva]$ sudo ./nvapeek 10200c
...
[aloew@aloew-lap nva]$ sudo ./nvapoke 10200c 10
[aloew@aloew-lap nva]$ sudo ./nvapeek 10200c
...
Maybe now another bug, as we don't seem to get any hex address and/or value output?
Please advise if we need to pass any additional parameters to get hex ouput...
BR,
Andreas