Xref: utzoo comp.sys.ibm.pc:51373 comp.sys.zenith:312 Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!uunet!zephyr.ens.tek.com!tektronix!sequent!upba!dsndata!unocss!cs002 From: cs002@unocss.unomaha.edu (cs002) Newsgroups: comp.sys.ibm.pc,comp.sys.zenith Subject: Re: Two Drives under Zenith 3.3+ Summary: Yes, indeed, that's what it does! Message-ID: <2975@unocss.unomaha.edu> Date: 26 May 90 16:45:51 GMT References: <1990May25.090543.22345@sun.soe.clarkson.edu> Distribution: usa Organization: U. of Nebraska at Omaha Lines: 31 In article <1990May25.090543.22345@sun.soe.clarkson.edu>, wargopl@sun.soe.clarkson.edu (Peter L. Wargo) writes: > > Here's something that I find interesting. Until recently, I had just (just, > he sez...) an 80M full-height in my Zenith Z-248. Today I got my hands on > a Seagate ST251-1 ... > When I got all done plugging in the hardware, I found out the following > happened with the auto-partitioning under Zenith's 3.3+: > Partition Physical Drive > C: 0 > D: 1 > E: 0 > F: 0 > G: 1 > Strange, I woulda thought all of physical drive 0, then all of 1, but no > go... Yes, indeed, that's exactly what happens (as you might guess, exactly the same thing happened to me). I have a Zenith 386 box which came with a 72M drive and as I was using both DOS and MINIX, and had both filesystems in different partitions, I needed more space, so I added a 80M drive as drive 1. Well let me tell you I was surprised when my MINIX filesystems showed up in strange places! I tried very hard to make things look like what I wanted (essentially what you wnated, too - C: D: and E: on drive 0 then F: and G: on drive 1), but nothing worked. Good old ASGNPART doesn't exist in 3.3+, so there's nothing to be done but live with it. It surely would have been nice for Zenith (or Microsoft?) to include some very visible mention of this behavior in the documentation ... Stan Wileman Math/CS Dept., U. of Nebraska at Omaha, Omaha, NE 68106