If you get that message it means you have inserted the adapter or device incorrectly. In my case the adapter needed to be at the rear end of the pins and it caused this message.
Do not ignore this message as it may appear to work but you will get errors and in reality your chip will not be erased or programmed even if it appears like it is working.........
If you remove the white label on the chip (near the CMOS battery) you will find the following details about it:
SST 49LF080A 33-4C-NHE
It is the PLCC32 type and can be pried and removed safely (but be very careful) with an eye glass flat head screw driver.
If you just have a bad flash you may be able to reprogram your original or just buy another one with the part# above and reprogram it.
This is great news for people who have bricked th........
Which one does the OS care about? blkid says the UUID is "787f1fa4-b010-4d77-a010-795b42884f56" while md insists its UUID is "4d96dd3b:deb5d555:7adb93cb:ce9182d9"
When in doubt, do we assume the OS takes the one from blkid?
/dev/md0: UUID="787f1fa4-b010-4d77-a010-795b42884f56" TYPE="ext3"
[root@localhost ~]# mdadm -D /dev/md0
Version : 0.90
Codelite is a great choice and I intend on getting back into C++ development and I think Codelite is great being cross platform.
It looks like it was designed with a lot of thought and should do the job better. I really dislike the bloated and confusing IDE's from big companies like Microsoft where you usually have to use .NET and other useless technologies that just give Microsoft the advantage over you, the programmer, and the users.........