Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 07/27/2009 in Posts

  1. OnePiece Windows XP Post-SP3 UpdatePack v1.0.9 FINAL ENU Update (22 June 2017) Update (22 June 2017) Update (22 June 2017) Hash MD5 7A2AC7C5DD72BB4BC0C18D677A8B8FB1 Filesize: 206.18 MB (216198876 bytes) This XP post-SP3 All-in-One QFE/LDR Update Pack differs from RyanVM's/user_hidden's one as it includes by default more stuff like IE8, DX updates, all .NETs and WMP11 for an easier integration, along with official and nearly all request-only hotfixes (RyanVM's Update Pack is more selective with request-only hotfixes, which is fine): all in a few MBs and integrated in native "true" mode. Onepiece's XP Update Pack can be used along with Nlite from v1.4.9.1 or RVM Integrator from v1.6.1 b2.1 on a clean (untouched) XP SP3 ENU source. From v3.5.1 XP post-SP3 AIO UpdatePack can be integrated in a XP MCE 2005 SP3 source. Please don't ask for inclusions or exclusions: if you like a different configuration use one of the existing vanilla XP UpdatePacks with your preferred addons and you'll get your own XP disc without the need to remove anything. However if you don't like all the additional stuff included in OnePiece's XP Update Pack, you can easily uninstall some of them from Windows Components Wizard after windows setup. Then you can use a Run window to totally delete the components from your live system, typing this command: rundll32.exe advpack.dll,LaunchINFSection OPMWXPUP.inf,%OptionalComponentsNAME%.CleanUp Other supported switches are HIDE (removes the component from Windows Component Wizard list) and SHOW (shows the component in Windows Component Wizard list): Alternatively, you can also disable their installation listing the one you don't like to install (but not .net 2.0!) in a Winnt.sif file (see also here), under [components] section, with an "= off" by their side. For example, if you want to disable installation of Windows Desktop Search you will add this string: [Components]...WDSearch = off... All the Winnt.sif optional components codes are shown below. List only those you want to disable! BitLockerToGo = BitLocker To Go ReaderBrowserChoice = Browser ChoiceDirectX = DirectX Post-SP3 UpdateICCDSCD = Windows Feature Pack for StorageIMAPI2 = Image Mastering APIMDX = DirectX Managed CodeMSXML4 = MSXML 4.0 SP3 Parser (KB2721691)MU = Microsoft UpdateNETFX30 = Microsoft .NET Framework 3.0 Service Pack 2NETFX35 = Microsoft .NET Framework 3.5 SP1NETFX40 = Microsoft .NET Framework 4PowerShell = Windows PowerShellPowerShellISE = Windows PowerShell ISESilverlight = Microsoft SilverlightWDSearch = Windows Desktop SearchWgaNotify = Windows Genuine Advantage NotificationsWinRM = Windows Remote Management (WS-Management)WRMC = Windows Rights Management ClientXP_EOS = Microsoft Windows XP End of Service Notification Or, again, you can remove them from XP source after UpdatePack integration. Simply extract one or more of the small RVM-only addons from this suite and run a single new RVM-i integration session for every one of them on your updated source: OnePiece Remove AddOn Update (8 April 2014) Update (8 April 2014) Update (8 April 2014) Update (8 April 2014) Update (8 April 2014) Update (8 April 2014) Update (8 April 2014) Update (8 April 2014) Update (8 April 2014) Update (8 April 2014) Update (8 April 2014) Hash MD5 07C39C13FEC9099B603BC00C3B209234 Filesize: 19.8 KB (20303 bytes) NB *"REMOVE" addons are RVMIntegrator-only!! the entries.ini removal values are not supported by Nlite. ** Please note also that, due to a RVMi limitation, Removal Addons could break XP setup if integrated in the source at once in the same RVMi session: you must run your regular integration with Nlite or RVMi then, before making the .iso, one or more additional sessions of RVMi to finish off your source with the desired removal addon. ***OnePiece_Remove_Windows_Management_Framework_Core_AddOn.cab removes all single WinMFC components. So if you use it, you don't need to add: OnePiece_Remove_WinMFC(PowerShellv2)_AddOn.cab OnePiece_Remove_WinMFC(PowerShellISE)_AddOn.cab OnePiece_Remove_WinMFC(WinRM)_AddOn.cab to your integration list Let's recap! the right order is: Run RVMi and integrate Update Pack - rerun RVMi and integrate first Removal addon - rerun RVMi and integrate second Removal addon - ... - rerun RVMi and integrate last Removal addon - rerun RVMi and integrate your preferred SW - make the .iso. Integration side effects (not UpdatePack bugs): setuperr.log will point out harmless error messages about some IE files like imgutil.dll, inetcpl.cpl, inseng.dll, mshtml.dll, msrating.dll, pngfilt.dll, occache.dll, webcheck.dll (caused by the patched Syssetup.dll used for integration and then restored with the original one). If you don't tolerate it you can integrate in addition Onepiece Repair IE8 cosmetic problems addon which does nothing else than cleaning those false errors in your setuperr.log file. Please note that in some rare configurations the integration of this "repair" addon could cause issues, so we don't suggest to use it. OnePiece Repair IE8 Cosmetic Problems AddOn Updated (March 27-2009) Hash MD5 5C7AF8CA9F637C993F4AEEFFB63F39ED Filesize: 1.28 Kb There's an incompatibility of new msi installer official release KB981669 with a single app of Windows Live suite, Photogallery. Microsoft hasn't fixed it yet so if you need that specific app you must revert to very old KB967756 using this addon by 5eraph. If you don't want to loose the new version, there's also a temporary workaround for working systems that allows you to install Photogallery in an updated XP What's inside Onepiece's XP Update Pack: Hotfixes List What's new in latest release: Changelog To update the included Adobe Flash Player ActiveX use Create OnePiece Adobe Flash Player True AddOn and integrate the resulting OnePiece_Adobe_Flash_Player_v%Version%_True_AddOn.cab after UpdatePack. As an example this is v20.0.0.228 True AddOn just created with Create OnePiece Adobe Flash Player True AddOn OnePiece Adobe Flash Player v26.0.0.131 True AddOn Update (22 June 2017) Update (22 June 2017) Update (22 June 2017) Hash MD5 69F5516C9CCDF0DB62B11450925B7E5D Filesize: 9.04 MB (9483969 bytes) You can also extract both the UpdatePack and the OnePiece_Adobe_Flash_Player_v%Version%_True_AddOn.cab, delete entries_Flash.ini file, copy/move newer Adobe Flash Player AddOn files inside UpdatePack, overwriting the older one and then archive UpdatePack again. How to update the DotNet True AddOn Complete mirrors, including prerelease and legacy versions, are available here: Localized XP Updatepack final releases (main languages):Onepiece International XP Post-SP3 AIO Update Packs FINAL Made with DXUPAC! only DotNet LangPacks are not included (as they're useless) but if you want them too, integrate OnePiece_NetFxLangPack_SvcPack_AddOn_%Lang%.cab (download it from one of Onepiece's Files Repositories) after UpdatePack. All credits are in entries.ini file: however many, many thanks especially to RyanVM, Nuhi, Siginet and Xable.
    1 point
  2. 1. Install Windows 7 to VHD from DVD ----------------------------------------------------- With Windows 7, you now have the option to boot the OS from a VHD, a virtual disk file, instead of a partition. This way, you don't have to reconfigure your hard drive partitions. Limitations: Hibernate is not supported. Here are the simplified instructions: 1) Start Windows 7 installation from DVD. 2) Press Shift+F10 to start the command prompt. 3) Start diskpart. 4) Use the "create vdisk file=D:\Win7.vhd maximum=xxxxx" to create a virtual hard disk. Choose your drive and filename accordingly. xxxxx is in MB. 5) Type "select vdisk file=D:\Win7.vhd". 6) Type "attach vdisk". You will get a confirmation that it was attached. 7) Type "exit" to exit diskpart. And then close the command prompt. 8) Click on "Install Now" and install as you would normally by clicking on "Custom Install". Choose your attached vdisk as the location. The installation takes care of adding the boot option to bcd. You don't have to do anything. See Virtual Hard Disk Booting on a tutorial for VHD booting. also check this out: Install Windows 7 to a VHD and add boot option to Vista's menu. Basically, instead of installing windows 7 to your physical HDD by getting rid of Vista or even dual booting off another partition, you can install to a virtual HDD (in VHD format), and boot off the VHD so you actually get the hardware functionality to play with!! Build 7068 does not allow calculation of the WEI score. 2. Install Existing VHD to Boot Menu of Windows 7 ------------------------------------------------------------------- If you already have a VHD that you want to boot from, you can simply add it to the boot menu rather than going through the above steps. If you have a Virtual PC image, for example, you can syprep it, then add it to Windows 7 menu. Vista's boot manager will not work - you have to update it to Windows 7 boot manager if you want this to work. First, here how to add the vhd to the boot menu: Open elevated command prompt, then type the following commands in sequence: CODE C:\>bcdedit /copy {current} /d "My New VHD Description" C:\>bcdedit /set <guid> device vhd=[driveletter:]\<directory>\<vhd filename> C:\>bcdedit /set <guid> osdevice vhd=[driverletter:]\<directory>\<vhd filename> C:\>bcdedit /set <guid> detecthal on Note: The first command will Return the GUID of the Loader Object that you will use to replace <guid> below Note: vhd=[driveletter:]\<directory>\<vhd filename> is the new syntax supported for BCDEdit.exe to locate VHD File and Bootmgr will locate the partition containing the VHD File to boot from. Type bcdedit /v to check the bcd store. 3. How to Boot VHD without Windows 7 Installed ----------------------------------------------------------------- If you have Vista and want to boot a Window 7 VHD, then you need to copy the boot manager of Windows 7 to Vista's partition. You need to copy C:\bootmgr and C:\windows\system32\bcdedit.exe to an external source from Windows 7. You could extract these files from the Windows 7 VHD using WinImage or another program. Then, open an elevated command prompt in Vista and unhide bootmgr (attrib -h -r -s bootmgr) and replace it with Windows 7's. Do same for bcdedit. You might consider making backup copies of these files before replacing them. Then, add the VHD item to the boot menu using #2 above. 4. How to Remove ------------------------- To remove, run the following command in a elevated command prompt: CODE bcdedit /delete {guid} /cleanup Delete the vhd file. Greets to spacesurfer!
    1 point
  3. We're pleased to inform you that our forum has successfully been upgraded to the latest version of IPB forum software. For a start, you should mark board as read so we can avoid server crashes Hopefully you'll all enjoy this new look and features. We still have to update several areas of the board, but no matter that, it can safely be used from now on. Wincert.net Admin Team.
    1 point
  4. Th5Mupp5t

    Problem with WMP12

    Ok i've just did what you've done and i'll get back to you with it. I'll edit this post and tell you how i got on. EDIT: Right i've just got all my music files back into windows media player. What i did is right click on Music (In the list on the left hand side) and click on Manage Music Library. I have my music on a different HDD so what i did was removed that folder. added an album folder. then it added my music files. So then I removed that folder from the Manage Music librarys and then added back the folder with ALL my music files. So if you have yours in the default Music folder add that to the list and it should work. (Please tell me it does!!) LOL
    1 point
  5. Th5Mupp5t

    Problem with WMP12

    Ok this sometimes happens with me and what i normaly do is highlight all music files (not folders if they are in folders then go into them and highlight all the music files in there) and after you've highlighted right-click and click on Add To Windows Media Player List. It should play them but also it should just add them to the library. This should work.
    1 point
×
×
  • Create New...