Clue me in guys, how does developing this operating system component work in reality? Do you all for example develop in BeOS, and run the app_server instead of the original Be V5 app? Do you have to serial/remote debug? My only experience of development in BeOS is drivers using BeIDE. Most debugging has been reliant on serial debug output. Give me an example of one of your simpler tasks, how and what you used to write the code (be ide, Styled edit, Linux, other?) What you did you do for test and verification? On another note, is the A/S server usable? Does it run, just not functionally complete? What about the other kits, I can't get a good grip on the status and run-ability of the current teams. What can I currently play with, and see for real? I heard something about builds of app_server a while a go. Are there any recent binary builds? Darkwyrm's site (may he rest his fingers in peace) doesn't appear to be up according to www.openbeos.org On a sadder note my 3com net interface embedded in my Nforce2 chipset has died, so I'm going to have to try getting the 2nd integrated lan interface (Nvidia) adapter working in beos. That's my first task before BeOS becomes usable! Not to mention pulling out one of the 512MB dimms. He he. Euan