I have actually reverted to "echo off" as my only autorun command
Emeric
Member Since 06 May 2020Offline Last Active May 10 2020 12:32 AM
Community Stats
- Group Member
- Active Posts 2
- Profile Views 2197
- Age Age Unknown
- Birthday Birthday Unknown
-
Gender
Not Telling
User Tools
Friends
Emeric hasn't added any friends yet.
Latest Visitors
Posts I've Made
In Topic: Baldur's Gate Trilogy v1.21
07 May 2020 - 12:12 PM
In Topic: Baldur's Gate Trilogy v1.21
06 May 2020 - 09:41 AM
Hi modders,
First of all, thanks so much for your work on the Infinity Engine games. I recently got the urge to replay BGT and was delighted to find everything still available.
I had the following trouble with my installation. I solved the problem myself, but I thought I would mention it here in case anyone else can benefit from it.
The last time I failed to install BGT, the problem was some custom configuration I had set up for my Windows shell (i.e. Windows Command Prompt, or "cmd.exe"). New cmd.exe instances were configured to set their working directory to a fixed location, namely "d:\". By default, the working directory would be inherited from the process that started the particular cmd.exe instance. For BGT, that process was setup-bgt.exe (or some other process started by setup-bgt.exe). When setup-bgt.exe was run, files that should have been written into the BG game directory (or a subdirectory of it) were instead written into "d:\". The BGT installation would fail because it could not find files it thought it had written into the game directory.
The solution was to temporarily remove the custom configuration from cmd.exe. In the Windows registry, I changed "HKEY_CURRENT_USER/Software/Microsoft/Command Processor/" from "echo off & cd /d d:\" to "echo off", ran the installation, then changed it back. This worked perfectly.
I don't know if this is worth a line in the FAQ or a code change to guard against. Do as you wish with the information, and thanks again.
- Spellhold Studios
- → Viewing Profile: Posts: Emeric
- Guidelines