Date: Sat, 29 Dec 2018 20:35:55 +0100 From: Polytropon <freebsd@edvax.de> To: freebsd-questions@freebsd.org Subject: Re: Hello(trouble with magic number) Message-ID: <20181229203555.cd63a0ed.freebsd@edvax.de> In-Reply-To: <SN1PR20MB210973E0C103946B29C2567880B00@SN1PR20MB2109.namprd20.prod.outlook.com> References: <CAP=T6ZPz7JEKb9P1ReiZ%2B1GbwDQKkjAjQa=j=cvyBztF8s=Ohw@mail.gmail.com> <CAP=T6ZO-%2B_VKH3VZccBUF1C21hg2f6foK5WKo-4J=o_0yrOqzA@mail.gmail.com> <CAP=T6ZN0GBb=Va4OFd4gGDrULsfxXEQZpFA6Lwbxz2Jw=TVXzg@mail.gmail.com> <CAP=T6ZNT7epbYGF1xo4QrzEJ1WFfXLP1K4wbqO%2BxR3eeSVpp6A@mail.gmail.com> <CAP=T6ZNNuVE4%2BM2DiBC_Uid9Mj64ZCVz=svEEQ_N1H16rHm91Q@mail.gmail.com> <CAP=T6ZO3ZC8X2gzDUrad4rraaf7m62yVHw48ydp5AVDj2twmWQ@mail.gmail.com> <CAP=T6ZM8uRcTnzAi9an_Gr0NhAN=xZL%2BShPQvcfbsEYyd51Kqg@mail.gmail.com> <CAP=T6ZMX3qpQyiPQtRvgKZk-FO_K0Luarnk6t2u8EhoeTBFVow@mail.gmail.com> <CAP=T6ZNxEwyP8cwXuecxzC=w%2BJfKSk7HLQPPuWk_UOC1uhTM1g@mail.gmail.com> <20181228152218.596c04c1.freebsd@edvax.de> <CAP=T6ZMq-ry7V3z84AgAoG8QMSj9vPdodb8RS067SrtkG6shKQ@mail.gmail.com> <CAP=T6ZOPOc-efMHFNFXseDtjmU=DeQWKcOHsvqRtJKwH_YHjTw@mail.gmail.com> <20181229150556.dcddc29a.freebsd@edvax.de> <SN1PR20MB210973E0C103946B29C2567880B00@SN1PR20MB2109.namprd20.prod.outlook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 29 Dec 2018 15:12:52 +0000, Carmel NY wrote: > On Sat, 29 Dec 2018 15:05:56 +0100, Polytropon stated: >=20 > >Interesting, you didn't mention "Windows" before. Sure, > >yes, "Windows" doesn't have a native tool to write > >image files to media. But as I said: You'll have to > >write the image 1:1, not "open" it and deal with its > >content. >=20 > I don't think that is correct. >=20 > https://www.lifewire.com/mount-burn-iso-windows-8-10-3506971 I'm not sure this applies here (even though native support for dealing with ISO images is a fundamental OS feature). Section 2.3.1.1. procedure 2.2. of The FreeBSD Handbook states: 1. Obtaining Image Writer for Windows=AE Image Writer for Windows=AE is a free application that can correctly write an image file to a memory stick. Download it from https://sourceforge.net/projects/win32diskimager/ and extract it into a folder. 2. Writing the Image with Image Writer Double-click the Win32DiskImager icon to start the program. Verify that the drive letter shown under Device is the drive with the memory stick. Click the folder icon and select the image to be written to the memory stick. Click [ Save ] to accept the image file name. Verify that everything is correct, and that no folders on the memory stick are open in other windows. When everything is ready, click [ Write ] to write the image file to the memory stick. This is where I pointed to. Nothing there makes me assume that it is needed to access the image's internals. The article mentions "mount or burn", and the part "burn" would certainly apply to FreeBSD CD or DVD images ("OSI images", refering to ISO 9660). However, the USB image might require a different treatment, as it won't be written to an optical unit, but to a USB stick, which it is intended for. The discussion was explictly about USB sticks and how to access their content, and contained a lot of misunderstandings, and then it was about VirtualBox virtual machines networking... ;-) --=20 Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20181229203555.cd63a0ed.freebsd>