ffxi-boot crashing

[msulli1355]

If it matters, I'm running revision 2093 on my linux box. Whenever I connect from my Windows Vista laptop and try to talk to a mission npc, ffxi-boot crashes. Windows, of course, gives me no information whatsoever. Does ffxi-boot make a log file anywhere? Last time I hadn't even spoken to the mission npc yet. I walked near him and targeted him. The following is the server output from just before the crash:

[20:30:13][Info] mapsession:192.168.2.101:54090 is coming to world...
[20:30:13][Info] parse: 00A | 0001 0000 2E from user: Dechelsea
[20:30:13][Debug] CZone:: Bastok_Markets IncreaseZoneCounter <1> Dechelsea
[20:30:13][Info] parse: 011 | 0002 0001 04 from user: Dechelsea
[20:30:14][Info] parse: 0DB | 0003 0002 14 from user: Dechelsea
[20:30:14][Info] parse: 00C | 0003 0002 06 from user: Dechelsea
[20:30:14][Info] parse: 061 | 0003 0002 02 from user: Dechelsea
[20:30:14][Info] parse: 01A | 0003 0002 08 from user: Dechelsea
[20:30:14][Debug] CLIENT Dechelsea PERFORMING ACTION 14
[20:30:14][Info] parse: 04B | 0003 0002 0C from user: Dechelsea
[20:30:14][Info] parse: 0E0 | 0003 0002 4C from user: Dechelsea
[20:30:14][Info] parse: 00F | 0003 0002 12 from user: Dechelsea
[20:30:14][Info] parse: 05A | 0003 0002 02 from user: Dechelsea

[msulli1355]

It's not just the mission npcs. It's pretty much any npc I try to interact with. The curious thing is that deChelsea was able to get a signet from Crying Wind before this started happening. Here's some more server output:

[20:30:14][Info] parse: 00C | 0003 0002 06 from user: Dechelsea
[20:30:14][Info] parse: 061 | 0003 0002 02 from user: Dechelsea
[20:30:14][Info] parse: 01A | 0003 0002 08 from user: Dechelsea
[20:30:14][Debug] CLIENT Dechelsea PERFORMING ACTION 14
[20:30:14][Info] parse: 04B | 0003 0002 0C from user: Dechelsea
[20:30:14][Info] parse: 0E0 | 0003 0002 4C from user: Dechelsea
[20:30:14][Info] parse: 00F | 0003 0002 12 from user: Dechelsea
[20:30:14][Info] parse: 05A | 0003 0002 02 from user: Dechelsea
[20:31:22][Debug] map_cleanup: Dechelsea timed out, session closed
[20:31:22][Debug] CZone:: Bastok_Markets DecreaseZoneCounter <0> Dechelsea
[20:31:25][Debug] map_close_session: session closed
[20:34:11][Debug] UpdateWeather Finished
[20:37:27][Info] mapsession:192.168.2.101:54090 is coming to world...
[20:37:27][Info] parse: 00A | 0001 0000 2E from user: Dechelsea
[20:37:27][Debug] CZone:: Bastok_Markets IncreaseZoneCounter <1> Dechelsea
[20:37:27][Info] parse: 011 | 0002 0001 04 from user: Dechelsea
[20:37:28][Info] parse: 0DB | 0003 0002 14 from user: Dechelsea
[20:37:28][Info] parse: 00C | 0003 0002 06 from user: Dechelsea
[20:37:28][Info] parse: 061 | 0003 0002 02 from user: Dechelsea
[20:37:28][Info] parse: 01A | 0003 0002 08 from user: Dechelsea
[20:37:28][Debug] CLIENT Dechelsea PERFORMING ACTION 14
[20:37:28][Info] parse: 04B | 0003 0002 0C from user: Dechelsea
[20:37:28][Info] parse: 0E0 | 0003 0002 4C from user: Dechelsea
[20:37:28][Info] parse: 00F | 0003 0002 12 from user: Dechelsea
[20:37:28][Info] parse: 05A | 0003 0002 02 from user: Dechelsea
[20:37:52][Info] parse: 01A | 003A 0039 08 from user: Dechelsea
[20:37:52][Debug] CLIENT Dechelsea PERFORMING ACTION 00
[20:37:53][Info] parse: 016 | 003B 003A 04 from user: Dechelsea

[ethril]

I'm having the same problem all of the sudden. This didn't happen until after I updated the server. I don't think mine is as bad as yours because we can still talk to NPCs, but it keeps crashing during fights in Taragongi Cavern and Goblins from the Haruto Ruins. It didn't before, during r1996. I now have r2095. Though it did just start, we didn't crash earlier. I was using the Ashita client and I crashed, my friend was using ffxi-boot, we both keep crashing at the same time.



EDIT: Since posting this I found this in the Bugs section, which sounds exactly like whats happening to us: http://forums.dspt.info/viewtopic.php?f=15&t=583

[diminish]

I'm also having the same problem as well though I'm running windows, but after i updated the client it crashes every time i talk to any npc, but only started after the update from SE