Doomsday+Snowberry - Portable [e.g. USB] Info + HowTo
Case: Use relative pathnames for IWAD's to allow a "portable" Doomsday/Snowberry installation. Example folder structure is like so:
Result 1: Doomsday crashes less than 1/4 of the "wheel" up. Running Windows x64. doomsday.out had no error, just an abrupt end. Whatever.
Attempt 2: Discovered that the IWAD path must be relative to the userdir, which is E:\Games\Doomsday\snowberry\runtime - setting the new IWAD path to ..\..\WADS\DOOM.WAD should work, however that doesn't adhere to the Snowberry IWAD exist-check and it won't save.
Fix 2: Edit E:\Games\Doomsday\snowberry\conf\doomsday.conf, around line 26...
Attempt 2: Restart Snowberry, set IWAD path to ..\..\WADS\DOOM.WAD - success and done.
Well there ya go, pretty detailed but I wanted to give some info incase someone has a use for this. Maybe an ultra-ultra-low priority bugfix (?) could be to improve the way snowberry detects IWADS, even putting in ..\ parent-folder sequences itself would be pretty fancy. It's not important at all really, but it's worth mentioning anyway.
I'll put this on the Wiki when/if I get access, ill keep it much shorter than this thread was :P
E:\Games\Doomsday
E:\Games\Doomsday\snowberry\snowberry.exe
E:\Games\Doomsday\WADS\DOOM.WAD
Result 1: Doomsday crashes less than 1/4 of the "wheel" up. Running Windows x64. doomsday.out had no error, just an abrupt end. Whatever.
Attempt 2: Discovered that the IWAD path must be relative to the userdir, which is E:\Games\Doomsday\snowberry\runtime - setting the new IWAD path to ..\..\WADS\DOOM.WAD should work, however that doesn't adhere to the Snowberry IWAD exist-check and it won't save.
Fix 2: Edit E:\Games\Doomsday\snowberry\conf\doomsday.conf, around line 26...
file iwad (
option: -iwad
must-exist: yes
allowed types (file-type-iwad = wad)
Attempt 2: Restart Snowberry, set IWAD path to ..\..\WADS\DOOM.WAD - success and done.
Well there ya go, pretty detailed but I wanted to give some info incase someone has a use for this. Maybe an ultra-ultra-low priority bugfix (?) could be to improve the way snowberry detects IWADS, even putting in ..\ parent-folder sequences itself would be pretty fancy. It's not important at all really, but it's worth mentioning anyway.
I'll put this on the Wiki when/if I get access, ill keep it much shorter than this thread was :P
Comments
I was looking for the info on how to make Doomsday 1.9 portable. Unfortunately, for me the method you gave failed.
Doomsday hangs at about the first quarter of the wheel and can be closed only through the Task Manager.
I have done everything as described, but... no luck.
The Doomsday 1.9 betas will only work with a completely unmodified Iwad. Dday 1.8.6 and other ports are considerably more lax at this.
A forum search would have revealed past threads about this. I'd imagine that Dday 1.9/2.0 final will be able to detect a modified Iwad and abort; hanging during loading isn't a good first impression or indicative of the problem.
Besides, when config files are restored to their original state, Doomsday is started without any problems with the same iwads.
I guess, an attached log file would help?
But it loses addons every time I move it to another folder, because paths to their folders in the '\snowberry\conf\addon-paths.conf' cannot be replaces with relative paths.
Did you somehow managed to solve it?
But in result the Snowberry's started.... and all it's subfolders are recreated right in the root of the Doom folder. Can this be fixed somehow?
My guess is that it's the starting folder. Try something like this in the BAT file first:
To find the working/starting folder which Steam launches in and you can work from there. So in the BAT file, use the correct starting folder for Snowberry. Note that you can use %CD%\..\snowberry if needed, .. being 'parent folder' which you may already know, and you can chain many together. Example:
Those two empty "" are needed to specify a title, it's a 'feature' of using the START command with >8.3 filepaths and/or FQDN's.