Good day, all:
The person who did this is very knowledgeable and believes that
FDISK did, in fact, trash the partition table. I had this exact
thing happen to me when running fdisk. FDISK displayed a bunch
of garbage in response to a display partitions option and then
the partition table was destroyed. This was some time ago.
Since the computer was acting up before I did that, I cannot
say for sure that FDISK caused the problem.
I am going to run FDISK again on that laptop (an HP Pavillion)
AFTER I back up the partition table! I will do that this evening
and see if I can reproduce a problem.
This was running FDISK WITHOUT an fdisk.ini file. Any ideas?
Is there a safer DOS tool that just shows the partition table?
I know the Linux ones, but not the DOS ones.
Mark
[EMAIL PROTECTED] wrote:
Hi Kenneth:
No, I am not sure, of course. I had something similar happen to
me once as well. Fortunately, gpart fixed that one...but it did
happen after I ran FDISK.
I don't believe he HAD a problem except that NTFS4DOS didn't
recognize the XP partition.
Are there any FreeDOS tools that just DISPLAY the partition
information? How about save and restore it?
I know some of the Linux tools, but not DOS.
Thanks!
Mark
[EMAIL PROTECTED] wrote:
Hello, all:
I just suggested that someone who was having trouble with
NTFS4DOS not recognizing an NTFS partition run fdisk with the
development kernel.
I requested that he enable large disk support and use option
[4], "List Partition Information."
This appears to have removed the partition information from the
MBR.
Are you sure fdisk did this and that wasn't his problem to begin with?
or something else related to his problem caused the error?
Anyone have any ideas about this? Is FDISK so dangerous that
even using it to examine partition tables is a bad idea?
Thanks.
Mark Bailey
I haven't looked at fdisk's code in a while, but from my usage, I have
never seen it alter the MBR/partition table without issuing a command
that involves such a change (ie option 4 never made any changes). And a
brief reexamination of the code seems to confirm this (it has checks for
changes so only writes if a change has occurred).
Brian could tell you for sure (or anyone who wants to read the sources),
but I feel pretty confident in saying that using (Free)Fdisk to examine
the partition tables should not cause any harm -- but not a method I'd
recommend (users can do some funny things), so a tool designed just to
display the partition tables would be better.
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
