Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by RisingXun

  1. http://www.wincert.net/forum/index.php?showtopic=5747
  2. Im pretty much using a simple Windows XP Sp3 Disc. Heres the steps how i made to check what was the problem. 1. Added Addons/update Packs with Ryanvm Integrator. (also patched bootscreen resources so i wouldnt have to recabbed the Drivers.cab 2. Used nLite to slim down Xp Source 3. Tested the Windows XP Sp3 (Yeah it worked) 4. Then From here i tested the 2 ways of applying the resources.
  3. LOL, oh man, i wondered how you think kay was kaylar, the posts within this topic was not even directed to kaylar. the only posts he/she has in this topic was about intro.wmv. yeah kay for me is actually "Okay"
  4. have you tested the new Xptsp batch with the ResPacker?
  5. oh does it? hmmm i guess ENU_USER's ResPacker is not compatible with the latest pack anymore EDIT: kay, ive just used the addon itself and it worked perfectly.
  6. have any had any problems with the XPtsp v1.4.5.2 update on a clean xp install disc? im getting a "setup.exe was unable to be copied correctly", then once the OS reboots and tries to enter GUI setup mode, it crashes a restarts. I remember having v1.4.x (i think i was using v1.4.1) and it was working perfectly. i know its the updated files because i tested the Xptsp Black version and i dont get these errors.
  7. I think you should have your first post to Redirect to the main topic http://www.wincert.net/forum/index.php?showtopic=3842 It would just be much easier to update one post.
  8. im sure that the script patches the resources and the msc are just being replaced. the script just copy the files in the appropriate directory Edit: when i say replace, i mean that the file must exist before there, this is in the script because i dont want to add files that i took out prior to the clean install of windows
  9. Well ive tested the XptspScriptLive with SfcEnabled . While patching the annoying dialogs shows up constantly. but in the end the patching still works. . if anybody out there that has sfc enabled. test and confirm it please. Else it would just be my system doing its charm i dont have a problem releasing my scripts. i already did with the XptspScript (Source Patcher). its just right now i dont feel like i should.
  10. Yeah, my system was already had pre-patched sfc on a clean install. and that is why i found no files in the DLLCACHE except for catalogs files. I will probably switch back to an original sfc dll to do more testing
  11. im Not sure if the method in VISO.Live works but i just converted it into autoit These Lines Here: Reg Add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /v "SfcDisable" /t REG_DWORD /d 4294967197 /F>nul Reg Add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /v "SfcQuota" /t REG_DWORD /d 1 /F>nul Reg Add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /v "SFCScan" /t REG_DWORD /d 0 /F>nul Reg Add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /v "SFCShowProgress" /t REG_DWORD /d 0 /F>nul Reg Add "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager" /v "AllowProtectedRenames" /t REG_DWORD /d 1 /F>nul [Released] XptspScriptLive Version: 1.4 Changes: +Rewrote Patching method +Added Registry to AutoLogon +Added a "Check" For Res And Files +Took Out Patching For "NTKRNLPA.EXE" & "NTOSKRNL.EXE" (Just Until i can Make sure that it will not be corrupted, Else you wont be able to boot up your system ) DLhere: http://www.mediafire.com/?mjez3dklwmy
  12. well yeah because you script might be setup to be something like And still work. in my case it wont, i use the "$Filename[$X][0]" array as a indication of what res file i would use. as for the BOOTSCR.RES for 4 different files, i would have to edit add a few lines
  13. can you look into the ResPatch.log and tell me if theres any errors?
  14. thats a very weird situation. Was the XptspScriptLive1.X.exe Placed in the same Directory as Xptsp.bat? Edit: After running the script: there should be a ResPatch.Log and Checksum.txt created in the same directory, Check it and see whats the error *I have also tested this with the Xptsp.Blue and Xptsp.Purple to see if this script is working, and it is Okok, its just because i based the File list off your Xptsp AND the VISO Live. so what if there was a line like this. IEXPLORE.DLL.MUI=%Prog%\Internet Explorer\en-US\ Note*theres only 1 Line like that. Question: is there suppose to be a NTOSKRNL.EXE.Res and NTKRNLPA.EXE.Res in the Xptsp?
  15. Yeah i know its in your ini file. im stating that i think it has a typo or somewhat FROM This: WUAUCPL.MUI=%Sys%\WUAUCPL.CPL.MUI WUCLTUI.MUI=%Sys%\WUCLTUI.DLL.MUI TO This: WUAUCPL.CPL.MUI=%Sys%\WUAUCPL.CPL.MUI WUCLTUI.DLL.MUI=%Sys%\WUCLTUI.DLL.MUI EDIT: well i dont know how you setup your script for patching, these lines may not be a problem 1 More Lines that are missing the .ext, Again, i do not now how you would use these name for patching. Filename (left of the "=") may just be for reference, i dotn know.. HMMAPI.MUI=%Prog%\Internet Explorer\en-US\hmmapi.dll.mui "HMMAPI.MUI=" >> "HMMAPI.DLL.MUI=" =========================================== I never believed that the patching would be done in about 2 mins (Referring to amnesia previous post asking me how long it would take to convert the VISO.Live to autoit) ScreenShot: Now i Do!!! 136 Seconds!! How Fast Can your Computer Patch =========================================== [Released] XptspScriptLive Version 1.1 Language: Autoit3 Updates: +Does Search for all Files that needs to be patch. (Lists Are based on VISO Live 2.7) +Replaces Existing Files such as *msc *wav *bmp etc... with files from Xptsp\Extras to Appropriate paths *Basically its does Everything the VISO Live 2.7 and Live.Patcher from the Xptsp GUI EXCEPT 1. Add Fonts 2. Add/Replace Cursors 3. DOES NOT!! Patch Logonui.exe, its seems to be corrupted after the patching To me, those was not important at all. DLHere: http://www.mediafire.com/?3ynntqujedm
  16. EDIT: @dougiefresh, i believe there are 2 Lines that must be corrected. Found this out when making my XptspScritLive WUAUCPL.MUI=%Sys%\WUAUCPL.CPL.MUI WUCLTUI.MUI=%Sys%\WUCLTUI.DLL.MUI Heres an XptspScript For Live Patching. Its just 50~70 Lines or so. this actually took 3 hours total with testing. i was way off from my estimate of 2-3 days. Written in Autoit3. *Note: This Script Just patch the Files in "Windows\" and "System32\", i just wanted the "main" files to be patched. Also, it does NOT keep the backup files Instruction: 1. Extract Xptsp v1.X batch or Higher 2. Place XptspScriptLive.v1.0.exe in Directory containing XPtsp.bat 3. Run Script Simple eZ and Fast. Enjoy Download : http://www.mediafire.com/?maymoydtoyt
  17. what are the changes to Xptsp 1.3, i dont know which .res files to update (personal preference) if i dont know which 1 was updated.
  18. Lmfao, ive spent so much time extracting and re-archiving the sfx file when i couldve just open it in winrar and add the file to have an updated sfx with XptspScript.exe. WinRAR is KING
  19. well it depends on how i would want it to patch the files, it might take two day maybe three. basically its based on the best way to setup the program. Copying the files > Patching > moving it back is easy and there are no converter that i know of at the moment Edit: well the XPtsp GUI already has a function for a Live Patching.
  20. whao this is a very nice mapping of where the *.res files are placed, at first i thought it was just a Directory where we had to place all the res files in Like Plugings\XPtsp\*.res i think that picture should be posted on your main post for reference
  21. Woot Nice, It will be very Convenient to have it setup like this -Plugins -----XPtsp ---------Extra ---------Resources Updating the Resource would be very Easy that way. Just a thought
  22. that can be easily fixed... First you would have to see if the RvmTemp Dir Exists... Then Check what files there are to patch If files are found then copy/move to Temp\ Folder to be patched Delete Found File in RvmTemp Move Patched file in Temp\ Back to RVMTemp I based my little "Fix" on this quote here. i believe it allows the script to be ran right before the driver gets cabbed. And also, this script wont support the sp?.cab that exist because when i create my disc in RvmIntegrator, the Driver.cab and Sp?.cab are combined as one EDIT: there drivers get extracted to rvmtemp\extracted by the integrator
  23. i wasnt even sure that the script batch even do that. I basically used the same command found in the XPtsp.bat file. ResHack -addoverwrite Temp\Filename.Ext, Temp\Filename.Ext, Resources\Filename.Ext.Res,,, there are no other codes that shows the removal of Resources in the files before patching =================================== Yeah, since im a RVMIntegrator user also, for addons/updates i know that it has to decompress and recab the file, but it wont take as long... O_o the files the script adds >> thats only because the batch does check if the files exist before it tries to replace it. so if i run my script AFTER nLite. there would be no problems of that because i do check if the file exists on the i386 source to be replace.
  • Create New...