Burning a USB drive with VMware ISO file


Dear Guys,

I just entered the IOT area and have to migrate an environment from vmware vsphere 5.1 to 5.5 for support. Problem is that I work in mac environment and now am learning how to use terminal after 30 years staying away from it (Unix 5.3). Trying to copy an ISO file downloaded from vmware.com to a USB disk was daunting. I downloaded etcher because I am moving a PLC and Java project programmed the old way from under windows 7 on VMware to a Java environment - in other world upgrading my industrial IOT to modern supportable IIOT. Thats why I am here. The Balena open source not world looks good. The etcher was a plus.

Problem I have now is that I have to create lots of different bootable OS’s on usb to help migrate our code from Win7 in Vmware 5.1 to Win10 in Vmware 5.5 then to 6., RasberriPi 2 to rasberriPi 3, Win 7 to Win 10. SO I ma building a lot of usb and sd cards. I may have experience 30 years ago burning images and editing them. the media and layouts are so different.

Will using BalenaEtcher to flash ISO images on other OS’s work. Ima getting error messages that the USB is not formatted in way to accept ISO image.

Oldie and inexperienced newby



Hi @nicksassow

This question comes up a lot as it’s not obvious when you’re starting out. Etcher does a great job of putting exactly what it’s told onto a SD card, flash drive or other device. The image file you flash can contain filesystems that are not readable by the OS that you’re using to actually carry out the flashing process. For example, you can flash a Linux installer image to a card using Etcher running on Windows. Assuming the image was valid, this card will work perfectly to install Linux and be readable on Linux computers, but Windows is not able to read Linux filesystems so your card can appear ‘broken’ after flashing and give error messages about being ‘unreadable’ or requiring formatting.

However, that being said, Etcher does not currently support burning/creating Windows installer devices. See this GitHub issue for more information: https://github.com/balena-io/etcher/issues/210



so its like dd under Unix console or Macos terminal. The version of dd I learned is 30 years old with an update 20 years ago for Solaris. I wanted a visual tool cause I have fatfingers and I type with 2 fingers in 6 languages. Thought I could do it with Etcher, Failed then used UNetbootin and stepped on my archive Lacie drive as it was in adjacent USB port to the HP USB card. Now have a recovery issue - another story due to rushing around.

Image is Valid Vmware image - I then failed in getting HP Proliant 8 with ILO4 to boot properly. Learned from HP there is another secret way to load an ISO to USB so the HP boots correctly. Frustrating - so it is pushing me to open hardware architecture and open source code that is examinable, but is compiled to maintain function and security. ARgh!!! - - - -

In my old age I have become happier with apps and graphics that transcend command line as the syntax changes over the years. Like french italian spanish portugese romanian, ladino all came from Roman Latin. I just like simple tools because I like to branch to new things like iIOT to manage smelly bugs and not worry that tools I use are evolving to make me obsolete. I do not like reinventing the wheel, redesigning is okay, reinventing is not.

Thank you for your honest response. How does etcher tool evolve?