On Sun, 31 Jul 2005 17:40:56 +0100, you wrote:
Hi Gerry,
>> GUI (the current version should be UI)
>Sorry, UI
Never mind.
>Yes, I'm not against the UI, I'm just saying I've never needed it and
>(in my opinion) it's actually less confusing to use commands only.
Because you're not novice :-)
>
Hi Johnson,
GUI (the current version should be UI)
Sorry, UI
is for the beginners and
operators, I don't mind using UI or GUI since FDISK is not a TSR, size
is not a problem. And easier navigation only made the program more
user friendly, you can keep using command line.
Yes, I'm not again
On Sun, 31 Jul 2005 11:47:48 +0100, you wrote:
Hi Gerry,
>Well so far I really like FDISK, it's small and fast and appears to do
>everything it's supposed to.
I like FDISK also, almost identical interface as MS and have enhanced
functionality.
>I've never needed to use the GUI.
GUI (the curre
Hi,
2) Vote here, keep Free DISK or switch to XFDISK
Well so far I really like FDISK, it's small and fast and appears to do
everything it's supposed to.
I've never needed to use the GUI.
I have not been hit by the MBR bug, despite testing on a wide range of
systems with both SCSI and IDE
On Sun, 31 Jul 2005 05:57:13 +0200, you wrote:
Hi Aitor,
>> The correct procedure should be:
>>
>> 1) Contact Brian and ask him if he still works on Free FDISK or not
>(or someone else if Brian can't)
>> 2) Vote here, keep Free DISK or switch to XFDISK
>> 3) Someone have to examine XFDISK's sou
Hi,
Johnson Lam escribió:
On Sat, 23 Jul 2005 03:17:48 +0200 (MEST), you wrote:
Hi,
XFDISK? I mean, XFDISK is open source. It only does not LOOK like
the old MS DOS user interface, but hey, that was crap anyway...
The correct procedure should be:
1) Contact Brian and ask him if he still
Eric Auer wrote:
Hi Jeremy, thanks for the updates but...
- Changes from 1.2.1 version (see fdisk.diff at same location):
From Eric, it has some changes to carry usage in extended int13 detection.
No, I just sent you a minimized (i.e. excluding changes in whitespace
and comments) between F
Hi Jeremy, thanks for the updates but...
> - Changes from 1.2.1 version (see fdisk.diff at same location):
> From Eric, it has some changes to carry usage in extended int13 detection.
No, I just sent you a minimized (i.e. excluding changes in whitespace
and comments) between FDISK 1.2.1 and 1.3
Hi, I think you will be safe as you apply FDISK to NEW harddisks:
The problem is "only" that if you get a read error while reading
the existing partition scheme, our FDISK has the stupid strategy
to write a new empty partition table as "automatic solution".
Your new PCs should not show read errors
On Sat, 23 Jul 2005 03:17:48 +0200 (MEST), you wrote:
Hi,
>XFDISK? I mean, XFDISK is open source. It only does not LOOK like
>the old MS DOS user interface, but hey, that was crap anyway...
The correct procedure should be:
1) Contact Brian and ask him if he still works on Free FDISK or not
2) V
Hi, while it would be easy to remove the "write new empty partition
table if reading the partition table failed" nonsense from FDISK,
would it be against the FreeDOS SPECS to just replace it by, say,
XFDISK? I mean, XFDISK is open source. It only does not LOOK like
the old MS DOS user interface, b
11 matches
Mail list logo
