Archive for February, 2011

I Just went through a problem on my friends laptop it has windows XP. He wanted to enable “Use Fast User Switching”.  But it gave a strange alert saying “client services for netware has disabled the welcome screen and fast user switching” to disable the “netware”.

Lets see what is netware ?

NetWare is a network operating system (NOS) that provides transparent remote file access and numerous other distributed network services, including printer sharing and support for various applications such as e-mail transfer and database access.

Fix:

To enable welcome screen login, you need to disable the netware client services.

Follow the steps below to disable Netware client services:

How to disable netware client services?

1. Go to Control Panel > Network Connection . This will open up the network connections available on your computer.

2. Right click on the connection and select Properties.

3. In general tab, uncheck the option for Client Services for NetWare and press OK.
As shown in the picture below.

4. Repeat step 2 and 3 for all the connections shown in network connections.

5. Restart your computer.

6. To enable welcome screen now, go to Control Panel > User Accounts > Change the way users login and select the option Use Welcome Screen. We hope following the above procedure you will be able to fix the trouble.

Released in 2001, Internet Explorer 6 has been one of the most frustrating browsers ever released. Since it doesn’t support a lot of key web standards, a high percentage of websites look awful on IE6, to a level where it makes the site almost unreadable.

Unfortunately, the browser is still used by millions of people around the world, therefore a large number of high profile people and companies support projects such as IE 6 No More and Bring Down IE6.

Today I would like to show you a range of WordPress plugins which force or encourage visitors to upgrade their browser if they are using Internet Explorer 6. It may sound like a drastic step however it’s worth doing if your design doesn’t work on IE 6 (unfortunately many top designs are). Most of these plugins work in a similar way so I recommend trying a few in your test area and choosing which one suits you.

I hope you’ve found this article useful.

Best of luck :)

To open a new window using javascript can use the following function. You just have to do is send the link and the window name.

function popup(mylink, windowname)
{
if (! window.focus)return true;
var href;
if (typeof(mylink) == ‘string’)
href=mylink;
else
href=mylink.href;
window.open(href, windowname, ‘width=800,height=800,scrollbars=yes’);
return false;
}

The non-DOM property innerHTML can’t add options to a tag select in Internet Explorer.

Example not working:

document.getElementById("my_select").innerHTML 
= "<option value='1'>not</option> 
<option value='2'>work</option>"; 

The correct way to insert options in a select is using appendChild or addOption functions. But that’s tiring if we are working with Ajax.

Use innerHTML is not the standard but it is very useful.

The function above, will help you to insert options like using innerHTML, in IE, Firefox or Opera.

Updated: now supports option-selected

Using my function:

var inner = 
"<option value='1'>Now</option> 
<option value='2'>work</option>"; 


select_innerHTML(document.getElementById("my_select"),inner);

The function. Add to your lib.

function select_innerHTML(objeto,innerHTML){

    objeto.innerHTML = ""
    var selTemp = document.createElement("micoxselect")
    var opt;
    selTemp.id="micoxselect1"
    document.body.appendChild(selTemp)
    selTemp = document.getElementById("micoxselect1")
    selTemp.style.display="none"
    if(innerHTML.toLowerCase().indexOf("<option")<0){
        innerHTML = "<option>" + innerHTML + "</option>"
    }
    innerHTML = innerHTML.toLowerCase().
replace(/<option/g,"<span").replace(/<\/option/g,"</span")
    selTemp.innerHTML = innerHTML
      
    
    for(var i=0;i<selTemp.childNodes.length;i++){
  var spantemp = selTemp.childNodes[i];
  
        if(spantemp.tagName){     
            opt = document.createElement("OPTION")
    
   if(document.all){ //IE
    objeto.add(opt)
   }else{
    objeto.appendChild(opt)
   }       
    
   //getting attributes
   for(var j=0; j<spantemp.attributes.length ; j++){
    var attrName = spantemp.attributes[j].nodeName;
    var attrVal = spantemp.attributes[j].nodeValue;
    if(attrVal){
     try{
      opt.setAttribute(attrName,attrVal);
opt.setAttributeNode(spantemp.attributes[j]
.cloneNode(true));


     }catch(e){}
    }
   }
   //getting styles
   if(spantemp.style){
    for(var y in spantemp.style){
     try{opt.style[y] = spantemp.style[y];}catch(e){}
    }
   }
   //value and text
   opt.value = spantemp.getAttribute("value")
   opt.text = spantemp.innerHTML
   //IE
   opt.selected = spantemp.getAttribute('selected');
   opt.className = spantemp.className;
  } 
 }    
 document.body.removeChild(selTemp)
 selTemp = null
}

Sometimes you get those errors that just pick at you and you can’t seem to find a solution. It happened to me this morning when testing a JavaScript library I’m writing in IE7. FireFox worked without a hitch, but IE threw an ‘expected identifier, string or number’ error pointing to the last line of the variable declaration. Of course it didn’t help that my copy of MS Script Debugger wanted to lock up my computer.

 

Here’s a very shortened example of the code I was working on.

JavaScript:

  1. var variableName =
  2. {
  3. function1:   function()
  4. {
  5. //  Do something
  6. },
  7. function2:   function()
  8. {
  9. //  Do something else
  10. },
  11. variable1:    ‘Some value’,
  12. variable2:    ‘Another value’,
  13. };

The error was reporting a problem on line 13. So after hacking my way around trying to figure out why it was giving me this error, I went out Googling. About 10 pages into the search results I found the solution.

Look at line 12. See the comma after ‘Another value’? That’s what was causing the error. I had taken out a variable under that one but forgot to remove the comma. FireFox ignored the error, but not IE.

One little misplaced character, so much wasted time. Hopefully y’all will spend less time finding the fix than I did.