Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by kukubau

  1. Was this integrating into Windows 8.1 RTM or Windows 8.1 Update 1? I used Windows 8.1 Enterprise + Update 1 iso - en_windows_8.1_enterprise_with_update_x64_dvd_4065178.iso I've built another iso with wintoolkit (latest build) today and I've added those two updates under the silent installers. The installation hanged in Virtual Box with the RunOnce window opened. It wouldn't finish installing the updates no matter how long I waited for it.
  2. Needles to say, I've put in wintoolkit KB2919355 and all the other included updates before KB2962409 and KB2955164.
  3. Hi I've just tried the latest Wintoolkit build and two updates don't integrate properly: KB2962409 and KB2955164. They show up in Windows Update. What is curious is although the *.MSU's are 49.6 MB and respectively 97.4 MB, after running Windows Update they show up as being only couple of Kbytes large (~200 KB). Thanks kukubau
  4. Hi I don't know if this a bug or not, but right after I open the "All in one Integrator" and load the pre-existing preset that shows up, the one that got saved after the previous session, not all the updates get loaded. In my case just 2 out of 9. To make it work I have to delete the saved preset and import it again. Only then the updates that should've been loaded in the 1st place appear under the Upates+Languages tab. Thank you
  5. Unknown Error X: Status: Installing Driver: I get this error for every driver I'm trying to integrate. Using the latest version Adding them by DISM command line works but not when using the app's Driver Installer option. Ty
  6. Did you use the latest tool (dated August 15th) for that??? With the previous build before this it didn't work as I explained in my post. I'll build the addon with this latest tool and get back to you.
  7. Thanks, long time since I had problems with txtsetup.sif. No, I didn't integrate IE8 twice. I always use a clean source(XP+SP3) when building my nlited xp. I've tested this 4 times. Twice I added only the IE8(with KB2183461) addon to nlite and twice IE8(with KB2183461) + with the other post SP3 hotfixes. It crashes because of the last KB2183461 hotfix. If I build the addon just with the previous files (KB982381 not replaced-that worked) and add KB2183461 next in nlite, no issues what-so-ever. If I build the addon with KB2183461 replacing KB982381, it crashes. So in nlite it works if I have it like this: OnePiece_IE8_WinXPSP3_True_AddOn_FRA.7z - it was built for the French language. IE8-WindowsXP-KB2183461-x86-FRA.exe the setup doesn't crash. If I replace KB982381 with KB2183461 and build the addon, I get errors after errors. I'll check txtsetup.sif. So the culprit is IE8-WindowsXP-KB2183461-x86-FRA (IE8 cummulative addon, same thing with ENU addon) that messes things up. I've noticed onepiece updated his update addon creator. Is it going to fix this or not? I guess not. Greets
  8. 10th of august has brought new updates including for IE, some replacing older ones. I've rebuilt my IE8 addon replacing KB982381 with KB2183461 because the MS bulletin is saying so. Now I get this error while copying files:"Setup cannot copy the file: ieframe.mui" and lots of errors during installation. If I add the previous addon built with KB982381, I get no errors. Any solution?
  9. nonno When I try to build a localized french IE8 true-addon, IE8 exe is left out, only the hotfix files are added to the addon. IE8-WindowsXP-x86-FRA.exe IE8-WindowsXP-KB982632-x86-FRA.exe IE8-WindowsXP-KB982381-x86-FRA.exe IE8-WindowsXP-KB981332-x86-FRA.exe IE8-WindowsXP-KB976662-x86-FRA.exe IE8-WindowsXP-KB971961-x86-FRA.exe Is there a solution to this?
  10. Hi I don't know who to ask, you or Nonno Fabio?!?!!? I looked over the hotfixes included in the post sp3 addon pack and have noticed there are a lot of hotfixes included that I have never seen pushed over by windows update. Is it really needed to include them?!?! Like: KB817688 - "Error on a Request to Write Data to Media" error message when you use Ntbackup.exe KB897571 - FIX: A DCOM static TCP endpoint is ignored when you configure the endpoint for WMI on a Windows Server 2003-based computer etc. I want to create an addon pack just with post SP3 hotfixes WU is pushing them after a Windows XP SP 3 installation. Nothing more. Why do I need to include all the extra garbage?!?!?! I know that if I create the pack with only those hotfixes, nlite throws some errors and the instegration process breaks. Let me know. Thanks.
  11. @OnePiece Can you post all the hotfixes and updates you used for your latest created addon? A spoiler would be nice. Thanks.
  12. OnePiece There are two English threads regarding the addon creator and one Italian. Wouldn't be better to merge the two English threads in one? It is very confusing when I'm looking for an answer to mine or other's questions. I get an error when trying to create a Post Windows XP SP3 addon. Do I have to add all the post SP3 hotfixes? Which one? What does Nonno Fabio mean by "exactly all the hotfix installers and additional components listed in Onepiece's AIO UpdatePack topics" ??? Where are those topics??? Can you post all the hotfixes and updates you used for your latest created addon? A spoiler would be nice.
  13. @Jonnyboy I know that your time is scarce, but you mentioned you've been working on an update. Is it still on? Greets.
  14. KB898461 is not obsolete. Whatever I use to integrate post sp3 addon pack created with your tool, it breaks installation. Nlite also throws that H-Index error. What do you mean by "needs all hotfixes"??? I need to create one only with 56 hotfixes or so. It doesn't work for me.The IE8 addon function works though. That is all I find useful about it. I will continue to use nlite for integrating hotfixes. Waiting for an update.
  15. I never select "install the extensions globally", so it has to be something else that's breaking the installation. Thank you. Waiting for your last version.
  16. @Jonnyboy Hi I am using your addon since ever and I find it very useful. But using the las two versions I stumbled upon a few problems. First, a question or two. What is with this function "Addon Installation Paths" "Click to enter the Addon's Destination folder of your choice, or you can create a new folder.". I don't want to enter a new folder for the addons, I want to use the default path. What is the default path? c:\Program Files\Mozilla Firefox or the profile path C:\Documents and Settings\Andrei\Application Data\Mozilla\Firefox\Profiles\random_name.default By default, in your tool is entered C:\Program Files\Firefox. If that is set,will FF install there instead of c:\Program Files\Mozilla Firefox\ ?!?! I just reinstalled XP today and ran FF silent built with your addon maker and it failed to install fully. I had to install the original Firefox Setup 3.6 Beta 1 over the first installation so I could open FF. Bad thing is that all my addons were gone. Good thing is that all the bookmarks were there. That was a life saver. Do you know what did I do wrong? I am attaching the settings.rar to see for yourself. One thing that has come up my mind is that problems could have arisen due to the fact that I didn't use the FF 3.6 beta 1 from the link inside the addon maker, but FF 3.6 bet 1 build 3 from Mozilla's ftp. It is very unlikely as I did that before and never had issues. I am eagerly waiting for your reply Thank you Kukubau
  17. It seems that whatever I do and whatever I use nlite or RyanVM Integrator, the setup breaks when using a source that was added an post SP3 update pack created with your tool, to it. If I use nlite for integrating it I get this If I use RyanVM I get a lot of missing files. Probably they are referenced and not found after DRIVER.CAB recompression or don't know. Anyway my tests were successful only when integrating the IE8 addon pack (with nlite). The post SP3 addon tests were all failures. Here are the hotfixes I used: rootsupd.exe Windows-en-US-KB943729.exe Windows-KB909520-v1.000-x86-ENU.exe WindowsMedia11-KB929399-v2-x86-INTL.exe WindowsMedia11-KB939683-x86-ENU.exe WindowsMedia11-KB954154-x86-ENU.exe WindowsXP-KB905474-ENU-x86.exe WindowsXP-KB923561-x86-ENU.exe WindowsXP-KB941569-x86-ENU.EXE WindowsXP-KB942288-v3-x86.exe WindowsXP-KB946648-x86-ENU.exe WindowsXP-KB950762-x86-ENU.exe WindowsXP-KB950974-x86-ENU.exe WindowsXP-KB951066-x86-ENU.exe WindowsXP-KB951376-v2-x86-ENU.exe WindowsXP-KB951748-x86-ENU.exe WindowsXP-KB951978-x86-ENU.exe WindowsXP-KB952004-x86-ENU.exe WindowsXP-KB952287-x86-ENU.exe WindowsXP-KB952954-x86-ENU.exe WindowsXP-KB954459-x86-ENU.exe WindowsXP-KB955069-x86-ENU.exe WindowsXP-KB956572-x86-ENU.exe WindowsXP-KB956744-x86-ENU.exe WindowsXP-KB956802-x86-ENU.exe WindowsXP-KB956803-x86-ENU.exe WindowsXP-KB956844-x86-ENU.exe WindowsXP-KB957097-x86-ENU.exe WindowsXP-KB958644-x86-ENU.exe WindowsXP-KB958687-x86-ENU.exe WindowsXP-KB958869-x86-ENU.exe WindowsXP-KB959426-x86-ENU.exe WindowsXP-KB960225-x86-ENU.exe WindowsXP-KB960803-x86-ENU.exe WindowsXP-KB960859-x86-ENU.exe WindowsXP-KB961118-x86-ENU.exe WindowsXP-KB961371-v2-x86-ENU.exe WindowsXP-KB961501-x86-ENU.exe WindowsXP-KB967715-x86-ENU.exe WindowsXP-KB968389-x86-ENU.exe WindowsXP-KB968537-x86-ENU.exe WindowsXP-KB969059-x86-ENU.exe WindowsXP-KB970238-x86-ENU.exe WindowsXP-KB970653-v3-x86-ENU.exe WindowsXP-KB971486-x86-ENU.exe WindowsXP-KB971557-x86-ENU.exe WindowsXP-KB971633-x86-ENU.exe WindowsXP-KB971657-x86-ENU.exe WindowsXP-KB973354-x86-ENU.exe WindowsXP-KB973507-x86-ENU.exe WindowsXP-KB973525-x86-ENU.exe WindowsXP-KB973815-x86-ENU.exe WindowsXP-KB973869-x86-ENU.exe WindowsXP-KB974112-x86-ENU.exe WindowsXP-KB974571-x86-ENU.exe WindowsXP-KB975025-x86-ENU.exe WindowsXP-KB975467-x86-ENU.exe WindowsXP-WindowsMedia-KB952069-v2-x86-ENU.exe WindowsXP-WindowsMedia-KB954155-x86-ENU.exe WindowsXP-WindowsMedia-KB968816-x86-ENU.exe WindowsXP-WindowsMedia-KB973540-x86-ENU.exe Should I exclude the media player's hotfixes like WindowsXP-WindowsMedia-KBxxxxxx-x86-ENU.exe and create a WM player addon?
  • Create New...