QUOTE(jaclaz @ Oct 9 2007, 10:04 AM)

Ok, I see (IMG:
../forums/style_emoticons/default/smile.gif) , the mis-understanding about your
published work derives from the different meanings of the verb "to publish".
That would also explain your feeling:
On the Merriam Webster:
http://www.m-w.com/cgi-bin/dictionary?book...p;va=publishing
You were using definition 1b "to make public announcement of" whilst I read it in the sense of 2a "to disseminate to the public" or 2b "to produce or release for distribution".
The purpose would be for 2b. I'm free to announce data to the public with the exception that it causes a problem for either users or my equipment. I made an announcement of my tools a year ago and provided links to the whitepapers freely authorized to the public. That was the worst mistake I ever made. I had to lock down the scripts because they were being crawled by self-employed disasters like Googlebot, Alexa and all kinds of other foreign devices, schools and telecoms. You have no idea how frustrating it is when the most abusive attacker you have is an overseas phone company. Yes, a
phone company is crawling me. This needs to stop. Now. o_O
I employed the use of ASP.NET even further with membership roles. The problem is mitigated, but it's still a problem.
QUOTE(jaclaz @ Oct 9 2007, 10:04 AM)

Still, as I see it, it does not make much sense to publicly announce something that is not available, and for which not even a tentative "timeline" or "roadmap" for release exists.
It's publicly available but it has no roadmap due to self-sufficiency. If I see something that would greatly help, I create it. If an associate requests a bolt, I categorize the relevancy and create it. I need to finish writing the Whitepapers, but they're accessible to an authorized and authenticated public.
QUOTE(jaclaz @ Oct 9 2007, 10:04 AM)

All the references to your project I happened to find in your posts here and on 911CD appear to me like bits and pieces, all I could get is that you are working to create a form of WinPE called DaemonPE.
DaemonPE is a horrible time-consuming masterpiece that I had to abandon when I left Seattle in mid 2006. I have references to it available on my site. The documentation is completed but it's nothing incredibly special to use. I've often looked into it since then for the purpose of skipping over the first reboot after the file-copy stage of Windows setup. This project is on hold, it's not cancelled.
QUOTE(jaclaz @ Oct 9 2007, 10:04 AM)

I've often looked in that section and I'm wondering if I can get help with a script if I post it there. (IMG:
../forums/style_emoticons/default/unsure.gif)
QUOTE(jaclaz @ Oct 9 2007, 10:04 AM)

describing your project, it's goals and whatever other information you feel like sharing about it, like the way you are carrying it on, omitting the technical details that you find are your exclusive intellectual property.
The idea behind this is to keep fully revised copies of my code available for distribution. If I post my current code on some site and a month later I have a revised copy that a few people are starting to see, I'm most likely going to receive several messages from a lot of people I don't know because they used my outdated code and they want a revision. I'm going to go out on a limb here and say posting my code on any site other than my own is a very
bad idea. (IMG:
../forums/style_emoticons/default/huh.gif)
I just got another w3wp error pop up as I was typing this. (IMG:
../forums/style_emoticons/default/sad.gif)