rebuild search patch?

Do you need help? Ask here!

Bug reporting belongs here: http://developer.wz2100.net/newticket
knowall
Greenhorn
Posts: 6
Joined: 10 Oct 2009, 12:29

rebuild search patch?

Post by knowall »

info |08:12:28: [rebuildSearchPath] * Failed to remove path C:\Program Files/data/\ again
info |08:12:28: [rebuildSearchPath] * Failed to remove path C:\Program Files/share/warzone2100/\ again
info |09:08:14: [rebuildSearchPath] * Failed to remove path C:\Program Files/data/\ again
info |09:08:14: [rebuildSearchPath] * Failed to remove path C:\Program Files/share/warzone2100/\ again

can anybody tell me what that means?
Ilr
Trained
Trained
Posts: 61
Joined: 07 Sep 2009, 22:11

Re: rebuild search patch?

Post by Ilr »

I get it ALL the time too and still have no idea what would fix it. I searched my ENTIRE registry looking for its source but still couldn't find the problem. I'm assuming it's only native to windows XP and is some kind of directory data conflict (that most likely causes the voodoo "silent crash")

...I still don't understand why it needs TWO separate data directories (one in the root, and another in your "My Documents")...

edit: spoke too soon...its definitely still happening in every version I use
User avatar
Zarel
Elite
Elite
Posts: 5770
Joined: 03 Jan 2008, 23:35
Location: Minnesota, USA

Re: rebuild search patch?

Post by Zarel »

Ilr wrote:...I still don't understand why it needs TWO separate data directories (one in the root, and another in your "My Documents")...
One is for data installed by the installer (which can write to Program Files), and one is for data created by the game (which cannot).
Ilr wrote:I get it ALL the time too and still have no idea what would fix it.
You're not going to be able to "get rid of" those errors, since those are errors in the code.
cybersphinx
Inactive
Inactive
Posts: 1695
Joined: 01 Sep 2006, 19:17

Re: rebuild search patch?

Post by cybersphinx »

Zarel wrote:You're not going to be able to "get rid of" those errors, since those are errors in the code.
Sounds like we should get rid of that message (or did it ever help to solve anything?).