Has anyone else observed this? Does anyone have experience with the
Tyan S2882-D motherboard?

I'm having a problem booting my Tyan S2882-D motherboard from
a SCSI disk when a SATA disk is has been added.

Tyan suggested changing the PCI bus scanning order from Descent to
Ascent. I tried this but observed that the PCI bus address for the
on-board SATA controller and my video card are moving when I change
the scan order. No matter what I try the on-board SATA controller
always is detected before the on-board SCSI controller.

Scanpci -v output with BIOS PCI scan set to ascent:

pci bus 0x0001 cardnum 0x05 function 0x00: vendor 0x1095 device 0x3114
Silicon Image, Inc. SiI 3114 [SATALink/SATARaid] Serial ATA
Controller
STATUS 0x02b0 COMMAND 0x0007
CLASS 0x01 0x80 0x00 REVISION 0x02
BIST 0x00 HEADER 0x00 LATENCY 0x40 CACHE 0x10
BASE0 0x00008c01 addr 0x00008c00 I/O
BASE1 0x00008881 addr 0x00008880 I/O
BASE2 0x00008801 addr 0x00008800 I/O
BASE3 0x00008481 addr 0x00008480 I/O
BASE4 0x00008401 addr 0x00008400 I/O
BASE5 0xfc4ffc00 addr 0xfc4ffc00 MEM
BASEROM 0xfc400000 addr 0xfc400000 not-decode-enabled
MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x01 INT_LINE 0x0b
BYTE_0 0x02 BYTE_1 0x00 BYTE_2 0x00 BYTE_3 0x00

pci bus 0x0002 cardnum 0x06 function 0x00: vendor 0x9005 device 0x801d
Adaptec AIC-7902B U320
CardVendor 0x9005 card 0x005e (Adaptec, Card unknown)
STATUS 0x0430 COMMAND 0x0047
CLASS 0x01 0x00 0x00 REVISION 0x10
BIST 0x00 HEADER 0x80 LATENCY 0x40 CACHE 0x10
BASE0 0x0000a001 addr 0x0000a000 I/O
BASE1 0x00000000fc8f6004 addr 0x00000000fc8f6000 MEM 64BIT
BASE3 0x00009801 addr 0x00009800 I/O
BASEROM 0xfc780000 addr 0xfc780000 not-decode-enabled
MAX_LAT 0x19 MIN_GNT 0x28 INT_PIN 0x01 INT_LINE 0x05
BYTE_0 0xc6 BYTE_1 0xe3 BYTE_2 0x00 BYTE_3 0x80

pci bus 0x0002 cardnum 0x06 function 0x01: vendor 0x9005 device 0x801d
Adaptec AIC-7902B U320
CardVendor 0x9005 card 0x005e (Adaptec, Card unknown)
STATUS 0x0430 COMMAND 0x0047
CLASS 0x01 0x00 0x00 REVISION 0x10
BIST 0x00 HEADER 0x80 LATENCY 0x40 CACHE 0x10
BASE0 0x0000a801 addr 0x0000a800 I/O
BASE1 0x00000000fc8fc004 addr 0x00000000fc8fc000 MEM 64BIT
BASE3 0x0000a401 addr 0x0000a400 I/O
BASEROM 0xfc800000 addr 0xfc800000 not-decode-enabled
MAX_LAT 0x19 MIN_GNT 0x28 INT_PIN 0x02 INT_LINE 0x09
BYTE_0 0xc6 BYTE_1 0xe3 BYTE_2 0x00 BYTE_3 0x80

pci bus 0x0004 cardnum 0x03 function 0x00: vendor 0x10de device 0x0322
nVidia Corporation NV34 [GeForce FX 5200]
CardVendor 0x3842 card 0xb309 (eVga.com. Corp., Card unknown)
STATUS 0x02b0 COMMAND 0x0007
CLASS 0x03 0x00 0x00 REVISION 0xa1
BIST 0x00 HEADER 0x00 LATENCY 0x40 CACHE 0x00
BASE0 0xfd000000 addr 0xfd000000 MEM
BASE1 0xf0000008 addr 0xf0000000 MEM PREFETCHABLE
BASEROM 0xfeae0000 addr 0xfeae0000 not-decode-enabled
MAX_LAT 0x01 MIN_GNT 0x05 INT_PIN 0x01 INT_LINE 0x00
BYTE_0 0x42 BYTE_1 0x38 BYTE_2 0x09 BYTE_3 0xb3

Scanpci -v output with BIOS PCI scan set to descent:

