New Error Messages

[Buckwheet]

Started to get these around the 26th. Not 100% sure what changed.

But some behavior I am now seeing is that the Narost window doesn't come up it just sits on the task bar for Windows 7. Optimus appears not able to determine what %xp I am at so it runs once then stops.

Not sure if they are related or not.

But I am able to connect.

info: Sun Dec 27 08:14:50 -0800 2009
info: $lich_dir: C:/Users/Administrator/Documents/lich/
info: $script_dir: C:/Users/Administrator/Documents/lich/scripts/
info: $data_dir: C:/Users/Administrator/Documents/lich/data/
info: $temp_dir: C:/Users/Administrator/Documents/lich/temp/
info: HAVE_REGISTRY: true
info: HAVE_GTK: true
info: no launch file given
info: no force-mode info given
error: registry_get: The system cannot find the file specified.
C:/Program Files/Ruby-1.8.6/lib/ruby/1.8/win32/registry.rb:668:in `read'
C:/Users/Administrator/Documents/lich/lich.rbw:5576:in `registry_get'
C:/Program Files/Ruby-1.8.6/lib/ruby/1.8/win32/registry.rb:532:in `open'
C:/Program Files/Ruby-1.8.6/lib/ruby/1.8/win32/registry.rb:608:in `open'
C:/Users/Administrator/Documents/lich/lich.rbw:5575:in `registry_get'
C:/Users/Administrator/Documents/lich/lich.rbw:6380
C:/Users/Administrator/Documents/lich/lich.rbw:7366:in `call'
C:/Users/Administrator/Documents/lich/lich.rbw:7366
C:/Users/Administrator/Documents/lich/lich.rbw:6638:in `initialize'
C:/Users/Administrator/Documents/lich/lich.rbw:6638:in `new'
C:/Users/Administrator/Documents/lich/lich.rbw:6638
info: gamehost: storm.gs4.game.play.net
info: gameport: 10024
info: game: STORM
info: launcher_cmd: "C:\PROGRA~1\SIMU\Launcher.exe" C:\Users\Administrator\Documents\lich\temp\lich.sa l
info: waiting for client to connect...
info: connected
info: connecting to game server (storm.gs4.game.play.net:10024)
info: connected

Thanks!

[Tillmen]

The error messages aren't related to your issues. It's pretty common to get a registry error there. It's just from failing to read a registry key that doesn't exist when populating the launch order on the install tab.

The problem with narost not coming up is also somewhat common on Windows.. for some people. Try as I might, I can't recreate the problem myself, which makes it pretty hard to work around. You just need to maximize the narost window, then close it, then start up narost again and resize the window. I think that becomes more difficult on Win7. Someone else will know exactly what to do on Win7 if you can't figure it out.

Not really sure what the problem with optimus would be. I'm not really sure what you mean by "runs once then stops" either. You could try these and see if they're correct:


;e echo percentmind
;e echo checkmind(7)

checkmind(7) should return false unless you're fried or saturated.

I'd guess the problem was something else. People who don't use mana while hunting often complain that optimus stops hunting and waits for mana. It could be either of those or something else.

[Buckwheet]

So I did a little testing.

I installed XP SP3 and Vista with all the updates. I get the same error messages in the log file under the virtual machines.

However Narost, and Optimus did work on the clean installs. So I deleted the narost.sav file on the Windows 7 install. This got Narost back working.

I removed the optimus.sav file and I am in the process of seeing if that is back to working.

If anyone doesn't know already Sun makes an awesome free virtual machine software.

http://www.virtualbox.org/

Lets me test just about any OS I can think of and works great. If anyone is going to do testing and would like me to host isos of specific operating systems let me know. Of course they would be without keys.

[Buckwheet]

In regard to running once and stopping: I would kill stuff until fried, return to the resting area and then just sit there.

If I killed optimus and manually re-ran it, it would just go back to waiting. A clean exit out of everything and a relaunch would get it to go again.

After deleting the .sav file it is again working.

Based upon this it appears there was/is a problem with running this across several accounts at the same time, possibly making changes at the same time. I will just work around this by using virtual machines and multiple instances.

No biggie.