From owner-freebsd-hackers@freebsd.org Thu Jul 11 11:50:13 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D2D9415CFC59 for ; Thu, 11 Jul 2019 11:50:13 +0000 (UTC) (envelope-from freebsd-hackers@m.gmane.org) Received: from blaine.gmane.org (195-159-176-226.customer.powertech.no [195.159.176.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 71B8B735E7 for ; Thu, 11 Jul 2019 11:50:12 +0000 (UTC) (envelope-from freebsd-hackers@m.gmane.org) Received: from list by blaine.gmane.org with local (Exim 4.89) (envelope-from ) id 1hlXaM-000H86-9u for freebsd-hackers@freebsd.org; Thu, 11 Jul 2019 13:50:02 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hackers@freebsd.org From: =?UTF-8?Q?Jean-Pierre_Andr=c3=a9?= Subject: Re: mkntfs doesn't install NTFS's bootcode during formatting Date: Thu, 11 Jul 2019 12:11:32 +0200 Message-ID: References: <20190710192048.00001ca2@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.4 In-Reply-To: <20190710192048.00001ca2@gmail.com> Cc: ntfs-3g-devel@lists.sf.net X-Rspamd-Queue-Id: 71B8B735E7 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.93 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.93)[-0.931,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jul 2019 11:50:14 -0000 Domagoj Smol=C4=8Di=C4=87 wrote: > FreeBSD 11.2-RELEASE-p9 > fusefs-ntfs-2017.3.23 > > When slice/partition is being formatted, bootcode(';=20 containsMicrosoft Windows XP/VISTA bootloader BOOTMGR') isn't applied,=20 thus rendering it unbootable. > Under Win, after 'bootsect /nt60 ...' has been used on NTFS created=20 with mkntfs, THEN it becomes bootable. This BOOTMGR bootcode is proprietary, and it depends on the targeted Windows version, hence mkntfs cannot insert it. However mkntfs creates the boot sector of the partition, which is part of the ntfs file system structure. Nevertheless can you explain in what circumstances this would be useful. On several occasions, I have formatted an ntfs partition before installing Window 7 or Windows 10, and these installers insert the boot code they want without formatting the partition. I do not have XP or Vista any more, but I would be very surprised if they do not insert their own boot code as well (possibly while reformatting the partition). > > When slice/partition is being formatted directly under Win, bootcode=20 IS also being applied. No, this is not done while formatting. The Windows formatting is limited, and the full formatting occurs when the partition is mounted the first time. So, when upgrading Windows, you can format with the old version before installing the new one. > So, if you need a bootable NTFS, why to bother in a first place with=20 mkntfs, then transferring device to Win machine and using command line=20 under Win to run 'bootsect' tool, when you can simply click 'Format...'=20 & Start?!? Can you explain what you want to boot into ? Jean-Pierre