Creature offset checker borks (again)

[Lollorian]

Hey there!

A BWP install shows this error when trying to run the creature offset checker:

Code: [Select]

[WeiDU.exe] WeiDU version 22000
[WeiDU.exe] Using scripting style "BG2"
WARNING: unable to open [temp/0/UNINSTALL.0]: Sys_error("temp/0/UNINSTALL.0: Permission denied")
      Will be unable to UNINSTALL later.
ERROR: Sys_error("temp/0/ARGS.0: Permission denied")
PLEASE email the file nul to me
Automatically Skipping [creature offset checker] because of error.
The debug log attached in this post.

Oh and reason for posting here is ... umm ... no clue but the offset checker has no forum/thread and it's not even a mod and the error seems all WeiDU-y

[the bigg]

Looks like the temp/ or temp/0/ directories became read-only. It's certainly most likely not something caused by a change in WeiDU - 220 didn't change anything related to file access relative to 219 (in fact, it only fixed a regexp regression that showed up in 219), and neither did 219 change anything file-related. Even so, 219 has been out for more than a month, so I'd guess it's somewhat safe to assume that the bug is unrelated to WeiDU.

By the way, you shouldn't use temp/ for backups - the game writes and reads to that folder when it saves games, and spurious backup files might ruin the process.

[Lollorian]

Thanks for the quick reply!

Looking at the BWPFixpack.bat, it runs the cre_check.tp2 through this bit:

Code: [Select]

:cre_check
IF EXIST "%WEIDU%" (
    call :show_message "%MESSAGES%\cre_check.txt"
    "%WEIDU%" --noautoupdate --force-install 0 --nogame --log nul "%UTILS%\cre_check.tp2" --args "%UTILS%" | %TEE_CMD%
)where the variables are:

Code: [Select]

SET MAIN_DIR=BiG World Fixpack
SET UTILS=%MAIN_DIR%\_utils
SET MESSAGES=%MAIN_DIR%\_messages
SET TEE_CMD="%UTILS%\tee" -a "BiG World Debug.txt"
SET WEIDU=WeiDU.exe... not sure exactly how the temp folder gets in here

[Lollorian]

... also, could it be possible that the error came up not because the temp/ folder became read-only, but because there's no temp/0/ folder?? Vanilla BGII-SoA installs don't usually have a 0 folder inside the temp ... or do they??

[the bigg]

... not sure exactly how the temp folder gets in here

cre_check.tp2 begins with

Code: [Select]

BACKUP tempIt uses COPY + to avoid creating backup files, so save files shouldn't be corrupted by using that folder for backup purposes.

... also, could it be possible that the error came up not because the temp/ folder became read-only, but because there's no temp/0/ folder??

UNINSTALL ~a/b/c/d/~ will create, in order, a/, a/b/, a/b/c/ and a/b/c/d/, so that is not possible.

OTOH, if temp or temp/0 is a regular file, WeiDU might barf out with a similar message. In fact, a well known bug on OSX is that temp is a regular file, so that might be the cause of the problem.

[Lollorian]

cre_check.tp2 begins with

Code: [Select]

BACKUP temp

That's almost ... an epiphany Awesome! So changing that to something cre_check-specific would prolly do, no?? Why not just use the BWPFixpack folder itself?

Err, can the backups be done in folders with spaces in their names?? Like

Code: [Select]

BACKUP "BiG World Fixpack\_utils"?? (this is where the .tp2 is)

OTOH, if temp or temp/0 is a regular file, WeiDU might barf out with a similar message. In fact, a well known bug on OSX is that temp is a regular file, so that might be the cause of the problem.

If Arkenor does use OSX ... wow! :bow:

[the bigg]

Err, can the backups be done in folders with spaces in their names?? Like

Code: [Select]

BACKUP "BiG World Fixpack\_utils"?? (this is where the .tp2 is)

People who put spaces in file names should be raped in the ass by a donkey and shot into the sun by his ejaculation. Other than that, WeiDU should deal with space in file names correctly.

[Lollorian]

O_o

Well that was ... ok I can't stop imagining that <must ... stop ... SMILING!!!>

Kinda harsh though ...

[Echon]

He will post something like that whenever people do not meet whatever arbitrary standards he goes by. You will get used to it.

[the bigg]

whatever arbitrary standards he goes by.

You don't use the command line very often, or you'd feel like I do about spaces.

[Echon]

Not very often, no. But the DOS prompt in recent versions of Windows is cool with spaces so even if I did, it would make no difference.

[the bigg]

Cygwin is less forgiving than cmd.exe about spaces (especially once you start playing around with redirections and whatnot). Also, cmd.exe being forgiving about spaces is a security hole (I can't seem to find the article where I read that; basically, if it exists, C:\Programs.exe is run instead of C:\Program Files\Whatever\File.exe).

[Arkenor]

OTOH, if temp or temp/0 is a regular file, WeiDU might barf out with a similar message. In fact, a well known bug on OSX is that temp is a regular file, so that might be the cause of the problem.

If Arkenor does use OSX ... wow! :bow:

Nope. I use Windows 7, and my temp/0 folder is alive and well.

Edit: though as it turns out, it's contents had mysteriously become read-only, which explains why the installer choked. Now I just need to figure out how they became read-only in the first place.