Changes between Version 2 and Version 3 of FAQ

Timestamp:

02/13/08 17:02:37 (5 years ago)

Author:

hvolos

Comment:

--

FAQ

@@ -12 +12 @@
 On the stable branch or 3.1.* tarballs this should work:
 
+
+{{{
   ./configure --disable-all-components --enable-usrp
   make
+}}}
+
 
 
 On the trunk
 
+
+{{{
   ./configure --disable-all-components \
               --enable-usrp --enable-omnithread --enable-mblock --enable-pmt
   make
+}}}
+
 
 
@@ -34 +42 @@
 
 ''Answer:'' Right click the device in the device list 
+
+=== "Failed to resolve NameService" error when running nodeBooter ===
+ ''Answer:'' Make sure that omniNames is running
+
+==== The error persits even after starting omniNames ====
+
+   It appears the naming service is not starting.  Could you send the contents of
+   your omniNames.sh file?  As an alternative to using omniNames.sh, you can type
+   the following from the command line:
+
+
+{{{
+   killall omniNames 
+   omniNames -start -logdir /home/<your user directory>/logs &
+}}}
+
+
+   If you get an error message referring to log files, try typing
+
+    
+{{{
+rm /home/<your user directory>/logs/omninames*
+}}}
+  before running omniNames
+
+
+  ''Follow-up:''
+
+    Using the commands on the command line worked and I was able to get the
+    device registered.
+
+
+{{{
+    killall omniNames
+    omniNames -start -logdir /home/Oss/logs &
+}}}
+
+
+    Earlier my omniNames.sh was 
+
+
+{{{
+    killall omniNames [omniEvents]
+    rm /home/Oss/logs/omninames*
+    omniNames -start -logdir /home/Oss/logs &
+}}}
+
+
+    When I deleted the [omniEvents], the  script also worked fine.
+
+
+== OSSIE ==
+=== Is there a Windows implementation? ===
+
+
+''Answer:''
+
+  There is not a Windows implementation, and there are currently no plans to make one in the future.
+
+  The best solution for Windows users who don't have a machine they can install Linux on is to download VMware Player and use the OSSIE VMs, available on the downloads section of our website.
+