Changed multi-line C comments into another style.

The left side doesn't look unbalanced.

libsrc/em/em-kernel.s

@@ -94,8 +94,8 @@ copy:   lda     (ptr1),y
 ;----------------------------------------------------------------------------
 ; unsigned char em_uninstall (void);
 ; /* Uninstall the currently loaded driver and return an error code.
-;  * Note: This call does not free allocated memory.
-;  */
+; ** Note: This call does not free allocated memory.
+; */
 
 _em_uninstall:
         jsr     emd_uninstall           ; Call driver routine

libsrc/em/em_commit.s

@@ -3,11 +3,11 @@
 ;
 ; void em_commit (void);
 ; /* Commit changes in the memory window to extended storage. If the contents
-;  * of the memory window have been changed, these changes may be lost if
-;  * em_map, em_copyfrom or em_copyto are called without calling em_commit
-;  * first. Note: Not calling em_commit does not mean that the changes are
-;  * discarded, it does just mean that some drivers will discard the changes.
-;  */
+; ** of the memory window have been changed, these changes may be lost if
+; ** em_map, em_copyfrom or em_copyto are called without calling em_commit
+; ** first. Note: Not calling em_commit does not mean that the changes are
+; ** discarded, it does just mean that some drivers will discard the changes.
+; */
 
         .include        "em-kernel.inc"
 

libsrc/em/em_map.s

@@ -3,8 +3,8 @@
 ;
 ; void* __fastcall__ em_map (unsigned page);
 ; /* Unmap the current page from memory and map a new one. The function returns
-;  * a pointer to the location of the page in memory.
-;  */
+; ** a pointer to the location of the page in memory.
+; */
 
 
         .include        "em-kernel.inc"

libsrc/em/em_use.s

@@ -3,12 +3,12 @@
 ;
 ; void* __fastcall__ em_use (unsigned page);
 ; /* Tell the driver that the memory window is associated with a given page.
-;  * This call is very similar to em_map. The difference is that the driver
-;  * does not necessarily transfer the current contents of the extended
-;  * memory into the returned window. If you're going to just write to the
-;  * window and the current contents of the window are invalid or no longer
-;  * use, this call may perform better than em_map.
-;  */
+; ** This call is very similar to em_map. The difference is that the driver
+; ** does not necessarily transfer the current contents of the extended
+; ** memory into the returned window. If you're going to just write to the
+; ** window and the current contents of the window are invalid or no longer
+; ** use, this call may perform better than em_map.
+; */
 
 
         .include        "em-kernel.inc"