Author Topic: Our first v232 bug  (Read 2067 times)

Offline CamDawg

  • Infidel
  • Planewalker
  • *****
  • Posts: 836
  • Dreaming of a red Xmas
    • The Gibberlings Three
Our first v232 bug
« on: October 02, 2013, 08:43:48 AM »
HANDLE_AUDIO craps out in the decoding process if one of the files being converted has an ampersand or caret in the name.

Code: [Select]
********** Done decoding all input files. **********
 Could not find 'AURENASEPH\AUDIO\K#AUREP': The system cannot find the file spec
ified.


 ********** Done decoding all input files. **********
'.OGG' is not recognized as an internal or external command,
operable program or batch file.
ERROR: cannot locate aurenaseph/audio/K#AUREP&.wav
Stopping installation because of error.
Stopping installation because of error.
Stopping installation because of error.
Stopping installation because of error.
Stopping installation because of error.
Stopping installation because of error.

ERROR Installing [Auren Aseph for BG2:ToB], rolling back to previous state
Will uninstall 138 files for [AURENASEPH/SETUP-AURENASEPH.TP2] component 0.
Uninstalled    138 files for [AURENASEPH/SETUP-AURENASEPH.TP2] component 0.
ERROR: Unix.Unix_error(20, "rename", "aurenaseph/audio/K#AUREP&.wav")
PLEASE email the file SETUP-AURENASEPH.DEBUG to theacefes (theacefes@gibberlings
3.net)
It's an easy workaround, though probably something to look at for v233.
The Gibberlings Three - Home of IE Mods

The BG2 Fixpack - All the fixes of Baldurdash, plus a few hundred more. Now available, with more fixes being added in every release.

Offline Wisp

  • Moderator
  • Planewalker
  • *****
  • Posts: 1131
Re: Our first v232 bug
« Reply #1 on: October 02, 2013, 10:39:44 AM »
Okay, I haven't yet tested this on Windows, but on Linux It is enough to add a layer of quotation around the file names in the AT_NOW (otherwise you run afoul of what the shell considers to be special characters). Mea culpa.

With the reservation that you can't put funny characters in the path to oggdec, because Windows bites. However, that's far less common than funny characters in file names, so it shouldn't be a problem.
« Last Edit: October 02, 2013, 11:31:34 AM by Wisp »

Offline CamDawg

  • Infidel
  • Planewalker
  • *****
  • Posts: 836
  • Dreaming of a red Xmas
    • The Gibberlings Three
Re: Our first v232 bug
« Reply #2 on: October 02, 2013, 11:28:11 AM »
Okay, I haven't yet tested this on Windows, but on Linux it is enough to add a layer of quotation around the file names in the AT_NOW (otherwise you run afoul of what the shell considers to be special characters). Mea culpa.
No worries; I should have caught this earlier. I tested HANDLE_AUDIO on every platform I could find for Mur'Neth and it worked dandy so I assumed it would be fine for Auren, too.
The Gibberlings Three - Home of IE Mods

The BG2 Fixpack - All the fixes of Baldurdash, plus a few hundred more. Now available, with more fixes being added in every release.

Offline Silent

  • Planewalker
  • *****
  • Posts: 10
Re: Our first v232 bug
« Reply #3 on: October 08, 2013, 04:18:56 AM »
Maybe it's a second bug...
I'm trying install solafein, kelsy and kelsy-tob mods on clean bg2 with old weidu v231.13 and with new v232. With old weidu all installed correctly, but with new one i have this error:
Code: [Select]
[J#Klsy25.bcs] PARSE ERROR at line 530 column 1-7
Near Text: %KSONG%
syntax error

[J#Klsy25.bcs]  ERROR at line 530 column 1-7
Near Text: %KSONG%
Parsing.Parse_error
ERROR: parsing [J#Klsy25.bcs]: Parsing.Parse_error
Stopping installation because of error.

Debug-files: http://www.arcanecoast.ru/download.php?id=165

Offline Wisp

  • Moderator
  • Planewalker
  • *****
  • Posts: 1131
Re: Our first v232 bug
« Reply #4 on: October 08, 2013, 08:28:17 AM »
Maybe it's a second bug...
I'm trying install solafein, kelsy and kelsy-tob mods on clean bg2 with old weidu v231.13 and with new v232. With old weidu all installed correctly, but with new one i have this error:
This is a bug exposed by a previous bugfix. When the mus file already exists, ADD_MUSIC sets the wrong variable. It wasn't a problem before because ADD_MUSIC would always determine that the mus file did not already exist and add it anew.

I'll put out a beta later today tomorrow with a fix for this. When do you want v233, people?
« Last Edit: October 08, 2013, 11:45:38 AM by Wisp »

Offline The Imp

  • Planewalker
  • *****
  • Posts: 288
  • Gender: Male
Re: Our first v232 bug
« Reply #5 on: October 08, 2013, 06:46:06 PM »
When do you want v233, people?
How about the day before yesterday... as in as fast as you can to fix this.
There were a few people that failed at their BWS'es.

Offline Wisp

  • Moderator
  • Planewalker
  • *****
  • Posts: 1131
Re: Our first v232 bug
« Reply #6 on: October 09, 2013, 05:52:31 AM »
There were a few people that failed at their BWS'es.
If you are referring to the stuff about Amber, that's an unrelated problem. This issue affects mods that do ADD_MUSIC twice with the same MUS file.

Offline Lollorian

  • Planewalker
  • *****
  • Posts: 96
Re: Our first v232 bug
« Reply #7 on: October 09, 2013, 10:01:33 AM »
Tashia, Kelsey and KelseyToB use J#BLANK.MUS - causes an improperly set %KSONG% variable - results in catastrophic borkage at the climax of a BWP installation (good times) ;D

 

With Quick-Reply you can write a post when viewing a topic without loading a new page. You can still use bulletin board code and smileys as you would in a normal post.

Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.

Name: Email:
Verification:
Type the letters shown in the picture
Listen to the letters / Request another image
Type the letters shown in the picture:
What color is grass?:
What is the seventh word in this sentence?:
What is five minus two (use the full word)?: