#99 Making the setting "filter" and "windows size" saveable with command-line parameters

[Oleg N. Cher]

Dear FUSE developers,

I have fuse-1.2.0-win32 compiled by Sergio Baldoví.

Open the emulator with any RZX or TAP file specified in command-line. For example:

fuse apachegold.rzx

Change the window size to 3x3 of original resolution, and choose filter HQ 3x. Options -> Save (Options -> General -> Auto-save settings is enabled too). Close the emulator.

Open again:

fuse apachegold.rzx

Ooops, we have again 1x1 resolution and no filter selected. Can you make these settings saveable too?

P.S. Yes, if I do not specify an input file, the FUSE restores the settings well. But I need the same behavior with command-line parameters specified.

Thank you for perfect emul !

[Sergio Baldoví]

Hi Oleg,

I can't reproduce the error, it works to me. You should see this option:

<graphicsfilter>hq3x</graphicsfilter>

in %USERPROFILE%\fuse.cfg.

I would avoid the use of Auto-save as could enable conflicting peripherals. Just:

1. Delete %USERPROFILE%\fuse.cfg.
2. Open Fuse, set your default settings and save them with Options->Save
3. Run: fuse apachegold.rzx

Let me know if the problem persist. In that case, we should inspect apachegold.rzx and check that the hq3x filter is compatible with the emulated machine (i.e., non-Timex).

[Oleg N. Cher]

Dear Sergio,

I can still reproduce the error on two my computers - on desktop with Windows XP SP2 64 bit & laptop with Windows XP SP3 32 bit.

I delete %USERPROFILE%\fuse.cfg, open Fuse, set my default settings and save them with Options->Save. After these actions, the emulator opens with right settings (filter & window size) WITHOUT a specified file (in command-line).

If I run the emul and specify ANY .rzx or .tap file (in command-line), the emulator opens with no filter and standard 1x1 window size.

So I'm sure that problem is not in apachegold.rzx or compatibility of hq3x filter. I use normal ZX Spectrum 48k tape image and rzx from www.rzxarchive.co.uk . Maybe the problem reproduces only under Windows XP? Did you try on Windows 7, 8 or 10? Or on XP too?

[Oleg N. Cher]

Sergio, I hope it helps. See ReadMe.txt in the attach.

[Oleg N. Cher]

As it turned out, I was not quite accurate in the description of the error.

Now it is absolutely clear that the problem only occurs if the emulator is associated with extensions TAP or RZX and when it starts by double click on a TAP/RZX file.

OR when FUSE is called from the script in such a manner:

@START BigCircles.tap

If we rewrite the line so:

@START d:\WIN32APP\Emulz\Fuse\fuse.exe BigCircles.tap

( where d:\WIN32APP\Emulz\Fuse\fuse.exe is the full path to the emulator )

the problem disappear.

[Sergio Baldoví]

Thanks for the detailed information. I'm still struggling to reproduce the error. Works OK on with XP SP3 and W7 SP1, both virtualized. I'll try with other machine in a few days.

I've tried with C: drive. Is your D: drive a network share? There could be some restriction.

@START BigCircles.tap
@START d:\WIN32APP\Emulz\Fuse\fuse.exe BigCircles.tap

In theory, both methods should behave the same way. Unless there is a bad registry setup. IIRC, the installation setup the association at HKEY_CLASSES_ROOT (system wide), and don't try to overwrite any custom user association made in HKCU...\Explorer.

Could you check the open process with the double-click method? It should have the path of your expected folder. "Process Explorer" is a nice tool for this.

[Oleg N. Cher]

Dear Sergio,

I understood and found the cause. You can close this discussion.

I have two versions of the emulator installed (unpacked): 1st in d:\WIN32APP\Emulz\Fuse\ and 2nd in d:\WIN32APP\Emulz\ZxSpec\Fuse\
All launched files opened in the old version of FUSE. I re-associated them, and now all is OK.

I apologize for the confusion. Good luck!

[Sergio Baldoví]

Glad you have nailed down the problem.