> Am 10.03.2023 um 19:53 schrieb Bernd Böckmann :
>
> /SMBR command to write the MBR to disk
to file of course…
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
Hi,
I hope I have eliminated the most critical bugs and I am now in a cleanup
phase. I noticed that the /SMBR command to write the MBR to disk does not do
what its name suggests. It only writes the 440 code bytes to the file and fills
the rest of the 512 bytes with zero, leaving FDISK with no m
On Sun, 5 Mar 2023 20:41:58 +0100
Bernd Boeckmann via Freedos-devel
wrote:
> FDISK now aligns all partitions to 4K if the configuration option
> ALIGN_4K=ON, which is the default.
>
> For backwards compatibility, ALIGN_4K=OFF restores the old behavior
> (cylinder alignment). Then it also points
Hi,
I am so far through with the implementation of functionality I want to have in
version 1.4. I still have to test it properly and hopefully have a version that
can be included in the next FreeDOS monthly.
The current build, compiled with Open Watcom 1.9 for 8086, can be obtained from
https:
>>> The reason why partition boundaries are aligned on cylinder boundaries
>>> is that a lot of other OSes also rely on that.
>> any example of this? I don't any (not completely braindead) operating
>> system would rely on that; it's just the way that FDISK and friends
>> place partitions on the d
On 3/1/2023 9:13 AM, tom ehlert wrote:
The reason why partition boundaries are aligned on cylinder boundaries
is that a lot of other OSes also rely on that.
any example of this? I don't any (not completely braindead) operating
system would rely on that; it's just the way that FDISK and friends
Hallo Herr Ralf Quint,
am Mittwoch, 1. März 2023 um 18:08 schrieben Sie:
> On 3/1/2023 8:22 AM, Bernd Boeckmann via Freedos-devel wrote:
>> Hello,
>>
>> I am now reaching a state where I think that FDISK not any longer breaks the
>> partition layouts created by itself.
>>
>> However, there is at
> Am 01.03.2023 um 18:08 schrieb Ralf Quint :
>
>> b) If it would be ok (at least as an interim solution) to make FDISK refuse
>> handling disks with such type of partition layout, because the user must
>> have another partition manager to create such layouts anyway. While not
>> being optima
On 3/1/2023 8:22 AM, Bernd Boeckmann via Freedos-devel wrote:
Hello,
I am now reaching a state where I think that FDISK not any longer breaks the
partition layouts created by itself.
However, there is at least still one MAJOR flaw when dealing with partition
layouts created by other partition
Hello,
I am now reaching a state where I think that FDISK not any longer breaks the
partition layouts created by itself.
However, there is at least still one MAJOR flaw when dealing with partition
layouts created by other partition managers:
If there exists an extended partition with a start a
Hi,
On Tue, 28 Feb 2023 at 20:31, Eric Auer wrote:
>
> PS: Interesting that Bing ChatGPT answers Aitor using his own
> mails, does it at least include some thanks to the author? :-)
>
Lol it does not, but it links to the log of pages, etc. where it took the
answers from. That's how I found out.
Hi Eric,
> Now I would like to know how long each of those bugs has been
> in FDISK, can you see that in change logs or by comparing your
> version to various older versions? It must have been ages :-o
I will try to find out and leave a note in CHANGES.md for all critical
(potential data loss) e
Hi Bernd,
thank you for your work on FDISK!
Version 1.3.5 (unreleased)
--
- CRITICAL: Fix FDISK loading wrong head and sector values from MBR if
operating in LBA mode. The previous incorrect behaviuor was hardcoding
them to cylinder boundaries instead of
Hi Rugxulo,
thanks for the advice!
> Is makefile.bor still maintained? Do you still (also) support building
> it with that toolset (presumably freeware-ish TC++ 1.01 would work)?
Yes! At the moment I have it compiling with Borland C++ 3.1, Turbo C++ 3.0 and
Open Watcom 1.9. While mainly develop
Hi,
On Sun, Feb 26, 2023 at 1:07 PM Bernd Boeckmann via Freedos-devel
wrote:
>
> in the last two weeks I ported Free FDISK to Watcom C and started fixing the
> bugs people mentioned
> at the bttr forum and in the issue trackers.
Great news! Thanks a ton for your work on this.
BTW, it seems you
> However, when the disk already has a partition and is full…
>
> fdisk 1 /prio:2000 ; no error, no partition created, exit errorlevel 0
> fdisk 1 /pri:100,100 ; divide error, no partition created, exit errorlevel 3
Nice finding!
Fixed in
https://github.com/boeckmann/fdisk/commit/0299059669147
Hi Bernd,
> On Feb 27, 2023, at 12:57 PM, Bernd Boeckmann via Freedos-devel
> wrote:
>
>
>> Am 27.02.2023 um 17:28 schrieb jer...@shidel.net:
>>
>> I think I will go with a max partition of 2GB (FAT16) on real hardware and
>> the entire disk (FAT32) inside Virtual Machines.
>
> If you want
> Am 27.02.2023 um 19:31 schrieb jer...@shidel.net:
>
> Using your example, I think it would be easier for a user to understand as:
>
> fdisk 1 /clear /pri:2048 /ext:max /log:4096 /log:max
>
I agree and implemented it as you suggested. The MAX quantifier now internally
is the same as the 100
> On Feb 27, 2023, at 12:02 PM, Bernd Boeckmann via Freedos-devel
> wrote:
>
>> Seriously, thank you. :-)
>
> Glad I could help :-)
>
>> On a side note: It might be nice to support '/prio:max’ and '/pri:max’.
>
>
> Shouldn’t do /pri:100,100 the trick?
Yep, works fine.
> The ,100 indica
> I'm not sure if this fdisk can already do that, but additionally it
> would also be very useful if it could align partitions to 4k rather
> than 63 sectors to lower wear on flash drives (SSD, CompactFlash).
You can certainly make a case for aligning things on 4k boundaries on both
modern and ol
> Am 27.02.2023 um 17:28 schrieb jer...@shidel.net:
>
> I think I will go with a max partition of 2GB (FAT16) on real hardware and
> the entire disk (FAT32) inside Virtual Machines.
If you want it to be FAT-16 I would suggest not doing /PRIO:2048 but instead
/PRIO:2047 or even less, because f
On Mon, 27 Feb 2023 16:55:31 +0100
tom ehlert wrote:
> I hate feature flags as they must be decovered first.
>
> hiding it behind
>
>if lba_supported_by_disk and
> total_disk_size > 8,4 GB // max total size for CHS addressing
> {
> place partitions on 4K boundary
> }
> Seriously, thank you. :-)
Glad I could help :-)
> On a side note: It might be nice to support '/prio:max’ and '/pri:max’.
Shouldn’t do /pri:100,100 the trick? The ,100 indicates that the first value is
to be interpreted as a percentage. If you want to specify the size in MB you
must NOT gi
Hi,
> On Feb 27, 2023, at 7:27 AM, Bernd Boeckmann via Freedos-devel
> wrote:
>
> Hi Jerome,
>
>> Am 26.02.2023 um 23:31 schrieb Jerome Shidel :
>>
>> Unfortunately, the current FDISK performs this task be creating a bunch of
>> 2GB partitions. This tends to annoy users installing on real h
Hallo Herr Bernd Boeckmann via Freedos-devel,
am Montag, 27. Februar 2023 um 13:07 schrieben Sie:
>> Am 27.02.2023 um 07:26 schrieb Deposite Pirate :
>>
>> I'm not sure if this fdisk can already do that, but additionally it
>> would also be very useful if it could align partitions to 4k rather
Hi Jerome,
> Am 26.02.2023 um 23:31 schrieb Jerome Shidel :
>
> Unfortunately, the current FDISK performs this task be creating a bunch of
> 2GB partitions. This tends to annoy users installing on real hardware with
> very large disks.
Yes at the moment it sadly is hardcoded to creating partit
> Am 27.02.2023 um 07:26 schrieb Deposite Pirate :
>
> I'm not sure if this fdisk can already do that, but additionally it
> would also be very useful if it could align partitions to 4k rather than
> 63 sectors to lower wear on flash drives (SSD, CompactFlash).
The current behaviour is to alway
On Sun, 26 Feb 2023 17:31:12 -0500
Jerome Shidel wrote:
> Hi Bernd,
>
> Since you are working on fixing and improving FDISK, there are two
> features that would be great to add for end users.
>
> During the installation of FreeDOS, when no partitions are present,
> the installer will try to us
Hi Bernd,
Since you are working on fixing and improving FDISK, there are two features
that would be great to add for end users.
During the installation of FreeDOS, when no partitions are present, the
installer will try to use FDISK to automatically partition the drive.
Unfortunately, the curr
29 matches
Mail list logo
