Using BOOTWS folder as is on USB-stick failed for Install of XP on second harddisk (GUI-mode error NTLDR missing).
Did you start GUI mode from the internal disk? Which one? Where boot files were placed? Was boot.ini correct?
My intentions for BOOTWS were to replicate default Windows behavior and get boot.ini generated correctly. What cdob posted is a workaround, in case you explicitly want to install in a particular disk, and has to be created manually. What do we do if you want to install on the first disk using the same entries? Or what entries would we create to get some universal solution?
I'd say the better solution in case one wants to get around these limitations is to disable the unneeded disk during setup, rather that changing boot order and forcibly redirecting setup.
Another way around could be a set of BOOTWS folders/entries and en entry for each of them in menu.lst, something like:
Install to first internal disk
Install to second internal disk
I can't see a way to "understand" what BIOS boot order was and adjust accordingly, since both Setup and grub4dos do not take it in account.
Yet to test what happens in SATA/AHCI mode, it may produce different results. I will be testing tomorrow, just need to check if the test machine had option to switch IDE/AHCI.
Possibly for support of x64 XP it is needed to write
Setupldr.bin in x64 is in I386, txtsetup.sif is in AMD64.
BTW- did you encounter the same behavior with the arrow keys while in winsetup.lst menus?