XP does not see data drive

Hi,

I have a system with two drives, one with win98 and the
other with XP Home. I have a drive selector, and there is a
third drive that is a data drive which is accessed by both
operating systems. It has been like this for a long time
and worked fine until recently the drive with XP on it went faulty. I
replaced it and installed XP. However, now XP does not see the data
drive like the old drive did.

When I reboot and change to the drive with win98, win98 still
sees the data drive just like it used to.

So far I have done the following:

In XP drive BIOS; I made sure AUTO/LBA is selected for
both IDE slave drives.

Run 'rescan' in Device Manager in XP and rebooted.

Turned off the firewall and run rescan and rebooted.

The XP is formatted as NTFS and the data drive is FAT32 but
I don't think this is a problem since it is a seperate drive.


Any hints? I know its just a software setting because the old
drive with XP home worked fine, and the drive with win98 can
still access the data drive.

Thanks for any assistance.

itchy

what does computer
management via admin
tools state about that
drive?

--
db·´¯`·...¸)))º
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces
- @Hotmail.com
- nntp Postologist
~ "share the nirvana" - dbZen

~~~~~~~~~~~~~~~



"internaughtfull" wrote in message
...
Hi,

I have a system with two drives, one with win98 and the
other with XP Home. I have a drive selector, and there is a
third drive that is a data drive which is accessed by both
operating systems. It has been like this for a long time
and worked fine until recently the drive with XP on it went faulty. I
replaced it and installed XP. However, now XP does not see the data
drive like the old drive did.

When I reboot and change to the drive with win98, win98 still
sees the data drive just like it used to.

So far I have done the following:

In XP drive BIOS; I made sure AUTO/LBA is selected for
both IDE slave drives.

Run 'rescan' in Device Manager in XP and rebooted.

Turned off the firewall and run rescan and rebooted.

The XP is formatted as NTFS and the data drive is FAT32 but
I don't think this is a problem since it is a seperate drive.


Any hints? I know its just a software setting because the old
drive with XP home worked fine, and the drive with win98 can
still access the data drive.

Thanks for any assistance.

itchy

"internaughtfull" wrote in message
...
Hi,

I have a system with two drives, one with win98 and the
other with XP Home. I have a drive selector, and there is a
third drive that is a data drive which is accessed by both
operating systems. It has been like this for a long time
and worked fine until recently the drive with XP on it went faulty. I
replaced it and installed XP. However, now XP does not see the data
drive like the old drive did.

When I reboot and change to the drive with win98, win98 still
sees the data drive just like it used to.

So far I have done the following:

In XP drive BIOS; I made sure AUTO/LBA is selected for
both IDE slave drives.

Run 'rescan' in Device Manager in XP and rebooted.

Turned off the firewall and run rescan and rebooted.

The XP is formatted as NTFS and the data drive is FAT32 but
I don't think this is a problem since it is a seperate drive.


Any hints? I know its just a software setting because the old
drive with XP home worked fine, and the drive with win98 can
still access the data drive.

Thanks for any assistance.

itchy


Using the drive selector for booting, I assume that all drives are IDE
types.

If the new XP drive is not set as Master with slave but is using cable
select (as many drives are shipped that way) you possibly will get the issue
you are talking about with slave drive. Ensure that the jumper on the new
drive is set properly for the scenario you have created.

If the slave drive (data drive) is set by the jumpers as slave then the XP
drive needs to be set as Master or Master with slave depending on the
drive's manufacturer. If the slave drive is set to CS (cable select) you
need to have the XP drive set the same way (and I don't recommend this way
with a drive switch box.)

Let us know if this was the issue.

On Sep 21, 12:17*pm, "LVTravel" wrote:
"internaughtfull" wrote in message

...



Hi,

I have a system with two drives, one with win98 and the
other with XP Home. I have a drive selector, and there is a
third drive that is a data drive which is accessed by both
operating systems. It has been like this for a long time
and worked fine until recently the drive with XP on it went faulty. I
replaced it and installed XP. However, now XP does not see the data
drive like the old drive did.

When I reboot and change to the drive with win98, win98 still
sees the data drive just like it used to.

So far I have done the following:

In XP drive BIOS; I made sure AUTO/LBA is selected for
both IDE slave drives.

Run 'rescan' in Device Manager in XP and rebooted.

Turned off the firewall and run rescan and rebooted.

The XP is formatted as NTFS and the data drive is FAT32 but
I don't think this is a problem since it is a seperate drive.

Any hints? I know its just a software setting because the old
drive with XP home worked fine, and the drive with win98 can
still access the data drive.

Thanks for any assistance.

itchy

Using the drive selector for booting, I assume that all drives are IDE
types.

If the new XP drive is not set as Master with slave but is using cable
select (as many drives are shipped that way) you possibly will get the issue
you are talking about with slave drive. *Ensure that the jumper on the new
drive is set properly for the scenario you have created.

If the slave drive (data drive) is set by the jumpers as slave then the XP
drive needs to be set as Master or Master with slave depending on the
drive's manufacturer. *If the slave drive is set to CS (cable select) you
need to have the XP drive set the same way (and I don't recommend this way
with a drive switch box.)

Let us know if this was the issue.

Right-click "My computer", Go to Computer Management and then Disk
Management on the left. See if it shows up there.

On Sep 21, 12:17*pm, "LVTravel" wrote:
"internaughtfull" wrote in message

...





Hi,

I have a system with two drives, one with win98 and the
other with XP Home. I have a drive selector, and there is a
third drive that is a data drive which is accessed by both
operating systems. It has been like this for a long time
and worked fine until recently the drive with XP on it went faulty. I
replaced it and installed XP. However, now XP does not see the data
drive like the old drive did.

When I reboot and change to the drive with win98, win98 still
sees the data drive just like it used to.

So far I have done the following:

In XP drive BIOS; I made sure AUTO/LBA is selected for
both IDE slave drives.

Run 'rescan' in Device Manager in XP and rebooted.

Turned off the firewall and run rescan and rebooted.

The XP is formatted as NTFS and the data drive is FAT32 but
I don't think this is a problem since it is a seperate drive.

Any hints? I know its just a software setting because the old
drive with XP home worked fine, and the drive with win98 can
still access the data drive.

Thanks for any assistance.

itchy

Using the drive selector for booting, I assume that all drives are IDE
types.

If the new XP drive is not set as Master with slave but is using cable
select (as many drives are shipped that way) you possibly will get the issue
you are talking about with slave drive. *Ensure that the jumper on the new
drive is set properly for the scenario you have created.

If the slave drive (data drive) is set by the jumpers as slave then the XP
drive needs to be set as Master or Master with slave depending on the
drive's manufacturer. *If the slave drive is set to CS (cable select) you
need to have the XP drive set the same way (and I don't recommend this way
with a drive switch box.)

Let us know if this was the issue.- Hide quoted text -

- Show quoted text -

I tried both ways and XP did not see the drive. It does not show up
under Disk Management. I have AUTO/LBA selected in BIOS.

I did note that in Win98, using MaxBlast [the maxtor drive utility
that came with
the Maxtor data drive] that it showed the following:

Primary ATA: C:
Secondary ATA: none
Adaptor: Promise 1+0 Stripe/Raid0 D: and E: [D and E are the two
partitions on the Maxtor data drive]

However, when I booted up using the XP drive, only Primary ATA was
shown, and nothing was listed
under 'Promise'.

I think this may be the problem but I thought the Promise software was
installed when the
mother board was setup, and that data was held in a chip by the
lithium battery on the board.

As an aside, shortly after I installed the XP system, if anything is
plugged into a usb port when I boot
up using the win98 disk,
the system hangs right after the win98 splash screen disappears.
Probably a reinstall
will fix this.

Btw, I did disconnect the data drive when I installed XP and the SP2
update. Then I reconnected it.


Thanks for any help on this.

itchy

"internaughtfull" wrote in message
...
On Sep 21, 12:17 pm, "LVTravel" wrote:
"internaughtfull" wrote in message

...





Hi,

I have a system with two drives, one with win98 and the
other with XP Home. I have a drive selector, and there is a
third drive that is a data drive which is accessed by both
operating systems. It has been like this for a long time
and worked fine until recently the drive with XP on it went faulty. I
replaced it and installed XP. However, now XP does not see the data
drive like the old drive did.

When I reboot and change to the drive with win98, win98 still
sees the data drive just like it used to.

So far I have done the following:

In XP drive BIOS; I made sure AUTO/LBA is selected for
both IDE slave drives.

Run 'rescan' in Device Manager in XP and rebooted.

Turned off the firewall and run rescan and rebooted.

The XP is formatted as NTFS and the data drive is FAT32 but
I don't think this is a problem since it is a seperate drive.

Any hints? I know its just a software setting because the old
drive with XP home worked fine, and the drive with win98 can
still access the data drive.

Thanks for any assistance.

itchy

Using the drive selector for booting, I assume that all drives are IDE
types.

If the new XP drive is not set as Master with slave but is using cable
select (as many drives are shipped that way) you possibly will get the
issue
you are talking about with slave drive. Ensure that the jumper on the new
drive is set properly for the scenario you have created.

If the slave drive (data drive) is set by the jumpers as slave then the
XP
drive needs to be set as Master or Master with slave depending on the
drive's manufacturer. If the slave drive is set to CS (cable select) you
need to have the XP drive set the same way (and I don't recommend this
way
with a drive switch box.)

Let us know if this was the issue.- Hide quoted text -

- Show quoted text -

I tried both ways and XP did not see the drive. It does not show up
under Disk Management. I have AUTO/LBA selected in BIOS.

I did note that in Win98, using MaxBlast [the maxtor drive utility
that came with
the Maxtor data drive] that it showed the following:

Primary ATA: C:
Secondary ATA: none
Adaptor: Promise 1+0 Stripe/Raid0 D: and E: [D and E are the two
partitions on the Maxtor data drive]

However, when I booted up using the XP drive, only Primary ATA was
shown, and nothing was listed
under 'Promise'.

I think this may be the problem but I thought the Promise software was
installed when the
mother board was setup, and that data was held in a chip by the
lithium battery on the board.

As an aside, shortly after I installed the XP system, if anything is
plugged into a usb port when I boot
up using the win98 disk,
the system hangs right after the win98 splash screen disappears.
Probably a reinstall
will fix this.

Btw, I did disconnect the data drive when I installed XP and the SP2
update. Then I reconnected it.


Thanks for any help on this.

itchy

If you have a Promise IDE controller card in the computer you need to also
install the drivers in the XP side.

On Sep 22, 11:49*am, "LVTravel" wrote:
"internaughtfull" wrote in message

...



On Sep 21, 12:17 pm, "LVTravel" wrote:
"internaughtfull" wrote in message

....

Hi,

I have a system with two drives, one with win98 and the
other with XP Home. I have a drive selector, and there is a
third drive that is a data drive which is accessed by both
operating systems. It has been like this for a long time
and worked fine until recently the drive with XP on it went faulty. I
replaced it and installed XP. However, now XP does not see the data
drive like the old drive did.

When I reboot and change to the drive with win98, win98 still
sees the data drive just like it used to.

So far I have done the following:

In XP drive BIOS; I made sure AUTO/LBA is selected for
both IDE slave drives.

Run 'rescan' in Device Manager in XP and rebooted.

Turned off the firewall and run rescan and rebooted.

The XP is formatted as NTFS and the data drive is FAT32 but
I don't think this is a problem since it is a seperate drive.

Any hints? I know its just a software setting because the old
drive with XP home worked fine, and the drive with win98 can
still access the data drive.

Thanks for any assistance.

itchy

Using the drive selector for booting, I assume that all drives are IDE
types.

If the new XP drive is not set as Master with slave but is using cable
select (as many drives are shipped that way) you possibly will get the
issue
you are talking about with slave drive. Ensure that the jumper on the new
drive is set properly for the scenario you have created.

If the slave drive (data drive) is set by the jumpers as slave then the
XP
drive needs to be set as Master or Master with slave depending on the
drive's manufacturer. If the slave drive is set to CS (cable select) you
need to have the XP drive set the same way (and I don't recommend this
way
with a drive switch box.)

Let us know if this was the issue.- Hide quoted text -

- Show quoted text -

I tried both ways and XP did not see the drive. It does not show up
under Disk Management. I have AUTO/LBA selected in BIOS.

I did note that in Win98, using MaxBlast [the maxtor drive utility
that came with
the Maxtor data drive] that it showed the following:

Primary ATA: C:
Secondary ATA: none
Adaptor: Promise 1+0 Stripe/Raid0 *D: and E: [D and E are the two
partitions on the Maxtor data drive]

However, when I booted up using the XP drive, only Primary ATA was
shown, and nothing was listed
under 'Promise'.

I think this may be the problem but I thought the Promise software was
installed when the
mother board was setup, and that data was held in a chip by the
lithium battery on the board.

As an aside, shortly after I installed the XP system, if anything is
plugged into a usb port when I boot
up using the win98 disk,
the system hangs right after the win98 splash screen disappears.
Probably a reinstall
will fix this.

Btw, I did disconnect the data drive when I installed XP and the SP2
update. Then I reconnected it.

Thanks for any help on this.

itchy

If you have a Promise IDE controller card in the computer you need to also
install the drivers in the XP side.

Same goes if you're using any kind of RAID controller.

"Hodges" wrote in message
...
On Sep 22, 11:49 am, "LVTravel" wrote:
"internaughtfull" wrote in message

...



On Sep 21, 12:17 pm, "LVTravel" wrote:
"internaughtfull" wrote in message

...

Hi,

I have a system with two drives, one with win98 and the
other with XP Home. I have a drive selector, and there is a
third drive that is a data drive which is accessed by both
operating systems. It has been like this for a long time
and worked fine until recently the drive with XP on it went faulty.
I
replaced it and installed XP. However, now XP does not see the data
drive like the old drive did.

When I reboot and change to the drive with win98, win98 still
sees the data drive just like it used to.

So far I have done the following:

In XP drive BIOS; I made sure AUTO/LBA is selected for
both IDE slave drives.

Run 'rescan' in Device Manager in XP and rebooted.

Turned off the firewall and run rescan and rebooted.

The XP is formatted as NTFS and the data drive is FAT32 but
I don't think this is a problem since it is a seperate drive.

Any hints? I know its just a software setting because the old
drive with XP home worked fine, and the drive with win98 can
still access the data drive.

Thanks for any assistance.

itchy

Using the drive selector for booting, I assume that all drives are IDE
types.

If the new XP drive is not set as Master with slave but is using cable
select (as many drives are shipped that way) you possibly will get the
issue
you are talking about with slave drive. Ensure that the jumper on the
new
drive is set properly for the scenario you have created.

If the slave drive (data drive) is set by the jumpers as slave then
the
XP
drive needs to be set as Master or Master with slave depending on the
drive's manufacturer. If the slave drive is set to CS (cable select)
you
need to have the XP drive set the same way (and I don't recommend this
way
with a drive switch box.)

Let us know if this was the issue.- Hide quoted text -

- Show quoted text -

I tried both ways and XP did not see the drive. It does not show up
under Disk Management. I have AUTO/LBA selected in BIOS.

I did note that in Win98, using MaxBlast [the maxtor drive utility
that came with
the Maxtor data drive] that it showed the following:

Primary ATA: C:
Secondary ATA: none
Adaptor: Promise 1+0 Stripe/Raid0 D: and E: [D and E are the two
partitions on the Maxtor data drive]

However, when I booted up using the XP drive, only Primary ATA was
shown, and nothing was listed
under 'Promise'.

I think this may be the problem but I thought the Promise software was
installed when the
mother board was setup, and that data was held in a chip by the
lithium battery on the board.

As an aside, shortly after I installed the XP system, if anything is
plugged into a usb port when I boot
up using the win98 disk,
the system hangs right after the win98 splash screen disappears.
Probably a reinstall
will fix this.

Btw, I did disconnect the data drive when I installed XP and the SP2
update. Then I reconnected it.

Thanks for any help on this.

itchy

If you have a Promise IDE controller card in the computer you need to
also
install the drivers in the XP side.

Same goes if you're using any kind of RAID controller.

Agreed and I could be wrong but it looks like the OP was using a Promise
Raid controller card with one drive partitioned into two data drives. I had
(until it "blew up") a Promise Raid card that I had used in the same way but
with two hard drives until I decided to use the Raid features of the card.

On Sep 22, 11:49*am, "LVTravel" wrote:
"internaughtfull" wrote in message

...





On Sep 21, 12:17 pm, "LVTravel" wrote:
"internaughtfull" wrote in message

....

Hi,

I have a system with two drives, one with win98 and the
other with XP Home. I have a drive selector, and there is a
third drive that is a data drive which is accessed by both
operating systems. It has been like this for a long time
and worked fine until recently the drive with XP on it went faulty. I
replaced it and installed XP. However, now XP does not see the data
drive like the old drive did.

When I reboot and change to the drive with win98, win98 still
sees the data drive just like it used to.

So far I have done the following:

In XP drive BIOS; I made sure AUTO/LBA is selected for
both IDE slave drives.

Run 'rescan' in Device Manager in XP and rebooted.

Turned off the firewall and run rescan and rebooted.

The XP is formatted as NTFS and the data drive is FAT32 but
I don't think this is a problem since it is a seperate drive.

Any hints? I know its just a software setting because the old
drive with XP home worked fine, and the drive with win98 can
still access the data drive.

Thanks for any assistance.

itchy

Using the drive selector for booting, I assume that all drives are IDE
types.

If the new XP drive is not set as Master with slave but is using cable
select (as many drives are shipped that way) you possibly will get the
issue
you are talking about with slave drive. Ensure that the jumper on the new
drive is set properly for the scenario you have created.

If the slave drive (data drive) is set by the jumpers as slave then the
XP
drive needs to be set as Master or Master with slave depending on the
drive's manufacturer. If the slave drive is set to CS (cable select) you
need to have the XP drive set the same way (and I don't recommend this
way
with a drive switch box.)

Let us know if this was the issue.- Hide quoted text -

- Show quoted text -

I tried both ways and XP did not see the drive. It does not show up
under Disk Management. I have AUTO/LBA selected in BIOS.

I did note that in Win98, using MaxBlast [the maxtor drive utility
that came with
the Maxtor data drive] that it showed the following:

Primary ATA: C:
Secondary ATA: none
Adaptor: Promise 1+0 Stripe/Raid0 *D: and E: [D and E are the two
partitions on the Maxtor data drive]

However, when I booted up using the XP drive, only Primary ATA was
shown, and nothing was listed
under 'Promise'.

I think this may be the problem but I thought the Promise software was
installed when the
mother board was setup, and that data was held in a chip by the
lithium battery on the board.

As an aside, shortly after I installed the XP system, if anything is
plugged into a usb port when I boot
up using the win98 disk,
the system hangs right after the win98 splash screen disappears.
Probably a reinstall
will fix this.

Btw, I did disconnect the data drive when I installed XP and the SP2
update. Then I reconnected it.

Thanks for any help on this.

itchy

If you have a Promise IDE controller card in the computer you need to also
install the drivers in the XP side.- Hide quoted text -

- Show quoted text -

After reading this group and the alt.os.xp group,
I went into Device Manager and deleted the ? near 'Unknown Device'
[there were three: Multimedia Controller, RAID Controller, and
Universal
Serial Bus Controller] and
rebooted. XP then started up a software wizard and I inserted a floppy
with the
Promise Raid drivers and that worked. Voila, it saw the drives no
problem.

I think the Multimedia controller is a PCI audiowerk card that I have
not
installed the drivers for, or maybe the Matrox Millenium card drivers.
The USB
? just did not come back.

Anyway, it sees the drives yay! So in this case I did not have to
run
repair or reinstall. In difficult times, one cannot beat the library
and free
internet.

itchy