updated 4/15/2010 added the table move and patching routines suggested by Yen XP bootcode failed on my laptop so reverted to Windows 7 bootcode with TPM routines stripped.
Does it mean that for 15 04 code WindSLIC_bootsect.exe /nt52 sys is wrong? (as you say XP bootcode failed) sebus
no if it works then it is fine, I got the blinking cursor on one of my computers changed the boot code and then it booted, not sure what the problem was I will look into it EDIT: the problem was caused from booting from a WindSLIC usb drive and then installing WindSLIC_bootsect, which caused the sys drive to be detected incorrectly installed the bootsect to the usb drive and marked the true sys drive as inactive (non bootable) the recovery procedure fixed the boot and installing WindSLIC bootsect after booting from the hard drive fixed the issue. Ill keep the Windows 7 bootcode since it is easier to read.
As i understand, this is for NTFS volume, however, there' re some rare cases, where active partition (the one, which holds BOOT folder and bootmgr) may need to be kept formatted as FAT32... so i just wonder if there's any chance to port this patch into FAT32 bootsector? Doesn't look like bootsect.exe can be used though, as far as it can mod only 1.5 KBytes (first 3 sectors) in FAT32 volume, and i think they're all used by the system, but if to dump more sectors, there would be more free space found reserved there.
Ill look into the fat32 stuff but Im not sure about it, the code to find bootmgr is NTFS specific, but might be possible with a little hacking updated 4/22/2010 changed to stronger encryption, check config.ini to set the encryption key clears old SLIC from memory if present.
Yes, but it's an artificial restriction, for example i installed Win7 on third partition by running setup from under another OS ( XP, on d: with c: boot partition formatted as fat32), so setup just placed bootmgr and BOOT folder on C:, and the OS itself (all other system folders) on that third partition. A bit off-topic, but i have to tell you about one more surprizing experience - i wanted to learn if Win 7 would remain functional on FAT32 filesystem, so i installed it on vhd (because it's always made seen like C: from inside by setup) and then copied (being under another OS of course, and mounting vhd from there) all folders with content (except junk (link) folders like "Documents and settings", etc, cause fat32 doesn't support this feature) from vhd to real c: (which is fat32), added entry to bcd to start Win 7 from real C:... weird but everything seems to work fine.
If the System Volume is taken up by another OS, Windows 7 does not create the System Reserved Partition, instead it puts the Boot and Recovery Files into the Install Partition itself.
nononsence, thank you for all the hard work you're doing here on MDL forum with different WindSLIC applications, it all looks very interesting and promising.
Updated 05/18/2010 added chipset vendor id check, DISABLE_BIOS_RW can be left at default value, unless you have a spcific problem.
Thanks primarily... how to make WindSLIC_bootsect.exe's $OEM$ pre-activated folder ? sorry my english...
Nononsence, there's no need to detect the OEMID using a script, if you place the certs in System32 inside $OEM$, like this: $OEM$\$$\System32\cert1.xrm-ms $OEM$\$$\System32\cert2.xrm-ms Windows picks the right one.