Guess 3 times what "silent install " means?alban wrote:
OK how do I use this dotNet35SP1_1.07.exe -ai when i double click on the dotNet35SP1_1.07.exe without seeing the dialog box
Thanks
then let me know what you want to see...
dotNet35SP1_1.07.exe -aialban wrote:OK how do I use this dotNet35SP1_1.07.exe -ai when i double click on the dotNet35SP1_1.07.exe without seeing the dialog box of choosing
Click "Yes" to begin installation. Click "No" to cancel and exit.
How do I set automatically to YES
I'm asking this cause I need this package of yours user_hidden and the reason is that you keep it to data and I like you work.
Thanks
has anyone mentioned to double click the exe ?alban wrote:This command dotNet35SP1_1.07.exe -ai is not working when is double click on dotNet35SP1_1.07.exe I still get this dialog BOX
what about "%wpipath%\Install\dotNet35SP1_1.07.exe" -aialban wrote:Thanks for helping me, the problem was that I was trying to use this package on me WPI collection of software's and the command on wpi looks like this "%wpipath%\Install\dotNet35SP1_1.07.exe".
The problem is that when I try this "%wpipath%\Install\dotNet35SP1_1.07.exe -ai" as you telling me all the time IT IS NOT WORKING, the setup won't start.
Is there any other solution for this?
Thanks.
Microsoft .NET Framework V3.5 SP1 FULL 1.08 - 20100224zilan wrote:User hidden you have 3 release so far for .NET Framework, which should i use for integrate with RVMi?
Microsoft .NET Framework V3.5 SP1 FULL 1.08 - 20100224
Microsoft .NET Framework 3.0 SP2 & 3.5 SP1 - 20100224
Microsoft .NET Framework 1.1 SP1 - 20091013
thx
zilan wrote:User hidden you have 3 release so far for .NET Framework, which should i use for integrate with RVMi?
Microsoft .NET Framework V3.5 SP1 FULL 1.08 - 20100224
Microsoft .NET Framework 3.0 SP2 & 3.5 SP1 - 20100224
Microsoft .NET Framework 1.1 SP1 - 20091013
thx
not new, and is included in the installer.laddanator wrote:New Netframework update out...not sure if u guys seen it.
KB951847...cant find a link to it
any addons with your integration ?laddanator wrote:I am using your new update pack with the newest frame network pack and for some reason its showing up in Microsoft updates
i do not touch those reg keys, they are being written by the MS installer based on integrated KB msp updates.adric wrote:I noticed that there's a difference in the 3.5 reg keys after installation when using this addon as opposed to a WU install. For example:
normal update
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 3.5 SP1\SP1\KB958484
addon update
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 3.5 Service Pack 1\SP1\KB958484
The same for KB963707. I don't know why Ms changed the naming convention starting with 3.5
If it's not too much trouble, can this be changed to reflect the new name?
Al
The cause is that u_h's changed the property table for productname.adric wrote:I noticed that there's a difference in the 3.5 reg keys after installation when using this addon as opposed to a WU install. For example:
normal update
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 3.5 SP1\SP1\KB958484
addon update
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 3.5 Service Pack 1\SP1\KB958484
The same for KB963707. I don't know why Ms changed the naming convention starting with 3.5
If it's not too much trouble, can this be changed to reflect the new name?
Al
I see two properties with the same value. ProductName and LocProductName. I also looked at your .msi and you did not change any of those property values although your reg keys are correct. What changes did you make to correct the reg entries?yumeyao wrote: The cause is that u_h's changed the property table for productname.
you can safely change both.adric wrote:I see two properties with the same value. ProductName and LocProductName. I also looked at your .msi and you did not change any of those property values although your reg keys are correct. What changes did you make to correct the reg entries?yumeyao wrote: The cause is that u_h's changed the property table for productname.
Al
Sorry, I should have been more clear. I was referring to YumeYao's .NET msi installer. He did not change any of the mentioned properties in his msi and has the same values as in your msi. I was wondering how YumeYao made his changes because he previously had the same problem with the regkey discrepancy.user_hidden wrote:you can safely change both.adric wrote:I see two properties with the same value. ProductName and LocProductName. I also looked at your .msi and you did not change any of those property values although your reg keys are correct. What changes did you make to correct the reg entries?yumeyao wrote: The cause is that u_h's changed the property table for productname.
Al
there is no shortproductname in the original msi.adric wrote:Sorry, I should have been more clear. I was referring to YumeYao's .NET msi installer. He did not change any of the mentioned properties in his msi and has the same values as in your msi. I was wondering how YumeYao made his changes because he previously had the same problem with the regkey discrepancy.
I did see that YumeYao had an additional property called ShortProductName with the correct value which is not in your msi. Maybe that is how he fixed it.
I know you folks are busy and apologize for bombarding you with questions that may not interest anyone else. Thanks again.
Al
I had a problem with Addon_Microsoft.Net_Family.35SP1_ROE_1.09.7z. I'm trying to see if I can reproduce it again. This is what I did:user_hidden wrote:updated version 1.09 20100510 ....
(fixed cosmetic registry entry)
Timbo wrote:used nlite to remove stuff and set unattended
used nlite to slipstream in OnePiece_Windows_XP_Post-SP3_UpdatePack_v3.7.0
used integrator v1.61b21 to integrate Addon_Microsoft.Net_Family.35SP1_ROE_1.09.7z.
Integrated driver pack
it is in the KB982524 rollup update.adric wrote:Is there a download link for KB976576 available?
The link in the KB article keeps redirecting you to KB977354.
Al