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 FDISK 1.2.1 and 1.3.0-beta, not my "creation".
Notice that the BETA is compiled with debug mode on (you can put a
WRITE OFF line in the ini file) and with beta mode on (?).
I didn't mean to miscredit anyone, it's just I never saw a 1.3.0-beta
version and you supplied me with an overview/diff of the differences.
...
- All disk writes are delayed until just before a normal program exit;
so on any errors (*) no changes are written; also no changes will be
made if you select abort from advanced menu, or if you reboot instead of
exiting fdisk. *any errors writing to disk during the end phase are
still ignored*...
Not good - rebooting is meant to be "write changes and reboot", because
FDISK assumes that the reboot makes sure that DOS reads the new partitions.
I think you misunderstand, I don't mean if you exit normally and fdisk
reboots your computer for you (or prompts you indicating you should do
so). I mean if instead of pressing Esc to exit at the main menu to end
fdisk, you reboot your computer (ie never quitting fdisk, just
restarting the computer), then no changes will be written, as the
writing is delayed until the exit. Ahh good catch, there is a bug where
I don't flush them because of the reboot is called and the user
interaction routine never returns. I'll fix that tommorrow or Wed.
- To avoid changes but still see the partition table, use fdisk /info
(it doesn't seem to have the forced MBR update).
Do not use "seem" here - you can ZAP that entire "create MBR if MBR read
error" function completely. Whoever REALLY has an empty MBR should use
FDISK /MBR manually, which is much safer. If you are not sure whether
FDISK would crash when the MBR is empty, make it exit with an error
message (suggesting to use FDISK /MBR) when an empty MBR is detected. How-
ever, FDISK seems (oops) to already have code which avoids reading the
partition data from a broken MBR.
... it comes back with 4MB free
and if you press enter (such as to create a 2nd logical partition of 4MB
or by accident) it will screw up the partition table horribly.
Can you explain "screw up horribly" somewhat more?
well it displays some error message about extended starting cylinder not
matching something and ends up with a partition table consisting of 4
non-dos partitions each 4MB in size.
Eric
Jeremy
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
