On Sat, 10 Jun 2006 08:00:53 +0400, you wrote:
Hi Arkady,
MS-FDISK _never_ writes MBR code (at least, if MBR not empty), unless
you do this explicitly through undocumented /MBR option.
Suddenly a flash come across my mind -- You and those replied all
correct, this is me who're wrong. I
On Thu, 8 Jun 2006 14:46:52 +0300, you wrote:
Hi,
This behavior is by design and documented. If you want to use fdos'
fdisk then you should take advantage of it's features and read before
you use it unattended in batch files. It is a drop-in replacement for
the MS counterpart, but it corrects
On Wed, 07 Jun 2006 18:32:07 -0400, you wrote:
Hi Jeremy,
Assumming I recall correctly, this is by design, if the MBR is
considered non-empty then it is not overwritten on purpose (also only
the MBR on the primary drive is ever written to). The purpose behind
this decision is to not overwrite
On 6/8/06, Johnson Lam [EMAIL PROTECTED] wrote:
[...]
This behavior is different from MS-FDISK, this will cause automated
batch file fail.
This behavior is by design and documented. If you want to use fdos'
fdisk then you should take advantage of it's features and read before
you use it
Hi Johnson,
I've always found FreeDOS FDISK works exactly as I'd expect both on new
and used hard drives including the option to install and remove the MBR.
Are you sure you read the readme that comes with it? All the machines on
our network started life with FreeDOS FDISK.
As I understand
Johnson Lam wrote:
Hi,
Actually it's not a BUG, FDISK always FORGET to write the Master Boot
Record to the hard disk, just test 2 hard disk this afternoon.
That's why the original hard disk still boot up showing LILO.
Hope someone can patch the FDISK, it should be easy to fix this minor
