Ansible
PS DSC
Downloads:
318
Downloads of v 1.03:
318
Last Update:
17 Mar 2022
Package Maintainer(s):
Software Author(s):
- FuSoYa
Tags:
lunar-ips lunarips lunar ips patching snestool snes-tool- Software Specific:
- Software Site
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
LunarIPS Patching Utility
- 1
- 2
- 3
1.03 | Updated: 17 Mar 2022
- Software Specific:
- Software Site
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
318
Downloads of v 1.03:
318
Maintainer(s):
Software Author(s):
- FuSoYa
LunarIPS Patching Utility 1.03
Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by FuSoYa. The inclusion of FuSoYa trademark(s), if any, upon this webpage is solely to identify FuSoYa goods or services and not for commercial purposes.
- 1
- 2
- 3
All Checks are Passing
3 Passing Tests
Deployment Method: Individual Install, Upgrade, & Uninstall
To install LunarIPS Patching Utility, run the following command from the command line or from PowerShell:
To upgrade LunarIPS Patching Utility, run the following command from the command line or from PowerShell:
To uninstall LunarIPS Patching Utility, run the following command from the command line or from PowerShell:
Deployment Method:
This applies to both open source and commercial editions of Chocolatey.
1. Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
2. Setup Your Environment
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the package and push it to a repository Download
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download lunar-ips --internalize --source=https://community.chocolatey.org/api/v2/ -
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'" - Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade lunar-ips -y --source="'INTERNAL REPO URL'" [other options]See options you can pass to upgrade.
See best practices for scripting.
Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.
If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:
choco upgrade lunar-ips -y --source="'INTERNAL REPO URL'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install lunar-ips
win_chocolatey:
name: lunar-ips
version: '1.03'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'lunar-ips' do
action :install
source 'INTERNAL REPO URL'
version '1.03'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller lunar-ips
{
Name = "lunar-ips"
Version = "1.03"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'lunar-ips':
ensure => '1.03',
provider => 'chocolatey',
source => 'INTERNAL REPO URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
4. If applicable - Chocolatey configuration/installation
See infrastructure management matrix for Chocolatey configuration elements and examples.
This package was approved by moderator flcdrg on 17 Mar 2022.
FuSoYa is not affiliated with this package in any way, so do not reach out to them for issues with this package. Likewise, problems with the LunarIPS software itself should not be reported to this package's Github issue tracker.
Please check the Software Site or installed README.txt for Lunar IPS information and how you can report issues with the software.
---
Lunar IPS (LIPS) is intended as an easy to use, lightweight IPS patch utility for windows to replace the SNESTool DOS program. It can both create and apply IPS patches.
As far as features go, LIPS has:
- IPS patch creation/application support.
- full RLE encoding/decoding support.
- file expanding/truncating support.
- the IPS encoder creates files that are the same size or smaller than files created with SNESTool.
- the IPS encoder avoids the rare "0x454F46 (EOF) offset bug" that SNESTool's IPS encoder has.
- logging feature for applying IPS patches (ROMFileName.log).
- registers the ".IPS" file type so that you can just double click on an IPS file and choose the file to apply it to for convenience.
- support for patching files up to 16 MB in size, which is the limit of the IPS format. The files can technically be larger than that, but the IPS format cannot record changes beyond the 16 MB mark due to 24-bit addressing. The IPS file itself can be any size.
Note that the logging and file registration options are saved to the registry.
$ErrorActionPreference = 'Stop'
# We need to remove the manually generated shim for the 64-bit version
Uninstall-BinFile 'Lunar IPS (64-bit)'
# Remove the start menu shortcuts
"$env:ALLUSERSPROFILE",
$env:AppData | Foreach-Object {
if ( Test-Path -PathType 'Container' ( $removePath = "$_/Microsoft/Windows/Start Menu/Programs/Lunar IPS" ) ) {
Write-Host "Removing Start Menu shortcuts from '$removePath'"
try {
Remove-Item -Recurse -Force $removePath -EA Stop
}
catch {
# A warning is sufficient in case the user installed as admin and removed as non-admin, or vice versa
Write-Warning "Unable to remove Start Menu shortcuts from '$removePath': $_"
}
}
} #Requires -Version 4.0
function Confirm-Administrator {
[Security.Principal.WindowsPrincipal]$me = [Security.Principal.WindowsIdentity]::GetCurrent()
$me.IsInRole([Security.Principal.WindowsBuiltInRole] "Administrator")
}
function New-StartMenuShortcut {
Param(
[ValidateSet('Machine', 'CurrentUser')]
[string]$ShortcutScope = 'Machine',
[Parameter(Mandatory)]
[string]$Name,
[Parameter(Mandatory)]
[string]$Path,
[string]$Arguments,
[string]$WorkingDirectory,
[ValidateSet('Default', 'Maximimed', 'Minimized')]
[string]$WindowStyle = 'Default',
[string]$IconLocation,
[string]$Description
)
# Get the appdata folder to use based on machine or current user scope
$useAppData = switch ( $ShortcutScope ) {
'Machine' {
$env:ALLUSERSPROFILE
break
}
'CurrentUser' {
$env:AppData
break
}
default {
throw 'Invalid ShortcutScope'
}
}
# Shortcut folder path and name
$lnkFolder = "$useAppData/Microsoft/Windows/Start Menu/Programs/Lunar IPS"
$lnkName = "$Name.lnk"
$lnkFullPath = "$lnkFolder/$lnkName"
if( Test-Path $lnkFullPath -PathType Leaf ) {
Write-Warning "Shortcut already exists at '$lnkFullPath'. Removing before creating new shortcut."
Remove-Item -Force $lnkFullPath
}
# Determine correct WindowStyle Value
# 1 is Default
# 3 is Minimized
# 7 is Maximized
# This was an enum but community packages must be 4.0 compliant
$useWindowStyle = switch( $WindowStyle ) {
'Default' { 1; break }
'Minimized' { 3; break }
'Maximized' { 7; break }
default { throw 'Unknown WindowStyle specified' }
}
# For some reason the Windows Scripting Host remains the only way to create
# .lnk files outside of the Win32 API
$shell = New-Object -ComObject 'WScript.Shell'
if ( !( Test-Path $lnkFolder -PathType Container ) ) {
Write-Warning "Creating folder for Start Menu shortcuts at '$lnkFolder'"
mkdir $lnkFolder -Force -EA Stop | Out-Null
}
$lnk = $Shell.CreateShortcut($lnkFullPath)
$lnk.TargetPath = $Path
$lnk.Arguments = $Arguments
$lnk.WorkingDirectory = $WorkingDirectory
$lnk.WindowStyle = $useWindowStyle
$lnk.IconLocation = $IconLocation
$lnk.Description = $Description
$lnk.Save()
}Log in or click on link to see number of positives.
- lunar-ips.1.03.nupkg (c5d66076cb70) - ## / 62
- lips103.zip (508c65db4802) - ## / 59
- Lunar IPS.exe (9e67a1f31050) - ## / 67
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
2022 FuSoYa
Release notes can be found on FuSoYa's Niche news page, or in the readme provided with the LunarIPS software itself.
-
- chocolatey-core.extension (≥ 1.1.0)
Ground Rules:
- This discussion is only about LunarIPS Patching Utility and the LunarIPS Patching Utility package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or LunarIPS Patching Utility, or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.