Can't boot XP off new SATA drive

On 08/07/2012 11:56 AM, Rebel1 wrote:
On 7/8/2012 10:03 AM, Yousuf Khan wrote:
(2) Your current XP is setup to work only with IDE drives, rather than
SATA drives. SATA drives can be made to look like standard IDE drives,
but you have to do that in BIOS. When you go into the BIOS setup, make
sure you select IDE rather than AHCI or RAID modes. There is no
performance difference between IDE and AHCI mode, just a few extra power
management features which are unimportant in desktops.

I can't find a way in the BIOS to select IDE for a SATA drive.

Okay then, then that means it doesn't offer that additional mode, so
it's not likely the problem. Just for your record, even though this
doesn't likely affect you, when you run a SATA drive with IDE drivers,
then you are running it according to the ATA version 7 specs, but when
you run these drives with AHCI drivers, then you are running it
according to the ATA version 8 specs. Only SATA drives can be run with
either ATA7 or ATA8 specs, older EIDE drives can only be run on the ATA7
specs.

(3) Why are you partitioning these drives so heavily? I agree that it's
a good idea to partition out the boot partition on its own into a small
100-200GB partition, but I'd just keep the remainder of the drive as one
single separate partition. This might be confusing boot process.

Can't give a simple answer. Programs are on the C: drive, and data they
create are in other partitions on the same drive. (The hope is that if a
virus attacks, it will be confined to C: and the other stuff is not
lost. Very large music and video files, and various backups are on the
second drive. When the system is back to two drives, there will be five
partitions on the SATA drive and two on the other Western Digital drive.

These days most viruses don't attack your data: they may steal your data
and give it to someone else (eg. bank accounts, passwords, etc.), but
leave it intact mostly. The days of the malicious data wiping virus are
long over, these days there is big business in data theft, rather than
simple pranks to erase your data. Besides, many of those data wiping
viruses were also able to erase partition tables too, so having separate
partitions was not going to be a safeguard.

(4) Why are you setting up a new XP rather than cloning the old XP?

The old XP had annoyances, like not being able to turn off the computer
if any instances of Windows Explorer are open.

I think you may find that problem still occurs even after you've gotten
a fresh install of XP onboard. Have you considered going to Windows 7 yet?

Yousuf Khan

On 08/07/2012 11:44 AM, Rebel1 wrote:
On 7/8/2012 10:38 AM, Rick wrote:
You neglected to mention if you installed the SATA drivers. You need to
copy the drivers from your MOBO disk and when prompted press F6 to
install the drivers.

I can't find SATA drivers on the MOBO disk.

You mentioned in another posting that you can't find a way to change the
settings for IDE vs. AHCI mode in the BIOS, so that means it's likely
defaulting to IDE. So you really don't have to worry about this anymore.
However, if you need the latest drivers for your motherboard, you can
always go to your mobo mfg's website and download the latest.

Yousuf Khan

I never had to locate separate SATA drivers and I never had to press F6
during installation. I'm puzzled as to why some of you suggested
pressing it, since I don't have RAID or ACHI.

I should have not cursory read your message.

--
@~@ Remain silent. Nothing from soldiers and magicians is real!
/ v \ Simplicity is Beauty!
/( _ )\ May the Force and farces be with you!
^ ^ (x86_64 Ubuntu 9.10) Linux 2.6.39.3
�借貸! ��騙! ��交! �打交! �打劫! �自殺! 請考慮綜� (CSSA):
http://www.swd.gov.hk/tc/index/site_...sub_addressesa

On Jul 8, 8:26 pm, Rebel1 wrote:
After making very slow progress, I finally decided to install XP with
just the new SATA connected. I first removed all the partitions using
Partition Manager. Windows dutifully assigned the partition as C:.
Everything went okay; no problems booting.

I never had to locate separate SATA drivers and I never had to press F6
during installation. I'm puzzled as to why some of you suggested
pressing it, since I don't have RAID or ACHI.

I reconnected the two ATA drives, and Windows merely assigned them new
letters. Now I have the ordeal of reinstalling my programs, drivers, etc.

Many thanks to all who graciously commented. This was a real education.

R1

Windoze handling a correction of Easeus's (sp?) screw up, just
confirms what I already suspected, mentioned, and how I also handled
that ... just a little differently, though.

I'd made already two active PRIMARY drives on the same thing, a 1T at
least or bigger 1.5T drive. Little dinky things, 3G/FAT32 for a
Windoze OS (sans all installs, which get linked back from another
LOGICAL drive for another, more or less, story), and about a 528M DOS
- 98 or facsimile IBMDOS, 4DOS, TRISHDOS, what have you in FAT16/20,
or may even be 32. Rudimentary, crudely but purposefully so, DOS for
binary for thingies like WD image type software.

Good ol' Easeus. Didn't just didn't want to say, grab your ankles and
count on it. Only, I didn't screw around, booted a HIREMs disc cause
I knew good and damn well what was going on as soon as I saw that
crap. (I did, however, trust Easeus's layout, how it's sector/
custering the HD structure and left it alone. No problems, in other
words, so far. . .).

Soon as I ran a FDISK variant off HIRENS with /MBR (ooo..Master, Boot
Repair..ooo please) -- solvency. Up and on the ol' merrily, merrily
and off we go to hiho again.

On Jul 9, 1:26 pm, Flasherly wrote:

PS - And a Belated Greeting, as well:

Welcome, conceptually, to KLUDGE (where on earth would computers be
without all these bugs and traps -- pure Chaos Theory, indubitably).

Yousuf Khan wrote:


Here's your problem. There is no Windows of any kind that can boot off
of a logical partition, they must boot off of primary partitions. Linux
in this context is far superior, as it doesn't make any distinction
between logical or primary partitions, it can boot off of either.

Yousuf Khan

There's a subtle distinction here. Windows uses a primary partition,
and the boot flag. That's what the boot loader in the MBR is using
in terms of facilities.

But the entire Windows OS doesn't have to be in a primary. The majority
of the OS files can be located in a logical. It's just the part that supports
the initial boot process, that sits in a primary.

When I dual booted two copies of Win2K, the second copy sat in a
logical. The first install, sitting in a primary, boots and puts
up the boot menu. When you select the second instance of Win2K,
that runs from its logical partition. So the instance in the
logical partition, can't start by itself. But it can be made
to run, if another Windows "bootstraps it".

Paul

"Rebel1" wrote in message
...

Here's what Microsoft has to say:
• You cannot mark a logical drive as active.
• You can only mark a partition as active on a master boot record (MBR)
disk.

(https://www.microsoft.com/resources/....mspx?mfr=true)

On the new drive, all the partitions are logical. So the problem becomes
making the new drive a MBR drive.

For Western Digital users, the WD DLG cloning routine does this
quicklessly and flawlessly.

--
Don Phillipson
Carlsbad Springs
(Ottawa, Canada)

On Mon, 9 Jul 2012 16:40:31 -0400, "Don Phillipson"
wrote:

"Rebel1" wrote in message
...

Here's what Microsoft has to say:
• You cannot mark a logical drive as active.
• You can only mark a partition as active on a master boot record (MBR)
disk.

(https://www.microsoft.com/resources/....mspx?mfr=true)

On the new drive, all the partitions are logical. So the problem becomes
making the new drive a MBR drive.

For Western Digital users, the WD DLG cloning routine does this
quicklessly and flawlessly.

At a sedate time of my life I like quicklessly, Don. No need to rush
things.
--
Robin Bignall
Herts, England