> > (1) I forget whether this used to be an issue (I very rarely open
> > RAR files in ZTW), but "O"pening an image inside an Alt-F5ed RAR
> file
> > using the latest DLLs extracts the file to (for example):
> >
> C:\Users\johnl\AppData\Local\Temp\ZTMP000\tmpB803.tmp\image.jpg
> > But passes the path:
> > C:\Users\johnl\AppData\Local\Temp\ZTMP000\image.jpg
> > To the Image viewer, which then points out its unhappiness.
> > I should mention that I'm using the fixed DLLs from RarLabs:
> > UnRAR .dll 291,928 1-08-23
> > UnRAR64 .dll 346,200 1-08-23
>
> Don't think unrar(64).dll is a factor - clearly the file was
> extracted.
>
> Are you using a jpg.bat to associate an application?
>
> What happens if you View the file, rather than Open it?
>
> Not seeing the problem here btw, full correct path of the extracted
> file is passed to my viewer.

E.g. I have a .rar file full of images
I highlight the file (I actually set a path of *.rar and then b to find some archives) and do Alt-F5, and ZTW shows the file list
I highlight a image file and press o
I get the path error mentioned above
My JPG.BAT is:
@Start "Irfanview" "C:\Program Files\IrfanView\i_view64.exe" %1 @exit
If I rename JPG.BAT to something else Irfanview opens the file correctly as it's the program registered with Windows to do that.
Is this my fault, sorry if so, I see the .bat files in the ZTW directory date from 2016. I assume I can just nuke them all (the Irfanview ones that is) or is there a down-side?

2.4.213
Win 10 x64 Pro 2H2
Started from a desktop icon as: C:\ZTW\ZTW64.EXE /XT /L1 /XP /ROWS:50 /COLS:96 /APIT /ZV"C:\ZTW\FILELIST.ZLOG"

Best Regards