> Some useful improvements, but you knew that. I never get a second > error now and I can eliminate all errors whenever I specify the path > for the Namesapce. I can get the error when specifying the Namespace > if I have anti-virus (avast) _and_ Google Web Accelerator both > enabled. Disabling either one allows the process to complete without > error. Guess which one is going to be deleted from my system?
Heh. Yeah, you're on your own on that one. I never run antivirus software. > There is still a problem when trying to create a nemspace using the > default path condition. Now I consistently and immediately get an > asp.net error page telling me that flexwiki.config is being used by > another process. This happens in every case 100% of the attempts (5 so > far) with different key input timings to give some randomness to the > testing. In none of the cases is there any input to the > flexwiki.config file or any creation of a directory anywhere to > satisfy the namspace requirements. Blast! I did test this, and it worked on my system. Can you once again post the complete error? I have to imagine it's coming from somewhere else now, but I can't figure out where. > I should also mention that this is really a MacBook Pro with a 2GHz > Core Duo (not the Core 2 Duo) running WinXP 32bit natively through > Boot Camp. the reason for mentioning this is that I have not set any > processor affinity preferences. > > I just did a sixth try with TaskManager running to see how the dual > procs were handling the various tasks. It is quite interesting. > Accessing pages within flexwiki show that the dual processors are both > active during the processing of a request. The very act of running > Task Manager and monitoring the processors allows the unspecified path > for the namespace process to run without error, _but_ with no > namespace created or any changes to the flexwiki.config file.???? Hmm. OK, I can't imagine this has anything to do with it being a Mac. And to tell you the truth, I think I saw something similar when I was testing, but I couldn't repro it. I.e. the creation process proceeded without error but the namespace wasn't created. I figured I just did something wrong because I couldn't reproduce it. As to why a second processor would be active, I'm guessing that it has to do with the fact that the FileSystemWatcher calls come in on a second thread. So you're seeing the configuration reload simultaneously with the namespace creation. That's a guess. Let's tackle the error first. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Flexwiki-users mailing list Flexwiki-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flexwiki-users
