<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-1636737993958994426</id><updated>2011-04-22T06:50:13.553+06:00</updated><title type='text'>redoxin - dinorex</title><subtitle type='html'></subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://dinorex-redoxin.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1636737993958994426/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://dinorex-redoxin.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>dinorex - redoxin</name><uri>http://www.blogger.com/profile/02114892916981084258</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>14</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-1636737993958994426.post-3296349328240180898</id><published>2009-02-05T19:44:00.003+06:00</published><updated>2009-02-05T19:47:17.995+06:00</updated><title type='text'>centralised blog</title><content type='html'>Hi all,&lt;br /&gt;&lt;br /&gt;I have compiled all the entries in the sharing in &lt;br /&gt;&lt;br /&gt;&lt;a href="http://dinorex.no-ip.biz/blog/"&gt;http://dinorex.no-ip.biz/blog/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;therefore, the new entries will be added down there instead. Interesting parties can visit my current blog for the latest entries :)&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1636737993958994426-3296349328240180898?l=dinorex-redoxin.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dinorex-redoxin.blogspot.com/feeds/3296349328240180898/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=1636737993958994426&amp;postID=3296349328240180898' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1636737993958994426/posts/default/3296349328240180898'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1636737993958994426/posts/default/3296349328240180898'/><link rel='alternate' type='text/html' href='http://dinorex-redoxin.blogspot.com/2009/02/centralised-blog.html' title='centralised blog'/><author><name>dinorex - redoxin</name><uri>http://www.blogger.com/profile/02114892916981084258</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1636737993958994426.post-1397852010444890030</id><published>2008-11-14T05:11:00.003+06:00</published><updated>2008-11-14T05:37:56.972+06:00</updated><title type='text'>make migrated .NET 3.5 web apps from 1.2  to be truly supported by multi-browsers</title><content type='html'>when you migrate the web applications from .NET 1.2 to version 3.5 you will discover all validator controls are not functioning at all in non-IE environments (that's the same for all web applications developed in .NET 1.2 )&lt;br /&gt;&lt;br /&gt;I have used one whole night to google, and found out the following workaround&lt;br /&gt;&lt;br /&gt;source : &lt;a href="http://forums.asp.net/t/1283702.aspx"&gt;http://forums.asp.net/t/1283702.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Put it simply, in 'Web.Config', delete the following line: -&lt;br /&gt;&lt;br /&gt;&lt;span style="color: rgb(102, 0, 0);"&gt;'&lt;'xhtmlConformance mode="Legacy"/'&gt;'&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;quote from the original source: -&lt;br /&gt;&lt;br /&gt;-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-&lt;br /&gt;&lt;p&gt;&lt;span style="font-size:78%;"&gt;set in your web.config, then client-side validation is disabled in firefox. &lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size:78%;"&gt;To see why, we have to jump down into the validation framework that ASP.Net sends to the web browser. The actual Javascript validation function looks like: &lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size:78%;"&gt;function ValidatorValidate(val) { &lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size:78%;"&gt;      val.isvalid = true;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size:78%;"&gt;      if (val.enabled != false) {&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size:78%;"&gt;            if (typeof(val.evaluationfunction) == "function") {&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size:78%;"&gt;                  val.isvalid = val.evaluationfunction(val); &lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size:78%;"&gt;            }&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size:78%;"&gt;      }&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size:78%;"&gt;      ValidatorUpdateDisplay(val);&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size:78%;"&gt;}&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size:78%;"&gt;Using Venkman, I was able to see that val.evaluationfunction wasn't a function at all, therefore the page wasn't getting validated because of this. A bit more searching found that this evaluationfunction is an expando attribute. In ASP.Net v1, this expando is an IE-only HTML expando, defined directly in the HTML markup. In ASP.Net v2, this is a Javascript expando attribute, defined on the DOM via Javascript, and therefore compatible with both IE and Firefox. &lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size:78%;"&gt;For example, the RequiredFieldValidator calls RegisterExpandoAttribute. You can call this method yourself like:&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size:78%;"&gt;&lt;br /&gt;Page.ClientScript.RegisterExpandoAttribute(TextBox1.ClientID, "value", TextBox1.Text);&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size:78%;"&gt; This produces a block of Javascript just before the closing tag like:&lt;/span&gt;&lt;/p&gt;&lt;blockquote&gt;&lt;p&gt;&lt;span style="font-size:78%;"&gt;&lt;br /&gt;&lt;b&gt;'&lt;'script type="text/javascript"'&gt;'&lt;/b&gt;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size:78%;"&gt;&lt;b&gt;'&lt;'!--&lt;/b&gt;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size:78%;"&gt;&lt;b&gt;var TextBox1 = document.all ? document.all["TextBox1"] : document.getElementById("TextBox1");&lt;/b&gt;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size:78%;"&gt;&lt;b&gt;TextBox1.value = "";&lt;/b&gt;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size:78%;"&gt;&lt;b&gt;// --'&gt;'&lt;/b&gt;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size:78%;"&gt;&lt;b&gt;'&lt;'/script'&gt;'&lt;/b&gt;&lt;/span&gt;&lt;/p&gt;&lt;/blockquote&gt;&lt;p&gt;&lt;span style="font-size:78%;"&gt;where "value" has become the new expando attribute. In the case of the RequiredFieldValidator, the expando name is" evaluationfunction" and it is added to the representing the control at runtime. &lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size:78%;"&gt;&lt;br /&gt;It turned out that this block of Javascript wasn't being sent to Firefox in my situation, and I didn't know why. Instead, the evaluationfunction expando attribute was being rendered directly on the &lt;span&gt; element in HTML.&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size:78%;"&gt;&lt;br /&gt;So after good deal of decompilation using Reflector, and debugging using Reflection Invokeing of private methods, I discovered the problem was that RegisterExpandoAttribute checks the XHTML Rendering Mode prior to generating the Javascript and if that rendering mode is set to Legacy, then the expando is rendered directly onto the &lt;span&gt; element and no Javascript code is rendered. The result of this is to prevent Firefox from performing client-side validation when Legacy XHTML mode is set.&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size:78%;"&gt;&lt;br /&gt;I have no idea why the ASP.Net team chose to do this for validation. Perhaps the Legacy XHTML setting should have been called "ASPNetv1Conformance" because that's actually what it does. The docs for Legacy mode state:&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size:78%;"&gt;&lt;br /&gt;"Reverts a number of rendering changes made for conformance to the v1.1 rendering behavior."&lt;/span&gt;&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1636737993958994426-1397852010444890030?l=dinorex-redoxin.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dinorex-redoxin.blogspot.com/feeds/1397852010444890030/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=1636737993958994426&amp;postID=1397852010444890030' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1636737993958994426/posts/default/1397852010444890030'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1636737993958994426/posts/default/1397852010444890030'/><link rel='alternate' type='text/html' href='http://dinorex-redoxin.blogspot.com/2008/11/make-migrated-net-35-web-apps-from-12.html' title='make migrated .NET 3.5 web apps from 1.2  to be truly supported by multi-browsers'/><author><name>dinorex - redoxin</name><uri>http://www.blogger.com/profile/02114892916981084258</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1636737993958994426.post-4748574667986921602</id><published>2008-10-19T20:00:00.008+06:00</published><updated>2008-11-29T13:56:47.028+06:00</updated><title type='text'>My web site is built</title><content type='html'>I have bulit a web site: -&lt;br /&gt;&lt;a href="http://dinorex.no-ip.biz/" target="_blank"&gt;http://dinorex.no-ip.biz/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;and have a demo for my recently written real estates management system.&lt;br /&gt;&lt;br /&gt;For the demo link and demo login info, please feel free to contact me directly via email (i.e. &lt;a href="mailto:dinorex@dinorex.no-ip.biz"&gt;dinorex@dinorex.no-ip.biz&lt;/a&gt;)&lt;br /&gt;&lt;br /&gt;Enjoy !&lt;br /&gt;&lt;br /&gt;&lt;img src='http://www.mocasting.com/main/album/3504/original/108819.png' height=234 width=473&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1636737993958994426-4748574667986921602?l=dinorex-redoxin.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dinorex-redoxin.blogspot.com/feeds/4748574667986921602/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=1636737993958994426&amp;postID=4748574667986921602' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1636737993958994426/posts/default/4748574667986921602'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1636737993958994426/posts/default/4748574667986921602'/><link rel='alternate' type='text/html' href='http://dinorex-redoxin.blogspot.com/2008/10/my-web-site-is-built.html' title='My web site is built'/><author><name>dinorex - redoxin</name><uri>http://www.blogger.com/profile/02114892916981084258</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1636737993958994426.post-3148839400527357374</id><published>2007-06-08T07:54:00.000+06:00</published><updated>2007-06-08T12:11:24.623+06:00</updated><title type='text'>Symantec Antivirus Corporate Edition 10</title><content type='html'>Today when I tried to uninstall this guy in a particular machine, it returns "Fatal Error During Installation" halt and no go.&lt;br /&gt;&lt;br /&gt;Further investigations reveal that the LiveUpdate (version 2.6) is not working properly and returns this error.&lt;br /&gt;&lt;br /&gt;Therefore the workaround is to uninstall the LiveUpdate first and then next to SAV CE 10.&lt;br /&gt;&lt;br /&gt;Hope this can solve some of the people worries.... XD&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1636737993958994426-3148839400527357374?l=dinorex-redoxin.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dinorex-redoxin.blogspot.com/feeds/3148839400527357374/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=1636737993958994426&amp;postID=3148839400527357374' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1636737993958994426/posts/default/3148839400527357374'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1636737993958994426/posts/default/3148839400527357374'/><link rel='alternate' type='text/html' href='http://dinorex-redoxin.blogspot.com/2007/06/symantec-antivirus-corporate-edition-10.html' title='Symantec Antivirus Corporate Edition 10'/><author><name>dinorex - redoxin</name><uri>http://www.blogger.com/profile/02114892916981084258</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1636737993958994426.post-5106452634904601561</id><published>2007-05-25T20:13:00.000+06:00</published><updated>2007-05-25T20:38:37.170+06:00</updated><title type='text'>Little Introduction of myself</title><content type='html'>I am a gadgeteer: Zaurus Linux PDA, Windows Mobile (PocketPC), Palm, Mac OS X, Windows XP, Windows 2003 ...&lt;br /&gt;&lt;br /&gt;Therefore, inside this web-log, many techniques dealing with these kinds of stuff will be seasoned....&lt;br /&gt;&lt;br /&gt;For my current job, I am a C# / ASP.NET and Coldfusion developer, so some techniques for them are also discussed....&lt;br /&gt;&lt;br /&gt;Stay tuned.....&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1636737993958994426-5106452634904601561?l=dinorex-redoxin.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dinorex-redoxin.blogspot.com/feeds/5106452634904601561/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=1636737993958994426&amp;postID=5106452634904601561' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1636737993958994426/posts/default/5106452634904601561'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1636737993958994426/posts/default/5106452634904601561'/><link rel='alternate' type='text/html' href='http://dinorex-redoxin.blogspot.com/2007/05/little-introduction-to-myself.html' title='Little Introduction of myself'/><author><name>dinorex - redoxin</name><uri>http://www.blogger.com/profile/02114892916981084258</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1636737993958994426.post-3999726691323559115</id><published>2007-05-24T19:15:00.000+06:00</published><updated>2007-05-24T19:24:31.902+06:00</updated><title type='text'>A mixture feeling....</title><content type='html'>This is a new web-log.&lt;br /&gt;However, I have another old web-log which is in Chinese / English.&lt;br /&gt;&lt;br /&gt;Therefore, the functionality of this web-log may be different from my origin first blog which is dealing the sharing of incidences, while this web-log may rest upon the technical information sharing (in my expertise - IT-related).&lt;br /&gt;&lt;br /&gt;Hope this web-log can be a good referee to my career.&lt;br /&gt;&lt;br /&gt;PS. the original web-log (&lt;a href="http://dinorex.mocasting.com"&gt;http://dinorex.mocasting.com&lt;/a&gt;) is still functional....&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1636737993958994426-3999726691323559115?l=dinorex-redoxin.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dinorex-redoxin.blogspot.com/feeds/3999726691323559115/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=1636737993958994426&amp;postID=3999726691323559115' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1636737993958994426/posts/default/3999726691323559115'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1636737993958994426/posts/default/3999726691323559115'/><link rel='alternate' type='text/html' href='http://dinorex-redoxin.blogspot.com/2007/05/mixture-feeling.html' title='A mixture feeling....'/><author><name>dinorex - redoxin</name><uri>http://www.blogger.com/profile/02114892916981084258</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1636737993958994426.post-1941214266127075941</id><published>2007-05-24T08:07:00.000+06:00</published><updated>2007-06-08T12:05:11.381+06:00</updated><title type='text'>[C#] Loading and reading the Microsoft Excel file contents using C#</title><content type='html'>If you are not lazy, you can search the following CodeProject via Google within seconds: -&lt;br /&gt;&lt;a href="http://www.codeproject.com/useritems/Excel_Application_in_C_.asp" target="_blank"&gt;http://www.codeproject.com/useritems/Excel_Application_in_C_.asp&lt;/a&gt;&lt;br /&gt;This mechanism can be used, but it has some considerations: for your deployment, you need to apply the Office component (which is using Microsoft.Office..blah blah blah..Excel, instead of the mentioned using Excel; ~!) to read the cells, that means, the deployment machine needs to purchase an extra Office licence for the deployment - most of the small businesses are reluctant to do so.. moreover, since this Office Object is version dependent, when the developer has an office version different from that in the client site, a nightmare .. XD&lt;br /&gt;Therefore, you must ask: How can I accomplish that goal then?..&lt;br /&gt;&lt;strong&gt;The answer is: SIMPLY USE StreamReader to directly read the file LINE BY LINE!..&lt;br /&gt;&lt;/strong&gt;If you don't trust me, you can try it yourself by setting similar Console App and you 'll get amazing results~!&lt;br /&gt;This workaround is valid even for Visual Studio 2003, and the behind scene mechanism of that fussy StreamReader Object is a mystery to me..&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1636737993958994426-1941214266127075941?l=dinorex-redoxin.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dinorex-redoxin.blogspot.com/feeds/1941214266127075941/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=1636737993958994426&amp;postID=1941214266127075941' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1636737993958994426/posts/default/1941214266127075941'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1636737993958994426/posts/default/1941214266127075941'/><link rel='alternate' type='text/html' href='http://dinorex-redoxin.blogspot.com/2007/05/c-loading-and-reading-microsoft-excel.html' title='[C#] Loading and reading the Microsoft Excel file contents using C#'/><author><name>dinorex - redoxin</name><uri>http://www.blogger.com/profile/02114892916981084258</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1636737993958994426.post-338692299896424302</id><published>2007-05-11T12:11:00.000+06:00</published><updated>2007-06-08T12:13:12.630+06:00</updated><title type='text'>[MSN] Solution to solve Windows Live Messenger 8.0 or above 1603 installshield problem</title><content type='html'>everyone searching the web for the installation problem 1603 in Install_Messenger.exe for Windows Live Messenger 8.0 or above should be very annoying to the various Google Results coming from this kind of 'install MSN error 1603', as all of them are useless..&lt;br /&gt;I have this problem for a while and finally I have got a 'brutal force' solution to that.. XD&lt;br /&gt;1. find a clean computer to install MSN 8.0 or above using Install_Messenger.exe&lt;br /&gt;2. In your target machine, install MSN Messenger 7.0 which is error free for installation&lt;br /&gt;3. rename the directory name in your target machine C:\Program Files\MSN Messenger as different name (somewhat C:\Program Files\MSN Messenger.bak .. XD)&lt;br /&gt;2. copy out C:\Program Files\MSN Messenger\ and put to your target machine&lt;br /&gt;3. copy C:\Windows\System32\sirenacm.dll and put to your target machine&lt;br /&gt;4. edit the MSN messenger 7.0 icon as you like in C:\Program Files\MSN Messenger\msnmsgs.exe .. XD&lt;br /&gt;Then your installation will be successful.. XD .. cheers.. XD&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1636737993958994426-338692299896424302?l=dinorex-redoxin.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dinorex-redoxin.blogspot.com/feeds/338692299896424302/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=1636737993958994426&amp;postID=338692299896424302' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1636737993958994426/posts/default/338692299896424302'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1636737993958994426/posts/default/338692299896424302'/><link rel='alternate' type='text/html' href='http://dinorex-redoxin.blogspot.com/2007/05/msn-solution-to-solve-windows-live.html' title='[MSN] Solution to solve Windows Live Messenger 8.0 or above 1603 installshield problem'/><author><name>dinorex - redoxin</name><uri>http://www.blogger.com/profile/02114892916981084258</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1636737993958994426.post-2881132688274758444</id><published>2007-04-18T12:17:00.000+06:00</published><updated>2007-06-08T12:31:48.339+06:00</updated><title type='text'>[browser technique] print a web page without print dialog box popup</title><content type='html'>&lt;div&gt;Thousands of materials in web are talking about this topic, but I found none of them works..&lt;br /&gt;So I just trying that all by myself..&lt;br /&gt;just copy and paste the following html code into your web page and test, then you can get a fancy result..&lt;br /&gt;(PS. Please don't ask me why javascript counterpart cannot hide the print dialog box, since I also don't know.. Orz)&lt;br /&gt;* I guess maybe that's M$ strategy to force you to write stuff on VBScript instead of Javascript..&lt;br /&gt;&lt;a href="http://www.mocasting.com/main/album/3504/original/73400.png"&gt;&lt;img style="FLOAT: left; MARGIN: 0px 10px 10px 0px; WIDTH: 480px; CURSOR: hand" alt="" src="http://www.mocasting.com/main/album/3504/original/73400.png" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1636737993958994426-2881132688274758444?l=dinorex-redoxin.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dinorex-redoxin.blogspot.com/feeds/2881132688274758444/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=1636737993958994426&amp;postID=2881132688274758444' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1636737993958994426/posts/default/2881132688274758444'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1636737993958994426/posts/default/2881132688274758444'/><link rel='alternate' type='text/html' href='http://dinorex-redoxin.blogspot.com/2007/04/browser-technique-print-web-page.html' title='[browser technique] print a web page without print dialog box popup'/><author><name>dinorex - redoxin</name><uri>http://www.blogger.com/profile/02114892916981084258</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1636737993958994426.post-8733402617208994499</id><published>2007-04-01T12:13:00.000+06:00</published><updated>2007-06-08T12:17:12.789+06:00</updated><title type='text'>[Zaurus] Zope in Zaurus pdaXrom, a OO database and web server</title><content type='html'>Owing to my one of the recent project requirements, I need to investigate a system called Zope (and its ZODB which is a OO database). It is easily installed in XP environment, but surprisingly, I found that the zaurus support to this is quite less….. Therefore, that triggers me to try to install this Zope inside my lovely pdaxrom….&lt;br /&gt;All in all, the experiment is in vain (how come my recent trials are all in vain?….  ), but I would like to share my experiences during the trials, and hope (maybe) any interested parties to play around this stuff on their spare time.&lt;br /&gt;1/ Since the python in pdaxrom is 2.4.1, which is quite out-dated in view of Zope current environment, we need to grab the previous versions of zope source code to compile - the one i chose is zope-2.9.1.tar.gz. During the compilation process, I stopped at a step which reports the python header is not fully satisfied, and using some others experiments certifying the header is really not fully satisfied. Therefore I gave up that direct compilation approach.&lt;br /&gt;2/ searching thru google i found that there is a version called something related to zope-2.5.1-python_2.1 to zaurus environment. that means previously zaurus should support this zope server; and surprisingly, debian also support zope server as well! and found a package called zope_2.5.1-1woody1_arm.deb for arm processor debian….&lt;br /&gt;3/ based on these observations, I tried to convert that deb to ipk. This is easy to be done by a simple script called deb2ipk.sh. When I really tried this converted ipk installation (my installation destination path is in /mnt/ide, which is not in the NAND area), I have encountered the following missing python scripts (and create a directory called /usr/lib/python2.1 linked to /usr/lib/python2.4): -&lt;br /&gt;a. glob.py, fnmatch.py, shutil.py, compileall.py - all can be easily obtained the python script code from the internet. However, for compileall.py, add a '-q' option do exactly the same as '-f' option (to fool the compiler seems the debian python compileall.py has another option -q which is for quiet mode, but i don't know how to make it, therefore I used -f as the substitute. (line 103 added for description, line 112 added for force endorsement)&lt;br /&gt;b. fcntl.py. This is obsolete (desperated in python term) in python 2.4.1 but still exists in python 2.1. on searching the web, you should be able to find the declaring as 'desperated' script, and apply it …. however, since there is a DOS version of FCNTL.py, you need to find that one for bullet-proofing. I adopt the one generated by h2py from /usr/include/sys/fcntl.h and put it in /usr/lib/python2.4 directory (together with fcntl.py).&lt;br /&gt;c. when you do that, you need to compile those .py files to .pyc, search google on related topic for python compilation to .pyc [should be something like import py_compilepy_compile.compile(”your.py”)]&lt;br /&gt;d. since the installation trials may involve the missing directory in /usr/lib/zope, you need to symbolic link the /usr/lib/zope to /mnt/ide/usr/lib/zope between installation failures so that you can pass the installation trials.&lt;br /&gt;after you have done the following remedial actions, you should be able to install the converted ipk successfully.&lt;br /&gt;4/ starting the zope server is simple : zope-z2 -w80 (port 80 for web, default is 9673, as seen in the help page when you carries -h parameter), then you should see your pdaxrom CPU time is nearly 100% ! And some warning messages shown up repeatedly in the terminal screen….. Therefore, I tried using telnet 80 port as a trial, can still cannot catch the port authentication…. therefore, I certified although the server is up and running in pdaxrom, the server processes cannot be utilized in the appropriate manner….&lt;br /&gt;Hope these sharings can ignites some zope users investigations to Zaurus, and can be able to make the zope server be used in Zaurus. I really don't mind if anyone can share me a full set of python 2.4.1 headers in pdaxrom so that I can compile the zope server directly on board, in order to alleviate such a tedious repeated trials….&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1636737993958994426-8733402617208994499?l=dinorex-redoxin.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dinorex-redoxin.blogspot.com/feeds/8733402617208994499/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=1636737993958994426&amp;postID=8733402617208994499' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1636737993958994426/posts/default/8733402617208994499'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1636737993958994426/posts/default/8733402617208994499'/><link rel='alternate' type='text/html' href='http://dinorex-redoxin.blogspot.com/2007/03/zaurus-zope-in-zaurus-pdaxrom-oo.html' title='[Zaurus] Zope in Zaurus pdaXrom, a OO database and web server'/><author><name>dinorex - redoxin</name><uri>http://www.blogger.com/profile/02114892916981084258</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1636737993958994426.post-9176333990554548348</id><published>2007-03-28T12:42:00.000+06:00</published><updated>2007-06-08T12:43:25.253+06:00</updated><title type='text'>Official Way to restart explorer</title><content type='html'>source from: &lt;a href="http://weblogs.asp.net/whaggard/archive/2003/03/12/3729.aspx"&gt;http://weblogs.asp.net/whaggard/archive/2003/03/12/3729.aspx&lt;/a&gt; &lt;br /&gt;Official way to restart explorer&lt;br /&gt;&lt;br /&gt;I found yet another Windows tip I did not know in Richard Birkby's &lt;a href="http://www.codeproject.com/csharp/ColumnHandler.asp"&gt;Explorer column handler shell extension in C#&lt;/a&gt; article at &lt;a href="http://www.codeproject.com/"&gt;The Code Project&lt;/a&gt;:&lt;br /&gt;&lt;br /&gt;&lt;em&gt;Finally, if you want to restart an instance of Windows Explorer, you should use the official way to shut down Explorer, rather than killing it from Task Manager! To shut down officially, hit Start-&gt;Shutdown (or Turn Off Computer on Windows XP), then while holding the control shift and alt keys, click cancel on the shutdown dialog. To start a new instance of Windows Explorer, bring up Task Manager by holding the control and shift keys, then hit escape. In Task Manager, choose File-&gt;New Task and enter “Explorer.exe”. This will have restarted Windows Explorer properly.&lt;/em&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1636737993958994426-9176333990554548348?l=dinorex-redoxin.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dinorex-redoxin.blogspot.com/feeds/9176333990554548348/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=1636737993958994426&amp;postID=9176333990554548348' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1636737993958994426/posts/default/9176333990554548348'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1636737993958994426/posts/default/9176333990554548348'/><link rel='alternate' type='text/html' href='http://dinorex-redoxin.blogspot.com/2007/03/official-way-to-restart-explorer.html' title='Official Way to restart explorer'/><author><name>dinorex - redoxin</name><uri>http://www.blogger.com/profile/02114892916981084258</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1636737993958994426.post-1526333350441599758</id><published>2006-11-25T12:43:00.000+06:00</published><updated>2007-06-08T13:10:10.184+06:00</updated><title type='text'>[Zaurus] pdaXrom font anti-aliasing</title><content type='html'>&lt;div&gt;Anyone who are using pdaXrom beta 4 or beta r121 or above maybe experiencing the 'checker character behaviour' in fluxbox, E17, fvwm windows manager....&lt;/div&gt;&lt;br /&gt;&lt;div&gt;&lt;/div&gt;&lt;br /&gt;&lt;div&gt;mjotad in oesf.org has mentioned some workarounds to that in the oesf.org forum, which is located here: -&lt;/div&gt;&lt;br /&gt;&lt;div&gt;&lt;/div&gt;&lt;br /&gt;&lt;div&gt;&lt;a href="http://www.oesf.org/forums/index.php?showtopic=21829"&gt;http://www.oesf.org/forums/index.php?showtopic=21829&lt;/a&gt;&lt;/div&gt;&lt;br /&gt;&lt;div&gt;&lt;/div&gt;&lt;br /&gt;&lt;div&gt;and the following screenshot is coming from my Zaurus (under pdaXrom beta 4 environment)&lt;/div&gt;&lt;br /&gt;&lt;div&gt;&lt;/div&gt;&lt;a href="http://img86.imageshack.us/img86/4986/antialiasyz6.jpg"&gt;&lt;img style="FLOAT: left; MARGIN: 0px 10px 10px 0px; WIDTH: 480px; CURSOR: hand" alt="" src="http://img86.imageshack.us/img86/4986/antialiasyz6.jpg" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;div&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1636737993958994426-1526333350441599758?l=dinorex-redoxin.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dinorex-redoxin.blogspot.com/feeds/1526333350441599758/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=1636737993958994426&amp;postID=1526333350441599758' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1636737993958994426/posts/default/1526333350441599758'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1636737993958994426/posts/default/1526333350441599758'/><link rel='alternate' type='text/html' href='http://dinorex-redoxin.blogspot.com/2006/11/zaurus-pdaxrom-font-anti-aliasing.html' title='[Zaurus] pdaXrom font anti-aliasing'/><author><name>dinorex - redoxin</name><uri>http://www.blogger.com/profile/02114892916981084258</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1636737993958994426.post-8370865472809468148</id><published>2006-07-02T21:17:00.000+06:00</published><updated>2007-05-25T21:19:44.654+06:00</updated><title type='text'>[Zaurus] pdaXrom 1.1.0 beta 4 - Auto Swap Partition Attachment</title><content type='html'>initially i have posted in hk http://www.pumb.org forum for this stuff, but i think that's worthy of mentioning in oesf.org, so i double post down there..&lt;br /&gt;you can re-format to the SD / CF in c1k (/dev/mmcblk0  /dev/hda1) or MD in c3k or above (/dev/hda1 - 3), however, for the sake of housekeeping the original SHARP ROM / cacko configuration, you'd better keep the partition table of MD in c3k or above in hda1 - 2 respectively..&lt;a id="more-65349"&gt;&lt;/a&gt;you can make use of fdisk /dev/mmcblk0 or fdisk /dev/hda to give the following partition table: -&lt;br /&gt;&lt;br /&gt;in c1k,&lt;br /&gt;/dev/mmcblk0p1 –&gt; Linux (swap partition) –&gt; suggest to use 128M as the basis../dev/mmcblk0p2 –&gt; data (ext3 format)&lt;br /&gt;in c3k or above,&lt;br /&gt;/dev/hda1 –&gt; leave it as is/dev/hda2 –&gt; leave it as is/dev/hda3 –&gt; Linux (swap partition) –&gt; suggest to use 128M as the basis../dev/hda4 –&gt; data (ext3 format)&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;format this swap partiton:-&lt;br /&gt;in c1k,&lt;br /&gt;mkswap /dev/mmcblk0p1&lt;br /&gt;in c3k or above,&lt;br /&gt;mkswap /dev/hda3&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;format the data partiton:-&lt;br /&gt;in c1k,echo y  mke2fs /dev/mmcblk0p2&lt;br /&gt;in c3k or above,echo y  mke2fs /dev/hda4&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;add the following line in /etc/fstab: -&lt;br /&gt;in c1k,/dev/mmcblk0p1 swap swap defaults 0 0&lt;br /&gt;in c3k or above,/dev/hda3 swap swap defaults 0 0&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;just use the fdisk /dev/mmcblk0 (for c1k) and fdisk /dev/hda (for c3k or above), modify the /dev/mmcblk0p1 or /dev/hda3 partition's system id (command t) as type '82' (Linux swap / Solaris)..&lt;br /&gt;the reason of changing as that in rc.sysinit, is so simple: you can take a look on the output to fdisk -l..&lt;br /&gt;since the partition listing in fdisk -l has no recognition to “Linux swap” type, the /etc/rc.d/rc.sysinit is capture those descriptors to do so, but, rc.rofilesys stage, which is absent in the booting process is not recommended to add back here..&lt;br /&gt;for closing the swap partition , you can make use of swapoff -a to perform mandatory closure.&lt;br /&gt;after this patch, during your pdaxrom booting, your dmesg will see this statement: “Found swap in /dev/{device name}, turn it on.. [OK] ” — that means you are successfully made..&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1636737993958994426-8370865472809468148?l=dinorex-redoxin.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dinorex-redoxin.blogspot.com/feeds/8370865472809468148/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=1636737993958994426&amp;postID=8370865472809468148' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1636737993958994426/posts/default/8370865472809468148'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1636737993958994426/posts/default/8370865472809468148'/><link rel='alternate' type='text/html' href='http://dinorex-redoxin.blogspot.com/2006/07/zaurus-pdaxrom-110-beta-4-auto-swap.html' title='[Zaurus] pdaXrom 1.1.0 beta 4 - Auto Swap Partition Attachment'/><author><name>dinorex - redoxin</name><uri>http://www.blogger.com/profile/02114892916981084258</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1636737993958994426.post-3313477049294560342</id><published>2005-05-02T20:53:00.000+06:00</published><updated>2007-05-25T21:16:44.373+06:00</updated><title type='text'>[Zaurus] Native Qt/E On-board Development Package</title><content type='html'>&lt;a title="Permanent Link: [Zaurus] Native Qt/E On-board Development Package" href="http://dinorex.mocasting.com/p/53648" rel="bookmark"&gt;[Zaurus] Native Qt/E On-board Development Package&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I bought this tiny SL-C3100 in mid-February, and keen on studying her functionality during these couple of months. . .&lt;br /&gt;So far, I haven’t changed the original SHARP ROM, any partition in /dev/hda3, and any other ROM-related customizations (even though those awesome cacko, pdaXrom images are v. attractive)&lt;br /&gt;By studying meanie’s customization page and pdf, I start to understand the preliminary procedures and related stuff down here, and was wondering by the AWESOME zgcc.cramfs and java.cramfs images which are widely adopted for my compilation of gcc and java packages...&lt;br /&gt;In view of this, there is a limitation for the NATIVE compilation (i.e. non-cross-compilation) in that tiny dog owing to the swap space limitation problem. Therefore, I have started seeking ‘work-around’ on that for a long time.&lt;br /&gt;recently, I am attracted by a forum poster in Hong Kong (my home city) saying that he can deploy a complete GNU man page package (via man.ipk package, and make use of less.ipk, and groff.ipk packages as the media for viewing the man pages directly in console) inside his dog - but that deployment was UNDER pdaXrom. I was very astonished and frustrated when I saw that the attached .ipk (groff-1.19.2_arm.ipk, less-392_arm.ipk) was compiled using not in gcc version 2.95.2 - instead it is in later release which cause the gcc lib cannot be loaded upon arm execution. In view of this environment, some thoughts are coming out of my mind: is SHARP ROM really very not so USEFUL and needs to be abandoned?&lt;br /&gt;Therefore, my gcc compilation journey starts. . .&lt;a id="more-53648"&gt;&lt;/a&gt;I took the groff-1.19.2.tar.gz, and less-392.tar.gz source code directly from GNU ftp site, and resides them under a /hdd3 loop image for compilation - by making use of the awesome meanie’s prepared zgcc.cramfs package. But this was a failure.&lt;br /&gt;Therefore, I trusted there is a swapfile limitation issue, and I enlarge the swapfile to be 512MB in size, and put it peacefully in /hdd3 as well. Although I have done that, the compilation was in vain…. groff cannot be compiled though.&lt;br /&gt;My searching was not stopped and further investigation is coming out. In a specific web page there is an introduction of &lt;a href="http://www.iaccarino.de/silvio/zaurusstuff.htm" target="_new"&gt;Native onboard QTE development. This is an enhanced version of the zgcc cramfs image&lt;/a&gt; in which the file is called dev-image_1.5.img...&lt;br /&gt;this gcc compilation environment is exactly the same as meanie’s zgcc.cramfs, but with the added full documentation on gcc env’t and Qt/E documentation down there, which makes the cramfs image doubles to meanie’s one. Another major difference is that it is not stationed permanently in the loop file system. Instead, it makes use of the /mnt/card/devel directory - which means the development env’t is made on demand.&lt;br /&gt;Therefore, after my studies on that env’t, I have drafted out a bash-shell script which can create the /mnt/card/devel directory, mount the loop image to that, and notify the developer NOT TO REMOVE the SD card during the development env’t is launched - otherwise the Zaurus may need to be rebooted; moreover, that shell script also does the stopping of the development env’t, and prompt the developer the SD card can be removed after that. That shell script, I named it as dev-img_ctl [start stop] ...&lt;br /&gt;After that development package is mounted, this &lt;a href="http://zaurus.xavierxeon.de/zaurus.php?group=devel&amp;topic=gcc" target="_new"&gt;link: GNU C Compiler&lt;/a&gt; for the Zaurus is needed to refer (as the lib version #s are different from that link) on creating manual linkages to the essential compilation libraries and includes for the environment (which can be a permanently symbolic link if you don’t plan to remove so). Concerning the Qt/E documentation, which are html pages, you can directly symbolic link to the apache / lighttpd directory for the local reference, and the man pages can be man-ed out when the ‘man-pages’ work in Qtopia is done...&lt;br /&gt;the screen shot of that env’t linkage is shown in the following picture (this is my Zaurus) :-&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://img352.imageshack.us/img352/6285/scrn0022jv.jpg"&gt;&lt;img style="FLOAT: left; MARGIN: 0px 10px 10px 0px; WIDTH: 480px; CURSOR: hand" alt="" src="http://img352.imageshack.us/img352/6285/scrn0022jv.jpg" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Here comes with the dev-img_ctl bash-shell scripts written by me: -&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;when this development env’t is set up, I am still v. frustrated by seeing that the groff ’s and less’ compilation are still backing off; So, I try to examine the underlying error message during the compilation. . .&lt;br /&gt;The error mesgs are saying ‘I/O error’ when a compilation is calling off - without any previous errors shown before that. Therefore, I suspect this error is coming from the ‘temporal directory disk space’ problem in the /tmp directory.&lt;br /&gt;passing ‘ls’ in the console, we can see that the /tmp is symbolicly linked to the /dev/shm/tmp directory.&lt;br /&gt;passing ‘df’ in the console, we can see that only 1M memory is allocated to /dev/shm as well. This maybe the core reason why the gcc cannot compile harsh compilations in SHARP original ROM Qtopia environment.&lt;br /&gt;if you study the /root/etc/rc.d/rc.rofilesys in detail, you can understand that the /dev/shm/tmp is in fact temporarily created inside this script, and I thought out one method on EXPANDING the /dev/shm/tmp directory size is to make use of loop file image method: we can dd a “whatever-sized” called tmp.ext2 in /hdd3 directory by this command (thanks meanie again by teaching me how to do so - this example shows creating a 512M tmp.ext2): -&lt;br /&gt;&lt;br /&gt;# su&lt;br /&gt;# dd if=/dev/zero of=/hdd3/tmp.ext2 bs=1MB count=512&lt;br /&gt;# echo y/sbin/mke2fs /hdd3/tmp.ext2&lt;br /&gt;&lt;br /&gt;inside the rc.rofilesys, this statement can be easily spotted out:-&lt;br /&gt;&lt;br /&gt;mkdir /dev/shm/tmp&lt;br /&gt;&lt;br /&gt;you can add the following statement after the HDD is initialized (don’t add that statement too far away since the /dev/shm/tmp may fill some temp files after the checking. . . )&lt;br /&gt;&lt;br /&gt;mount -o loop -t ext2 /hdd3/tmp.ext2 /dev/shm/tmp&lt;br /&gt;&lt;br /&gt;Please note that THERE ARE TOTALLY 3 INCIDENCES OCCURRED INSIDE this rc.rofilesys file, you need to fill the 3 incidencies out in order to achieve a permanent expansions on the /tmp directory. . .&lt;br /&gt;N.B. since rc.rofilesys file is mounted in a intrinsic read-only volume, you need to remount that volume by meanie’s taught command first: -&lt;br /&gt;&lt;br /&gt;# mount -o rw,remount /&lt;br /&gt;&lt;br /&gt;and after modifying the rc.rofilesys file, the following command is issued again. . .&lt;br /&gt;&lt;br /&gt;# mount -o ro,remount /&lt;br /&gt;&lt;br /&gt;and the final ‘df’ of my /tmp folder is shown in the following picture (i created a 128M loop image tmp.ext2 only): -&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;After this configuration is deployed, this tiny little Zaurus dog can now compile the complicated groff-1.19.2.tar.gz package, less-3.93.tar.gz, tar-1.15.90.tar.gz packages (even though the groff-1.19.2.tar.gz use her 1 hour for complete compilation [this is inevitable since it needs to pass so many loop devices to get it thru], the final binary is found to be successfully run and becoming my man page troff engine. . .)&lt;br /&gt;Concerning the man page package, the final output is shown in the following diagram: -&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://img299.imageshack.us/img299/4621/scrn0016ei.jpg"&gt;&lt;img style="FLOAT: left; MARGIN: 0px 10px 10px 0px; WIDTH: 480px; CURSOR: hand" alt="" src="http://img299.imageshack.us/img299/4621/scrn0016ei.jpg" border="0" /&gt;&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1636737993958994426-3313477049294560342?l=dinorex-redoxin.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dinorex-redoxin.blogspot.com/feeds/3313477049294560342/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=1636737993958994426&amp;postID=3313477049294560342' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1636737993958994426/posts/default/3313477049294560342'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1636737993958994426/posts/default/3313477049294560342'/><link rel='alternate' type='text/html' href='http://dinorex-redoxin.blogspot.com/2007/05/zaurus-native-qte-on-board-development.html' title='[Zaurus] Native Qt/E On-board Development Package'/><author><name>dinorex - redoxin</name><uri>http://www.blogger.com/profile/02114892916981084258</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry></feed>
