Conclusion-Do not use the ESP32CAM-MB boards unless you are lucky enough to have MB boards that work.
I was finally able to the get the time to try the "press RST button" workaround.
Alsa, no change.
Although I did encounter a twist. My original build used COM3 and when I connected while pressing the RST button the port changed to COM5. Dunno why. Using that port, I was able to connect and upload but ... the 105 error persists.
I did a google search ("ESP32-CAM MB error 105") and found some discussion about boards with power issues and pin configuration problems. Ugh.
Sorry, I have to push this off to another day. I've taken on too many projects and am teetering on information overload.
But thanks, @zander and sorry @hurrikane.
The one who has the most fun, wins!
@tfmccarthy a 105 error is either you didn't modify the #define statements to agree with the camera, OR the camera is not connected properly. When you insert the cable, you should notice a 'snap' when it is properly seated. In a further post of mine you didn't get to you will see the MB boards work just fine once I replaced a weirdly defective cable. No buttons being pressed of any kind.
First computer 1959. Retired from my own computer company 2004.
Hardware - Expert in 1401, 360, fairly knowledge in PC plus numerous MPU's & MCU's
Major Languages - Machine language, 360 Macro Assembler, Intel Assembler, PL/I and PL1, Pascal, Basic, C plus numerous job control and scripting languages.
My personal scorecard is now 1 PC hardware fix (circa 1982), 1 open source fix (at age 82), and 2 zero day bugs in a major OS.
I'm not sure how relevant this response is to your specific hardware, but I have struggled a lot with getting the camera module to work - error 105 always - but finally got it to work by doing two things:
1. The camera I have (OV2640) is mounted via a shield, and the ESP32 plugs into the shield - the shield has a separate socket for a rechargeable battery, and when I plugged in the battery (with the USB cable still plugged into the ESP32 board), the camera then started to work, i.e. the code delivered the URL to access the camera.
2. Whilst I got the URL working, the image displayed was terrible - more like a still image that changed every 10 seconds our so. But when I moved a lot closer to the router, it was much better. Though to be honest, still not good enough for video surveillance, for example. The boards have a tiny aerial, so perhaps an external aerial is the way to go. I know some boards have sockets to enable an external aerial to be connected.
This may not help you at all, but fingers crossed that it does.