Hello Bluetoothfrustrated, Could you clarify a few items related to your question: [1] The "new" gumstix hardware (and some software) apparently supports audio over bluetooth. See http://bluetooth-alsa.sourceforge.net/embed.html http://docwiki.gumstix.org/Frequently_asked_questions/Bluetooth (scroll to the bottom for the audio specific FAQ) for more information. If you were aware of this, what makes this solution inadequate for your problem? [2] What are your size / power limits? For example, would a PC/104 form factor be acceptable or "too large" or "too much power"? [3] How much performance do you need? For example, you mention the Gumstix (but not clock rate - 200 or 400 Mhz); is that the "minimum" level of performance or would something less capable be OK? [this obviously has to be balanced against the answer to 2] [4] I assume you also need a complete tool chain to build / download software. Are there other "required" capabilities (such as serial I/O or Ethernet) that the answer should address? --Maniac

I've been setting up Cruise Control .NET with NUnit to perform Continuous Integration/Unit Testing and kept hitting the wall after compiling my unit tests.

After looking at the debug logs I noticed that for some reason NUnit was looking for my test files in in C:\Documents and Settings\%Username%\Local Files\...Temp...\, instead of the working directory I had specified. Oddly enough, even though I had set a working directory, the NUnit framework still requires that the compiler creates Shadow Copies of the test files in this temp directory (unless you pass the /noshadow flag). NUnit's response is that Visual Studio tends to lock *.dll files even after runtime. Visual Studio's response, "We've logged this bug for our next release."

In any case, "adding a /noshadow switch doesn't sound so hard does it?" I said to myself as everyone in the office looked at me. Well it turns out the Cruise Control .NET 1.4 does not support additional arguments when setting up NUnit tasks.

Stuck in a hopeless situation I began tinkering with the Cruise Control source code. I modified the NUnitArgument.cs file to include the /noshadow parameter and what the heck, it works like a charm!

If you're interested, here are the steps:

1. Download the source from: http://ccnetlive.thoughtworks.com/CCNet-builds/1.4/1.4.0.3507/CruiseControl.NET-1.4.0.3507.source.zip

2. Download the modified NUnit args file from: http://www.kitsirota.com/media/code/cc.net/

3. Unzip CruiseControl.NET-1.4.0.3507.source.zip

4. Copy NUnitArguments.cs to {cc.net_source_root}\project\core\tasks\NUnitArguments.cs

5. Run {cc.net_source_root}\b.bat

6. Navigate to {cc.net_source_root}\projects\server\ and run ccnet.exe

No additional packages, no overhead, Enjoy!

If anyone is attempting to implement continuous integration into their project and is running into any sorf of issues or has any questions, feel free to shoot me an email. My contact info is on the Homepage

While it has been years since I've read about cell phone linkage to brain tumors, I was recently pointed towards an article that has compelled me to do some further research. The article, posted on ServenthGeneration's blog (http://www.seventhgeneration.com/learn/blog/new-cell-phone-study-says-hang-use-land-line) discusses the long term health concerns which may begin to propagate themselves within the next five years. Some take-away items from this are as follows:

• Use speaker phone or Bluetooth headset when possible (Note Bluetooth headsets should be worn when driving, typing, or doing something that requires your hands and NOT as an accessory =D )
• When choosing a phone, consider skipping the Treo line of phones, as they appear to be top ranking SAR emitting phones (all but one emit more than 1.26 W/kg)

It's interesting to note that while the site states, "Bluetooth cordless technology is even worse," almost every source I've looked at said that this was a much better alternative holding a cell phone to one’s head. The reason for this is the transmitted inside a Bluetooth headset is much weaker than a cell phone which has to broadcast a signal to the nearest tower. On the other hand, I assume wearing the Bluetooth headset whever ever you go even if you forgot your cell phone in the car (You know who you are) probably isn't the best thing for your brain either.

To find out how much radiation your phone emits, you can visit CNET at the following link: http://reviews.cnet.com/4520-6602_7-5020355-1.html

***Update***
And finally the truth begins to boil to the surface... http://money.cnn.com/2008/07/23/technology/cell_phone_cancer.ap/index.htm

The following is a 3.5 hour documentary which clearly defines the troubles with our economic system.
Please enjoy the video and if you like this video, please visit the author's website at http://www.themoneymasters.com/

Download the full DivX copy by right clicking here

Before I begin, I have to stress just how important I think this concept is. I believe that this but a glimpse into the next ten or fifteen years. We are living very interesting times, and this concept *phone* is the staple of innovation.

I guess I should start with a brief history.
The Morph concept designed by Nokia Research Center (http://research.nokia.com/) and the University of Cambridge, UK. It all began with an invitation to New York's Museum of Modern Art at their "Elastic Mind" exhibition (http://www.moma.org/elasticmind). This is where it all began, with an ambitious entry into a Museum exhibit.

Its important to recognize the technological boundaries that we see in our generation of electronics only to see the opportunities bestowed upon us in form of nanotechnology. With the advancements in nanotech within the coming years, we will see a surge of practical applications which will effect each and everyone of us on a daily basis (I am referring to uses far beyond silicone chips, memory modules, cpus, etc).

We, as a people, are clearly moving in the direction of instant information and total awareness. News travels between continents in milliseconds, not months as it did a couple of hundred years ago. As such imagine the possibilities of a communications device such as the Morph and the advancements it brings to the UMPC (Ultra Mobile PC) platforms.

Implementations

1. Morph concept is said to have a sense of smell. With a mesh of these devices scattered all over the world, or even a city, governments can monitor and alert citizens of a possible biological warfare attack. Lets pretend we're in a city, in the US, where ten percent of the population owns a Morph. Lets say that one such Morph detects the presence of a chemical in the air that resembles a nerve toxin. The device fires off a message to the department of homeland security. All of the sudden, a dozen more Morphs fire off the same message of a possible nerve toxin detected in location X Latitude Y Longitude. Now we have probable cause to evacuate civilians from a possible threat.

   Of course this begs the question of privacy. What if the government begins to also monitor drug activity. Now any Morph user is accountable for any drugs that may be within the phone's vicinity. There are of course quirks with any technology, especially when it involves privacy, but I do believe that this device is the staple of the innovation we will see in the coming years.

2. Just another thought. What if a mesh of these devices where to use GPS tracking to calculate speed, location, and g-forces such as deceleration and acceleration. If this is the case, we can use the Morph to control traffic patterns by alerting drivers to slow down if a car in front is slowing, or to speed up when necessary. A system such as this can also monitor heart rates to determine if a driver is falling asleep. In such an even it can attempt to wake the sleeping driver, and alert any other drivers in the vicinity.

Nokia's Press Release:

http://www.nokia.com/A4136001?newsid=1194251
http://www.nokia.com/A4852062

Cheers!
~Kit

• Establish a public blog for all my ADD ideas and rants.
• Establish a WIKI/Project page where I can document all of the projects I am currently working on.
• Tie this site in with other open source development projects (examples of personal implementations, and branching).
• Create a knowledge dump/tutorial section

Thank you,
~Kit Sirota