You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I followed the instructions given on the main page, but step 5 kept failing:
change the .ini file to the base path (BASE_PATH=/media/fat) where your vhds are located, /media/fat, /media/usb0, /media/fat/games/cifs, etc
Bizarrely, the base path reported in the error when the script failed would contain the path in duplicate, IE:
/media/fat/games/AO486
appeared as
/media/fat/games/AO486/media/fat/games/AO486
The .ini did have a BASE_PATH value I was editing, but when the script ran it could never find the .vhd file. I had a look at the shell script, and it looks like you're looking for INI_PATH rather than BASE_PATH:
INI_PATH="${ORIGINAL_SCRIPT_PATH%.*}.ini"
...editing the .ini to use INI_PATH fixed the script and allowed it to work. I'd think either updating the instructions to indicate the new variable name or changing the variable name itself might be the way to go? Unless of course I resolved the issue for a reason outside what my limited knowledge of scripting entails - maybe editing to INI_PATH just caused the script to fall back on a default value or something, since it no longer had a BASE_PATH entry and I got lucky.
The text was updated successfully, but these errors were encountered:
I followed the instructions given on the main page, but step 5 kept failing:
change the .ini file to the base path (BASE_PATH=/media/fat) where your vhds are located, /media/fat, /media/usb0, /media/fat/games/cifs, etc
Bizarrely, the base path reported in the error when the script failed would contain the path in duplicate, IE:
/media/fat/games/AO486
appeared as
/media/fat/games/AO486/media/fat/games/AO486
The .ini did have a BASE_PATH value I was editing, but when the script ran it could never find the .vhd file. I had a look at the shell script, and it looks like you're looking for INI_PATH rather than BASE_PATH:
INI_PATH="${ORIGINAL_SCRIPT_PATH%.*}.ini"
...editing the .ini to use INI_PATH fixed the script and allowed it to work. I'd think either updating the instructions to indicate the new variable name or changing the variable name itself might be the way to go? Unless of course I resolved the issue for a reason outside what my limited knowledge of scripting entails - maybe editing to INI_PATH just caused the script to fall back on a default value or something, since it no longer had a BASE_PATH entry and I got lucky.
The text was updated successfully, but these errors were encountered: