WinEQ 2.0 Lite discussion
Moderators: Lavish Software Team, Moderators
-
Lax
- Owner
- Posts: 6634
- Joined: Fri Jun 18, 2004 6:08 pm
Post
by Lax » Thu Nov 04, 2004 12:37 pm
Before this gets posted, WinEQ 2.0 RC3 wont work for the moment. I'm updating WinEQ 2.0 to RC4 at this time. Sorry, this should be done in about 10 minutes.
-
Lax
- Owner
- Posts: 6634
- Joined: Fri Jun 18, 2004 6:08 pm
Post
by Lax » Thu Nov 04, 2004 12:58 pm
The update has been completed, simply restart WinEQ 2.0 to update to RC4.
-
jabon
- Non-Subscriber
- Posts: 17
- Joined: Tue Aug 31, 2004 8:19 pm
Post
by jabon » Thu Nov 04, 2004 2:20 pm
Perhaps others are experiencing this too, but the patcher seems to be in an infinite loop downloading Lavish.dll and EQPlayNice.dll. End Process won't work, it results in an error saying that operation is not valid for this program. I'm trying to restart now.
-
jabon
- Non-Subscriber
- Posts: 17
- Joined: Tue Aug 31, 2004 8:19 pm
Post
by jabon » Thu Nov 04, 2004 2:23 pm
Restart worked, I got a complaint that wineq2.dll could not start because of the shutdown, perhaps that is where the loop is happening.
-
Eryi
- GamingTools Subscriber
- Posts: 8
- Joined: Wed Jul 14, 2004 5:52 am
Post
by Eryi » Thu Nov 04, 2004 9:33 pm
Perhaps others are experiencing this too, but the patcher seems to be in an infinite loop downloading Lavish.dll and EQPlayNice.dll. End Process won't work, it results in an error saying that operation is not valid for this program. I'm trying to restart now.
The End Process does work, but you have to be VERY VERY quick. The Processes switch between WinEQ2.exe and Lavishpatch(er).exe (Sorry, can't remember if there was an "er" on the end of that or not) and it switches between the two.. You can't pick the patcher and attempt to kill it after it switches to the WinEQ2.exe, or it'll complain.
If your quick, you can Select, End and kill the process before it switches, that will stop the loop.
-
Lax
- Owner
- Posts: 6634
- Joined: Fri Jun 18, 2004 6:08 pm
Post
by Lax » Thu Nov 04, 2004 9:36 pm
In the next release it's going to pop up a message box if it couldn't overwrite a file