87 replies to this topic

[Eric P.]

You want to convert both the target file and the patch file to Unix line endings, as I said (you should be able to set this in TextWrangler; patch will try to convert the CRLF into LF, but it's best not to give it any grief). The notes mean that you already changed the file (three of the patches were still valid even after your edits, but two of the patches weren't able to recover at all, while 4 were). With a clean download of the mod, you should get no failures (assuming you update the paths and the line endings). If WeiDU wasn't built to run on Windows, CRLF wouldn't even really be supported at all (LF is preferred, always), so you can mostly totally ignore that (the game doesn't really like its TLK entries to be CRLF anyway, so I'm not sure how those description updates are turning out, but whatever).

I don't know about any of the other patches, and you're known for crazy big installs, so I'm not sure it even really matters; you'll have to ask the other people who try tons of mods at once. For the patches that succeed with no failures, it certainly shouldn't hurt, but if you don't experience any installation issues or know of any compatibility problems with the unpatched mods, it's at your discretion. Good luck!

Should I tell TextWrangler to use Unicode line breaks? When I save these documents, I change their setting from DOS to UNIX.

Thanks!
Eric

[Eric P.]

No, just to Unix. Unicode line endings would break both patch and WeiDU. :-)

Now I'm unclear as to how to set this. In any case, I've applied the rest of the patches by using "patch [filename.xxx filename.xxx.patch] in the Terminal, with results as before: some patches are successful, some partially successful, and some fail on all "Hunks," possibly because I've already patched some or all of a given file.

- E

[Eric P.]

Item Revisions' Masterwork Weapons component is still not installing for me, due to a GLR parse error (whatever that is). I now suspect that it's not INNER_PATCH_SAVE that's the problem. The line where this appears reads "INNER_PATCH_SAVE thac0_line ~%description%~ BEGIN" so I wonder if "~%description%~" is the problem. In any case, apparently there's no way to solve this problem, so I'll have to skip the component and proceed. A shame, because I wanted the component, and it worked perfectly well before I applied the patch.

- E

[Eric P.]

This morning: deleted the entire BGII game folder to install anew from the discs. I'll back up critical files after applying the ToB 2.1.2 patch, then begin installing and testing mods again. This time, I won't patch any mod files, but will make sure everything in at the latest version.

If anyone can tell me how to partially or completely automate the mod install process under OS X, with WeiDU 213, I'm all ears!

Here we go again
- E

Edited by Eric P., 14 March 2010 - 09:14 AM.

[dabus]

You got a unix system under the hood, so use sh or shell to replace the batch.
I'd suggest you spare yourself some time and crop the stuff from top to the line 2551 (:BWSStart).
Do the same with all lines underneath 4447 (:BWSEnd).

Now open your backup-batch and look for all the lines at the top that begin with a SET.
Search & replace these variables in the shell-script with the readable text at the top.

Eg. line SET IFX=IF EXIST BWP_Expert tells you to replace %IFX% with IF EXIST BWP_Expert

Then replace the If-Statements and stuff like explained here.
Then go through the lines and remove unneeded stuff and replace windows-specific stuff with mac-stuff.
(Like replacing mtee with tee, strip the .exe from commands and such).

Then decide which version you want to have and create the dummy-files that are searched for by the script. (You know these from the SET-stuff at the top. Like BWP_English, BWP_Expert and such.)

Create a backup of your folder.
Go ahead and run the script.
Hopefully you will have fun.

[Eric P.]

You got a unix system under the hood, so use sh or shell to replace the batch.
I'd suggest you spare yourself some time and crop the stuff from top to the line 2551 (:BWSStart).
Do the same with all lines underneath 4447 (:BWSEnd).

Now open your backup-batch and look for all the lines at the top that begin with a SET.
Search & replace these variables in the shell-script with the readable text at the top.

Eg. line SET IFX=IF EXIST BWP_Expert tells you to replace %IFX% with IF EXIST BWP_Expert

Then replace the If-Statements and stuff like explained here.
Then go through the lines and remove unneeded stuff and replace windows-specific stuff with mac-stuff.
(Like replacing mtee with tee, strip the .exe from commands and such).

Then decide which version you want to have and create the dummy-files that are searched for by the script. (You know these from the SET-stuff at the top. Like BWP_English, BWP_Expert and such.)

Create a backup of your folder.
Go ahead and run the script.
Hopefully you will have fun.

Thanks, I'll try my hand at this surgery, and report the results
- E

[dabus]

Here is a testfile that has replaced variables. You need to do the other stuff though.

Edited by dabus, 14 March 2010 - 11:28 AM.

[Eric P.]

Here is a testfile that has replaced variables. You need to do the other stuff though.

I saved a copy of the file with the name BiG World Install.sh, then replaced DOS commands with Unix equivalents and again saved the file. When I navigate to /BGII\ -\ SoA in the Terminal, and drag/drop the file onto the Terminal window to run it, the following error appears:

-bash: /BGII - SoA/BiG World Install.sh: Permission denied

Huh? Please help! I'm getting there, but it's such slow going...

Thanks,
Eric

