-
Posts
1,954 -
Joined
-
Last visited
-
Days Won
26
Content Type
Profiles
Forums
Events
Posts posted by OnePiece
-
-
Hi dareckibmw , this was really cool , I did not notice at all hmmm
I've only seen your last post in list of new post to read today, and I did not see the date of the first post, and I saw that the bjfrog used the Windows 7 (to see in that OS was doing the test) I would shrewd immediately, since windows 7 and released in 2009 ehhhhhhhh, but did not see the date of the first post hmmmmmmm
thanks anyway for reporting
Ciao.
-
Hi bjfrog, in the Microsoft Silverlight multi-OS True AddOn INTL and an example how to register file with spaces in destination path
16425,,regsvr32.exe,,,"/S ""%16426%\%SilverlightDir%\xapauthenticodesip.dll"""
try
11,,regsvr32.exe,,,"/S ""%16422%\Beyond Compare 3\BCShellEx.dll"""
11,,regsvr32.exe,,,"/S ""%16422%\Elaborate Bytes\VirtualCloneDrive\ElbyVCDShell.dll"""
Sorry for my English
Ciao.
-
Link gia ripristinati
Ciao a tutti.
-
Ragazzi il link in primo post erano giù, adesso messi in SkyDrive Google Driver ect ect cosi non saranno più offline in futuro diciamo, cosi con questo caso anche già aggiornato
Aggiunti/Aggiornati
KB907980
MSXML 4.0 SP3 v4.30.2114.0 (KB2721691)
MSXML6 v6.20.2012.0 (KB2721693)
Adobe Flash Player v11.4.402.287
Microsoft.NET Framework v1.1.4322.2497
Microsoft.NET Framework v2.0.50727.3639
Microsoft Update v7.6.7600.257
MRT v4.13
Ciao a tutti.
-
Step 1 - I modified the entries_imgburn.ini and imgburn.inf like the example found in this video
Step 2 - Created CAB using DX Tools
Step 3 - Added to WinNT6.x True Integrator (Ignore-Ceck). The AddOn appears in the list at the bootom.
OK (but in this case regard Step 3 - if you choose Check-State you will see that the WinNT6.x True Integrator do not added the AddOn in the list)
Setp 4 - Click Apply -- DISM appears to sucessfuly compete the operation
2012-10-22 01:56:07 : Processing 2 of 2 - Adding package ImgBurn~~True AddOn~Multilanguage~2.5.7.0~Copyright © 2005 - 2012 LIGHTNING UK!~OnePiece~http://www.imgburn.com/ - C:\Users\Bryan\Desktop\System Builder\Addon CABS\ImgBurn_v2.5.7_INTL_TRUE_ADDON.cab
2012-10-22 01:56:09 : The operation was successful.However, the addon does not appear in the upper section 'Optional Component List'. Also the addon does not appear in the mounted image.
No
2012-10-23 02:05:46 : Mounting image - 1~Microsoft Windows PE (x64)~Microsoft Windows PE (x64)~1,188,599,952 bytes~x64~<undefined>~6.2.9200~16384~0~WindowsPE~WindowsPE~WinNT~~WINDOWS~2964~13133~7/26/2012 - 8:39:55 AM~10/9/2012 - 5:30:29 PM~en-US (Default)~D:\HRM_CCSA_X64FRE_EN-US_DV5\sources\boot.wim~D:\MountDir_TMP
2012-10-23 02:06:22 : The operation was successful.
2012-10-23 02:08:10 : Adding package ImgBurn
2012-10-23 02:08:10 : Processing 1 of 1 - Adding package ImgBurn~~~Multilanguage~2.5.7.0~~~http://www.imgburn.com/ - C:\Users\OnePiece\Desktop\Ricks_ImgBurn2.5.7_Intl_addon.cab
2012-10-23 02:08:14 : ERROR: Error: ImgBurn.inf - ImgBurn.exe not found.
@Error - I think you tried to Install\Integrate the AddOn in Windows x64 (DX WinNT6.x True Integrator rightly does not Install\Integrate the AddOn, because the AddOn indicates to install only Windows x32/x86 32 bit)
[sourceDisksNames.x86]1="Windows CD/DVD-Rom","ImgBurn.cab",,"i386"
AddOn tells them to find those files only in systems 32 bit INF SourceDisksNames Section
if you want to integrate the AddOn also on x64, also need to change this line so (and very important always need to ask the Creator of the AddOn if its AddOn can also be installed in Windows x32 or x64 ect ect)
[sourceDisksNames]1="Windows CD/DVD-Rom","ImgBurn.cab",,"i386"
Ciao.
-
@Legolash2o
and an easy thing, need only change the hex, I do not know the exact hex now, but I think and something that you can easily find, just compare the file after modification that makes the Theme Patcher and many other tools in web, After just open file in binary mod and change the binary\hex, save the file, and it's okay
here as it was the addon for windows xp (fate by Zacam) 6 years ago
;XP SP2
I386\UXTHEME.DLL|6.0.2900.2180|113178|83EC1C568D4DE4|33C0C9C2040090
Ciao.
-
Hi Legolash2o, perhaps better to move the topic here http://www.wincert.net/forum/forum/176-microsoft-windows-7/
Ciao.
-
It's recommended you always choose the Ignore-Check (is already default). only in cases like this we talk about 1-2-3 update choose
Check-State, Check-State is OK but it takes a very long time, it is not recommended to be used by defualt
always choose the Ignore-Check, and click Apply ect ect, and after installation ect ect always go to the %Temp%\WinNT6TI.log to see if everything went ok, and if not (why not ect ect)
when entering online Nonno Fabio, tell all the most well in good English
Ciao.
-
@Geej
I can not promise anything, but when I have free time when will update the WinNT6.x True Integrator, I see even this thing if we hold to do something about it, depends on how microsoft interpret it Now with the release of new tools, but it seems hmmmmmmm, microsoft already ignored a WinVista ehhhh, so in XP certain feature working but are not 100% OK, and useless now, maybe XP is the best system ever, but it is very very old now Ehhhhhh
@dotfusion
Yes, can add them, in everything he does DISM no one else knows better than DISM (so always indicates the update.cab or MSU to DISM, after and DISM see if the package is valid or need to install or not ect ect)
however in all cases where it doubts click Check-State in ComboBox
so the WinNT6.x True Integrator calls the DISM to Check if the packet is valid or not ect ect, default and Ignore-Check because a certain process takes a little time ehhhhh, nobody wants to add 200-300 update and wait for minutes and minutes ehhhh (because during the installation the DISM will check again the files before installing, so you double check hmmmm), however for cases just like yours we have added the option
however we have also added our manual controls us, and in this case the WinNT6.x True Integrator believes that he is working on update.cab or update.msu, so it tells you that the update for a newer OS
in this case ignore the message and click YES, and you will be Ok
we added that also WinNT6.x True Integrator that do have some control (in experimental stage), and control is right But only in that time we forgot to indicate to the WinNT6.x True Integrator that some control do not do it with the Feature Pack ect ect, because in Feature Pack versions change is not always connected with the OS version ect ect, and in this case those archive.cab are feature mod (As you can see already in the first image above, Release Type = Feature Pack), so in these cases always click YES (ignore the message)
However for everything else always check the %Temp%\WinNT6TI.log
sorry again for my English
Ciao a tutti.
-
Ragazzi tentando oggi aprire il vecchio laptop quello X64 (che dopo anni di VM e andato ehhhh) o notato che il DXTool lavorava Ok ma non al 100% in in un sistema 64 Bit riguardo Grant Admin Full Control (Permissions and Ownership), hm forse AuotoIt o che non so, comunque serviva compilare anche il exe in 64 Bit per essere 100% OK in sistemi x64, cosi chi e in 64 Bit e consigliato usare il DXTool x64
Ciao a tutti.
-
usbvideo.sys = http://support.micro...=971323&kbln=sv
usbccid.sys = http://support.micro...=967048&kbln=sv
dumpdrv.sys = http://support.micro...=916157&kbln=sv
for everything see the OPMWXPUP.inf in update pack
Ciao.
PS: uses spoiler in the previous post, because the post and very long
-
http://www.wincert.n..._100#entry90289
each hotfix enu which is ok in other languages, always need to remove the "ENU" in the end, or rename KBXXXX_ENU.exe in KBXXXX_FRA.exe, in this case the file will need to be Windows2000-XP-2003-KB950305-v2-x86-FRA.exe
instead about langpack.exe and everything ok, not been processed because this was not the dotnet1.1. True AddOn, need to download all true dotnet addon
OnePiece Microsoft.NET Framework v4.0.30319.282 True AddOn ENU
and after removing the ENU in the end of the name of the addon, example
sorry for my English, when will enter Nonno Fabio online explain all the most well
Ciao.
Rename WindowsXP-KB971276-v3-x86-ENU.exe in WindowsXP-KB971276-v3-x86-SVE.exe or WindowsXP-KB971276-v3-x86.exe
install_flash_player_ax.exe not need, You only need the OnePiece_Adobe_Flash_Player_v%Lastversion%_True_AddOn.cab
Ciao.
-
-
Ragazzi Update Pack già aggiornato per di piu guardate il primo post
Ciao a tutti.
-
Ragazzi Tool già aggiornato, aggiunto supporto per ultime release del Update Pack WinXP e Win2K3
Ciao a tutti.
-
Hi bphlpt, already done, Thank You
anyway here's DX WinNT6.x True Integrator syntax for Win7 addon makers
Ciao.
-
Kelsenellenelvian & ricktendo64 in perfectly right about entries.ini, this story just to keep compatibility with RVMi, because RVMi to this problem of entries.ini, because it is a program designed initially for RyanVM update pack, so the enties.ini and one that identifies an update pack, precisely for the addon need to add a name behind, instead in WinNT6.x True Integrator is not a problem, because working in WinNT6.x True Integrator does not matter what we in there, extracts each entires*.ini (each addon is extracted in different directory), because basic idea to imitate the update.exe inside windows hotfix, so basic idea and use a file entries.ini
WinNT6.x True Integrator supports almost all. not to say everything that you will be able to run from a file inf, WinNT6.x True Integrator supports much about it, so will be able to support all line in this case the process of svcpack addon and was still at update.exe from inside hotfix, or better to say according to the rules microsoft http://msdn.microsof...8(v=VS.85).aspx
Ja\;;; coment
v\ \\\\\ ;comment ect ect ect
;comment ect ect ect
;comment ect ect ect
;comment ect ect ect
a\ \\; comment ect ect ect
\\ \\ \ ;comment ect ect ect
comment ect ect ect
comment ect ect ect
.exe
interprets this command as java.exe
Or
dotNetFx40\;;; coment
_Full\ \\\\\ ;comment ect ect ect
_x64\ \\; comment ect ect ect
_x86\\ \\ \ ;comment ect ect ect
_SlimSetup.exe.exe \\
" "\; space and character of the separation
/y
interprets this command as dotNetFx40_Full_x86_x64_SlimSetup.exe /y
Or
"Ja va.exe" /silent
interprets this command as Ja va.xe /silent (Not Ja va.xe /silent, because the command would ja.exe va.xe /silent)
Or
"Ja;;;;;va.exe" /silent
interprets this command as Ja;;;;;va.exe /silent
WinNT6.x True Integrator interprets the line as well and after executing them, after about another depends on what supports windows ehhhhhhhh during the run of each file name ect ect, do not want to be wrong but the MAX_PATH = 256 http://msdn.microsof...3(v=vs.85).aspx
but these line RVMi nLite and do not know them, so to keep compatibility to integrate the addon in Windows NT5.x (2000/XP/2003) need to use normal line ect ect
however as said many times in WinNT6.x True Integrator we tried to imagine all possible scenarios, them can be done really everything, WinNT6.x True Integrator should be updated (but we are not finding the free time to do) but still a good structure, so in this case if you want you can use an addon svcpack who knows only WinNT6.x True Integrator, example esntires.ini & section [setupAddOnToRun]
example
;All Windows (x32 & x64) NT6.x (6.0 - 6.1 - 6.2 ect ect ect)
[setupAddOnToRun]
javaforwinnt6.exe /silent ect ect
Or
here WinNT6.x True Integrator supports x32 & x64 Windows version
;This section contains version info for WinNT6.x True Integrator[general]
builddate=2012-09-30T14:33:11Z
description=Windows6.1-KB2533552
language=Neutral
title=KBXXXXXX
version=6.1.7600.16385
website=http://www.Microsoft.com/
;;WinNT6.x True Integrator Optional info
;;processorArchitecture=x86
ReleaseType=SvcPack AddOn
Customizedby=Vostro Nome
Copyright=Microsoft
Company=Microsoft
InstallPackageName=Windows6.1-KBXXXXXXX.exe
LastUpdateTime=2012-09-30T14:33:11Z
[setupAddOnToRun.ntx86]
Windows6.1-KBXXXXXX-x86.exe
[setupAddOnToRun.ntamd64]
Windows6.1-KBXXXXXX-x64.exe
[strings]
In this case, if the OS and 32-bit WinNT6.x True Integrator integrates only Windows6.1-KBXXXXXX-x86.exe, if the OS and 64-bit WinNT6.x True Integrator integrates only Windows6.1-KBXXXXXX-x64.exe
config file used
;!@Install@!UTF-8!
RunProgram="%SystemRoot%\\System32\\WUSA.exe \"%%T\\Windows6.1-KBXXXXXX-x86.msu\" /norestart /quiet"
GUIMode="2"
;!@InstallEnd@!
;!@Install@!UTF-8!
RunProgram="%SystemRoot%\\System32\\WUSA.exe \"%%T\\Windows6.1-KBXXXXXX-x64.msu\" /norestart /quiet"
GUIMode="2"
;!@InstallEnd@!Or
;only in Windows 7 x32/x86
[setupAddOnToRun.ntx86.6.1]
Dotnet45_x32.exe
;only in Windows 8 x32/x86
[setupAddOnToRun.ntx86.6.2]
Dotnet45_64.exe
;only in Windows 7 x64
[setupAddOnToRun.ntamd64.6.1]
Dotnet45_x32.exe
;only in Windows 8 x64
[setupAddOnToRun.ntamd64.6.2]
Dotnet45_64.exe
or AIO mod
;only in Windows 7 x32/x86 & x64
[setupAddOnToRun.6.1]
Dotnet45_x32_64.exe
;only in Windows 8 x32/x86 & x64
[setupAddOnToRun.6.2]
Dotnet45_x32_64.exe
install the dotnet45 only in Windows 7 (6.1) and windows 8 (6.2) Not in Windows Vista (6.0),
see Sample INF Models Sections for Only One Target Operating System & Combining Platform Extensions with Operating System Versions
sorry again for my English, or written by me because Nonno Fabio rarely enters into the weekend, so answer remained Monday or Tuesday, so for everything else Nonno Fabio explains all the most well
as rightly bphlpt has already noticed this topic DX WinNT6.x True Integrator syntax for Win7 addon makers we forgot to put it here, but just come online Nonno Fabio will put immediately
Ciao a tutti.
-
I downloaded your Flash Player ActiveX and Silverlight Addons last week. They are already integrated and working fine. OnePiece_Directx_End-User_Runtime is for XP SP3? I downloaded your DirectX for integration and notice it was for XP SP3 only, Is this correct?
Nonno Fabio wrote
This DX WinNT6.x Integrator addon is compatible with Windows Vista and 7 x86 (32 bit) versions (for XP/2003 you must use latest releases of RVM Integrator or Nlite).Ciao.
-
Yes, you can do it by Kels_Java_SvcPack_AddOn and also from Kels_Java_Silent_Installers.exe
Ciao.
PS: However I also recommend the use of Flash Player ActiveX Microsoft Silverlight DirectX End-user Runtime (software like Media Player Classic ect ect need this ect ect )
-
@Tutti
Ragazzi link in primo post già aggiornati, ragazzi come si nota la dimensione del Update Pack e stato aumentato di 1-2 Mb, non e cambiato niente niente dentro Update Pack, cambiato solo il modo del archiviazione, adesso usato il modo tradizionale quello LZMA mod (peccato sembra che LZMA2 mod archivia piu bene mahhh)
ragazzi dispiace ancora di questa storia ma come capite da vuoi chi lo avrebbe mai pensato
Ciao a tutti.
-
try once you never know http://www.microsoft.com/en-us/download/details.aspx?id=16546
Ciao.
-
Guys there a problem with last Update Pack, nLite & RVMI fail to integrate, This is because they can not extract it properly, why say and success ehhhhh, history and as always I create update pack, integrate it in a CD WinXPSP3 Clean, and then I make a test VM, and if after all Ok, I put the link OnLine, but yesterday after all the tests and saw that everything was OK in VM,, after well by coincidence download and install the new 7-Zip 9.29 Alpa, and doing some tests I see that the new Update Pack with 7-Zip 9.29 was 1-2 MB less, so or extracted and stored again with the new 7-ZIP in LZMA2 mod, and then uploaded them ect ect
to put everything in place need to download the new 7-Zip 9-29 Alpa http://sourceforge.n...7/topic/5634786 after install or extract ect ect, but from the new 7-Zip need to take the new 7z.exe
after for those who use nLite serves replace the 7z.exe (v9.29) with one located in the directory of the installation of nLite
Instead, for those who use RVMi serves rename the new 7z.exe (v9.29) in 7zdn.exe and after replacing the 7zdn.exe in the Plugins folder which is located the directory where he works RVMi
or here are
7z.exe & 7zdn.exe v9.29
Hash MD5 3FAF803113F19768B9FB821A80A3433C
Filesize: 209 KB (214930 bytes)
or extract update pack, and after archive with the 7-zip official version or with Winrar ect ect and after integrate normally
sorry again for my English
when will enter online Nonno Fabio tell everything more well
sorry again, Ciao a tutti
-
Ragazzi ce un problema con ultimo Update Pack, sia nLite sia RVMI non riescano integrarlo, questo perché non riescano estrarlo correttamente, come mai e successo direte ehhhhh, la storia e che io come sempre creo update pack, la integro in un Cd WinXPSP3 Pulita, e dopo faccio un test in VM, e dopo se e tutto Ok metto i link OnLine, ma ieri dopo aver effettuato tutti i test e visto che anche in VM era tutto OK, dopo pure per coincidenza scarico e installo il nuovo 7-Zip 9.29 Alpa, e facendo dei test vedo che Update Pack con il nuovo 7-Zip veniva 1-2 MB di meno, cosi o estratto e archiviato ancora tutti i due Update Pack ENu & ITA con il nuovo 7-ZIP in LZMA2 mod, e dopo li uploadati ect ect
allora per mettere tutto a posto serve scaricare il Nuovo 7-Zip 9-29 Alpa http://sourceforge.n...7/topic/5634786 dopo o estrarlo o installarlo vedete da vuoi, ma dal nuovo 7-Zip serve prendere il nuovo 7z.exe
dopo per quelli che usano nLite serve sostituire il 7z.exe (v9.29) con quello che si trova nella direttori del installazione di nLite
Invece per quelli che usano RVMi serve rinominare il nuovo 7z.exe (v9.29) in 7zdn.exe e dopo sostituire il 7zdn.exe dentro la cartella Plugins che si trova nella direttori dove lavora RVMi
oppure ecco qui
7z.exe & 7zdn.exe v9.29
Hash MD5 3FAF803113F19768B9FB821A80A3433C
Filesize: 209 KB (214930 bytes)
Oppure estrarre Update Pack con 7-zip Winrar o altro, e dopo archiviatelo ancora con la versione ufficiale del 7-zip Winrar o altro, e dopo integratelo normalmente come sempre
Ciao a tutti.
-
OnePiece Windows XP Post-SP3 Update Pack e una raccolta di aggiornamenti integrabili direttamente sul cd di Windows XP SP3. A differenza di AutoPatcher che esegue gli aggiornamenti su un sistema gia installato, questo pack serve a creare un CD di Windows XP SP4 completo, che non contiene nessun tipo di tweak o miglioramento. Il vantaggio principale rispetto ad AutoPatcher e che se viene installato Windows da un CD che abbia il OnePiece Pack integrato dopo non e necessaria l'esecuzione di AP, perche i file che si vanno ad aggiornare con le patch sono gia aggiornati.
Attenzione: non applicare su precedenti Update Pack o AddOn, Ragazzi sia per quelli che usino nLite sia per quelli che usino RVMi, metterlo il pack da solo integrarlo, e dopo integrare o fare altri operazioni in quello cd, metterlo il pack inseme ai altri cose ce il rischio di sforzare tropo le applicazione come nLite e RVMi, e dopo che il rischio che forse anche sbagliano in qualche cosa, cosi il consiglio e sempre essere prudenti e metterli le cose in cd uno a uno, cosi siete sicuri 1000% che tutto andra ok
OnePiece Windows XP Post-SP3 UpdatePack v6.1.0 ITA
Hash MD5 32E06EF625839BE25B69DAF2957A05AC
Filesize: 216 MB (227034473 bytes)
Ragazzi un ringrazio speciale va a forum http://thehotfixshare.net da dove o presso tutti questi hotfix, davvero direi straordinario il lavoro di quelli ragazzi li.
Changelog della versione 6.1.0
Aggiunti:
KB2661254-v2 (Sostituisce KB2661254)
KB2705219-v2 (Sostituisce KB2705219)
KB2723135-v2 (Sostituisce KB2723135)
KB2724197 (Sostituisce KB2732488-v2)
KB2731847-v2 (Sostituisce KB2731847)
KB2749655
KB2756822 (Sostituisce KB2732052)
(KB890830) Strumento di rimozione malware v4.13
Adobe Flash Player 11 ActiveX v11.4.402.287
OnePiece's Windows XP Post-SP3 Update Pack Italian
in Update Packs for Windows XP
Posted · Edited by OnePiece
Nuova release