Can't Boot from New Maxtor Drive
Will
drive today. I have installed Western Digital drives before
and have had no problem. Today however, I installed the
Maxtor with a Promise Ultra 66 Board. During the install
process, the Maxtor software asked if I wanted to copy the
old drive on to the new one. I answered yes, since the
I wanted to copy the old 1.6GB WD drive onto the new
drive and then take it the old drive out. Everything went
fine but nowhere did I have the option to set the new drive
as active or bootable (as I recall the WD allows) . Now
when I removed the old drive, the systems gets past the
memory test and just stops. If I connect the old drive the
system boots fine off of it and I can see the new drive in
Windows 95B. When I use a W95 boot disk with Fdisk
on it to try to set the new drive as bootable, it only sees
the old drive, which is connected to the motherboard IDE
port. What am I missing? How do I set the new drive
as bootable so I can shut down, unplug the old drive and
have the new one boot up?
antag
drive to master?
Bill
running the old drive off the the motherboard IDE port
and the the new drive off the Promise Ultra 66 card.
Since they aren't on the same channels I didn't have
to mess with master/slave.
Bill
I noticed that when I boot off the old drive, the very next thing
that appears on the screen after the memory test is the
detection of the old drive on the motherboard IDE port. AFTER
that the Promise Ultra 66 board is detected. Shouldn't the
Promise board be detected before anything? When I boot up,
the very first thing that appears is detection of my Matrox
video card bios.
My motherboard setup program allows me to set up which
device boots the computer. It is set to boot of A:/ then if that
fails (no floppy installed), then C:/ then the CD Rom drive.
The weird thing is that the computer will not boot from the
floppy unless the old hard drive is installed. Again, the
boot up screen shows detection of the old drive, the Promise
board, and then checks the floppy drive, which fails so the
boot up continues from the C: drive. Should I disable the
old drive on my motherboard bios and see if the Promise
board takes it's place?
Jimmy
mb boot drive. Try changing the bios sequence to scsi first. Check the faq
or readme info on the Promise card, I believe this situation is covered
within those files.
"Bill" <Bi...@lans.net> wrote in message
news:3982772...@news.accessnv.com...
TKR
SCSI. Since you didn't mention that option, you may need to dig
a little deeper. Either in Promise' FAQs or in the manual for your
Ultra66 there is some info about how to choose the boot device.
Detecting the onboard IDE ports first is normal......
As a test, how about removing the old drive and disabling the onboard
IDE channels? Make sure the new drive is active. Use FDISK /MBR
to insure that has a good boot record and do a SYS C: to insure that
the necessary boot files are on the drive.
Mike Powers
SCSI by the computer.
Will wrote:
>
> I just purchased a Maxtor Diamond Max Plus 40 GB
> drive today. I have installed Western Digital drives before
> and have had no problem. Today however, I installed the
> Maxtor with a Promise Ultra 66 Board. During the install
> process, the Maxtor software asked if I wanted to copy the
> old drive on to the new one. I answered yes, since the
> I wanted to copy the old 1.6GB WD drive onto the new
> drive and then take it the old drive out. Everything went
> fine but nowhere did I have the option to set the new drive
> as active or bootable (as I recall the WD allows) . Now
> when I removed the old drive, the systems gets past the
> memory test and just stops. If I connect the old drive the
> system boots fine off of it and I can see the new drive in
> Windows 95B. When I use a W95 boot disk with Fdisk
> on it to try to set the new drive as bootable, it only sees
> the old drive, which is connected to the motherboard IDE
> port. What am I missing? How do I set the new drive
> as bootable so I can shut down, unplug the old drive and
> have the new one boot up?
--
Mike Powers
I was very lonely until I became part of the problem.
Bill
wrote:
>Your bios reads the Promise as a SCSI device, this is normal, then boots to
>mb boot drive. Try changing the bios sequence to scsi first. Check the faq
>or readme info on the Promise card, I believe this situation is covered
>within those files.
I had to set the onboard IDE drive as None to get it to work. Looking
at the boot up sequence on the screen, they don't take effect until
after the old drive is auto detected. Unplugging the old drive caused
the system to hang because it was looking for a drive that wasn't
there before it would even go to trying to boot from the floppy,
followed by the IDE, and SCSI drives. Now the only problems is
that the Max Blaster software won't copy the drive correctly. The
directory tree is missing several folders between the old and new
drives. Also, the Max Blaster software designates the first 526
Megs of the new drive as a No Fat partition with a volume label of ?.
It won't allow me to do anything with that first 526. I can partition
everything after that but not the first 536 MB.
Bill
wrote:
>As a test, how about removing the old drive and disabling the onboard
>IDE channels? Make sure the new drive is active. Use FDISK /MBR
>to insure that has a good boot record and do a SYS C: to insure that
>the necessary boot files are on the drive.
That did it. The system would hang trying to detect the old drive
which I unplugged. Setting the IDE for a drive of None took
care of the problem. Now the only problem is the Max Blast
software won't copy the drive correctly. Several folders are
missing in the directory tree between the old and new drives.
Of course that means some shortcuts and programs work and
some don't. Also, the Max Blast software sets up the first 526
MB as a No Fat drive with a letter of ? and won't allow me to
partition or do anything with it. I can only partition the rest of
the drive. Don't know if that is a separate problem from the
copy problem or related.
>> Okay, here is something I found which might be the problem.
>> I noticed that when I boot off the old drive, the very next thing
>> that appears on the screen after the memory test is the
>> detection of the old drive on the motherboard IDE port. AFTER
>> that the Promise Ultra 66 board is detected. Shouldn't the
>> Promise board be detected before anything? When I boot up,
>> the very first thing that appears is detection of my Matrox
>> video card bios.
>>
>> My motherboard setup program allows me to set up which
>> device boots the computer. It is set to boot of A:/ then if that
>> fails (no floppy installed), then C:/ then the CD Rom drive.
>> The weird thing is that the computer will not boot from the
>> floppy unless the old hard drive is installed. Again, the
>> boot up screen shows detection of the old drive, the Promise
>> board, and then checks the floppy drive, which fails so the
>> boot up continues from the C: drive. Should I disable the
>> old drive on my motherboard bios and see if the Promise
>> board takes it's place?
>>
Bill
very poor. Doesn't even mention any info
on the disk. I solved this problem, now the Max Blast
software is not copying all files and folders from the
old drive.
On Sat, 29 Jul 2000 19:19:47 -0500, Mike Powers
<mpo...@inebraska.com> wrote:
>You need to read everything. The promise card is seen as
>SCSI by the computer.
>
>Will wrote:
>>
>> I just purchased a Maxtor Diamond Max Plus 40 GB
>> drive today. I have installed Western Digital drives before
>> and have had no problem. Today however, I installed the
>> Maxtor with a Promise Ultra 66 Board. During the install
>> process, the Maxtor software asked if I wanted to copy the
>> old drive on to the new one. I answered yes, since the
>> I wanted to copy the old 1.6GB WD drive onto the new
>> drive and then take it the old drive out. Everything went
>> fine but nowhere did I have the option to set the new drive
>> as active or bootable (as I recall the WD allows) . Now
>> when I removed the old drive, the systems gets past the
>> memory test and just stops. If I connect the old drive the
>> system boots fine off of it and I can see the new drive in
>> Windows 95B. When I use a W95 boot disk with Fdisk
>> on it to try to set the new drive as bootable, it only sees
>> the old drive, which is connected to the motherboard IDE
>> port. What am I missing? How do I set the new drive
>> as bootable so I can shut down, unplug the old drive and
>> have the new one boot up?
>
Bo Edstrom
>now the Max Blast
>software is not copying all files and folders from the
>old drive.
Hi,
Maybe try Powerquest Drivecopy or Drivimage instead?
www.powerquest.com
/Bo
re...@newsgroup.please
wrote:
>IDE channels? Make sure the new drive is active. Use FDISK /MBR
Have a Maxtor 40+ with Promise Ultra66 and want to use the last 8G my
mbo couldn´t see - but the Promise should see - and want to use them
without reformatting. Is this possible?