Well, it wasn't the COM port number. Can't be that simple.
I realized I had a deeper problem when I couldn't get Xloader or AVRDUDESS to run. Apparently updating from Win 7 to Win 10 erases your libusb0.dll file. This shuts down Xloader's AVRDUDE and also AVRDUDESS. The AVRDUDESS web site addressed the problem to a large extent, but the solution wasn't totally accurate.
What I did was download the libusb-win32-bin-1.2.6.0/bin/x86/libusb_x86.dll file from Zak Kemble's AVRDUDESS site, extracted it and then dug libusb0_x86.dll out of it (here's where it is - libusb-win32-bin-1.2.6.0\bin\x86\libusb0_x86.dll). Then I renamed it to libusb.dll and then copied it to Windows\SysWOW64 (because I have a 64 bit computer).
I had found these instructions in a README file and they helped a lot:
ALL ARCHITECTURES:
x86\libusb0_x86.dll: x86 32-bit library. Must be renamed to libusb0.dll
On 64 bit, Installs to Windows\syswow64\libusb0.dll.
On 32 bit, Installs to Windows\system32\libusb0.dll.
So, I had no libusb0.dll file in Windows previously - - - (this is the error that AVRDUDESS displayed), and now I do, and now AVRDUDESS runs without a hitch.
Once I had that problem fixed, I thought I would try to get Flowcode 7 to compile for my Mega2560 R3 with EB083 combo board.
In the midst of all this madness I had performed a system restore (a shot in the dark). So now I had the opportunity to update the component files again & see if it helped. It didn't, I actually regressed to the original compiler error I was experiencing in the post above. So I put the component files back the way they were, so that I'm getting the timeout error again.
Does this error have a fix? I realize I have a workaround available now (AVRDUDESS) but thought I would ask anyway.
Sorry this turned into a novel, but I thought it might help someone else.
The Humble Stumbler, still stumbling and still humble.