delorie.com/archives/browse.cgi   search  
Mail Archives: opendos/2001/03/04/20:31:17

Message-ID: <01FD6EC775C6D4119CDF0090273F74A4021FB5@emwatent02.meters.com.au>
From: "da Silva, Joe" <Joe DOT daSilva AT emailmetering DOT com>
To: "'opendos AT delorie DOT com'" <opendos AT delorie DOT com>
Subject: RE: Hard drive question
Date: Mon, 5 Mar 2001 12:31:04 +1100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Reply-To: opendos AT delorie DOT com

Be more cautious.

First, check with FDISK to just display partition info for the drive - this
will tell you if the drive is accessible, and perhaps give some more clues.

Is the 586 MB old? Does it handle "> 1024 cylinders" OK? Did the
486 have Disk Manager or equivalent, to provide an "Int 13 upgrade"?
(just some ideas ...)

Joe.

> -----Original Message-----
> From:	Mark at Cross+Road's [SMTP:mark1 AT mich DOT com]
> Sent:	Monday, 5 March 2001 6:59
> To:	opendos AT delorie DOT com
> Cc:	editor AT juno DOT com
> Subject:	Re: Hard drive question
> 
> 
> Nope, the drive does not give a letter or in other words I haven't
> increased
> my partitions by any.  It's a Compaq and upon booting I know the computer
> saw the new drive because it required me to acknowledge the changes with a
> f1 before going on to boot.  I did set the drive 2 to slave according to
> the
> pins and left drive 1 as master.  I don't recall if there's any other
> setting on the 1st drive.
>     Either it's something very simple that I am missing here or there's a
> compatibility problem which isn't allowing the drive to be seen?
>     I'm not all that aware about the master boot records but in this case
> would that need to be rewritten in order for both drives to be used?
>     How is that done in Drdos 703?  Does it destroy data when rewriting a
> mbr?
>      Thanks,
>       Mark
> 
> 
> 
> On 2001-03-03 opendos AT delorie DOT com said:
>    >On Sat, 03 Mar 2001 15:30:13 +500 "Mark at Cross+Road's"
>    ><mark1 AT mich DOT com> writes:
>    >> Hello All,
>    >>     I've got Drdos 7.03 installed on a 486 and a 586 both on drive
>    >> C.
>    >>     I have a drive D on the 486 on which there are many back-up
>    >> files and I
>    >> desire to take this drive D and make it a D drive on the 586.
>    >>     It's a slave on the 486 and I have moved it to the 586 also as
>    >> slave.
>    >>     Its not being seen or not being understood by the 586.  The
>    >>bios  has
>    >> accepted the install of a 2nd drive without a problem but I cannot
>    >> use the
>    >> drive it's not being accepted to read and write. I can bring it
>    >>back  to the
>    >> 486 and it works fine there.
>    >>     How do I get those files to be seen on the 586 without having
>    >> to
>    >> reformat the entire drive on the new machine?
>    >>         Thanks,
>    >>       Mark
>    >When you type "d:<Enter>) at
>    >the DR-DOS prompt, does the
>    >drive letter in the prompt
>    >change, and if so, can you
>    >execute a DIR command and see
>    >filenames listed?  Is the D:
>    >drive acessible if you boot
>    >from a DR-DOS floppy or, for
>    >that matter, an MS-DOS or
>    >Win9x boot floppy?
>    >What I suspect is that the
>    >C: drive in the 586 is one of
>    >those that has a different
>    >jumper setting for "single-
>    >drive" and "master with slave
>    >present."
>    >________________________________________________________________
>    >GET INTERNET ACCESS FROM JUNO!
>    >Juno offers FREE or PREMIUM Internet access for less!
>    >Join Juno today!  For your FREE software, visit:
>    >http://dl.www.juno.com/get/tagj.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019