How to make a hdd bootable

I just used 'Copy Commander' to transfer the information
on one hdd to another, and now it won't boot up
successfully. I get an error msg, with 'F1' to re-boot,
then it finally goes into windows. I guess I can live with
it, but it should just boot straight into windows. Any
suggestions would be appreciated.

Mimi

Using a Win Me boot floppy, it has to be a Win Me boot floppy anything
else will not do, boot to DOS using the floppy and then at the DOS prompt
type
SYS C:
This should then make your active partition bootable.
--
Mike Maltby MS-MVP



mimi wrote:

I just used 'Copy Commander' to transfer the information
on one hdd to another, and now it won't boot up
successfully. I get an error msg, with 'F1' to re-boot,
then it finally goes into windows. I guess I can live with
it, but it should just boot straight into windows. Any
suggestions would be appreciated.

Thank you so much! How do I make a Win ME bootable floppy.
Sorry for the stupid question.

Mimi
-----Original Message-----
Using a Win Me boot floppy, it has to be a Win Me boot
floppy anything
else will not do, boot to DOS using the floppy and then
at the DOS prompt
type
SYS C:
This should then make your active partition bootable.
--
Mike Maltby MS-MVP



mimi wrote:

I just used 'Copy Commander' to transfer the information
on one hdd to another, and now it won't boot up
successfully. I get an error msg, with 'F1' to re-boot,
then it finally goes into windows. I guess I can live
with
it, but it should just boot straight into windows. Any
suggestions would be appreciated.

.

If you don't have a boot floppy you can create a boot floppy (EBD) or
start up disk as follows:
Control Panel | Add/Remove Programs | Startup Disk and follow the prompts.

If you get asked for the location of a "missing" file point the wizard
towards your Win Me cab files which should be in either the
windows\options\cabs or windows\options\install folder. Alternatively
point to the Win9x folder on the Win Me CD. Specifically look for the
file BASE2.CAB and then point the wizard at the folder containing
base2.cab..

If you are unable to create a boot floppy you can download the image of a
Win Me OEM boot disk from www.bootdisk.com. Download to your desktop,
double click to run and follow the prompts to transfer the image to a
floppy. I feel however that you should in this case only do this as a
last resort if you really are unable to make a disk using the instructions
in the previous paragraphs.
--?
Mike Maltby



Mimi wrote:

Thank you so much! How do I make a Win ME bootable floppy.
Sorry for the stupid question.

Hi Mike, I tried this and it seemed like it worked. It=20
said files transfered, or something like that. I rebooted=20
again, doing a cold boot and it came up with disk=20
controller failure, F1 to re-boot, or F10 to run set up. I=20
hit F1 and it went into the software just fine. I then re-
booted and still the same thing. It just won't boot by=20
itself. Anymore suggestions?

Mimi
-----Original Message-----
If you don't have a boot floppy you can create a boot=20
floppy (EBD) or=20
start up disk as follows:
Control Panel | Add/Remove Programs | Startup Disk and=20
follow the prompts.

If you get asked for the location of a "missing" file=20
point the wizard=20
towards your Win Me cab files which should be in either=20
the=20
windows\options\cabs or windows\options\install folder. =20
Alternatively=20
point to the Win9x folder on the Win Me CD. Specifically=20
look for the=20
file BASE2.CAB and then point the wizard at the folder=20
containing=20
base2.cab..

If you are unable to create a boot floppy you can=20
download the image of a=20
Win Me OEM boot disk from www.bootdisk.com. Download to=20
your desktop,=20
double click to run and follow the prompts to transfer=20
the image to a=20
floppy. I feel however that you should in this case only=20
do this as a=20
last resort if you really are unable to make a disk using=20
the instructions=20
in the previous paragraphs.
--=81
Mike Maltby



Mimi wrote:

Thank you so much! How do I make a Win ME bootable=20
floppy.
Sorry for the stupid question.

.

Mimi,

The messages you are seeing are not I think from the operating system but
rather from your motherboard's bios. Where does F10 take you, into the
bios setup? If so it appears you may have hardware problems. What does
your bios report about your hard disk(s)?
--
Mike Maltby MS-MVP



Mimi wrote:

Hi Mike, I tried this and it seemed like it worked. It
said files transfered, or something like that. I rebooted
again, doing a cold boot and it came up with disk
controller failure, F1 to re-boot, or F10 to run set up. I
hit F1 and it went into the software just fine. I then re-
booted and still the same thing. It just won't boot by
itself. Anymore suggestions?

The symptoms of a 'dying' CMOS battery perhaps?

Mart


"Mike M" wrote in message
...
Mimi,

The messages you are seeing are not I think from the operating system but
rather from your motherboard's bios. Where does F10 take you, into the
bios setup? If so it appears you may have hardware problems. What does
your bios report about your hard disk(s)?
--
Mike Maltby MS-MVP



Mimi wrote:

Hi Mike, I tried this and it seemed like it worked. It
said files transfered, or something like that. I rebooted
again, doing a cold boot and it came up with disk
controller failure, F1 to re-boot, or F10 to run set up. I
hit F1 and it went into the software just fine. I then re-
booted and still the same thing. It just won't boot by
itself. Anymore suggestions?

Mart wrote:

The symptoms of a 'dying' CMOS battery perhaps?

Thanks Mart,

Could well be if the system is redetecting the hardware each time the
system starts from cold but not on a reboot. As I think about it that has
to be the reason and sysing the drive was quite unnecessary. I clearly
allowed myself to be distracted by the title of the thread. :-(
--
Mike Maltby MS-MVP

Mike, I was with you all the way 'til that nagging F1 report twigged g

Mart


"Mike M" wrote in message
...
Mart wrote:

The symptoms of a 'dying' CMOS battery perhaps?

Thanks Mart,

Could well be if the system is redetecting the hardware each time the
system starts from cold but not on a reboot. As I think about it that has
to be the reason and sysing the drive was quite unnecessary. I clearly
allowed myself to be distracted by the title of the thread. :-(
--
Mike Maltby MS-MVP