[dabus]

I guess you did not make the file an executable. Set the bit and it should work.
Set it with your filemanager or open the terminal and do a

chmod 777 /BGII\ -\ SoA/BiG\ World\ Install.sh

Or run the file with

/bin/bash /BGII\ -\ SoA/BiG\ World\ Install.sh

The backslash is needed in a bash to tell the program that after the next space there is no next parameter but it's a part of the current one.

You could also spare yourself some trouble by converting the file to lowercase and avoid spaces.

[Mike1072]

For what it's worth, the IR fixes included in the BiG World Fixpack are the same ones we provide in the mod's forum, attached to the first post here. If you're having trouble with the .patch files, you'll probably find it easier to just extract the contents of v2_hotfixes.rar to your main BG directory and overwrite the files when it asks.

However, if you can get a Unix-friendly version of the BiG World Fixpack set up, you'll have a much easier time dealing with all the mods at once.

[Eric P.]

I guess you did not make the file an executable. Set the bit and it should work.
Set it with your filemanager or open the terminal and do a

chmod 777 /BGII\ -\ SoA/BiG\ World\ Install.sh

Or run the file with

/bin/bash /BGII\ -\ SoA/BiG\ World\ Install.sh

The backslash is needed in a bash to tell the program that after the next space there is no next parameter but it's a part of the current one.

You could also spare yourself some trouble by converting the file to lowercase and avoid spaces.

Changed the filename to bigworldinstall.sh, then navigated to BGII - SoA in the Terminal. Entered /bin/bash bigworldinstall.sh and got the following error message:

: command not found line 2:
bigworldinstall.sh: line 9: syntax error near unexpected token `('
bigworldinstall.sh: line 9: `:: Workaround to be able to use this patch 'lso without a megamod (shall not be applied without a megamod)

Some characters may need replacing. How do I correct and continue?

Thanks,
Eric

[dabus]

:: are comments. Replace :: at the beginning of a line with a #.

[Eric P.]

Forgot to back up the file, and I just had to delete the entire BGII folder, so I can install again from install discs. I was getting a KERN_PROTECTION_FAILURE error whenever I tried starting a new multiplayer game (which failure caused a CTD when the new game was almost finished loading). I uninstalled one mod at a time, in the reverse order of installation, and tried starting a new game after each uninstall. I took it all the way down to just BG2 Fixpack and Item Revisions being installed, and still the same error happened. Finally, I restored critical files, and tried starting a new game with this unmodified version of the game. Same error...without any mods!

I suspect that there are some files that get changed somewhere besides chitin.key and the data and override folders. In any case, I must reinstall everything again, then create a new .sh file for automating the mod installs.

Thanks,
Eric

[Eric P.]

Installed BGII - SoA/ToB with latest patch, maximum install on my PPC G4 Quicksilver Mac under OS X 10.4.11 (1.47 GHz PPC G4, 1.25 GB SDRAM, ATI RADEON 7500 AGP graphics card). Now extracting archives of my mod collection, dropping each extracted item into the BGII - SoA folder for processing and installation.

I'll see if a game will start before I begin installing mods, then take it one at a time again.

Happy modding,
Eric

[dabus]

Did you make a backup this time before you want to smash your head on your desk because the install fails and you have to play DJ again?

[Eric P.]

Finally, I've got a usable install! I learned that TextEdit is not a good choice for editing Baldur.ini, but TextWrangler does fine. I've installed the new version of BG2 Fixpack and started a test game. off to a fine start, as everything looks and behaves as it should. I'll run the game into Chapter 2, then probably install another mod (1PP is next) and continue the process.

Thanks,
Eric

[Eric P.]

With all the mods I plan to install located in the BGII - SoA folder, I made a zipped archive of the whole shebang. The only mod installed so far is BG2 Fixpack. The archive size is 6.87 GB.

OK, bonehead question: would the archive fit on a DVD? I have an external DVD +-RW drive that I can use, if so. Otherwise, I'll keep the archive on my data HD, which is separate from my boot drive.

Onward and upward,
Eric

[Jarno Mikkola]

The archive size is 6.87 GB.
OK, bonehead question: would the archive fit on a DVD?

The standard DVD is 4.7Gb... which becomes ~4.37Gb depending on what is calculated... The double layer DVD is promised to have 8.5Gb space... so the 6.87Gb does go well on a double layer DVD...

Edited by Jarno Mikkola, 15 March 2010 - 12:27 PM.

[Eric P.]

The archive size is 6.87 GB.
OK, bonehead question: would the archive fit on a DVD?

The standard DVD is 4.7Gb... which becomes ~4.37Gb depending on what is calculated... The double layer DVD is promised to have 8.5Gb space... so the 6.87Gb does go well on a double layer DVD...

Good deal; I'll see what I can do to archive...although I now wonder if perhaps I should at some point make a new, 100% clean + BG2 Fixpack installation for burning to a DVD, and not add anything more to the BGII folder, as many mods will continue to be updated. This makes me wonder if I should even install the Fixpack for such archiving purposes, since that will likely also be updated at some point.

Thanks,
Eric