Skip to content

[BUG]Gateway 1.0.1: NAM and IR files cannot be loaded after initially installing Gateway to a custom drive/path #674

Description

@yison9527

I am experiencing a file-loading issue with Gateway 1.0.1 on Windows.

Gateway opens normally and the file browser also works normally. However, after selecting either a .nam model or an IR .wav file, the file browser closes but nothing is loaded.

The model field continues to display:

Select model...

The same problem occurs when loading an IR.

There is no visible error message.

Important observation

I tested Gateway on two different Windows computers, and there is an important difference between them.

Computer A – Working

On this computer, I installed Gateway using the completely default installation settings and default C: drive location.

Result:

NAM models load correctly.
A2 NAM models load correctly.
IR files load correctly.
Gateway works as expected.

Computer B – Not working

On this computer, during the first installation of Gateway, I changed the installation location from the default C: drive location to a location on the D: drive.

From that first installation onward:

NAM files cannot be loaded.
A2 NAM files cannot be loaded.
IR WAV files cannot be loaded.

When I click Select model or select an IR, the Windows file browser opens normally.

I can select the file and click Open, but after the file browser closes, Gateway does not load the selected file.

The model field still displays Select model...

No error message is displayed.

Troubleshooting already performed

I have already tried completely reinstalling Gateway several times.

I uninstalled Gateway.

I used Geek Uninstaller to scan for and remove leftovers.

I removed Gateway-related registry entries.

I manually searched for and removed Gateway-related configuration and residual files.

I restarted Windows.

I reinstalled Gateway using the default C: drive installation path.

I tested files located directly on the C: drive.

I tested both NAM models and IR WAV files.

The problem still persists.

Once this problem occurred after the original custom D: drive installation, reinstalling Gateway to its default C: drive location did not restore file loading.

Why I suspect the installation path may be related

The second computer, where Gateway was installed with the default settings from the beginning, works correctly.

The problematic computer differs in that Gateway was initially installed using a custom D: drive installation location.

Even after uninstalling it and reinstalling to the default C: drive location, the problem remains.

This makes me suspect that Gateway may store some persistent path, file-dialog state, configuration, permission information, or other user-level state that is not removed by the uninstaller.

Expected behavior

After selecting a .nam model:

Select model → choose model.nam → Open

Gateway should load the model and display the loaded model.

Likewise, selecting a valid IR .wav file should load the IR.

Actual behavior

Select model → choose model.nam → Open

The file browser closes, but nothing happens.

Gateway still displays Select model...

The same behavior occurs with IR files.

There is no visible error message.

Gateway version

Gateway v1.0.1 x86-64

I have reproduced the issue with the standalone application.

Additional information

The same NAM and A2 files can be loaded successfully by Gateway on my other computer, so the files themselves appear to be valid.

Since both NAM models and IR files fail to load on the affected computer, this does not appear to be limited to A2 model compatibility.

It seems more likely to be related to file loading, path handling, or persistent configuration on this Windows installation.

I would be happy to provide additional logs, configuration files, example NAM files, or perform diagnostic tests if needed.

Could you please let me know if Gateway stores its file-loading paths or configuration anywhere outside the normal installation directory or registry, and whether there is a way to completely reset Gateway to a first-run state?

Thank you.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingpriority:lowLow priority issuesunreadThis issue is new and hasn't been seen by the maintainers yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions