Pocket Plane Group
Friends and Neighbors => Weimer Republic (WeiDU.org) => WeiDU => Topic started by: Kulyok on August 04, 2007, 10:32:14 AM
-
We're having a problem here with WeiDU 200:
Now each time Setup-Mod.exe runs, it creates a weidu.lock file in BG2 directory with its own path and name. While the file is there, the user can't launch any other Setup-Mod2.exe - Weidu will tell him "Sheesh, don't run two mods at once!" After the user installs the mod and presses Enter in the end, the file disappears.
However. If a user exits Setup-Mod.exe via pressing X button, weidu.lock remains here. So, unless the user deletes it manually, the user is not able to install other mods. Ever. Again.
(And the bigg is on holiday (http://forums.spellholdstudios.net/index.php?showuser=2083).)
So. Um. Yeah.
-
As posted on SHS:
Confirmed on retest.
WeiDU 200 acts as expected. At the end of an install, or at any time you use Q to quit, WeiDU asks you to press enter. Doing this results in expected behavior; WeiDu releases the lock and lets you proceed.
If, on the other hand, you yank the plug on the process by blowing it away instead of following the directions, on your head be it and a plague on all your house even unto the seventh generation, I say verily unto thee expect there to be serious problems :)
There is no more a fix for this than there is for running your car into a pedestrian. Just don't do it, for *any* command line program. Noone likes their little universe imploded; especially programs.
-
I can make the message more explicit and delete the file when "press enter to exit" is pressed.
-
It could not hurt to make the message more obvious; perhaps a warning up front reminding folks that in order for the installer to work it is important to follow directions?
I am not sure how to say "don't close WeiDU via the litle "x" on your screen - only close it by following directions and pressing "enter"."
-
I am not sure how to say "don't close WeiDU via the litle "x" on your screen - only close it by following directions and pressing "enter"."
I think you just said it.
-
It might be possible to force Windows to delete the lock file if closing via the X button, but it is easier to simply delete the lock file before displaying "please press enter to exit" (not to mention that forcing Windows to do stuff is not easy).
-
Deleting the file before displaying that message would help. There'll still be a problem of these users who close their setup-exe's in the middle of their installations, though(for example, if they installed an NPC mod and decided to skip 'optional portrait' component).
-
In which case, they'd deserve all bugs they get.
-
Yes, but imagine users doing it for several years and not getting any bugs, and then all of a sudden... I guess we'll just have to see how many "can't install this!" bug reports there'll be; I'm just worried I'll have to deal with my share, so to say.
-
They seem few enough as of now. Users doing as you say for years would suffer from broken .tlk anyway.
(I wish there was a way to display a pop up saying "YOUR AN IDIOT" if an user decides to close weidu via the x button. That'd be a much easier way to deal with the problem).
-
Part of that is probably moving the decompression of sound and area files from the end of the installation to the middle or beginning. Users were accustomed to waiting until all the sound files and tiles unpacked, so they'd wait until they got to the ENTER prompt, but now they don't have to, so they just close it with components still in the cue.
Gotta say that I've made just about every mistake possible while installing a mod from attempting it with the game running to trying to install two at once, to installing it in the wrong directory, but I would have never thought of hitting that x. Mostly because I was so sure I'd do it wrong that I wouldn't feel safe until it said it was done, and that it was safe to hit ENTER.
-
I received the "you cannot install two mods at the same time" prompt when trying to reinstall the same mod (WeiDU 200, BG1NPC preversion). I definitely did close any setup window with ENTER, not using the "x", that is for sure.
But I had a lot of CTDs before, from BGTutu because of a (confirmed) EDIT: engine! - bug, so I don't know what exactly happened there.
-
Is there any chance of having the option to turn the creation of the lock file off? It's really annoying.
-
In the next version of WeiDU weidu.lock will be ignored if it is empty (= you manually create an empty weidu.lock file in the bg2 directory).
If, once more W201 mods start being released (= where you can also close via 'X'), we'll continue to have lots and lots of people reporting "You can't install this", I'll remove the feature altogether.
-
This is the error message in WeiDU 201. Please provide feedback as to wether it's clear enough.
Also, manually saving an empty WeiDU.lock file would disable the feature (which you can do anyway by typing "two" at this prompt)
You cannot install more than one mod at a time or you will have bugs.
Try to install the mod once again, after the following:
blah_blah
has finished.
In the future, don't close the setup-xxx.exe window with the 'x' icon, but press
ENTER once instructed. Failure to do so (especially if you close via 'x' before
"Press ENTER to exit." is displayed) WILL result in a broken game.
If you are sure you received this message in error, then please type `one'
(without the quotes) and press ENTER to continue.
If you are an advanced user and would like to forever disable this message, then
please type `two' (without the quotes) and press ENTER to continue.
Press ENTER to exit.
-
Sounds good to me.
Not that I'd ever do this but what would you think of someone possibly including an empty weidu.lock in a mod release?
I just thought of this when I read your post.
-
Not that I'd ever do this but what would you think of someone possibly including an empty weidu.lock in a mod release?
I'm not going to stop you (or whomever), but ideally it's there for the modder's benefit, since its aim is to block, or reduce, people reporting dialog.tlk problems, if they happen because the user runs two setup-xxx.exe or close 'too early' via the 'x' button.
If it proves to cause more modder headaches than a broken .tlk (= statistically you get more weidu.lock reports than you were getting "wrong lines"), then I'll remove the feature.
-
I've noticed something while using WeiDU to test-compile prior to a debugging run: if everything goes fine during the installation, the weidu.lock is removed after hitting ENTER, but if I got a parse error (I did say it was a debugging run, didn't I?), the weidu.lock remained after hitting ENTER and had to be manually deleted.
Naturally, our released mods won't have parsing errors, so this is a non-issue, but I thought I'd bring it up anyway.
-
What command line did you use? Or did you refer to running setup-xxx.exe when setup-xxx.tp2 doesn't parse?
-
Er, sorry I wasn't clear. Technical terms aren't my strong suit, so I'll describe what I was doing in more detail, in the hopes that it answers that question.
I was running the regular weidu installer, using the setup-xxx.tp2 to install a mod that contained errors, like missing tildes, missing END's at the end of APPEND's, that kind of thing. Setup-xxx.tp2 was working just fine. It was the files that had bad code. I'd get the error message like I should, would select "quit" to stop the installation, hit ENTER to exit, the command window would close, I'd go fix the files that were messed up, and restart the installer. When the installer didn't hit any errors in the files it was compiling, the weidu.lock was deleted as I expected it to be, but if I did have errors severe enough to stop the installation, the weidu.lock remained after hitting ENTER to close the command window.
-
I'm rather afraid a part of my target audience doesn't pay attention to error messages, even well-written and detailed - especially when we're talking about foreign players. I mean, take a girl who just bought a computer, needs her brother or her dad to teach her how to install Baldur's Gate, and the only thing she can do with a mod is to 1) run .exe file; 2) if she sees a mistake, she deletes it and doesn't play it again, because she's too shy to post on the forums. (That's not some abstract girl, it's me - around the time SoA came out).
I love WeiDU to bits, and AT_NOW will have my heart forever - but as for this feature, I'm scared for these girls I mentioned.
-
the problem is that you consider people "advanced" enough to not close setup window via "x" button and at the same time "unadvanced" enough to install 2 mods at the same time. There's no such people, so this feature is vain. I use words "advanced" and "unadvanced" intentionally, as knowledge of computers has absolutely nothing to do with intelligence.
-
If somebody really knows what he's doing, he might be able to ctrl-c a mod install when he knows it won't cause problems (E.G. the tp2 doesn't overwrite override files, but works on a temp directory), and/or can fix weidu.log after force-stopping an installation.
Advanced people aren't those that never make stupid mistakes, they're those that can fix up the mess afterwards and learn from experience ;)
-
bigg, you're spending too much calories on these recent weidu issues. Just notify people that they have the power to fork the build.
-
?
-
Azazello: Drinking the beer make me a clear. More beer take and I can fly. Drinking on the fly: yess, I'm You! :)
-
What, I get my own spam thread now?
bigg, why was my comment moved from the other thread?
I was relating on the recent weidu change requests. They seem so, hmm, 'minor' (only nice word I could think of at the moment).
-
What, I get my own spam thread now?
bigg, why was my comment moved from the other thread?
No idea - I surely didn't move anything. JCompton might be able to access the DB and figure out who did what.
-
Oh, I actually though it was el ggrande who did it, so I didn't think anything of it. Was a global. You can rejoin them if you'd like.
-
This is the error message in WeiDU 201. Please provide feedback as to wether it's clear enough.
Also, manually saving an empty WeiDU.lock file would disable the feature (which you can do anyway by typing "two" at this prompt)
You cannot install more than one mod at a time or you will have bugs.
Try to install the mod once again, after the following:
blah_blah
has finished.
In the future, don't close the setup-xxx.exe window with the 'x' icon, but press
ENTER once instructed. Failure to do so (especially if you close via 'x' before
"Press ENTER to exit." is displayed) WILL result in a broken game.
If you are sure you received this message in error, then please type `one'
(without the quotes) and press ENTER to continue.
If you are an advanced user and would like to forever disable this message, then
please type `two' (without the quotes) and press ENTER to continue.
Press ENTER to exit.
Just confirming that this is included in v201, as foks seem to be having a good time getting torches and pitchforks going regarding this feature. Like ReadMe, I find this is an important source of user-reported errors, and would prefer to keep the behavior.
I am not going to run off in a huff or be upset if you disable it, but I think it is important enough to fight for.
-
I'm an user ... may be a blind one, but ... sorry ... i don't see the point adding this feature. Are we sure is it something that will help?
"Basic users" don't read messages, so ... i don't see the point here, sorry
Just my 2 cents,
mm75
-
Otherwise, some people will try to install two mods at the same time and get a broken .tlk.
If you don't read messages, then I don't care about you
-
If you don't read messages, then I don't care about you
Unfortunately this is the case of "basic users" where i mean "LOW profile users". Luckily enough it's not my case ;)
Anyway, do u think corrupted dlk files is an issue so often repeated? Of course you (modders) has more experience than me but i've never had a dlk corrupted. Dunnow ... it just seems to me that this option is giving some problems while it saves ... not that much.
Of course just my 2 cents, hat always for your work.
mm75
-
'you' is the generic pronoun (I.e. it can be read as 'somebody').
Every time a new high-profile mod appears, it receives a number of "bug: character says item description lines" reports, so I'd say it the problem is real.
-
I don't know why so many people object to this feature. As a modder, if it really doesn't delete the .lock for a parse error, that is annoying. But for players, I'd say I would prefer one (well, OK, a hundret) "can't install because it sais WeiDU is still running, but it isn't) over several "your mod wrecked my game!!111 All text lines are mixed up / text boxes are empty / etc.". It's far more player friendly than you folks make it look.
-
I don't know why so many people object to this feature.
Because people will discover BG2 and mods, get an error message, delete the whole directory quietly and go play Sims. Our work will go to waste.
It's already happening. Only, a few people actually post about it:
http://www.clandlan.net/foros/lofiversion/index.php/t32249.html
http://forums.spellholdstudios.net/index.php?showtopic=29349
http://forums.bioware.com/viewtopic.html?topic=584276&forum=18&sp=0
http://forums.pocketplane.net/index.php/topic,24423
http://forums.pocketplane.net/index.php/topic,24381
http://forums.pocketplane.net/index.php/topic,24419.msg304362.html#msg304362
- but others do not.
-
OK, OK. Feature deleted. I will push a new version soon enough (= as soon as the Mac compiler does his work). I wanted to do some architectural changes to allow more tp2 features, but it looks like they'll have to wait (besides, this'll allow also my Bigger Resolutions mod to appear earlier).
EDIT: It's uploaded at http://www.weidu.org/~thebigg (http://www.weidu.org/~thebigg). I'll announce formally once the Mac version is ready.
-
[begin rant]
I am sorry to reveal my ugly side, but I am seriously disgusted that people couldn't handle this.
Either folks just never get basic, simple, easy, straightforward instruction on how to use a computer, or I have seriously overestimated the average intelligence of the human population.
You don't stop a car by running into the back of a garage, you don't stop a conversation by executing the other participant, you don't change governments (usualy) by blowing up all polling stations and killing everyone in the current government, you don't shut down a computer by yanking the power cord out of the wall, ad you don't close a command process by blowing up it's little universe.
I am seriously disappointed in this. If*I* know this, at my relatively low level of computer competence and relatively low level of intelligence in general, I honestly cannot imagine what other people are thinking.
I am now going to go close my refrigerator by thowing it face forward onto the floor, turn off the lights in my house by cutting down the power line outside my condo, and start my car by pouring gasoline all over it and lighting a match.
Oh, and I am going to go delete the hours of work put into the ReadMe and documentation. Why bother? Perhaps it is time to mod for PS2, where the funny little magic box handles everything, and when it doesn't work right you take it back to the store and get a new box. Oh yeah. Fun.
[/end rant ]
-
Users, collectively, will not change. We can bang our head against the wall and insist that they're doing it wrong, or we can make it easier for them.
-
Understood. And I am over my rant, and had coffee, and agre. After all, when it comes right down to it, whatever makes it easier to get past the computer and into the story is exactly what we are supposed to be doing.
I must be getting old - gotta not post until *after* morning coffee.
-
What can I say - I just f***** up my BGII install, because I accidentally let a mod installation (the same mod) run simultaneously. The first run, still open and asking whether I want to install, showed the last install error, the second, started after I fixed the error (forgot about the first one), installed fine, I [q] the first one, not thinking what it would do to my WeiDU.log, and now I have the mod installed permanently. I could have written lines of deepest gratitude to the bigg for preventing me of doing this, instead I am cursing, thinking about the necessary reinstall of BGII and Tutu v4 that comes along with it. >:(
I agree to cmorgan's before coffee post. As I stated above: The errors and bugs, i.e. screwed up games produced by people that can't handle an install in a command window will be far more serious and will discourage them further as the error message they get when trying this with implemented lock file. I really think the lock file was a brilliant idea, and I thought so before this happened.
-
The trouble is, outside of BG2, there are plenty of screens that people legitimately close by hitting the x in the corner, so there's an ingrained habit of doing just that.
And, the mods pop up with a message saying "Mod successfully installed." It *looks* like it is done.
Leave the window open for a while, and it becomes apparent that something is still going on, but the initial message plus the x-closes-out tradition leads to misunderstanding.
-
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.
-
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.
-
In any case, I would really advertise keeping a clean backup (http://forums.pocketplane.net/index.php/topic,17555.0.html) for both your installations handy.
-
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.) :(
-
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...
-
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.
-
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.
-
Here I thought we would go back to the good old days of IAPs and Dialog.tlk replacement mods.
-
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.)
-
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 :)
-
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.
-
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. :)
-
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)
-
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.
-
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.