Siginet, on Oct 6 2009, 10:13 AM, said:
1. It seems that after txtmode setup Windows Guimode setup was unable to start because the boot.ini was incorrect.
Windows setup expect target drive at (hd0).
Most BIOS map boot USB drive to (hd0).
And give one internal hard disk, internal hard disk is mapped to (hd1).
Compare first post, use grub4dos map to change mapping:
map (hd0) (hd1)
map (hd1) (hd0)
In there is the default setupldr.bin patched with "i386" to "XPPC".
Plus a copy of setupldr.bin which is named "XPPC.bin"
the XPPC.bin file is patched with "i386" to "XPPC" plus all instances of "winnt.sif" are patched to "wXPPC.sif"
There is a wXPPC.sif file also in the Boot folder. This is the Unattended Answer file that should be used.
Unattended installation does work too.
I understand, there is a setupldr.bin containing winnt.sif.
And there is a XPPC.bin containing wXPPC.sif
There is a file wXPPC.sif, but no winnt.sif.
Did you call setupldr.bin or XPPC.bin?
Remember wimb's suggestion
And remember a a:\winnt.sif (a:\wXPPC.sif) goes first. This is the floppy image in this case.
Did you add a w*.sif to floppy image. No, this is not necessary.
Imagine there exist a file \I386\RAMBOOT.TXT
123456 refers to RAM load sectors count.
Grub4dos menu.lst dosn't contain sector numbers by default.
Do you have a idea to boot grub4dos, read RAMBOOT.TXT at grub4dos and call
map --mem (0xFE)+123456 (0xFF)