Hi!
Let me explain why sometimes Only a 2GB FAT16 and sometimes the Entire Drive as
FAT32.
On real hardware, the user is most likely going to want to multi-boot other operating systems. Therefore by default, when the Installer creates the partition it will limit it to 2GB. Again, this should
> On Jan 16, 2025, at 1:16 PM, Bernd Böckmann via Freedos-devel
> wrote:
>
>
>
>> Am 16.01.2025 um 18:29 schrieb Jerome Shidel via Freedos-devel
>> :
>>
>> Based on your tests, I wonder what type of hardware you were installing
>> FreeDOS.
>>
>
> It is an emulated Pentium system (86box
> Am 16.01.2025 um 18:29 schrieb Jerome Shidel via Freedos-devel
> :
>
> Based on your tests, I wonder what type of hardware you were installing
> FreeDOS.
>
It is an emulated Pentium system (86box) I attached disks of different sizes to
:)
__
Oh, I should have included this in the previous reply…
Let me explain why sometimes Only a 2GB FAT16 and sometimes the Entire Drive as
FAT32.
On real hardware, the user is most likely going to want to multi-boot other
operating systems. Therefore by default, when the Installer creates the
part
Hi Bernd,
> On Jan 16, 2025, at 6:44 AM, Bernd Böckmann via Freedos-devel
> wrote:
>
>
>
>> Am 16.01.2025 um 07:24 schrieb Jerome Shidel via Freedos-devel
>> :
>>
>> With recent builds of the OS Release Media, when the Installer partitions
>> the drive automatically, it should only create
> Am 16.01.2025 um 07:24 schrieb Jerome Shidel via Freedos-devel
> :
>
> With recent builds of the OS Release Media, when the Installer partitions the
> drive automatically, it should only create one large FAT32 partition.
Jerome, are you sure? I tested it with RC1 and different drive sizes.
> Am 16.01.2025 um 01:47 schrieb Eric Auer via Freedos-devel
> :
>
> Crazy how we survived using FDISK before those TWENTY
> critical and high importance fixes in version 1.4.0 :-o
To be fair, much of it was regarding edge cases or extensive usage. As long as
you used it to create partitions
> On Jan 15, 2025, at 7:47 PM, Eric Auer via Freedos-devel
> wrote:
>
>
> Hi Bernd,
>
> Thank you for this extremely bug-fixing FDISK update!
>
> Crazy how we survived using FDISK before those TWENTY
> critical and high importance fixes in version 1.4.0 :-o
>
> Does the FreeDOS installer
Hi Bernd,
Thank you for this extremely bug-fixing FDISK update!
Crazy how we survived using FDISK before those TWENTY
critical and high importance fixes in version 1.4.0 :-o
Does the FreeDOS installer still create 20 FAT16 drives if
your disk has 40+ GB, by the way? If yes, will the updated
F
I released FDISK 1.4.0: https://github.com/FDOS/fdisk/releases/tag/v1.4.0
I will put this also into the Gitlab archive for FreeDOS 1.4 RC2.
The changes to the last version 1.3.4 shipped with FreeDOS 1.3 are listed below.
Greetings, Bernd
Change log 1.4.0 - 1.3.4
---
I found a critical FDISK error leading to a wiped disk.
The error is luckily not commonly triggered. I found it because after Pauls
mail I tested how FDISK handles the case of maximum logical partitions. Turned
out not that great...
FDISK can handle a maximum of 23 logical partitions per disk.
Hi Jim,
> On Feb 22, 2024, at 3:35 PM, Jim Hall via Freedos-devel
> wrote:
>
> Excellent news! I'll post an item on the website about it.
>
> I can't login to Ibiblio from where I'm at right now, so I can't
> mirror it - maybe someone else with Ibiblio access can do that for me.
> Otherwise I'
Excellent news! I'll post an item on the website about it.
I can't login to Ibiblio from where I'm at right now, so I can't
mirror it - maybe someone else with Ibiblio access can do that for me.
Otherwise I'll mirror this to Ibiblio over the weekend.
Jim
On Thu, Feb 22, 2024 at 12:25 PM Bernd B
I imported FDISK 1.3.14 to the FreeDOS package repository. Changes from last
imported version are:
Fixes:
- CRITICAL: Fix a drive letter disagree between DOS and FDISK in cases
involving multiple disks and a mix of active and non-active
primary partitions.
- HIGH: Prevent querying LBA c
On at 2024-01-04 17:46 +0100, Bernd Böckmann via Freedos-devel wrote:
Hi Eric,
I would assume the kernel parameter is neither meant to be queried
at runtime nor is it used by a significant number of people at all.
There is no external API, but you may pull it from RAM, possibly.
No, the CONFI
The thing I would do to speak against it is that because none of the other DOS
versions, including older versions of FreeDOS, will be able to use it. I do
know different versions of DOS do the ordering of the drive letters differently.
I think the best thing to do is try to automate it as much
On Thu, 4 Jan 2024 00:57:18 +0100
Bernd Böckmann via Freedos-devel wrote:
> Hi,
>
> while hunting a FDISK bug reported to me on Github regarding the order
> of the drive letters FDISK assigns, I noted that the FreeDOS Kernel
> actually supports different drive sorting algorithms via its
> DL
Hi Eric,
> I would assume the kernel parameter is neither meant to be queried
> at runtime nor is it used by a significant number of people at all.
> There is no external API, but you may pull it from RAM, possibly.
I would only read kernel RAM directly if the kernel tells me the address, for
ex
Hi Bernd,
I would assume the kernel parameter is neither meant to be queried
at runtime nor is it used by a significant number of people at all.
There is no external API, but you may pull it from RAM, possibly.
Alternatively, you could extract settings from the kernel file of the
boot drive or
Hi,
while hunting a FDISK bug reported to me on Github regarding the order
of the drive letters FDISK assigns, I noted that the FreeDOS Kernel
actually supports different drive sorting algorithms via its
DLASortByDriveNo config setting. While it is unrelated to the bug, this
may impose a pro
Hi,
On Mon, Jun 26, 2023 at 5:56 AM Bernd Böckmann via Freedos-devel
wrote:
>
> I released FDISK 1.3.7.
>
> I also pushed HTMLHELP 5.3.6 to the unstable branch at gitlab.
>
> It everything goes well both should be included in the next interim build.
Thank you for your work on these.
__
Hi,
I released FDISK 1.3.7. Apart from the re-introduced /AMBR command line
argument, there are no significant changes. The /AMBR argument is used by some
external tools, specifically the SvarDOS installer.
https://gitlab.com/FreeDOS/base/fdisk/-/tree/1.3.7/
I also pushed HTMLHELP 5.3.6 to the
> the kernel *should* work with sector sizes != 512 (as MSDOS
> reportedly does), but it simply doesn't. I Think PerditionC tried to
> make this work, and was successful for 256, 512, 1024 and 2048.
> unfortunately he didn't succeed for 4096 (I don't know the reason)
> so the FreeDOS kernel is stuc
> Am 15.03.2023 um 19:59 schrieb tom ehlert :
>
> I hope I could help.
Yes, thanks :-)
For now I leave it as it is with the exception of adding a check if sector size
is really 512 bytes. If not access is disabled on a per-disk basis. Better play
safe.
If FreeDOS anytime in the future is ca
Hi,
> while hacking on FDISK and having some thoughts about different
> sector sizes I stumbled upon the problem that the extended INT13
> function 48 may return a sector size != 512 while the INT13,0X
> functions always seem to operate on „virtual“ 512 sector sizes.
all INT13 functions operate (
I don't think that sector sizes other than 512 are supported for hard
drives. (Floppy drives are a different story.)
Things that used non-standard sector sizes had to supply their own
formatting routines and their own BIOS extensions. The original Bernoulli
box is a good example: it used 256 byt
Hi,
while hacking on FDISK and having some thoughts about different sector sizes I
stumbled upon the problem that the extended INT13 function 48 may return a
sector size != 512 while the INT13,0X functions always seem to operate on
„virtual“ 512 sector sizes.
Unsure how to handle this case I t
rge.net
Subject: Re: [Freedos-devel] FDISK issue
from Wilhelm Spiegl:
[-- Attachment #1 --]
[-- Type: text/html, Encoding: 7bit, Size: 8.2K --]
Content-Type: text/html; charset=UTF-8
Hallo Eric,
ich verstehe es einfach nicht: Erst erhalte ich unter Qemu und Virtualbox ständig diese Fehler bei
from Wilhelm Spiegl:
[-- Attachment #1 --]
[-- Type: text/html, Encoding: 7bit, Size: 8.2K --]
Content-Type: text/html; charset=UTF-8
Hallo Eric,
ich verstehe es einfach nicht: Erst erhalte ich unter Qemu und Virtualbox
ständig diese Fehler beim Ausführen von Format - und plötzlich
sind sie
[email protected]
Subject: Re: [Freedos-devel] FDISK issue
Sorry for disturbing once again.
The vhd formatted by Windows 10 (FAT) Nr. 2 does not give out an error message when booting without fdconfig / fdautoexec.bat.
Willi
Beer will follow now!
Sent: Sunday, July 11,
[email protected]
Subject: Re: [Freedos-devel] FDISK issue
Now it becomes absolutely confusing:
format d: /u says:
Full formatting (wiping all data)
Zapping / checking 443889 sectors and after a standard message
[Error 36]
I repeated with format d: /u /d:
FAT1x size: 217, using F
[email protected]
Subject: Re: [Freedos-devel] FDISK issue
Hi!
> Boot sector unreadable, disk not yet formatted.
You can skip that check by explicitly requesting a
not undoable formatting, see FORMAT /? and use /U
or better /Q /U for quick unconditional format.
> Cannot find existing
Hi Eric,
Just some info I left out…
My test was on Pentium Pro to reproduce the 230mb FDISK/FORMAT issue...
Kernel 2042, with FAT32
FreeCOM 0.84-pre2
FDISK 1.3.4
Format 0.91w
A bunch of drivers running…
JEMMEX
LBACACHE
UDVD2
SUSCDEX
DOSLFN
3COM Packet Driver
DHCP setup
no mouse driver at prese
Hi!
> Boot sector unreadable, disk not yet formatted.
You can skip that check by explicitly requesting a
not undoable formatting, see FORMAT /? and use /U
or better /Q /U for quick unconditional format.
> Cannot find existing format - Not saving UNFORMAT data. Please enter
> volume label (none)
hi,
> On Jul 10, 2021, at 4:03 PM, Wilhelm Spiegl wrote:
>
> one more problem with fdisk 1.3.4:
>
> I just tried to create a ca. 230 MB big partition on a second HD in
> virtualbox. I ran fdisk 1.3.4 from the first virtual HD (C:) and executed it
> for the second HD via
> fdisk position 5, c
, July 10, 2021 at 8:33 PM
From: "Jerome Shidel"
To: "FreeDOS Developers"
Subject: [Freedos-devel] FDISK issue
Hi all,
I’ve just noticed a minor issue/wierdness with FDISK.
It is not a serious problem. It is just something it does not do that the Microsoft version does do.
Hi all,
I’ve just noticed a minor issue/wierdness with FDISK.
It is not a serious problem. It is just something it does not do that the
Microsoft version does do. Mostly just a little interesting.
Some back story… Several years ago, I took my Pentium Pro motherboard out of
it’s original mass
Hi,I just wanted to give some feedback too.does anybody really worry about the bug tracker?a) bug 304, hi tom, fdisk supports 2 tb in size, it is no problem to create a 999 gb partition, but it is not possible to create a 1001 gb partition because too less digits for entering the value are sup
On 2/14/2021 6:55 AM, Eric Auer wrote:
Hi!
FDISK 1.3.2 would not find volume labels, if the partition doesn't
start on a cylinder boundary. fixed in www.drivesnapshot.de/freedos/fdisk133.zip
BUT: at least in my environment, the most recent FORMAT91W is not able
to format logical partitions, bu
Hi!
> FDISK 1.3.2 would not find volume labels, if the partition doesn't
> start on a cylinder boundary. fixed in
> www.drivesnapshot.de/freedos/fdisk133.zip
>
> BUT: at least in my environment, the most recent FORMAT91W is not able
> to format logical partitions, but aborts with error.
Accor
FDISK 1.3.2 would not find volume labels, if the partition doesn't
start on a cylinder boundary. fixed in www.drivesnapshot.de/freedos/fdisk133.zip
BUT: at least in my environment, the most recent FORMAT91W is not able
to format logical partitions, but aborts with error.
is that only me and my en
Hello everyone,
I am sorry if this is a known bug and if I could not find it in bugs list.
I have booted a VM in VirtualBox v5.0.4 with FD12CD.iso. I have booted to shell
to manually partition a 1G disk. I am using fdisk v1.2.1, without FAT32
support. You can reproduce the bug with following st
Hi, forwarding a feature request for FDISK from Fritz Mueller :-)
Could FDISK automatically trigger the /MBR action when you:
1. have the code area (offset 0 to 0x1BD) filled with identical
bytes (for example all 00)
2. update partitions
3. after the update, there is an active (boot) partitio
For clarification, it crashes on startup or immediately returns to command
prompt, or doesn't do something? What kernel and freecom versions? Have
you tried without any memory managers?
Thanks for the answers. I will see if I can duplicate (and hopefully track
down the issue).
Jeremy
-
Hi,
FDISK 1.3.1 won’t run in the following VMs for me at least
* VirtualBox 5.1.8-11374
* VMWare Fusion 7.0.0
I did get it to run under Parallels 11.0.
This leaves me confused as to what is going on here.
Brian is busy, I guess, so I haven’t talked with him in a while. If someo
Hi,
There hasn’t been an update to FDISK yet that I have released because I am
working with Brian to get CATS into 1.3.1.
You can still use what is presently on iBiblio. I will send out something once
the update is done.
-Tony
> On Feb 5, 2016, at 10:06 AM, Paul Dufresne wrote:
>
> I am a b
Hi,
On Fri, Feb 5, 2016 at 9:06 AM, Paul Dufresne wrote:
>
> I am a bit confused as to what is/should be the current version.
Although I'm fairly certain that the Software List is still
"read-only" for the time being, the latest it mentions is 1.3.1 :
http://freedos.sourceforge.net/software/?pr
Hello Paul,
> On Feb 5, 2016, at 10:06 AM, Paul Dufresne wrote:
>
> I am a bit confused as to what is/should be the current version.
>
> Antony Gordon said he made modifications to v. 1.2.1 and 1.3 but I
> don't know if the changes have been published and if so where.
>
> Then there is (same c
I am a bit confused as to what is/should be the current version.
Antony Gordon said he made modifications to v. 1.2.1 and 1.3 but I
don't know if the changes have been published and if so where.
Then there is (same code, two different categories):
http://www.ibiblio.org/pub/micro/pc-stuff/freedos
Hi,
On Mon, Jan 11, 2016 at 10:59 AM, Antony Gordon wrote:
>
> I updated FDISK 1.2.1 and made some changes so that it would compile. I also
> managed to get in contact with Brian and he's helping me resolve the issues
> with the 1.3 code base that I'm having with compiling it.
>
> Hopefully soon
Sounds awesome, thank you!
Mateusz
On 11/01/2016 17:59, Antony Gordon wrote:
> Hi,
>
> I updated FDISK 1.2.1 and made some changes so that it would compile. I
> also managed to get in contact with Brian and he's helping me resolve
> the issues with the 1.3 code base that I'm having with compili
Hi,
I updated FDISK 1.2.1 and made some changes so that it would compile. I
also managed to get in contact with Brian and he's helping me resolve the
issues with the 1.3 code base that I'm having with compiling it.
Hopefully soon I will have something together and I can start on the rest
of CAT i
Hi,
I haven’t quite figured out whats wrong with the 1.3 branch of FDISK, but I did
manage to get 1.2.1 to compile. I had to do some minor code tweaks to fix some
errors.
I also fixed the makefile so it works better with Borland/Turbo C. As I use
GitHub, I haven’t as of yet updated my reposito
(I'm replying to this discussion a bit late .. I just changed jobs and
I'm having a hard time staying on top of personal email.)
On Wed, Dec 23, 2015 at 5:40 AM, Paul Dufresne wrote:
[..stuff about catgets and gettext..]
> Now, Jim Hall have made a library, catgets, to use the first method.
> He
Hi,
'default' is a keyword. I am also reworking the makefile so that hopefully
it will rebuild outside of the environment, then I'll work on OW
compatibility and maybe even Pacific C as well.
On Mon, Jan 4, 2016 at 7:01 PM Rugxulo wrote:
> Hi,
>
> On Mon, Jan 4, 2016 at 9:54 AM, Antony Gordon
Hi,
On Mon, Jan 4, 2016 at 9:54 AM, Antony Gordon wrote:
>
> I’m attempting to recompile FDISK and apparently you need to assemble
> bootnorm.asm
> and booteasy.asm and I’m getting this error when assembling booteasy.asm
>
> booteasy.asm:260: error: invalid parameter to [default] directive
> Th
You'll likely need MASM or TASM to assemble. WASM/JWASM may work in
compatibility mode.
On Mon, Jan 4, 2016 at 1:09 PM, Antony Gordon wrote:
> Hi,
>
> I’m using NASM. It seems to work well with all the other labels.
>
> In my digging, I have found that default may be a keyword. I’ll try that
>
> On Jan 4, 2016, at 4:09 PM, Antony Gordon wrote:
>
> Hi,
>
> I’m using NASM. It seems to work well with all the other labels.
>
> In my digging, I have found that default may be a keyword. I’ll try that too
> just to be sure.
I think you are correct that it is a keyword. (I’ve never used
Hi,
I’m using NASM. It seems to work well with all the other labels.
In my digging, I have found that default may be a keyword. I’ll try that too
just to be sure.
-T
> On Jan 4, 2016, at 4:07 PM, Jerome E. Shidel Jr. wrote:
>
>
>> On Jan 4, 2016, at 10:54 AM, Antony Gordon wrote:
>>
>> Hi
> On Jan 4, 2016, at 10:54 AM, Antony Gordon wrote:
>
> Hi,
>
> I’m attempting to recompile FDISK and apparently you need to assemble
> bootnorm.asm and booteasy.asm and I’m getting this error when assembling
> booteasy.asm
>
> booteasy.asm:260: error: invalid parameter to [default] directiv
Hi,
I’m attempting to recompile FDISK and apparently you need to assemble
bootnorm.asm and booteasy.asm and I’m getting this error when assembling
booteasy.asm
booteasy.asm:260: error: invalid parameter to [default] directive
This is line 260 below.
default db '?',' '+80h
Any th
arten
-Oorspronkelijk bericht-
Van: "Maarten Vermeulen"
Verzonden: 28-12-2015 21:53
Aan: "Technical discussion and questions for FreeDOS developers."
Onderwerp: RE: [Freedos-devel] fdisk translation
I think you just need to do that, then we look if it is good to use i
I think you just need to do that, then we look if it is good to use it etc. I
think (and hope). :)
Maarten
-Oorspronkelijk bericht-
Van: "Antony Gordon"
Verzonden: 28-12-2015 17:18
Aan: "Technical discussion and questions for FreeDOS developers."
Onderwerp
Hi,
Since I still have the Borland Compilers in my VMs, I can take over FDISK
if needed. I can try to re-work it to work with OW. Let me know a time
frame for completion so if I take it, I don't drag the project out.
-T
On Wed, Dec 23, 2015 at 8:26 PM Paul Dufresne wrote:
> I have encountered
I have encountered a little bit similar problem that is not really
one, but looks like one.
That was with testing the new installer floppy image, with a freshly
created disk of 100Mb, and all_cd.iso under QEMU.
After fdisk had created the partition, the virtual system reboot.
After reboot, the sys
Hi,
On Wed, Dec 23, 2015 at 6:09 AM, Mateusz Viste wrote:
>
> An additional note: v1.3.1 is buggy on VirtualBox, which might be a
> symptom of a more serious problem, while v1.2.1 is working fine on both
> real hardware and vbox.
Have you reported a bug to them (VBox) or tried latest 5.x series?
I now see: https://sourceforge.net/p/freedos/bugs/65/ although I am
unaware of a 1,3.2 version.
But I will not look any further on this for next 10 hours.
--
___
Freedos-devel ma
On 23/12/2015 12:40, Paul Dufresne wrote:
> Now the fun part about fdisk, is that it contains the catgets.zip
> library created by Jim Hall, which contains his HOWTO doc file about
> translatings. But the fdisk source does not appears to me (at first
> glance) to use it... yet.
I actually looked i
I am in the learning about translating programs.
I was aware of that page:
https://ftp.gnu.org/old-gnu/Manuals/glibc-2.2.3/html_chapter/libc_8.html
Basicaly, there is two different methods (and set of C functions) to
translate a string.
The first method is:
char * catgets (nl_catd catalog_desc, in
> On Dec 22, 2015, at 11:51 AM, Paul Dufresne wrote:
>
> When testing the installer, it was not feeling right to go from the
> french installer to the english fdisk... how could fdisk be
> translated?
Just a note, when FDI launches, if the LANG variable is set it uses that
setting. If it is not
Thanks for the info. As someone who never delved that deeply into the
technicalities of the program, I think that's pretty awesome!
On 12/22/2015 4:30 PM, Eric Auer wrote:
> Hi!
>
> We already have command line control for at least one of the fdisk
> variants which usually ship with FreeDOS, but
That sucks, especially considering his FDisk is a valuable tool at the
heart of many, many FreeDOS installs. It's a shame that those with that
attitude penalize the entire FreeDOS project by turning away benevolent
developers with years of skill and experience behind them who happen to
have som
Yeah, I have no idea why I just *assumed* the source code was
unavailable. I guess out of my own experience with software which is no
longer under active development and has long lost sources. I suppose I
was forward-projecting that on this situation as well.
Oops. lol
On 12/22/2015 3:57 PM, R
Hi!
We already have command line control for at least one of the fdisk
variants which usually ship with FreeDOS, but using that to let the
installer auto-kill all the data of the user gives me nightmares.
You can simply use FDISK /? (who would have guessed it) to get a
list of the command line c
On 12/22/2015 9:59 AM, Rugxulo wrote:
> Hi,
>
> On Tue, Dec 22, 2015 at 11:05 AM, Mercury Thirteen
> wrote:
>> If it's still maintained, we can ask the developer to do it.
> I don't think it is. I haven't seen or heard from that guy (Brian
> Reifsnyder) in a few years. Somebody could send him a qu
On 12/22/2015 9:05 AM, Mercury Thirteen wrote:
> If it's still maintained, we can ask the developer to do it. If it's
> not... well, Idk the legitimacy of us poking around inside the binary
> and editing the text strings manually.
>
Excuse me? =-O
That's why FreeDOS is supposed to be Open Source,
Hi again,
On Tue, Dec 22, 2015 at 11:59 AM, Rugxulo wrote:
>
> On Tue, Dec 22, 2015 at 11:05 AM, Mercury Thirteen
> wrote:
>>
>> The best option would be to make it controllable from the command line
>> a'la *nix ("never assume humans will be the sole users of your program")
>> so that the user
Hi,
On Tue, Dec 22, 2015 at 11:05 AM, Mercury Thirteen
wrote:
>
> If it's still maintained, we can ask the developer to do it.
I don't think it is. I haven't seen or heard from that guy (Brian
Reifsnyder) in a few years. Somebody could send him a quick message,
but I don't think it's crucial eno
If it's still maintained, we can ask the developer to do it. If it's
not... well, Idk the legitimacy of us poking around inside the binary
and editing the text strings manually.
The best option would be to make it controllable from the command line
a'la *nix ("never assume humans will be the so
When testing the installer, it was not feeling right to go from the
french installer to the english fdisk... how could fdisk be
translated?
--
___
Freedos-devel mailing list
Free
Hi!
27-Июл-2006 17:42 [EMAIL PROTECTED] (Imre Leber) wrote to
[email protected]:
IL> Seems that fdisk doesn't allow you to change between FAT16 and FAT32.
IL> When you choose FAT32 support on an 800MB image, it will create a FAT32
IL> partition automatically.
IL> Maybe there sho
I was just installing freedos.
Seems that fdisk doesn't allow you to change between FAT16 and FAT32.
When you choose FAT32 support on an 800MB image, it will create a FAT32
partition automatically.
Maybe there should be a message indicating this?
Imre
PS. it stops halfway the installation, b
Hi,
Jeremy's site up again, and I got the latest FDISK. However, I try to
partition a 40GB hard disk and got this:
Error 0 reading sector 0x3f
I try to use the old one FDISK 1.2.1, it works.
Rgds,
Johnson.
---
SF.Net email is sponsored by:
83 matches
Mail list logo
