drbob
12-14-2011, 07:40 PM
The problem:
On a new disk, I create 2 logical partitions (one 1GB, one 100MB) in ms-dos 6.22 with fdisk - works fine from within dos but the 1GB partiton will not mount in windows 7. If I create the partitions within windows they mount fine in windows but are not visible in DOS. fdisk can see the extended partition but not the logical partitions within it.
I've managed to work around the issue by creating 3 primary partitions but would love to know if anyone here knows why/what may have caused this issue. In the dim mists of my memory I seem to remember reading an article that mentioned the dos fdisk being quirky but my google fu hasn't thrown up any examples of this exact issue.
Background:
A close family member has been nursing a DOS app that is key to his business since the maker stopped supporting it (amazingly this was only in 2007).
I've been going in regularly and taking disk image back-ups from the ancient 486 server as I did not trust the zip disk based backup solution provided by the manufacturer (restore instructions - call us to talk you through it at $$$ per incident)
Yes, I've been trying to convince him to upgrade but the sofware company wants a lot of money (think 5 figures) to license the shiny windows version and for migration from DOS to a modern system. The old software still currently meets his modest needs.
Recently the 1.2GB WD caviar drive in the server started to fail so I was tasked with replacing it (with an 80GB WD caviar blue, clipped via jumper settings to 2GB) which led to the partitioning problems described above.
I've tried creating the partitions manually in windows using Paragon Partiton Manager, I've also seen the problem when restoring the disk image using Macrium reflect (annoyingly it doesn't seem to do a true full disk image, I think it recreates the partitions using windows calls before restoring into them rather than a true sector by sector restore of the entire disk including partition table)
On a new disk, I create 2 logical partitions (one 1GB, one 100MB) in ms-dos 6.22 with fdisk - works fine from within dos but the 1GB partiton will not mount in windows 7. If I create the partitions within windows they mount fine in windows but are not visible in DOS. fdisk can see the extended partition but not the logical partitions within it.
I've managed to work around the issue by creating 3 primary partitions but would love to know if anyone here knows why/what may have caused this issue. In the dim mists of my memory I seem to remember reading an article that mentioned the dos fdisk being quirky but my google fu hasn't thrown up any examples of this exact issue.
Background:
A close family member has been nursing a DOS app that is key to his business since the maker stopped supporting it (amazingly this was only in 2007).
I've been going in regularly and taking disk image back-ups from the ancient 486 server as I did not trust the zip disk based backup solution provided by the manufacturer (restore instructions - call us to talk you through it at $$$ per incident)
Yes, I've been trying to convince him to upgrade but the sofware company wants a lot of money (think 5 figures) to license the shiny windows version and for migration from DOS to a modern system. The old software still currently meets his modest needs.
Recently the 1.2GB WD caviar drive in the server started to fail so I was tasked with replacing it (with an 80GB WD caviar blue, clipped via jumper settings to 2GB) which led to the partitioning problems described above.
I've tried creating the partitions manually in windows using Paragon Partiton Manager, I've also seen the problem when restoring the disk image using Macrium reflect (annoyingly it doesn't seem to do a true full disk image, I think it recreates the partitions using windows calls before restoring into them rather than a true sector by sector restore of the entire disk including partition table)