Since the last post, I was able to (re)download Raspbian, unzip it with 7zip, and boot (somewhat). The difference? only thing I can think of is that I used a 32GB Samsung
microsd in a Samsung
adapter when imaging. The others were 16GB Lexar and SP Elite. I wouldn't think that would have anything to do with the decompressing errors though. At this point I've placed the imaged micro sd (the Samsung 32GB) in the Rpi zero w and it booted to a somewhat distorted screen. by that I mean some of the pixels on the desktop "sparkled". In addition, the usb port appears to be dead. I plugged in (via adapter) the same usb bluetooth dongle I use with my Pi 2b which works fine.There does appear to be voltage on the proper pins of the usb plug. That's as far as I got. I'm going to try copying my latest downloaded raspbian over to the other computer to see if I encounter errors in the unzip/ image process (yeah I'm a bit masochistic) As far as checksum goes, although I do understand what it is and how it works I don't have the knowledge as to how to check it. My experience (ancient) with it was incorporating it into file transfer subroutines.
I did successfully write a system on one of the 16 GB micro sd cards using my Win 10 desktop. I put in in the Rpi zero w and it did the same as the original. It booted to the Pixel desktop, but I have no control via the usb port. I'll reiterate that all that is plugged into it is the bluetooth transceiver that provides connectivity to a wireless Keyboard and mouse. And also reiterate that the keyboard and mouse work fine on the Rpi 2b and the desk top.I tried this "trick" described here viewtopic.php?f=28&t=58151#p850218
with positive results. According to the author it is an indicator that the pi is not dead. I'm really not sure where to go from here. Interestingly I've seen many reports of the usb port not working but have seen no real conclusive single fix for any of them. Can anyone offer any suggestions? Thanks in advance
At this point I've tried several approaches without success. I've changed usb adapters, added a powered usb hub, and nothing appears to have changed. I did however pay closer attention at boot and prior to the Pixel Desktop appearing, there were several lines of text. I tried to take a photo of the screen but it was fuzzy, I'll try again later, but the essence of the first line was
"[ 5.379003] usb usb1=port 1: connect-debounce failed" .
Does this indicate a hardware failure or.....?