pci bus 0x0001 cardnum 0x03 function 0x00: vendor 0x10de device 0x0322
nVidia Corporation NV34 [GeForce FX 5200]
CardVendor 0x3842 card 0xb309 (eVga.com. Corp., Card unknown)
STATUS 0x02b0 COMMAND 0x0007
CLASS 0x03 0x00 0x00 REVISION 0xa1
BIST 0x00 HEADER 0x00 LATENCY 0x40 CACHE 0x00
BASE0 0xfb000000 addr 0xfb000000 MEM
BASE1 0xf0000008 addr 0xf0000000 MEM PREFETCHABLE
BASEROM 0xfc4e0000 addr 0xfc4e0000 not-decode-enabled
MAX_LAT 0x01 MIN_GNT 0x05 INT_PIN 0x01 INT_LINE 0x00
BYTE_0 0x42 BYTE_1 0x38 BYTE_2 0x09 BYTE_3 0xb3

pci bus 0x0002 cardnum 0x06 function 0x00: vendor 0x9005 device 0x801d
Adaptec AIC-7902B U320
CardVendor 0x9005 card 0x005e (Adaptec, Card unknown)
STATUS 0x0430 COMMAND 0x0047
CLASS 0x01 0x00 0x00 REVISION 0x10
BIST 0x00 HEADER 0x80 LATENCY 0x40 CACHE 0x10
BASE0 0x00007801 addr 0x00007800 I/O
BASE1 0x00000000fc8f6004 addr 0x00000000fc8f6000 MEM 64BIT
BASE3 0x00007401 addr 0x00007400 I/O
BASEROM 0xfc780000 addr 0xfc780000 not-decode-enabled
MAX_LAT 0x19 MIN_GNT 0x28 INT_PIN 0x01 INT_LINE 0x09
BYTE_0 0xc6 BYTE_1 0xe3 BYTE_2 0x00 BYTE_3 0x80

pci bus 0x0002 cardnum 0x06 function 0x01: vendor 0x9005 device 0x801d
Adaptec AIC-7902B U320
CardVendor 0x9005 card 0x005e (Adaptec, Card unknown)
STATUS 0x0430 COMMAND 0x0047
CLASS 0x01 0x00 0x00 REVISION 0x10
BIST 0x00 HEADER 0x80 LATENCY 0x40 CACHE 0x10
BASE0 0x00008401 addr 0x00008400 I/O
BASE1 0x00000000fc8fc004 addr 0x00000000fc8fc000 MEM 64BIT
BASE3 0x00008001 addr 0x00008000 I/O
BASEROM 0xfc800000 addr 0xfc800000 not-decode-enabled
MAX_LAT 0x19 MIN_GNT 0x28 INT_PIN 0x02 INT_LINE 0x05
BYTE_0 0xc6 BYTE_1 0xe3 BYTE_2 0x00 BYTE_3 0x80

pci bus 0x0004 cardnum 0x05 function 0x00: vendor 0x1095 device 0x3114
Silicon Image, Inc. SiI 3114 [SATALink/SATARaid] Serial ATA
Controller
STATUS 0x02b0 COMMAND 0x0007
CLASS 0x01 0x80 0x00 REVISION 0x02
BIST 0x00 HEADER 0x00 LATENCY 0x40 CACHE 0x10
BASE0 0x0000bc01 addr 0x0000bc00 I/O
BASE1 0x0000b881 addr 0x0000b880 I/O
BASE2 0x0000b801 addr 0x0000b800 I/O
BASE3 0x0000b481 addr 0x0000b480 I/O
BASE4 0x0000b401 addr 0x0000b400 I/O
BASE5 0xfeaffc00 addr 0xfeaffc00 MEM
BASEROM 0xfea00000 addr 0xfea00000 not-decode-enabled
MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x01 INT_LINE 0x0b
BYTE_0 0x02 BYTE_1 0x00 BYTE_2 0x00 BYTE_3 0x00

Maxblast (for maxtor hardrives) can detect a new sata drive when windows can't. You can use the maxblast cd as the boot device and partition and format either drive. I use it to make an exact copy for a backup hardrive, but this has to be done while running windows. Other hardrive manufacturers have similar software. I have never tried connecting a new hardrive while the computer is already running, so I don't know if you can do this safely or if windows will detect it properly.

I would unplug the sata drive and boot up to the scsi. If the scsi has windows, then I would install maxblast or other hardrive software to set up the new sata drive. Then try installing the sata drive while windows is running. If the sata drive has files you want to save, then you will have to back them up first. You may have to search for "other devices" to get the sata to show up in your maxblast setup. Once maxblast finds it, then you can select it as the new boot device or as a second drive. Maxblast only allows you to make changes to the new drive, and not the one you're running in windows. It will erase and partition the sata drive, and if you like, make an exact copy of the scsi files so the sata becomes the new boot device. If you want to run both drives together, this may be easier than trying to get the motherboard to boot off the scsi drive.