Post reply

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:
Subject:
Message icon:
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)?:

shortcuts: hit alt+s to submit/post or alt+p to preview


Topic Summary

Posted by: berelinde
« on: October 06, 2007, 09:20:26 AM »

For the record, if you start an installer, and decide you don't want to install at that time, but might want to do so later, hitting Q is a perfectly acceptable solution. You won't install anything at all. The computer will just pause a brief moment while it performs a couple internal operations that close the program without installing anything (won't even be noticeable on faster machines), then you'll be asked to hit ENTER to close the window and delete weidu.lock.
Posted by: Kulyok
« on: October 06, 2007, 09:14:44 AM »

 
Quote
Am I right in assuming I can just delete these?  So far I haven't actually installed anything yet.

Sure, go ahead, it won't cause any harm. As long as you're not actually installing multiple mods at the same time, everything should be fine.
Posted by: Valdemar
« on: October 06, 2007, 06:43:18 AM »

Yeah, I had a similar experience except I wasn't installing BG2Tweaks I was just running the exe that drops the folder and tp2 etc. into my BG2 game folder.

The dos window opened, I told it Q and it closed.  Then I noticed the lock file.  I moved it away to a safe place. 

Then I was running the Crossmod banter exe, not installing it mind you, just running the exe to drop everything into the game folder and it autostarted weidu too. 

Except this time the only message it gave me was to hit enter to install the mod. 

I've been up all night RE-installing the game from ground up and wasn't installing anything just yet - hadn't even gotten around to the BG2Fixpack yet and so I was afraid of actually installing the Crossmod pack if I hit enter. 

Now, this probably would have just launched the tp2 and I could have selected "quit" from there, but I wasn't taking any chances. 
Anyway, I hit the dread X to close the dos window - sorry, but I just couldn't see any other way out with installing something before I was ready. 

So that produced my second lock file. 

Am I right in assuming I can just delete these?  So far I haven't actually installed anything yet. 

for the record: I've never run multiple weidu setups over one another and garbled my tlk file (which as I understand it, is what this whole lock file is trying to prevent)

btw- thanks to many of the folks in this thread for some fine mods (and helpful tutorials too)
Posted by: iru
« on: October 03, 2007, 05:14:37 AM »

For some reason my BG2_Tweaks.exe opened and closed in a flash first time I tried installing the mod, creating the .lock but from what I can see it did nothing else before closing.
You guys solved the problem easy enough for me; a google search for "bg2 can't install mod" gives this thread as the first result.
After a manual delete of the lock and a new try at the installation it works perfectly and I'm enjoying the game.

Thanks for the wonderful creations you bring. :)
Posted by: jcompton
« on: October 02, 2007, 09:26:47 AM »

Do any of those have a demonstrably nonzero chance of screwing with people's minds?

The cure is worse than the disease, gang. Flat out.
Posted by: the bigg
« on: October 02, 2007, 09:21:00 AM »

Quote from: jcompton on October 02, 2007, 09:16:32 AM
Although the march of progress is a fine and wonderful thing, I would like the pro-weidu.lock organization to please sit down and wonder for a moment why this wasn't done sooner in WeiDU's 6+ year history.

The same could be said for INCLUDE, READ_LN or DEFINE_PATCH_MACRO  :)
Posted by: jcompton
« on: October 02, 2007, 09:16:32 AM »

Although the march of progress is a fine and wonderful thing, I would like the pro-weidu.lock organization to please sit down and wonder for a moment why this wasn't done sooner in WeiDU's 6+ year history.

(hint: it's not because Wes lacked the technology.)

(second hint: it's not because people have suddenly gotten dumber.)
Posted by: CoM_Solaufein
« on: October 02, 2007, 06:58:49 AM »

Here I thought we would go back to the good old days of IAPs and Dialog.tlk replacement mods.
Posted by: berelinde
« on: October 02, 2007, 05:51:36 AM »

Quote from: Azkyroth on October 02, 2007, 02:46:22 AM
II discovered WeiDU.lock either today or yesterday in that fashion, and if this has happened at times other than WeiDU choking on my own Alphas, I can't remember them. O.o

Yeah, that was how I found out about it, too. When the installation goes smoothly, you never even know it's there, for the most part. But installing your own alpha, if it doesn't install because of errors, it stays on.

In any case, WeiDU 201 ignores it.
Posted by: Kulyok
« on: October 02, 2007, 03:14:10 AM »

Quote
Yes, a backup for the Tutu-install would have been a cool idea. Would have been. Gha.

I'm sorry I cannot do anything for your German install, but if you have EasyTutu, please, check the link I posted - the backup attached there(for EasyTutu) should be working.

I must say, though, I am happy that weidu.lock is no longer a feature: it is too dangerous to non-proficient users in any form; however, since some popular mods(BG1 NPC Project, Tweaks) have been updated with Weidu 200 already, it'll be a long while, yet, before the problem is gone entirely.


And welcome to PPG, Azkyroth.
Posted by: Azkyroth
« on: October 02, 2007, 02:46:22 AM »

I share CMorgan's incredulity.  The only times I've ever closed WeiDU by hitting the "X" have been when it refused to install the mod in question, for whatever reason, and brought me back to the option menu that has Install, something, Quit.  I discovered WeiDU.lock either today or yesterday in that fashion, and if this has happened at times other than WeiDU choking on my own Alphas, I can't remember them. O.o

That said, does anyone else think it sounds like a good idea to have at least an optional setting for WeiDU to automatically delete the WeiDU.lock file when it A) encounters an error that prevents installation of the component it's on and B) has not successfully installed any other components of the same mod?  This would be mildly less frustrating to me, but I'd have to agree that it's a relatively trivial feature...
Posted by: jastey*
« on: October 02, 2007, 02:05:00 AM »

Yes, a backup for the Tutu-install would have been a cool idea. Would have been. Gha.
(Backup? No, that won't happen to me again, that I'll screw up my install, would it? I knew how to do that, so I don't need a backup.) Maybe I should print a "it was my own fault" sign and attach it to my forehead. (Surely would lead to some discussions in the office.) :(
Posted by: Kulyok
« on: October 02, 2007, 01:19:27 AM »

In any case, I would really advertise keeping a clean backup for both your installations handy.
Posted by: jastey
« on: October 02, 2007, 01:04:28 AM »

I was thinking about this, too. I like your idea, berelinde. Only problem would then be that people don't find their weidu.logs if problems arise.
What I came up with, was, would it be possible to include the lock file for the MODDER mode, at least, if it makes any sense? I think for me, it would have made a lot of sense. If it closes / gets deleted correctly for an installation that is ended by [n] or [q], of course.
Posted by: berelinde
« on: October 01, 2007, 06:48:49 PM »

Thing is, we can't have it both ways. Either we have to advise people six ways from Sunday not to close installer windows by hitting X and still have isolated incidents where weidu.lock isn't deleted, or we wind up with users who hose their installs.

Annoying, ain't it?

WeiDU201 ignores weidu.lock if it's empty, right? I wonder what would happen if the debug file for the mod was saved in weidu.lock during compliation and only migrated to setup-MyMod.debug after all processes are completed? Maybe as the last function before the prompt to hit ENTER pops up? That way, the user who insists on closing the window with X after the mod has installed completely can still do so (assuming he sees the ENTER prompt at all), but the user who attempts to install two mods at once will have that nice debug file in weidu.lock to prevent it from being ignored by WeiDU201.

OK, just wondering aloud. Don't anybody shoot me, please.