Extended/logical partition goes missing in dos
xp...@my-dejanews.com
I have a Deskstar 8 (8.4GB) as master and Deskstar 3 (3.2GB) as slave.
I have created one 2GB primary patition (C:) and three 2GB logical partitions
(E: F: and unformatted) on the first HD.
If I create a 2GB primary partition (D:) and 1GB logical partition (drive G:)
on the 2nd HD, I can see drive G: in fdisk, Partition Magic and Win95.
But I don't see the drive G: in DOS!
I have already looked at the ATA/IDE FAQ and tried using fdisk /x. Apparently
using Partition Magic(another solution) doesn't work as well. I even got
unknown error #727 in PM after using fdisk.
I originally wanted to place only logical partitions on the 2nd drive so as
not to mess up the drive order. But dos is unable to see any extended/logical
partitions on the 2nd HD. (but fdisk can see it!)
Any other suggestions? I will installing WindowsNT soon. Will WindowsNT be
able see the drive G: ? I prefer not to use FAT32 since I'm using NT.
Thanks for any info.
-----== Posted via Deja News, The Leader in Internet Discussion ==-----
http://www.dejanews.com/ Now offering spam-free web-based newsreading
Keith R. Williams
On Mon, 25 May 1998 07:18:33, xp...@my-dejanews.com wrote:
> I have a Deskstar 8 (8.4GB) as master and Deskstar 3 (3.2GB) as slave.
> I have created one 2GB primary patition (C:) and three 2GB logical partitions
> (E: F: and unformatted) on the first HD.
I have the same setup, but backwards. My DS8 is the slave.
> If I create a 2GB primary partition (D:) and 1GB logical partition (drive G:)
> on the 2nd HD, I can see drive G: in fdisk, Partition Magic and Win95.
> But I don't see the drive G: in DOS!
Don't put any primaries on the second drive. IThere is no
advantage to doing it and it may cause problems later.
What does the LASTDRIVE= say in config.sys? You should have a
LASTDRIVE=Z (or some such high letter) in the config.sys. Also
look for a fixed CDROM drive letter interferring with the new
drives.
> I have already looked at the ATA/IDE FAQ and tried using fdisk /x. Apparently
> using Partition Magic(another solution) doesn't work as well. I even got
> unknown error #727 in PM after using fdisk.
>
> I originally wanted to place only logical partitions on the 2nd drive so as
> not to mess up the drive order. But dos is unable to see any extended/logical
> partitions on the 2nd HD. (but fdisk can see it!)
I do it all the time. I don't use DOS much anymore but never had
this problem. What DOS version?
> Any other suggestions? I will installing WindowsNT soon. Will WindowsNT be
> able see the drive G: ? I prefer not to use FAT32 since I'm using NT.
Sure. I have drives out to K: on this system and O: or P: on one
systems at work. Your problem has something to do with the way
your DOS is set up.
----
Keith R. Williams
k...@ibm.net
Robert Nichols
In article <6kb609$km$1...@nnrp1.dejanews.com>, <xp...@my-dejanews.com> wrote:
:
:If I create a 2GB primary partition (D:) and 1GB logical partition (drive G:)
:on the 2nd HD, I can see drive G: in fdisk, Partition Magic and Win95.
:But I don't see the drive G: in DOS!
Sounds like you used Windows 95 to create the extended partition. In
the interest of incompatibility, Win95 uses a different type code (0x0f
instead of 0x05) when it makes an extended partition. DOS won't look
inside of what it sees as an unknown partition type. Simplest solution:
create the extended partition and logical drive with DOS.
--
Bob Nichols rnic...@interaccess.com
Finger rnic...@cluster.interaccess.com for PGP public key.
PGP public key 1024/9A9C7955
Key fingerprint = 2F E5 82 F8 5D 06 A2 59 20 65 44 68 87 EC A7 D7
xp...@my-dejanews.com
>
> I have the same setup, but backwards. My DS8 is the slave.
>
> > If I create a 2GB primary partition (D:) and 1GB logical partition (drive
G:)
> > on the 2nd HD, I can see drive G: in fdisk, Partition Magic and Win95.
> > But I don't see the drive G: in DOS!
>
> Don't put any primaries on the second drive. IThere is no
> advantage to doing it and it may cause problems later.
I have a reason why I need the primary on DS3. I have a CD writer and I may
ocassionally remove the DS3 and replace it with another HD so as to back-up
the data into the the CD-writer. Just in case the temporary HD has a primary
partition, this will not mess up the drive letters.
Do you think this is a bad idea?
>
> What does the LASTDRIVE= say in config.sys? You should have a
> LASTDRIVE=Z (or some such high letter) in the config.sys. Also
> look for a fixed CDROM drive letter interferring with the new
> drives.
Oops, I don't have the LASTDRIVE in config.sys. My config.sys is very bare.
Hopefully, this well help.
I did not load any CD-ROM drivers in DOS, so this should not be the problem.
Instead I assigned manually the CD-ROM drives letters to I: and W: in
Windows95.
>
> > I have already looked at the ATA/IDE FAQ and tried using fdisk /x.
Apparently
> > using Partition Magic(another solution) doesn't work as well. I even got
> > unknown error #727 in PM after using fdisk.
> >
> > I originally wanted to place only logical partitions on the 2nd drive so
as
> > not to mess up the drive order. But dos is unable to see any
extended/logical
> > partitions on the 2nd HD. (but fdisk can see it!)
>
> I do it all the time. I don't use DOS much anymore but never had
> this problem. What DOS version?
DOS 7.0, comes with OSR2.
xp...@my-dejanews.com
> Sounds like you used Windows 95 to create the extended partition. In
> the interest of incompatibility, Win95 uses a different type code (0x0f
> instead of 0x05) when it makes an extended partition. DOS won't look
> inside of what it sees as an unknown partition type. Simplest solution:
> create the extended partition and logical drive with DOS.
I'm using Partition Magic to create the partitions.
I've already tried DOS fdisk that comes with OSR2 - but still no go.The
problem when using fdisk is that PM cannot handle them. I get error #727.
Windows95 itself can't create partitions, right?
xp...@my-dejanews.com
>
> >
> > What does the LASTDRIVE= say in config.sys? You should have a
> > LASTDRIVE=Z (or some such high letter) in the config.sys. Also
> > look for a fixed CDROM drive letter interferring with the new
> > drives.
>
> Oops, I don't have the LASTDRIVE in config.sys. My config.sys is very bare.
> Hopefully, this well help.
>
Seems that LASTDRIVE doesn't help :(
Keith R. Williams
On Tue, 26 May 1998 03:11:32, xp...@my-dejanews.com wrote:
> I have a reason why I need the primary on DS3. I have a CD writer and I may
> ocassionally remove the DS3 and replace it with another HD so as to back-up
> the data into the the CD-writer. Just in case the temporary HD has a primary
> partition, this will not mess up the drive letters.
>
> Do you think this is a bad idea?
Wait, your DS3 is on drive 2, no (*mine's* on drive 1 ;-)? I
don't see where this makes a difference. Move the CDROM and CD-R
up to, say R and W? Leave the hard drives fight out the low
numbers. Maybe I don't understand your situation.
> > What does the LASTDRIVE= say in config.sys? You should have a
> > LASTDRIVE=Z (or some such high letter) in the config.sys. Also
> > look for a fixed CDROM drive letter interferring with the new
> > drives.
>
> Oops, I don't have the LASTDRIVE in config.sys. My config.sys is very bare.
> Hopefully, this well help.
>
> I did not load any CD-ROM drivers in DOS, so this should not be the problem.
> Instead I assigned manually the CD-ROM drives letters to I: and W: in
> Windows95.
This isn't going to help DOS a bit. You need to load the drivers
for DOS as well.
> > I do it all the time. I don't use DOS much anymore but never had
> > this problem. What DOS version?
>
> DOS 7.0, comes with OSR2.
Well, that's sorta DOS. ;-)