what i did is formating usb in fat32 and i aded only the patch bin is it the wright way thanks
Yes, That's it!
All I can guess is that your usb port might be dead then.

(or loose cables)
what i did is formating usb in fat32 and i aded only the patch bin is it the wright way thanks
i have opened the box i am asking if there a special place or boton to reseat it thanks a lot
It is obvious that your receiver is not responding to your remote control and I think you stated that the front panel buttons do not seem to give a response either. This may be bad news if reseating the connectors doesn't help.
Since your upgrade menu appears, that means that the box isn't totally dead or too terribly corrupt. It also means that it IS identifying that something is plugged into your USB port, otherwise that menu would not appear, so that is a good sign. It simply isn't responding to external commands.
Put a new set of batteries in the remote, just to be certain and have that ruled out. You may see the "red" LED on the remote flash when you press a button, but that doesn't mean that it has enough power to transmit a signal to the box. Keep that in mind.
The need to rename it depends on where you got the file, since if you get it from the official Azbox site where the box itself gets them, they already have the patch.bin filename. Ie from:.....
..............
P.S. NOTE: When you copy the firmware file to your USB stick, you need to "rename" the file. I recommend that you rename it simply as "patch" as opposed to "patch.bin".
I think I know what you're referring to here, but I don't think that it's really the fault of the OS, so much as a fault in whatever program you're using, and a problem caused by your settings in the OS. Windows has an option that does what you refer to, ie to omit known extension types when displaying the file names, however the extension info is there for programs to use, and it's up to the program itself to be smart enough not to be fooled.....
Some computer operating sustems will imbed the "*.bin" extension in the file name for you. If this is the case, then if you try to rename the file "patch.bin" it actually ends up being "patch.bin.bin" which confuses the AZBox and it won't acknowledge the file.
Yeah, my Azbox stopped responding to my remote last week. No lights on my Azbox remote, but I could see the lights blinking on my TV and RS Pyramid, so I knew it was sending, but the Azbox wasn't responding. I eventually tried changing the batteries, and that seemed to fix it. The low batteries must have caused it to send corrupted signals.
The need to rename it depends on where you got the file, since if you get it from the official Azbox site where the box itself gets them, they already have the patch.bin filename. Ie from:
http://azupd.com/0.9.3725/patch.bin
replacing the 0.9.3725 in the example with the version you're looking for. Only problem then is remembering what patch.bin is which version. Get it from there, and you don't have to rename it.
I think I know what you're referring to here, but I don't think that it's really the fault of the OS, so much as a fault in whatever program you're using, and a problem caused by your settings in the OS. Windows has an option that does what you refer to, ie to omit known extension types when displaying the file names, however the extension info is there for programs to use, and it's up to the program itself to be smart enough not to be fooled.
Unfortunately explorer (or MyComputer) isn't written very well, and does what you describe. Programs that I write myself, when I call the OS directory/filename functions to display and alter file names, it displays the whole filename with the extension, and that mistake doesn't happen. Even if you bring up those .bin files in MS Word, and re-save, Word is smart enough not to add an extra .bin. It's just the darn MyComputer explorer program that's trying to be too smart for it's own good. But it's really not the OS, because the OS supplies the whole filename including the extension to the program, it's just that explorer chooses not to handle it properly.
I always uncheck that "Hide known extensions" option in the "view" tab of explorer options. That way there shouldn't be any likelihood of adding an additional .bin to the filename.