H
m, been a long time and an OS change since I used bitburner. Installed AVR
Studio 7 to get drivers for the AVR ISP mkII (strange by the way that
BitBurner has both a avrispmkII and an avrisp2. Wonder what's the
difference ;-).
But I'm very disappointed in the error messages: Nothing but
"read/write/verify failed"
. I do remember having to manually add the ATmega48PA that I use - but I'm
pretty sure that Bitburner used to tell me if the IDs did not match (so I
could figure out what to write in the .conf file). In any case if "failed"
is the level of info BitBurner (v.0.0.1.0/AVRdude v.6.3) can give on
errors, I don't think I have the energy to ever get it working again. Sad
but true. :-(
But frankly it seems so unrealistic stupid that I'm probably missing
something? Possibly it's just not compatible with newer Windows versions?
Best regards,
Anders
PS: I also find it strange that the program does not appear as an active
program in the task bar of Windows 10. But the settings dialog does! That's
very strange.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
H
m, been a long time and an OS change since I used bitburner. Installed AVR
Studio 7 to get drivers for the AVR ISP mkII (strange by the way that
BitBurner has both a avrispmkII and an avrisp2. Wonder what's the
difference ;-).
But I'm very disappointed in the error messages: Nothing but
"read/write/verify failed"
. I do remember having to manually add the ATmega48PA that I use - but I'm
pretty sure that Bitburner used to tell me if the IDs did not match (so I
could figure out what to write in the .conf file). In any case if "failed"
is the level of info BitBurner (v.0.0.1.0/AVRdude v.6.3) can give on
errors, I don't think I have the energy to ever get it working again. Sad
but true. :-(
But frankly it seems so unrealistic stupid that I'm probably missing
something? Possibly it's just not compatible with newer Windows versions?
Best regards,
Anders
PS: I also find it strange that the program does not appear as an active
program in the task bar of Windows 10. But the settings dialog does! That's
very strange.