Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country


Everything posted by Tinywoods

  1. WindowsXP-KB896727-x86-JPN.exe was Deleted Looking for the correct folder, wait a moment windowsmedia10-kb902344-x86-intl.exe(added: Nov 01)
  2. Sorry, I thought you used Japanese OS because your name. In case of JP OS, we have to delete some lang-data.
  3. Is there any way to change font color category by category? I know font color can be changed if I modify WPI.CSS. But it is impossible to change the color category by category. In case of WPI 3.5, I could change them if I use below commands, but I can not do the same way in 4.3.5 cat[pn]=['<u><font color=#000099">Security</font></u&gt]
  4. Use "AutoIt". It's the easiest way. Search "AutoIt".
  5. Finally, I could install 16 Installshield update files. I could not modify WPI files but AutoIt. Thanks for glent’s advise, I was able to stick on a way of batch file install. Here is my script ;; Installshield update ; Move msi files from DVD DirCreate("C:\WPI\Temp") Sleep(1500) FileCopy("ISScript7.msi", "C:\WPI\Temp\*.*", 1) Sleep(1500) FileCopy("ISScript8.Msi", "C:\WPI\Temp\*.*", 1) Sleep(1500) FileCopy("isscript9.msi", "C:\WPI\Temp\*.*", 1) Sleep(1500) FileCopy("ISScript10.Msi", "C:\WPI\Temp\*.*", 1) Sleep(1500) FileCopy("ISScript1050.Msi", "C:\WPI\Temp\*.*", 1) Sleep(1500) FileCopy("ISScript11.Msi", "C:\WPI\Temp\*.*", 1) Sleep(1500) ; Delete Old Installshield files from C: DirRemove("C:\Documents and Settings\Administrator\Local Settings\Temp\{B0530A72-3B27-4A74-9EC0-CC3D5AE435A5}", 1) Sleep(1500) DirRemove("C:\Program Files\Common Files\InstallShield\engine", 1) Sleep(1500) DirRemove("C:\Program Files\Common Files\InstallShield\Driver\7", 1) Sleep(1500) DirRemove("C:\Program Files\Common Files\InstallShield\Driver\8", 1) Sleep(1500) DirRemove("C:\Program Files\Common Files\InstallShield\Driver\9", 1) Sleep(1500) DirRemove("C:\Program Files\Common Files\InstallShield\Driver\10", 1) Sleep(1500) DirRemove("C:\Program Files\Common Files\InstallShield\Driver\1050", 1) Sleep(1500) DirRemove("C:\Program Files\Common Files\InstallShield\Driver\11", 1) Sleep(1500) DirRemove("C:\Program Files\Common Files\InstallShield\Professional\RunTime\07\00", 1) Sleep(1500) DirRemove("C:\Program Files\Common Files\InstallShield\Professional\RunTime\07\01", 1) Sleep(1500) DirRemove("C:\Program Files\Common Files\InstallShield\Professional\RunTime\08\00", 1) Sleep(1500) DirRemove("C:\Program Files\Common Files\InstallShield\Professional\RunTime\09\00", 1) Sleep(1500) DirRemove("C:\Program Files\Common Files\InstallShield\Professional\RunTime\09\01", 1) Sleep(1500) DirRemove("C:\Program Files\Common Files\InstallShield\Professional\RunTime\10\00", 1) Sleep(1500) DirRemove("C:\Program Files\Common Files\InstallShield\Professional\RunTime\10\01", 1) Sleep(1500) DirRemove("C:\Program Files\Common Files\InstallShield\Professional\RunTime\10\50", 1) Sleep(1500) DirRemove("C:\Program Files\Common Files\InstallShield\Professional\RunTime\11\00", 1) Sleep(3000) ; Install the latest Installshield engines RunWait("IkernelUpdate2.exe") Sleep(2000) RunWait("IkernelUpdate6.exe") Sleep(2000) RunWait("msiexec.exe /qb /i C:\WPI\Temp\ISScript7.msi /qb") Sleep(2000) RunWait("msiexec.exe /qb /i C:\WPI\Temp\ISScript8.Msi /qb") Sleep(2000) RunWait("msiexec.exe /qb /i C:\WPI\Temp\isscript9.msi /qb") Sleep(2000) RunWait("msiexec.exe /qb /i C:\WPI\Temp\ISScript10.Msi /qb") Sleep(2000) RunWait("msiexec.exe /qb /i C:\WPI\Temp\ISScript1050.Msi /qb") Sleep(2000) RunWait("msiexec.exe /qb /i C:\WPI\Temp\ISScript11.Msi /qb") Sleep(2000) ; Install the latest Installshield update files ; Use "RunWait" instead of "Run" RunWait("InstallShieldEngineUpdate700.exe") Sleep(2000) RunWait("InstallShieldEngineUpdate701.exe") Sleep(2000) RunWait("InstallShieldEngineUpdate901.exe") Sleep(2000) RunWait("InstallShieldEngineUpdate1000.exe") Sleep(2000) RunWait("InstallShieldEngineUpdate1001.exe") Sleep(2000) RunWait("InstallShieldEngineUpdate1050.exe") ; Only 1100.exe popup a window, so can not use "RunWait" If ProcessWaitClose("InstallShieldEngineUpdate1050.exe") then Run("InstallShieldEngineUpdate1100.exe") Endif WinWait("InstallShield", "InstallShield 11") WinActivate("InstallShield", "InstallShield 11") Sleep(2000) ControlClick("InstallShield", "", "Button1") ProcessWaitClose("InstallShieldEngineUpdate1100.exe") Sleep(3000) ; Delete C:\WPI\Temp and all files DirRemove("C:\WPI\Temp", 1) Sleep(3000) In this time, I have no problem about number of command lines. However, I wolud be pleased if I could have more commandLines.
  6. Hello glent, Thank you for your interest. Yes, to make (a) batch file(s) is the best way, I agree. But I got in trouble to install apps using a batch file. Honestly speaking, I do not know how to write a batch file to run all files that I want to install except AutoIt What I want to do is…. Installing latest installshield update files that I can get from Installshield update . There are 8 installshield engines (Ver. 2,6,7,8,9,10,10.50,11 with *.msi) and 8 update files (Ver.700 to 1100 with *.exe), totally 16 files. In addition, I need to delete some old Installsheild program files from C:\Program Files\Common Files\InstallShield before updating, so I use AutoIt to delete them. Therefore, there are 17 files that I want to execute. What I did…. I made an AutoIt batch file to install 16 files + delete old files. Though I could run 16 files from my AutoIt batch file, only 8 update files were executed in onetime, not file by file. (*.msi files could start file by file). I did ‘WinWaitClose (“”, “DONE”)’, but it did not work. I do not understand reason why “WinWaitClose” commands did not work for those Installsheild file. I guess “WinWaitClose” command does not work for Splash Text in popup window. So, I have to give up using AutoIt for 16 files installation this time. Though I do not know programming at all, I edited 3 WPI *.js files to increasing command lines. When I run WPI to install 17 files, CommandLine8 was executed at first. After that CommandLine9 was executed, then #10, 11, 12…17, 1, 2, 3….6 were executed file by file. I would like to install 17 files in the right order.
  7. Hello For Japanese, I updated lang.js file. BTW, when I visit http://members.aon.at/equinox/wpi/, I got 403. Why?? lang.js
  8. Hello I want to add more command lines in one installation. I mean, in case of WPI 3.5.1.that I use, I can run only 6 commands in one install. cmd1[pn]=['CommandLine 1'] cmd2[pn]=['CommandLine 2'] | cmd6[pn]=['CommandLine 6'] ....like this. I want to perform at least 17 commands in one installation. I modified below 3 files, then I could run 17 commands, but WPI starts from “CommandLine 8”, not CommandLine 1. -configwizard.js -generate.js -program.js Will you let me know how I can modify *.js to add commands?
  9. Hello Just try as below. 1. Make and keep a copy of "lang.js" file for emergency 2. Open "lang.js" (edit mode) 3. Delete all language data from the file except your language, and save. In my case, it works. (but WPI version is 3.5.1)
  10. I edited the top of my thread. * 959KB: SVC-HF1\Windows-KB890830-V1.9-JPN.exe * 4848KB: SVC-HF1\WindowsXP-KB896688-x86-JPN.exe * 528KB: SVC-HF1\WindowsXP-KB899589-x86-JPN.exe * 5086KB: SVC-HF1\WindowsXP-KB900725-x86-JPN.exe * 1024KB: SVC-HF1\WindowsXP-KB901017-x86-JPN.exe * 4823KB: SVC-HF1\WindowsXP-KB902400-x86-JPN.exe * 1363KB: SVC-HF1\WindowsXP-KB904706-x86-JPN.exe * 608KB: SVC-HF1\WindowsXP-KB905414-x86-JPN.exe * 570KB: SVC-HF1\WindowsXP-KB905749-x86-JPN.exe
  11. I edited the top of my thread. Windows-KB890830-V1.8-JPN.exe
  12. ironside, Have you ever tried to put "GDITOOL.EXE" in SVC-CF2 then running "XPCREATE.CMD"? I think you can use "GDITOOL.EXE" in "SVC-CF2" instead of "gdidettool.exe" in "SVC-GDI". In my case, I can use "gdidettool.exe" in "SVC-GDI" without no error. But after running XPCREATE.CMD, I can see "GDITOOL.EXE" in CF2 that is created automatically.
  13. OK I understand. Thank you, Bitfrotter Sorry, jobbie.
  14. jobbie, Why don't you check XPCREAT HOTFIXES? Or my thread as you should know. Update files for windows update are WGAINSTALL.EXE WindowsUpdateAgent20-x86.exe above 2 files.
  15. I edited the top of my thread.
  16. Hello GreenMachine, It was rash of me to publish the patch file without knowing you. I deleted the patch file from previous my post. I like your XPCREATE which is very famous in Japan as a convenient tool. However, due to language problem, XPCREATE has not been able to use on Japanese OS. Many Japanese people who were interested in slipstream-tools knew about it. A Japanese guy made patches for XPCREATEs since XPCREATE was introduced in Japan. I expected a new patch for the new XPCREATE from him, but I found he closed his website where we can get some patches for XPCREATEs. I do not know the reason why he closed the website. I’m afraid that there were few needs to have XPCREATE patches because nobody could get the latest XPCREATE until quite recently. After few days he close his site, I noticed that the new XPCREATE was published. And no USER ID is required. I was happy to hear that. Then, I decided to modify an old patch to match with the new XPCREATE. I have not enough skill to make a patch program. To modify the old patch was just what I could. GreenMachine, you will receive PM in your mail box. I’ll inform you where you can get my modified XPCREATE.CMD and the patch file. Please check them. TW ************ Edited I could not sent you PM. How can I inform you?
  17. Hello GreenMachine, I think we need WindowsXP-KB886677-x86-XXX.exe in SVC-HF1 folder in a case of XP.
  18. Hello, Japanese and other Asian languages users. As you may know, without file modification, we can not use XPCREATE due to 2 byte OS. No folder is produced (SVC-HF1, HF2 and so on) in the XPCREATE folder, strange fonts may be appeared and stop installing Then, I made a patch file for Japanese. Though I've not checked it yet, I hope it works on other Asian OS. Step 1) Install XPCREATE Aug 20 version. Step 2) Set your WinXP CD on your CD-drive or set a image file on your virtual CD-drive.   ***Don't click XPCREATE.CMD before step 3). Step 3) W-crick XC_AUG20_2byte.EXE. (You’ll see patch result) Step 4) Revise your new XPCREATE.INI  If you do not understand well how to modify the INI file, pls refer my INI file as follows. Step 5) W-click XPCREATE.CMD   Folders (SVC-HF1, HF2 and so on) should be appeared in the XPCREATE folder. Step 6) Set Hotfixes and Bootimage (if there is no boot image file in the BOOT folder) Step 7) W-click XPCREATE.CMD  File copy starts, and in the same time, CD source is checked.   "Looking for CD Source & Create local CD Source" may take 30-60sec. Step 8) ISO file will be in the XPCREATE folder.  [XPCREATE] BOOTIMGFILE=BOOT\XPCTBOOT.BIN <------ CDBURNER= <------ CDERASE=NO CDLABEL=WXPSPOEM_JA <------ CDSPEED=12 CDTYPE=CD COPYSOURCE=NO DELISOS=NO DELROOT=YES DELTEMP=YES DOCABS=YES DOCD=YES DOISO=YES DOPATH=NO DOSATA=YES DOSVCPACK=YES DRIVERDIR=$OEM$\$1\Drivers\Nic\LAN;Drivers\VGA\ATI <------ EXITQUIET=NO OVERWRITEOEM=YES QLOG= RENAMEF=YES SILENTINSTALL=YES SLIPHF1=YES SLIPHF2=YES SLIPMDC=YES SLIPSPK=YES STARTSWITCH=/WAIT /MIN USERFILESCD=FILESCD USERWINLANG=JAP <------ XPISO=WXPSPOEM_JA.ISO <------ XPSOURCE=CDSOURCE <------ marking points should be changed Japanese (patch for 2 byte OS) [the file was removed, sorry] I've not checked whether the patch works on other XP machines or not, however, it may works on Asian OS, I hope. If your XPCREATE does not work on your OS, pls try it. On limited western languages OS such as ESP, FRA, PLK, PTB, TRK and ELL you can NOT use this patch !! Cheers,
  19. Hello, AUG 18 version did not work. (did not start) AUG 20 version also did not work on JPN OS. I'm tring to slove this problem. There are some errors that I've never seen. ***************** EDIT ***************** I made a patch for Japanese. Pls see XPCREATE Aug20 for Japane and other Asian people **************** EDIT ***************** The file was removed, sorry
  20. WGAINSTALL.EXE may not work in SVC-CF2 but works in SVC-EXE
  21. Regarding Current Hotfixes in xpcreate.com, we may not have "SVC-WUA" folder in Feb version, I'm afraid. PS. WindowsUpdateAgent20-x86.exe works in SVC-MRT of Feb version.
  22. PeterGau, thank you for your support. But.... Ok, I understand. Someone think nlite is better than XPCREATE. I do not care, someone loves nLite and other guys love other tools. There are lots of auto patch tool for Windows. Most of them are nice tools, I believe. I do not want to talk about which tool is the best one. I just want to ask readers about Hotfix and other update files for XPCREATE, and useful information for XPCREATE users. XPCREATE is available now again. Will you please do not talk about other tools and Strength and weakness points of tools in this thread?! ************************************** Edit GOOD NEWS ! ************************************** GM will come back soon, and Hotfix information in XPCREATE site has been updated. Edit2 However, it is a list for Next coming XPCREATE. Because current XPCREATE does not have SVC-WUA folder. Don't worry, WindowsUpdateAgent20-x86.exe works in SVC-MRT. I comfirmed.
  23. Still I'm waiting your information. Thanks readers !
  24. Hi jobbie. Yes, I will let you know but in another thread. Pls visit "the latest update files" because I want to keep the thread. If you have anything about windows update files for XPCREATE, let's discuss there.
  25. Additional information in Aug 17. KB892130 wgainstall_9160b6b3929938243b7d18417810677d9b9983b7.exe was added on the top of this thread. I renamed this file neme from wgainstall_9160b6b3929938243b7d18417810677d9b9983b7.exe to KB892130-WGAInstall.exe, because the original file name is too long to burn on a DVD. KB892130-WGAInstall.exe is an install for LegitCheckControl.dll and GWFSPIDGen.dll. Actually, the file is not windows update file, I think. It is a update file for windows update. Cheers,

  • Create New...