Fab's AutoBackup 7 Pro - a must have tool for techs

I have to disagree here that the use of "primarily grey" icons with an outline would be better.

I still like the idea of a bright outline on any selected control as it does make it easier to see, and in a piece of software like this it can be an "opposite side of the color wheel" to the primary background to make the fact that it is selected very obvious.

But in the absence of that, the use of "full color" icons for selected controls versus grayscale icons for unselected ones is perfectly obvious, and in pretty common use elsewhere.
 
@fabs Yeah that definitely looks better but it's still not really obvious at a glance. It would probably take me a few seconds to realize that the colored icons were active. Making the box itself a different color when it's selected would be a lot more obvious. Obviously if you want to use blue you'll have to get rid of the blue color on the monitor and the blue Windows logo color but honestly you'd be better of with grey icons (not greyed out but like the selected icon on the upper right on your last image) with the only difference being the box that's selected will either be outlined or the box itself filled with a different color.

EDIT: Actually it's pretty obvious that the "This operating system" box is greyed out but only because of the grey Windows logo. If the selected icon (in the upper right corner of your last image) was greyed out, it wouldn't be obvious at all because it's a grey hard drive. If you were to replace that icon with something that wasn't grey, you might be able to get away with just greying it out.
This is a difficult one...
The fact is that I cannot change the "Box" background as this not a box but a button with embedded graphics. Buttons background cannot be changed. So, since the blue windows logo that turns grey when not selected seems to be acceptable, I've added a green (when selected) USB logo to the "Other drive" button. I hope this time, that will be obvious enough.
1687018744011.png

1687018776509.png
 
I curse day when "the flat look" took over the entire UI world, not only for myself, but for the vision-impaired clients I work with.

The old Windows Aero look with the 3D buttons, window frames, etc., was just so much easier to visually distinguish "states" under. I'm actually shocked that the flat look has lasted in the way it has.
 
It's almost intuitive.

I know what you mean. And if it's not truly intuitive, all of my training on all sorts of platforms with GUIs over the course of decades has exposed me to "greyed out"/"stippled out" as meaning either not selected or not available for selection, depending on the context.
 
  • Like
Reactions: GTP
@fabs I'm sure the Backup option used to allow typing in a destination folder name that doesn't yet exist, but for a while now it only enables Next if that folder exists. Very annoying, having to Browse and press New Folder etc every time when I know the drive letter and folder name I want.

Surely Autobackup Pro could simply create the specified destination folder if it doesn't exist?
 
@fabs I'm sure the Backup option used to allow typing in a destination folder name that doesn't yet exist, but for a while now it only enables Next if that folder exists. Very annoying, having to Browse and press New Folder etc every time when I know the drive letter and folder name I want.

Surely Autobackup Pro could simply create the specified destination folder if it doesn't exist?
Fab's has always worked like this : it will not enable the "next" button if no user profile is selected as source AND if destination folder does not exist. So, it has never created that folder on its own.
Since this is annoying, I'll try to do something about that like enabling that button if the typed drive or network share exists but no further check.
 
Question on Wireless networks. In my memory somewhere I thought at one time when doing a FABs on a machine and restoring to the new machine it would automatically transfer all know wireless networks and passwords so the machine would automatically connect to those. I just did a transfer last week with a fresh download of FABs and restored to the new machine but the only wireless network was the one I had already created on the machine before the restore.
Is my memory wrong and this was never done in the past or did it just not work?

Thanks
 
Question on Wireless networks. In my memory somewhere I thought at one time when doing a FABs on a machine and restoring to the new machine it would automatically transfer all know wireless networks and passwords so the machine would automatically connect to those. I just did a transfer last week with a fresh download of FABs and restored to the new machine but the only wireless network was the one I had already created on the machine before the restore.
Is my memory wrong and this was never done in the past or did it just not work?

Thanks
This part is done using Nirsoft WirelessKeyView. If this one has been stopped for any reason (anti-malware solution while backing up or restoring), this may explain why they were not reimported in this case.
 
Defender will block it.

It makes me insane that Windows Defender (and at least some other similar utilities) will not whitelist NirSoft utilities. They're not an unknown quantity. They are well-known to be legitimate tools. They are easily identified as being them, and not some facsimile of them. I just don't get why legitimate technician tools that have been in use for literally decades are not whitelisted!

Rant over.
 
It makes me insane that Windows Defender (and at least some other similar utilities) will not whitelist NirSoft utilities. They're not an unknown quantity. They are well-known to be legitimate tools. They are easily identified as being them, and not some facsimile of them. I just don't get why legitimate technician tools that have been in use for literally decades are not whitelisted!

Rant over.
Just because of the power those tools could have between bad hands I guess
 
  • Like
Reactions: GTP
Just because of the power those tools could have between bad hands I guess

But that's not what any antivirus should be checking. Perfectly legitimate tools can be used for illegitimate purposes. That's always been the case. But the problem does NOT lie with the tool itself.

Technician tools are always going to be "digging under the hood" in ways that malware does, too, but it's not difficult to distinguish between a well-known and respected tool and some other process/program, or it shouldn't be.
 
But that's not what any antivirus should be checking. Perfectly legitimate tools can be used for illegitimate purposes. That's always been the case. But the problem does NOT lie with the tool itself.

Technician tools are always going to be "digging under the hood" in ways that malware does, too, but it's not difficult to distinguish between a well-known and respected tool and some other process/program, or it shouldn't be.
I know that, you don't need to convince me. This was just a possible explanation, fair or not. That's a pain for techs and that's also why I always have to fight this the way I can.
 
Back
Top