How do I open .bin files on a 2021 MacBook Pro running Sonoma 14?
[Re-Titled by Moderator]
MacBook Pro 16″, macOS 14.1
danuke wrote:
I could open these .bin files from Nikon with a simple double click, at least until I went to a Sonoma, M2 machine Mac mini; i.e. my old intel iMac running Ventura. So something in Sonoma dumbed down.
Then I would simply move the extracted file to the Camera's SD card's root directory and install the upgrade. No issues.
FYI, the .bin file is the extracted file needed to be transferred to the camera. Files downloaded from the Internet are typically stored in a .zip archive which Safari "opens" by default. When Safari "opens" the .zip archive, it extracts the contents....namely the .bin file needed for the firmware update (macOS then automatically deletes the downloaded .zip file leaving only the extracted contents behind).
You don't open a .bin file (at least not .bin files associated with firmware updates).
You can prevent Safari from automatically "opening" files by going into "Safari --> Settings", clicking on the "General" tab. At the bottom of that page uncheck the option 'Open "safe" files after downloading'. This will prevent Safari from automatically extracting the contents of archive files such as .zip files & deleting the downloaded file. Of course people may want other document type files to open automatically so changing this setting may not be an option for them.
Did you try contacting support for instructions on how to apply the firmware update? The message just means macOS can't do anything further with the file.
when selected for a potential install I receive an error message on my Mac saying "Unable to expand 'fwdc228b.bin.' It's an unsupported format. This is the most recent firmware update for this camera. My thought process was to. hardwire the camera to the Mac to install the camera firmware. Is there a different process?
>> 'fwdc228b.bin.' It's an unsupported format
>>> HWTech: "Safari already [obviously] performed the extraction step. Re-read the instructions you are following carefully so you don't miss a step"
This is my comment to the link you provided.
I bought a PENTAX K1 from B&H Photo in NYC. Firmware was original 1.0. I downloaded the most recent version from your site. How do I install it on my K1? Thank you in advance.
This is the comment I received WITHOUT my submission going through.
‘There was a problem with your submission. Errors are marked under each field. Your entry appears to be spam!
Talk about frustrating!!!
back to my guy at Ricoh! I'm hoping he can clean up 'my submission.' Thx again for the link!
ludditE321 wrote:
‘There was a problem with your submission. Errors are marked under each field. Your entry appears to be spam!
Talk about frustrating!!!
How odd.
back to my guy at Ricoh! I'm hoping he can clean up 'my submission.' Thx again for the link!
You're welcome.
In case you need it…
Updating Procedure
Provide a formatted SD memory card for the update software.
The download file is self-extracting. The following file is extracted.
Fwdc228b.bin: This is the updated firmware.
Copy the above Firmware file [fwdc228b.bin] to the root directory in the SD card.
If your computer does not have a card slot, you can copy the firmware update file by inserting the SD card into your camera and then connecting the camera directly to your computer.
Insert the D-LI90 battery into the camera and confirm the battery is full by battery level indicator then turn the camera off.
Insert the update SD card (prepared in step 1) into the camera (slot 1) and close card cover.
Turn the camera power on while pressing the MENU button.
"Updates the camera firmware" appears in the LCD monitor.
Ver: 1.00/1.10/1.20/1.30/1.40 /1.41/1.42/1.43/1.50/1.51/1.52/1.53/1.54/1.55/1.60 /1.70 /2.00 /2.10 /2.20 →2.30 will be displayed.
Press the four-way controller to select "Start" and press the "OK" button.
"NOW LOADING" appears on the LCD monitor and updating starts.
Please do not under any circumstances switch off the power before the update is completed.
When update is completed, the "COMPLETE" will be displayed at the left bottom of the LCD monitor, then turn the camera off.
Remove the update SD card from the camera.
*Confirm the version of firmware with above [How to check version].
[Caution]
When updating is finished, the update SD card still contains the Firmware file.
If you want to use this card to take pictures, format the card by the camera to delete firmware file first.
Hi ALL!
First let me offer a GREAT BIG THANK YOU to all of you! I'm taking really tiny baby steps into the digital world after having been a professional and successful FILM photographer for over 20 years. At one time I owned a photo shop and did product photography, weddings, (ugh) portraiture and my favorite was magazine/editorial work for boating magazines. I left the industry when camera manufacturers decided to become online retailers and cut out smaller, independent shops from which they thrived for many years.
I FINALLY got the .bin into the camera thanks to ALL of your input as well as this YouTube video. Thanks again! Signing off until the NEXT issue arises. I'll try seeing what I'm shooting on the MacBook Pro LIVE in REAL TIME next!
[Edited by Moderator]
Color me red. I did not know that it did that automatically and it has been just long enough between updates that I forgot (I'll blame it on my old age).
Thank you for the education, I really do appreciate it, and hope that it does stick.
It indeed has been "interesting" shifting from my old iMac to this Mac mini.
With your help, my camera/lens upgrade went very smoothly.
danuke wrote:
Color me red. I did not know that it did that automatically and it has been just long enough between updates that I forgot (I'll blame it on my old age).
Thank you for the education, I really do appreciate it, and hope that it does stick.
It indeed has been "interesting" shifting from my old iMac to this Mac mini.
With your help, my camera/lens upgrade went very smoothly.
No problem. I've had issues where I could not find a downloaded file because of it when using another person's Mac or when accessing my organization's "admin" accounts where the defaults remain. I absolutely despise having the OS delete an item I downloaded as I usually want to keep the original item. I've also lost lots of special macOS installers due to the default option of "Move to Trash" being where I expect the "Ok" button to be. I thought I had been careful, but I guess not and those older installers are no longer available to download.
Keith Barkley wrote:
Though not a Mac, I recently had someone send us some software with a .txt extension. We were supposed to change the extension to ".exe" to make it an executable file.
Just...why?
"Just...why?"
I have no idea. It is an especially bad idea since Windows makes changing extensions non-obvious.
"I think that there is usually a chmod +x command line associated with the file to make it executable also."
Not on Windows. 8^)
"That's different. In Windows, an .exe file is one containing machine code. You can't magically change a file that contains text – which is what the .txt extension usually denotes – to one containing machine code – by renaming the file."
What the jamokes did was to rename *their* .exe to .txt - I guess in a lame attempt to avoid anti-virus software - and then had us reverse the process. So the "text" file we got was really a binary.
"Whereas Unix will ignore the extension?"
Traditionally, executables in unix had *no* extension - just the access bit in the permissions. Hence why you will see a lot of posts here about "Apple changed my photos to Unix executables!" since Apple would apply a generic unix executable icon to any file without an extension.
IdrisSeabright wrote:
Keith Barkley wrote:
Though not a Mac, I recently had someone send us some software with a .txt extension. We were supposed to change the extension to ".exe" to make it an executable file.
Just...why?
It lets the file slip past stupid IT departments.
Barney-15E wrote:
IdrisSeabright wrote:
Keith Barkley wrote:
Though not a Mac, I recently had someone send us some software with a .txt extension. We were supposed to change the extension to ".exe" to make it an executable file.
Just...why?
It lets the file slip past stupid IT departments.
"Please accept this large wooden horse named .TXT as a gift and take it within your walled city."
"Then once it is safely inside, please rename it .EXE to collect your 'gift'."
Servant of Cats wrote:
Barney-15E wrote:
IdrisSeabright wrote:
Keith Barkley wrote:
Though not a Mac, I recently had someone send us some software with a .txt extension. We were supposed to change the extension to ".exe" to make it an executable file.
Just...why?
It lets the file slip past stupid IT departments.
"Please accept this large wooden horse named .TXT as a gift and take it within your walled city."
"Then once it is safely inside, please rename it .EXE to collect your 'gift'."
That's a good one, too, but I've never seen it in real life. I've seen the moving executables around a lot. Sometimes it's just mp4's. Apparently Windows will run any arbitrary code embedded in other files, so IT tries to block them. I can't imagine that is still a vulnerability, but the great part of being IT is you don't have to think.
How to open .bin files on MacBook Pro running Sonoma 14?
