1) /opt/bamt/fixer has to be run multiple times (once for each update)
for me i just run the command one time and keep pressing 1 to uupdate, and eventually alll get done.
this is correct. I don't know where the idea you need to run it multiple times comes from, but it is not true.
run it once and hit enter or 1 until it's done, you will have all updates.
I think that it is an interface issue, once you run the initial update the screen doesn't prompt you to continue applying updates, nor does it show you an clean exit path, the wording is a ambiguous. It took me a while to realize that I had to hit 1 repeatedly until all of the updates were applied, then the tool exits and stats "Your BAMT is up to date."
Actions
-------
1) Apply fix
2) Display files in fix
3) Skip for now
4) Skip forever
5) Exit now, make no changes
Choose an action (1 - 5) [default 1]
thats ambiguous?
I can change it easy enough.. what would be a better way to present the things you can do?
First and foremost, thank you for your work on this tool! It has saved me hours of tinkering around with linuxcoin just to get a few bare-bone miner rigs up and running.
There just isn't any feedback to the user as the fixes are applied, screens full of information scroll past and then you are dropped back into the same menu system you started from.
Perhaps adding a dialog showing something like:
"Current fixes applied X ... Y ... Z"
"Un-applied fixes X ... Y ... Z"
Perhaps change option (5): "Exit now, fix level XYZ, X fixes remain"
That or just modify the script to run them all sequentially?
Add an option "Apply all fixes"?
This will all be moot with .5, since all of the updates will be rolled up, right?
Automatic fan control is the final feature that I am really missing in the current BAMT implementation, I am looking forward to trying it out when it is ready.
Ok, I think I see what you are saying.
fwiw, each individual fix is displayed, in the style:
New fix: bamt64_fix_6a.tar
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
another experimental, optional offering.
this one demonstrates a new high performance monitoring technique that I think
I will develope further and eventually use to replace gpumon/mgpumon.
the current client is basic, but can gather more data than gpumon and does it
much, much faster. system load is very minimal.
so.. restart mining, then run: /opt/bamt/pcontrol
watch and be amazed. ctrl-c to exit.
phoenix only
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Actions
-------
1) Apply fix
2) Display files in fix
3) Skip for now
4) Skip forever
5) Exit now, make no changes
Choose an action (1 - 5) [default 1]
The intent was that one would see the fix number, read the description since not all fixes are something you would want, some may cause your machine to do all sorts of things including interrupting your mining, etc.. and then choose what to do using the menu.
After on fix completes, it just loops... another New fix: some number, another description, another menu.
Now... I am going to guess that you didn't pay much attention to either the fix number or the descriptions if you didn't notice they were changing... that I think is something to worry about.
These messages are important, often they are the only notice I give as to the presence of a new
feature or significant change, and as I mentioned this text warns the user about things about to happen
that they might not like at all.
So..... Yeah it needs to be changed somehow to make this critical info "pop" I guess. Also it was never envisioned there would be 30 some fixes to apply to an image, for most cases its 1 (except for the first time you run it on your first download of 0.4b) and as you mentioned that will be less of an issue if the new image ever comes out. Eventually it will build up again though.
I'll think about it.. good points, thanks.
