Jump to content

neopets_35

Member
  • Posts

    5
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Malaysia

About neopets_35

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

neopets_35's Achievements

0

Reputation

  1. Managed to customize my Dell Windows XP SP2 disc with SP3 (and the Intel SATA driver too) integrated successfully. Tested and without any error. This time, I started anew by copying all contents of the Dell XP SP2 into my harddisk, and did the following tasks according to the order: Integrate SP3 and Intel SATA driver (both in one session) using nLite > Integrate WMP11 using WMP11 Slipstreamer (by booogy) > Integrate IE7 and some hotfixes in nLite (under the "Hotfixes, Add-ons and Update Packs") > Remove some components using nLite. Did tons of research, using a file manager, I managed to see some files being modified, some include SYSSETUP.DL_, SYSSETUP.IN_, TEXTSETUP.SIF and SFCFILES.DL_. These are my questions: 1. While I know SYSSETUP.DL_ must be hacked to remove components in SYSSETUP.INF, the newly modified date may seem to convince me that the DLL file has been hacked so that there won't be any signature check on SYSSETUP.INF. Referring to this web, I managed to hack the original XP SP2 SYSSETUP.DLL by changing 73 75 to 72 75 at offset 33679. While the page didn't refer to SP3, I managed to find the same set of hex at offset 33B29 (where I intentionally find the same set of hex, [8D B4 F5 FF FF 3B 48 04] before the hex, 73 75). So I assumed that after removing some components, nLite would have hacked the syssetup.dll file. However, I checked the DLL file in SYSSETUP.DL_ and found out that the the hex 73 75 didn't change at all, which means the digital signature check will still go on despite the SYSSETUP.INF have been modified. Any comment on this? 2. Since I didn't disable the Windows File Protection feature, does nLite modify SFCFILES.DLL according to the components I removed using nLite so that later it doesn't check for those components removed? I can see the SFCFILES.DL_ has been modified, but not sure whether my claim is true or not. So, what about it then?
  2. I've been doing hours of research of patching the syssetup.dll and setupapi.dll in Windows XP SP3. From what I know, patching syssetup.dll allows syssetup.inf to be edited without error in XP install, right? I'm not sure what does patch for the setupapi.dll for. Can you clarify this to me? http://www.neowin.net/forum/index.php?showtopic=636532 This website has the patched syssetup.dll for XP SP3, but the link isn't working at all! Can anyone share that if you have one? If not, do you know how to patch the syssetup.dll? Found the below web which explains the patching of syssetup.dll (of XP SP2). I'm not sure if it's gonna be the same for XP SP3 or not. But I can hardly understand what it's trying to point to. I managed to find the word, "pSetupVerifyFile" in the SP3's syssetup.dll though notepad and XVI32 hex editor, I just don't know from where to start. I don't now which hex to be edited and which hex address is it trying to refer to! Please explain!!! Please help!
  3. Oh, I see. Thanks for your reply, at least now I know that the Windows Media Player 11 Slipstreamer utility replaces the old WMP with the newer WMP11. Honestly speaking, it's not that I dislike the utility, but it's just that it would like it more if a portable or a "no-installation-needed" version is available for the utility, like nLite. And if possible, do you mind sending me just the executable (or portable) file for the WMP11 Slipstreamer? And anyway, why Service Pack 3 (SP3) first, I wonder? Sorry if I'm questioning too much, I just wanna' know why. Isn't it the same if I integrate WMP11 first before SP3? Anyway, is your method (SP3 > WMP 11 > IE7) entirely faultless, producing zero error? Thanks a thousand, anyway. Also, credits go to your Windows Media Player 11 Slipstreamer utility, it's a great tool, believe me! Thanks a lot!
  4. Currently I'm planning to slipstream SP3, WMP11 and IE7 into a Windows XP Home Edition SP2 media. While I've previously successfully slipstreamed SP3 into Windows XP SP2 using nLite 1.4.5 (without touching any other settings at all), now I've been doing loads of researches to integrate both Windows Media Player 11 and Internet Explorer 7. How do I integrate Windows Media Player 11? Do I really have to rely on the Windows Media Player 11 Slipstreamer utility? I know, many are using the tool, but is it possible for me to integrate WMP11 into my Windows XP installation disc using only nLite, eg. inserting the original WMP11 installer into the "Hotfixes and Update Packs" portion of nLite? If not, is using the add-on of WMP11 here in nLite same as integrating it with Windows Media Player 11 Slipstreamer? Through many researches I did, integrating Internet Explorer 7 is fine using only nLite. However, I did see many complaint of the Windows's System File Protection (SFP) errors when integrating both WMP11 and IE7 into the Windows XP installation disc. Do I really have to disable SFP first, then? Moreover, I don't see any error with integrating SP3 into my Windows XP SP2 previously. Besides, I do prefer things to be left at its default settings. Anyway, how should the sequence for the integration of SP3, WMP11 and IE7 into my XP (w/SP2) installation disc be? Also, please consider the updates that Service Pack 3 have for both WMP11 and IE7. Windows Media Player 11 Service Pack 3 (SP3) for Windows XP Finally, Internet Explorer 7 Will this be fine, in other words, will not cause any error? Is it also possible to integrate IE7 first before SP3? Well, this is because I know SP3 includes updates for Internet Explorer 7. But of course, I also know that installing IE7 before SP3 will render it uninstallable, but it isn't an issue to me. Windows Media Player 11 Internet Explorer 7 And finally, Service Pack 3 (SP3) for Windows XP What about this, then? Will it be the same then? Please guide me, please. Your help is highly appreciated. Thank you.
×
×
  • Create New...