jo_i_ells

Open the baldur.ini file with Notepad and check out what the drives are... list the six lines under the [Alias] word to a post.

Finally!! The directory that those six lines were refering had to be changed (my fault...) and now is working even with the other computer's savegame, so absolutely no problem now

Thank you all and specially Jarno for spending part of your time helping people like me

Run the game via the BGMain.exe, not the baldur.exe .

Not working this one:

An Assertion failed in ChDimm.cpp at line number 628
Programmer says: Unable to Open BIF:DATA\HD0GMSOC.BIF

In that case, what you probably should do is to copy the game from one computer to the other ... it's far better this way too if you want to install more than the 2 mods(Fixpack & BGT) cause this guarantees the two games are exact replicates, and if you intent to install the Widescreen mod, install that after the game have been copied to both games individually with their own set of resolution the monitor and GPU can use.

This morning, in my other computer (the one with BGT running) I've uninstalled all BG, because I had the widescreen mod installed, and installed all again without this one, and the game was running all with no problem. I've maken a copy of all the installation, just pasted now in my other computer (the one with BGT installing problems) and when I run the game, appears the little window with the options CONFIGURE, MOVIES, README, etc. but insted of play, I can only select INSTALL, and when I do it, just nothing happens.

Now I really don't know what to do

I've tried again, now without all the spanish additions, so just install GOG version of BG I & II and BGT and still having the same problem. I'm adding an image of the problem I told you about

I don't know what else to do... so I'll try what you said about making a copy of the game in the other computer in a few days.

Actually this is the first error it gives:

Yes, you're right, I typed that error direct from the DOS window and now I can't find it in the debug. Maybe this one is more specifical...