alx is not trying to reprogram his usbasp so none of that is relevant.
Uh.... That's not what I see.
Most of this thread looks to be about trying to update/re-program a USBasp device.
Look at the original post and then again at his comments in response #6
and the hex image he is using.
What I see is that the thread started about a question about an sck error/warning message
when attempting to burn a blank AVR
and then asking about using an UNO to update the USBasp device to the latest firmware.
Then, in response #6, actually attempting to update the USBasp device firmware with a setup using ArdinoISP.
Even the title of the thread is "Fixing USBasp ..."
as i mentioned before the sck period message has nothing to do with the targets fuses and is an avrdude warning that is to be ignored.
I disagree with this.
If trying to program a new part with the factory default fuses,
which is using the internal 1Mhz oscillator (which is controlled by fuses), sck period must be slower
so the "warning" is indicating why things are not working.
Also note that the original question relates to burning a blank part is what was stated as being done in the original post:
Whenever I try to program (either a sketch or burn bootloader on a blank chip) with it I get this message:
The older versions of USBasp firmware used a jumper to slow SCK down, the newer versions support doing this from avrdude.
If the clock is not slowed down when using a slow clock in the target AVR, avrdude will abort
or get strange errors since it can't talk to/program the part.
While I agree that the SCK warning can be ignored in some situations,
(like when the target has fuses set up to use an external crystal like a typical Arduino board)
the warning message does indicate why things may not be working on a virgin/blank AVR chip.
With the old firmware if you get this error/warning message and things are not working, often everything will work
if you simply jumper the slow SCK jumper on the USBasp device.
This is what I do on my USBasp device as I've not gotten around to updating my USBasp firmware so it can
be slowed down from avrdude rather than having to use a jumper.
Once the AVR has been programmed to use a faster external crystal, (which requires changing fuses)
the USBasp slow SCK jumper can be removed.
Future re-programming of that AVR can now be done faster
and the SCK error/warning can be ignored since the AVR is now running with a faster
external crystal and the faster SCK will not create any issues since the AVR can keep up