[caps_buster]

BTW, for the possibility of installing the already modified/different windows files, it is necessary to hack the setupapi.dll file (setupapi.dl_ in the i386 directory). Depecking (expand) it, hacking it, fixing the header (modifype setupapi.dll -c) and packing it with makecab again. Now there:
http://www.vorck.com...t-setupapi.html
Fred Vorck cover the need byte sequences for Windows 2000 SP4, Windows XP SP3 and Windows 2003 SP2.
While all this is worth every penny and nice, I do miss the byte sequences/offsets for Windows XP SP 1 (or rather SP1.0a) and Windows XP SP2.

Anyone know them?

[fdv]

I believe, IIRC, that the sequence is found at the only instance of the following byte sequence in the file:

90 90 90 90 90 8B FF 55 8B EC 8B 45 2C 33 C9 3B C1

So, search for that in any version of the file, and you should only find one such sequence, and that's the one to change.

[caps_buster]

Thank you, Fred, for your quite fast response. No, string "90 90 90 90 90 8B FF 55 8B EC 8B 45 2C 33 C9 3B C1" is not found in the Win XP SP1.0a version, at least not in the Czech one I'm about to try changing. You got PM with the file...

And I tried different approach. Since W2k and XP are mostly the same, I tried searching for the "55 8B EC FF 75" sequance as with the Win2k SP4 setupapi.dll case. Quess what. Also FOUR instances of it, as in the W2k SP4 setupapi.dll file. So, as in the W2k, I blindly try to modify the second instance (as with W2k) - it is at 4F17D address and report back what happend when I try install WinXP with some modified files AND this modification of the setupapi.dll




Brief preliminary report
Failure - first it worked well, but at the end of the file copy phase, before the 1st reboot it complained that sfc_os.dll file is not winblows file, so for next try I have it modifyPE -c it and hopefully no messages anymore.
After reboot everything seems to be good, but after the setups and CD key and so on it get to the network install. And there it just stop. The progress indicator is halted, the right down "working" indicator is moving, but that it is. CD detection work too, but it looks like that adding my 63kBy hosts file with blocked all M$ domains ( http://www.msfn.org/board/modifying-dnsapi...61.html&hl= ) is way too much for the network setup. Next try with standard hosts file.

So, failure, tough both problems can be explained by other way and MAYBE the suggested modification of the setupapi.dll file for Windows 2000 SP4 on your site, Fred, is applicable to XP SP1.0a Windows. Just the address where to modify (witch of the strings, the second one...) is 4F17D - at least for Czech version of these XP Windows.

Status - unconfirmed yet.

This post has been edited by caps_buster: 14 October 2009 - 05:18 PM

[caps_buster]

After some battling with the not working XP install without the scsi drive support (not finding any drives) I managed to win and observed this:
- after the modifyPE was used on the sfc_os.dll file, no warning message anymore (good)
- after reboot, everything is installing well, until come the networking. It progress to about 50, maybe 60% and then stop and wait there forever (well, I waited about 5 or 8 minutes, but it is clearly not working)

Conclusion - the hack I did "blind" to the setupapi.dll file is NOT working at all. Using the originall hosts file it hang too, so it was NOT my hosts file (that is a good news also), but the hack.

As far as the 90 90 90 90 90 8B FF 55 8B EC 8B 45 2C 33 C9 3B C1 string goes, Fred, it is NOT FOUND in the setupapi.dll file my Windows XP SP1.0a Czech use. Any help?

The file is for everyone awailable there to look that the string is nonpresent:
[Link removed.]
(BTW, it looks way more like the Windows 2000 SP4 file, that string matches - except the position...)


Help?

This post has been edited by dencorso: 23 October 2009 - 10:09 PM
Reason for edit: Link removed - violation of Rule # 1.b