Skip to content

Fix hardcoded user path in silent VBS launcher - #15

Open
0xdefec71f wants to merge 1 commit into
RMNO21:mainfrom
0xdefec71f:patch-1
Open

0xdefec71f wants to merge 1 commit into
RMNO21:mainfrom
0xdefec71f:patch-1

Conversation

@0xdefec71f

Copy link
Copy Markdown

Summary of Changes

Replace the hardcoded user-specific PowerShell script path with dynamic path resolution. Previously, the launcher used a hardcoded path containing "C:\Users\User", which caused it to fail for users with a different Windows username.

The VBS launcher now determines its own directory using WScript.ScriptFullName and starts DimOLED.ps1 from the same directory.

This ensures the launcher works correctly for all Windows users and installation paths without requiring any user-specific configuration or modifications during installation.

Verification

  • Tested locally on Windows
  • Verified zero regressions

Replace the hardcoded user-specific PowerShell script path with dynamic path resolution. Previously, the launcher used a hardcoded path containing "C:\Users\User", which caused it to fail for users with a different Windows username.

The VBS launcher now determines its own directory using WScript.ScriptFullName and starts DimOLED.ps1 from the same directory.

This ensures the launcher works correctly for all Windows users and installation paths without requiring any user-specific configuration or modifications during installation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant