In the SCSI ROOT NTBOOTDD.SYS in NOT present, it's present only NTDETECT.COM (hidden file)
Ok, as said it is NEEDED that you copy to the ROOT of the SCSI drive the appropriate driver for the SCSI card and rename it to NTBOOTDD.SYS.
Take some time to read the MS KB referenced in the thread I referenced before:
http://www.msfn.org/...ive-t25365.htmlthis KB:
http://support.micro...b;en-us;q102873You cannot boot a SCSI disk without the driver, when you give it with F6 and floppy it is "temporary", the Windows setup should copy it to both the %SystemRoot%\System32\drivers\ and the ROOT of the first active primary partition of first hard disk, renaming it to NTBOOTDD.SYS and adding the needed Registry entries.
It is possible that this has failed in your case, for reasons yet to be found.
Yes, in the new Windows XP Installation on the SATA Hdd I've installed Nero too.
Good, though Nero is a bit of overkill to just burn a .iso...
I've already (without batch by V.Laurie) tried disconecting SATA drive, Booting from Windows XP CD, pressing F6, and then pressing R for Recovery console.
This happens: C:\WINDOWS> prompt
and the C: Hdd (SCSI) seems working right.
for example, by executing CHKDSK it's all ok.
Do I have to try with batch by V.Laurie?
No, it was just a way to check that you could boot through RC to the SCSI HD with F6 and with the SATA drive disconnected, if needed I will guide you through the building of a more featured CD.
But until we do not have a confirmation that you have the proper NTBOOTDD.SYS, no further steps are possible.
To recap booting process (when using SCSI hardware and scsi() syntax):
1) Motherboard BIOS loads BIOS extension in the SCSI card then chainloads the MBR of the first drive (as seen by BIOSes)
2) the MBR chainloads the partition Bootsector of the Active Primary partition it finds on first drive (again as seen by BIOS)
3) the Bootsector chainloads NTLDR
4) NTLDR loads BOOT.INI
5) the user chooses one of the entries in BOOT.INI
6) NTLDR then loads NTDETECT.COM and, in the case of a scsi() entry, loads whatever NTBOOTDD.SYS file it finds in the ROOT of the same drive and partition where NTLDR, NTDETECT.COM and BOOT.INI are and uses it to access the drive
7) Windows starts booting
From the cited KB - about multi() syntax:
Theoretically, this syntax could be used to start Windows NT on any drive in the system. However, this would require that all drives are correctly identified through the standard INT 13 interface; since support for this varies from disk controller to disk controller and most system BIOS only identify a single disk controller through INT 13, in practice it is only safe to use this syntax to start Windows NT from the first two drives connected to the primary disk controller, or the first four drives in the case of a dual-channel EIDE controller.
In a pure IDE system, the MULTI() syntax will work for up to the four drives maximum on the primary and secondary channels of a dual-channel controller.
In a pure SCSI system, the MULTI() syntax will work for the first two drives on the first SCSI controller (that is, the controller whose BIOS loads first).
In a mixed SCSI and IDE system, the MULTI() syntax will work only for the IDE drives on the first controller.
You can see how the multi() syntax is prone to fail in some cases when SCSI hardware is used, on the other hand, another exerpt from same KB about scsi() syntax:
The SCSI() syntax is used on both RISC and x86-based computers and is used in all versions of Windows NT. Using SCSI() notation indicates that Windows NT will load a boot device driver and use that driver to access the boot partition.
On an x86-based computer, the device driver used is NTBOOTDD.SYS, which can be found in the root of the system drive (generally of drive C) and is a copy of the device driver for the drive controller in use.
.....
When using SCSI() notation the value of X depends upon NTBOOTDD.SYS. Each SCSI driver under Windows NT has its own method of ordering controllers, although generally they conform to the order that the BIOS on the controllers load (that is, if the BIOS is loaded).
scsi() syntax
NEEDS the driver NTBOOTDD.SYS and it is possible that the drive order is DIFFERENT from what reported by BIOS, thus different X,Y,Z,W values may be needed.
In other words, when booting from CD:
A.1) up to the "blue screen" of SETUP (where you press F6 to add the driver from floppy) the SCSI disk is accessed in "Real" mode through BIOS interrupts
A.2) after you have pressed "R" for Recovery Console, or went on with SETUP for installing, the SCSI disk is accessed through the driver loaded with F6+floppy
When (hopefully
) Windows is properly installed, a similar process applies,
B.1) up to BOOT.INI choices the SCSI disk is accessed in "Real" mode through BIOS interrupts
B.2) after a choice has been made, the SCSI disk is accessed through the NTBOOTDD.SYS driver
B.3) at a certain point of the windows loading, the actual SCSI .sys driver in %SystemRoot%\System32\drivers\ is loaded, "swapping" with the NTBOOTDD.SYS driver.
It seems like you miss the B.2) part, without which it is not possible to fill the gap between B.1) and B.3) above.
jaclaz
