"Installer needs the next part (.BIN) file"

[jarss]

I've tried this on two games I have, and I'm running into the same issue.
I create a new bottle and want to install a gog game I have the BIN file for. I point it to the exe to install and run it, it launches, and the GOG installer informs me that the the last BIN file is missing ("Installer needs the next part (.BIN) file"). The file is there, and I have the same issue with another game. Why doesn't GOG "see" that last BIN file?

[Qronikarz]

Bottles needs to have access to the files to use them.

Bottles is currently only provided as a flatpak and unfortunately flatpak doesn't yet have the the way to give access to neighbouring files.

You have two choices:

1. Copy the installer inside the bottle drive_c folder - there's a shortcut to it inside the bottle.
2. Give permissions to other folders - for example using Flatseal - https://docs.usebottles.com/flatpak/expose-directories

[jarss]

Bingo. Thanks for that.

Because my file manager is kind of lacking (I'm still getting used to it) I went ahead with the Flatseal solution, from the link you provided.

I gave Bottles permissions to read my games folder (where I have the BIN files) and it now installs.

I wouldn't have guessed it's an access issue from the error it gave me. Thanks for the answer!

[ChG0815]

Hi there,
it seams, I have the same issue. I already copied the files to the drive_c folder:

I also gave permission using flatseal.
But still the same issue. When starting the bottle, I am selecting the executable from the drive_c, but still getting:

[ERROR] FATAL UNHANDLED EXCEPTION: System.IO.FileNotFoundException: Could not find file "Z:\run\user\1000\doc\d0cc0088\BrDlInst.cfg"

Can someone tell me, what I am doing wrong here?

[Qronikarz]

This one looks like a problem with Flatpak sandbox. If you are using Bottles installed from Flathub it would be good to fill an issue report in Bottles repository. I remember there were some similar reports.
Somebody mentioned that setting bottle's Working Directory fixed the issue.

[ChG0815]

I've set the working directory to drive_c, but it didn't change anything. Or what path should be set instead?