Errors in last build

[ChaosSlayer]

another atempt at this- now running eqlaunch.exe directly .
the windows XP reports:

The application has failed to start because its configuration is incorect. Try reinstalling it.


considering the only installation there is unpacking it from the zip file... I am at a total loss what to do. (redownloaded it twice - same thing)

[leslamarch]

Originally Posted by ChaosSlayer

another atempt at this- now running eqlaunch.exe directly .
the windows XP reports:

The application has failed to start because its configuration is incorect. Try reinstalling it.


considering the only installation there is unpacking it from the zip file... I am at a total loss what to do. (redownloaded it twice - same thing)

What is the file size for eqlaunch.exe? 220kb or 152kb? if its 152 Download this one and let me know how that works

[ChaosSlayer]

its in fact 132k
donwloading now...

[ChaosSlayer]

ok its laoded up! thanks much!
so why did the devs puted non working exe there =P

I am sure there gona be MORE errors, considering I am upgrading from 4th month ago build... will play with it for a bit and post later....

prety sure tasks gona be broken to...

[ChaosSlayerZ]

I have just updated to rev 535 and I have EXACT same problem - "eqlaunch.exe is NOT a windows aplication" file size 133 kb

[ChaosSlayerZ]

ok, little update

following leslamarch advice I installed .Net framewokr 3.5

eqlaunch.exe now starts up and seem like its starting up zones

however I am getting errors like:

world told us to start dymanic zone 01 but zone allready started
world told us to start dymanic zone 02 but zone allready started
etc

then it reports that zones were in fact started.

BUT in my minilogin windows I don't see the usual mesages that conection with the server has been established and if i run EQ its unable to connect to server as it doesnt even exists

[ChaosSlayerZ]

I have been digging through it all day and via trial and error I have found a number of errors i have since corrected.

the followign are significant changes since rev 302 (last time I updated) as 302 did not required any of the following

1. Perl must be updated to recent version
2. Must Install .net Frameworks 3.5
3. The opcodes.conf in Minilogin 6.2 is obsolite (its build date 2005!), but it kepts working all way till recent rev. Must be replaced with opcodes.conf from current build


I am still tryign to figure out if Db needs more sql updates to be 535 compateable