Monday, April 20, 2009

What to do when installing Additional Drivers on the print server doesn't work

For some printer (actually print device) models, the manufacturer does not package the drivers so that they can be installed as Additional Drivers on a print server. This is the case for many of the less expensive bubble jet, inkjet and multi-function (e.g. scanner/fax/printer) models. The manufacturers deem these to be "personal" printers for use only on the computer to which they are physically connected (parallel, USB or serial port). The manufacturer often says that printing over the network is "not supported" for these models.

If you attempt to install the drivers for these models as Additional Drivers (see for example Install Additional Driver on older OS), you will get some kind of an error or a request for the driver that can not be satisfied no matter what you do.

Unfortunately, there are some models that can not be used over the network because the print device and printer driver have to be in bi-directional communication throughout the printing process. The manufacturer's documentation does not always make this requirement apparent, although there may be FAQs or other documents on the manufacturer's web site that state this.

Except for those models discussed in the previous paragraph, you can bypass this problem by adding the printer as a local printer on the client computer and associating the printer with a network printer port (i.e. re-direct it to the printer share on the print server). No harm will be done by trying this approach if it doesn't work, so it's usually worth a try.

Here's tips trick computer how to install a printer locally and re-direct it to a network printer port. These instructions are written for Windows XP This technique does work with Windows Vista, 2008, 2003, 2000, and Windows 98 (they may work with Windows 95 and ME also), but the dialogs are a bit different, so you may have to read between the lines.

Logon at the client computer with a user account that has administrative rights and permissionsclient computer. on the

Click Start, Printers and Faxes

Right click in an empty space in the right pane and select Add Printer

Click Next

Select the Local Printer… radio button, remove the check mark from Automatically detect and install my Plug and Play printer; click Next

Select the Create a new port: radio button; from the Type of port: drop down list, select Local Port; click Next

In the Enter a port name: text box, key exactly the UNC name of the network printer (e.g. \\printservername\printersharename); click OK

Selecting the appropriate entries from the Manufacturer and Printers columns or click the Have Disk button as appropriate

Follow through the rest of the Add Printer wizard; when you get to the Name Your Printer panel, either accept the default, or key the name you want this printer to be known by on this computer.

Sunday, April 19, 2009

How a URL Works

http:// --- This indicates it's a web page address. It is quite common to leave this part off. In modern browsers, the http:// will automatically get prefixed to addresses you type in.

www.domainname.com --- This part is called the 'host name'. It indicates what computer the page resides on. A .com address is usually an American site (though not always), while a .nz address is a New Zealand site.

/path/to/ --- This part specifies the 'path' to the actual page you want to look at. Each '/' separates the name of the directories (or folders).

file.html--- This is the actual name of the file, or page you are looking at. Most pages have a suffix of .html or .htm. Other suffices could be .cgi, .asp, .gif, .jpg. Sometimes you'll find that there is no file name at all, and the url ends with a '/'. This means that the default page will be fetched (commonly index.html or home.html).

Sometimes there will what looks like a whole lot of garbage tacked on to the end of the address - something like this: query?pg=q&kl=XX&q=english+on+line

Believe it or not, this is actually useful information. It contains extra information that you might have supplied, for instance by using a search tool.

Checking your address

In the process of copying addresses from one place to another it is very easy to make mistakes.

  • Firstly, check that as far as you can see, the address that you typed matches exactly with the one you are copying from.
  • Check and experiment with punctuation:

The tilde character ~ can often be mistaken for a dash -. You can usually find the tilde key to the top-left of the '1' key.  Underscores _ also often get mistaken for dashes, or omitted completely. If there appears to be a space in the address, try using an underscore instead. You can get an underscore by typing shift-dash. Don't mix up t (letter of the alphabet) and + (addition symbol).  Look at the last part of the address. If you have a '.htm', try adding an 'l' to the end to make it '.html'. If you have a 'html', try removing the 'l' to make it '.htm'.

Copy this address and paste it into the location bar of your browser. See if you can discover the correct address.http://www.pantheon.org/mythica/articles/+/troll/html

Try this one too: http://www~dept.usm.edu~engdept/cinderella/cinderella.html

(Try changing some ~ to -, + to t as well as using your knowledge about what Web addresses should look like)

Working Backwards

If none of this works, the next step is to work backwards on the URL until you find a sensible page. For instance, here is an address that's meant to be a page called "Storms Viewed from Space": http://athena.wednet.edu/curric/whether/storm.html

The address just gives you a "Not Found" page, and no matter how hard you try you can't figure out what's wrong (it's a little bit obvious, but just pretend ok!). The trick is to start stripping things off the URL, starting from the end. First take off the storm.html bit, which gives you: http://athena.wednet.edu/curric/whether/

Nope, that still doesn't seem to work. Try stripping it to the next '/' character: http://athena.wednet.edu/curric/

Ok, now we're getting somewhere! This is a valid page called "Curriculum", which has links to "Space", "Weather", "Earth", "Oceans" and "More". The next step is to navigate through the site until you find the page that you are looking for. The "Weather" link sounds like a good start. On the weather page there is a link to "Storms from Space" which leads us to our intended destination.

This method can work for both the case where the URL was a little wrong to start with, and the case where the page you wanted has been renamed, or the site has been shuffled around so it's not in the same place anymore.

Here are some links that used to work, however they don't anymore. See if you can find the correct address by following the steps above.

That didn't work - what next?

Sometimes this method will not work very well. You might have stripped your address right down to the host name, and find yourself somewhere that is nothing to do with the topic of the page you are looking for. This is usually the home page of an ISP or a university. If you find yourself all the way back to an ISP or university page home page, your chances of finding the page you want become quite slim. Here is something you can try:

Navigate through the ISP site to try to find a list of links to clients' or students' web pages. If you find this, look through these by running your mouse over each link (don't press the button, just run the cursor over the link), looking at the address as it appears in the status bar at the bottom of your browser. If you find one that looks the same or very similar to your original address, try clicking it. If it works, you may have hit the jackpot!

If you end up at a university page, you can get some hints of where to find the page from the address. For instance, in the address:

http://www.emory.edu/ENGLISH/classes/Shakespeare_Illustrated/R&JPaintings.html

The "ENGLISH/classes" bit indicates that the page is located within the English Department's part of the site. From the university home page (http://www.emory.edu) you know to look for the English Department to start your search for the page.

If you can't find the page, you must face the unfortunate reality that the page you want has been removed from that server. This could mean that:

  1. The person who wrote the page has lost all interest in it and has pulled the plug.
  2. The site has been shifted to a different ISP with a different address.

If all else fails, your best bet might be to email the webmaster of the host site to ask if they know what has become of the page you are looking for.

Server Errors

No Response

Your web browser seems to be trying very hard to find the page, then gives up and comes back with an error that says something like "There was no response. The server could be down or is not responding". This error happens when your web browser decides that it can't fetch the page because it didn't get any response from the server. The cause of this could be:

  • The server is 'down' - the computer that holds the web page is simply not working, or not plugged into the network.
  • The network is too slow - there is too much congestion on the network to get your request for the page through.
  • Your own network connection is not working for some reason.

In the event of getting one of these errors, your best (and only) strategy is to just try again later. The problem could be fixed quite quickly (in a few minutes), however if the problem is with the remote server, it might take hours or even days for the server administrators to do something about it. Occasionally servers might be permanently taken out of commission. Sometimes the pages will be transferred to another server (try using a search engine to relocate them), otherwise they will be permanently unreachable.

Unable to Locate the Server

You type in your address and your browser comes back right away to say that it is unable to locate the server. This means that the host name part of the address you typed in doesn't exist, probably because there's an error in the address. Check it and try again!

Saturday, April 18, 2009

RAM, Virtual Memory, PageFile and all that stuff

Virtual Memory

In most modern operating systems, including Windows, application programs and many system processes always reference memory using virtual memory addresses which are automatically translated to real (RAM) addresses by the hardware. Only core parts of the operating system kernel bypass this address translation and use real memory addresses directly. The virtual memory management component of the operating system maintains the tables used by the hardware to provide the mapping of virtual addresses into real addresses. A small amount of RAM is used by those parts of the operating system that can not be paged out (for example, the virtual memory manager) and is thus not available for assignment to virtual memory.

The key point here is that Virtual Memory is always in use, even when the memory required by all running processes does not exceed the amount of RAM installed on the system.

Address Spaces and Process

Any process (e.g. application executable) running under 32 bit Windows versions gets a set of virtual memory addresses (a Virtual Address Space) going from 0 to 4,294,967,295 (2*32-1 = 4 GB), no matter how much RAM is actually installed on the computer. Actually, this is essentially the same for all operating systems running on 32 bit hardware that implement Virtual Memory.

In the normal, default 32 bit Windows OS configuration, 2 GB of this virtual address space are allocated to the process’ private use and the other 2 GB are allocated to shared and operating system use.

Only that portion of the address space that is actually referenced (used) by a process or the system is associated with a page frame in real memory, or in the pagefile.

Pagefile

RAM is a limited resource, whereas virtual memory is, to a large extent, unlimited in that there can be a large number of processes each with its own 4 GB virtual address space, of which 2 GB is private to the process (32 bit Windows). When the memory in use (that is, has been reference) by all the existing processes exceeds the amount of RAM available, the operating system will move pages (4 KB pieces) of one or more virtual address spaces to the computer’s hard disk, thus freeing some RAM for other uses. In Windows systems, these “paged out” pages are stored in one or more files with the name pagefile.sys. There can be one such file in each disk partition.

A frequently asked question is “how big should I make the pagefile”? There is no single answer to this question, because it depends on the workload on the computer, how much RAM there is and how much virtual memory space that workload requires.

With operating systems like Windows XP on older computers with a small amount of RAM it is not uncommon for power users to have many windows open (and thus processes running) and to exhaust the available RAM. In this situation, the goal is provide sufficient pagefile space to avoid running out of available virtual memory, which could cause application failures or at least, significant inconvenience.

There is quite a variety of ideas on this subject, but here’s a place to start for computers (typically older ones) that don't have much RAM:

  • If the computer has less than 1 GB of RAM
  • Minimum – 384 MB
  • Maximum – 1 GB (or less if disk space is in short supply)
  • If the computer has more than 1 GB of RAM
  • Minimum – 1 GB to the amount of RAM installed
  • Maximum – 1 GB to the amount of RAM installed

Most newer computers will have more than I GB of RAM and, in most cases, there is sufficient RAM available that having more virtual memory than the available RAM is a relatively rare occurrence. There is little point in allocating a large minimum size pagefile, since it typically won’t be used. However, having a relatively large maximum will avoid “out of virtual memory” conditions without dedicating a big chunk of disk space for that rare situation.

A common objective in configuring a server is to ensure sufficient RAM so that paging doesn’t happen. Providing a large maximum pagefile is insurance against “out of virtual memory” situations that could cause service interruptions. Servers running a few applications are typically configured with enough RAM that paging is rare. A possible exception are servers used for Terminal Services, where it would be common for some users to be relative inactive for long periods of time and paging may occur routinely without a significant performance penalty.

Friday, April 17, 2009

Web Browser

New Technologies

The technologies for speech-enabled browsers continue under development and some are available now. It will just be a matter of time until speech-enabled browsers become a reality. I have included a small section near the bottom of this page for speech-enabled browsers.

New Version Release of Internet Explorer

Users may download the Beta version of Internet Explorer 8 from the Microsoft Web site. Some like to wait for a later version, not a Beta version. In that case you will want to download a version of Internet Exlorer 7.

Blackberry mobile cellular browser:HTML Internet Browser

There is an icon on the main screen of the Blackberry mobile phones which is an Internet browser. Activation requires that you have a contract with a carrier such as AT&T Mobile. Then when you open the program for the browser you would see the AT&T logo with the browser name of "HTML Internet Browser" and instructions on how to begin browsing. When you come to websites not optimizing for hand-held devices you would have to scroll a lot using your track ball (both sideways and vertically) in order to see all of the Web page from such a small screen. Some sites such as the download sites for cell phones, at AT&T, are optimized for hand-held devices and are much easier to navigate using your Blackberry device.

Chrome

Chrome was released for free download from Google. Hitmill.com webmaster decided on a browser test for Chrome, and tried Chrome at ancestry.com with the following problem: When a person search was done the results came up nicely and one the links pointed to a census online at ancestry.com. I could not move the census page up or down, the page locked up and turned purple in color. I was able to exit the ancestry.com Web site without the browser freezing. So, only the page at ancestry.com froze up. This is an issue for the Chrome development team. Chrome Chrome was not able to print a copy of a census report at ancestry.com. (I shall try this test of Chrome again this week). In other features of the browser, I am very impressed and love it.

Here are a few links about the new browser:

Features of Chrome

  • Web Developers' FAQ about Chrome Browser (Google.com)
  • Google Chrome: A Developer's Perspective (InfoWorld)
  • How Chrome Changed the Web Overnight (WebMonkey)
  • Google Chrome: The First True Web 2.0 Browser (PC World)
  • A Linux Users Guide to Google Chrome (ITWire.com)

Firefox 3

Firefox 3 is now available for download from mozilla.org. This is a newer, faster browser and any extensions are available for Firefox at mozilla.org. Firefox is available for Windows, Mac OS X, and Linux i686 systems and is currently available in 27 languages. Read more about it at http://www.mozilla.com/.

Firefox 1.5 and what that was like

When I downloaded Firefox and installed it on a Windows 98 machine, then on a Windows XP Professional computer, Firefox 1.5.x did not display table bordercolor nor the color of horizontal rules. Table border width was distorted as was the width of the horizontal rules in the <HR> tags. This occurred with Firefox versions 1.0 and 1.5.x I was not able to edit a local Web page from within the browser.

Firefox was very good at having multiple instances open at the same time for searching, researching. Internet Explorer early versions were very good for editing Web pages on your local machine or thumb drive and saving the code.

  • Safari 3.1.2
  • Safari 3.1.2

is the default browser of the Mac OS X operating system by Apple Computer. Safari is fast, easy to use and was a real joy with its faster-loading Web pages and faster browsing. Internet Explorer is also available for the OS X operating system but in tests at home, Internet Explorer was slower-loading and I was unable to edit text on a local HTML page using Internet Explorer for the Mac OS X G4 system and the "View, Source". Hands down, Safari was faster on the Mac G4 OS X machine.

Mac OS X users and Windows PC users using XP or Vista can download Safari 3.1.2.

Note: The Mac and iMacs now utilize an Intel processor. Leopard is the current operating system version and Snow Leopard will be next, with hoopla.

Microsoft Internet Explorer

Internet Explorer is the browser belonging to Microsoft Corporation. They distribute this browser (free-of-charge) as freeware over the Internet. It is also known as Microsoft Internet Explorer and is abbreviated "MSIE" or "IE". Version 7 is current but version 8 is in Beta 2 release.

As far as the browsers go, this is the browser I like best when hand coding HTML documents in NotePad and checking the page in this browser. Open the Windows Explorer to locate the HTML document on the local computer you wish to edit. Click/or double click on the Web document to open it in a browser window such as in Internet Explorer then Click on View, Source in the browser menu bar, make an editing change on the local computer's Web page's code document, and hit the F5 key to refresh the Web page. You can toggle the pages back and forth between the viewable Web page and the source code by using Alt + Tab (to toggle the editing pages of the browser and the source code).

  • Internet Explorer 8 World-Wide Sites
  • Internet Explorer 8 Beta2 for XP Computers in English language download site
  • Security TechCenter at Microsoft
  • Microsoft Security Bulletin Search
  • AOL Navigator

Netscape Navigator was a browser which was created by Mark Andreesen and his team for Netscape Communications Corporation which Mr. Andreesen co-founded. Navigator was distributed over the Web as freeware, and free downloads are still available to AOL users. Netscape Navigator was acquired by AOL.COM. Their newer versions still had some proprietary features and did not support all of the features of CSS-P, CSS, and DHTML.

Last I checked, all of my links for this browser came up with 404 errors for "File Not Found". I still keep a copy of Netscape Navigator on a disk. I not longer use this browser. Newer technologies were not supported, such as the CSS-P, a technology incorportated into the coined phrase of DHTML for Dynamic HTML, a marketing term at one time used by Netscape and Microsoft to describe the features in their version 4 browsers.

Opera

Opera Software is the Norwegian developer of the Opera Browser. This browser had a US "registration fee" of $35.00> Now you can try Opera (free) for several operating systems, including for Windows, Mac, Linux, OS/2, symbian OS. This software takes up very little space on the hard drive in comparison to Netscape Navigator or Microsoft Internet Explorer. Read about the features of this browser and additional information about Opera in the links below.

  • Additional Information about Opera Browser
  • Opera Home Page
  • Opera's Features
  • Opera Download Page, for Windows (English)
  • Opera Support Desk and FAQ Link
  • Opera Plug-Ins
  • Opera and Other Applications
  • MyOpera Forums
  • Opera Press Releases
  • NCSA Mosaic

NCSA Mosaic is a client browser that was developed at the National Center for Supercomputing Applications at the University of Illinois, Urbana-Champain. It was one of the earliest graphical user interface (GUI) browsers. The NCSA Mosaic for X developers were Eric Bina and Marc Andreessen. The NCSA Mosaic Web sites at ncsa.uiuc.edu are no longer available... not one of the previous links nor download sites is working.

  • Mozilla
  • Mozilla.Org
  • Mozilla at a Glance
  • Mozilla Tutorial
  • Mozilla is open source code so this tutorial for programmers is about how to use and configure the browser.

Thursday, April 16, 2009

Get Configuration Information with ipconfig /all

The ipconfig /all command lets you easily view a computer’s connection information. If you know a little about TCP/IP (Transmission Control Protocol/Internet Protocol), you know that computers communicate on a network and over the Internet by using specific numbers called IP addresses, and these addresses distinguish them from other computers on the network. IP addresses are created from four sets of numbers, one to three digits each, such as 192.168.0.5.Each computer on a network must be configured with an IP address that is different from every other on the network, the same way a computer must have a computer name that is distinct. If you’ve created a home network (workgroup) using the Network Setup Wizard, these IP addresses were created automatically.

When performing advanced troubleshooting, you’ll want to verify that all IP addresses on the network have the same pattern of numbers. For instance, if the IP addresses of three of the four computers on the network take the form 192.168.0.x, where x represents a single-digit number, the other computer’s IP address must also follow that form. Again, each IP address must be distinct, which means in this example that x must be unique for each address. While IP addresses are similar but different, subnet masks are all the same. A subnet mask tells the computers who is on their network, and who is not. A computer with a different subnet mask from the others will not be reachable. An example of a subnet mask is 255.255.255.0.

When computers on a network can’t communicate, and you want to perform advanced troubleshooting, you can find out what IP address each computer has been assigned by using the ipconfig /all command. The information output by ipconfig /all may give you insight as to the problem. Figure 8-19 shows an example of the output. Notice the IP address and subnet mask for this computer.

To get this information and troubleshoot connectivity on the network, at each computer:

  1. Click Start | All Programs | Accessories | Command Prompt.
  2. At the command prompt, type ipconfig /all.
  3. Locate the IP address for the local area connection, generally under Ethernet Adapter. Verify that the IP addresses are all similar, 192.168.0.x, where x is unique for each so that there are no duplicate
    addresses.
  4. Locate the subnet mask for the local area connection, generally under Ethernet Adapter. Verify that the subnet mask for all computers is 255.255.255.0.

If you find a computer that does not have the correct IP address or subnet mask, you need to correct it. There are multiple ways to do this. One way is to run the Network Setup Wizard again. Another is to change the network settings in the Properties dialog box of My Computer:

  1. At each computer, right-click My Computer, choose Properties, and click the Computer Name tab.
  2. Note what each workgroup name is, and what each computer name is. On the computer that has been deemed the problem computer, click Change.
  3. In the Computer Name Changes dialog box, type in a new name for the computer if the name is not distinct on the network. Type in the correct workgroup name. Click OK.
  4. Click OK twice more, and then click Yes to restart the computer.
  5. Verify that you can reach network resources. If you cannot, run the Network Setup Wizard again on all computers. This will most likely not be necessary.

Wednesday, April 15, 2009

Tips Trick Domain and Active Directory Stuff

Links to pages about Windows Domains and Active Directory. Will be more later (when and if I get the time!). Generally, the information is about business environments and some may be applicable when there isn't actually a Windows Domain. Sorry, I don't know squat about Small Business Server, so see the SBS newsgroups on the msnews.microsoft.com news (NNTP) server for SBS specific info. Generic Rules for User Accounts, Groups, Permissions and Group Policy Objects in a Windows Domain.

Convert SID to name and vice-versa.

Below are links to a pair of downloadable Word documents about how to create a Windows 2008 Active Directory Domain. They explain basic concepts and contain tips trick for those that are new to Windows Domains. Although the detailed instructions are specifically for the Windows Server 2008 user interface, the concepts (with a few exceptions) apply to Windows Server 2003 as well. I've included explanations of the "why" as well as the "how to" as a sort of tutorial. There are many "Comments" that will only be visible if you have "Original Showing Markup" or "Final Showing Markup" selected (Word 2007 in the Review tab on the Ribbon - in earlier versions the Reviewing Toolbar).

Instructions are included that are specific to a Virtual Machine environment, but using Virtual Machines is definitely not a requirement, although useful. The files are in both the 2007 Office format (docx) and older Office format (doc). If you have an older version of Microsoft Word, you can download (free) an Office add-in so you can open the 2007 format files - see http://support.microsoft.com/kb/923505 or http://www.microsoft.com/downloads/details.aspx?familyid=941b3470-3ae9-4aee-8f43-c6bb74cd1466&displaylang=en.

I don't know why, but when I download the Office 2007 format files with IE 6 or 7, they get the file extension ".zip" instead of ".docx". However, they do open correctly in Word 2007. Change the file extension from .zip to docx in the download dialog (or after the download is complete). I know that the Word 2007 file format is a "zip" file, but that does not exactly explain why IE changes the file extension from .docx to .zip. If I look at this site with an ftp client, it tells me that these files actually have the .docx file extension.]

Concepts about and instructions for installing Windows Server 2008, setting up basic networking in a home or small business type environment for testing/experimenting, installing Active Directory Domain Services, creating a basic Organizational Unit structure:

  • 133 KB WindowsServer2008BaseInstall.docx
  • 185 KB WindowsServer2008BaseInstall.doc

Building on the Domain built in the above document, adds sets of user accounts and groups, delegates administrative authority, builds basic set of Group Policy Objects, shared folders and printers.

  • 106 KB GettingStartedwithWindows2008Domains.docx
  • 213 KB GettingStartedwithWindows2008Domains.doc

64 Bit Processors and Address Spaces

64 bit processor architectures provide virtual and physical address spaces greater than 4 GB, which can be advantageous for some applications. 64 bit architectures can provide other advantages to applications that are not directly related to the amount of addressable memory, but those are not discussed here. It is important to realize that a 64 bit architecture does not necessarily mean a 64 bit virtual or physical (RAM) address space is available. Processor, mother board, chip set and operating system design may well limit the available virtual or real addresses to less than 64 bits.

The size of the address spaces provided by these architectures appears, at this juncture, to be more than one could imagine using. However, history has shown that our ability to predict address space requirements for future systems has been pretty poor. For example:  The designers of the IBM 360 architecture in the early 1960’s provided a 16 MB address space (24 bits). RAM on those early mainframes was typically in the 10’s of Kbytes, so 16 MB was out of sight. By the 1970’s, 16 MB had already become a real limitation, so the architecture was changed to provide 31 bit (2 GB) address spaces, both virtual and physical. Why 31 instead of 32 bits had to do with the way backward compatibility for systems and applications designed and coded for the 24 bit address architecture was implemented.

 

The designers of the IBM PC architecture in the 1980’s said they could not conceive of anyone requiring more than 1 MB of memory (a 20 bit address space) on a PC (despite the relatively recent experience with the IBM 360/370 architecture!). By the end of the 1980’s, this was becoming a significant limitation that lead to the design of “expanded memory” (a form of memory mapping related to the AWE scheme implemented in Windows NT etc.) and “extended memory” – an enlarged address space.

Maximum RAM supported by 64 bit editions of Windows:

  • Windows XP: 128 GB
  • Windows Vista Home Basic: 8 GB
  • Windows Vista Home Premium: 16 GB
  • Windows Vista Business, Enterprise and Ultimate: 128+ GB
  • Windows Server 2003 Enterprise Edition for Itanium: 64 GB
  • Windows Server 2003 Datacenter Edition: 2 TB
  • Windows Server 2003 Datacenter Edition for Itanium: 1 TB
  • Windows Server 2003 R2 Standard Edition: 32 GB
  • Windows Server 2003 R2 Enterprise Edition: 2 TB
  • Windows Server 2003 R2 Datacenter Edition: 2 TB
  • Windows Server 2003 R2 Datacenter Edition for Itanium: 2 TB
  • Windows Server 2008 Web Edition: 32 GB
  • Windows Server 2008 Standard Edition: 32 GB
  • Windows Server 2008 Enterprise Edition: 2 TB
  • Windows Server 2008 Datacenter Edition: 2 TB Windows Server 2008 for Itanium-Based Systems: 2 TB

See:

  • http://www.microsoft.com/downloads/details.aspx?FamilyID=bbc16ebf-4823-4a12-afe1-5b40b2ad3725&DisplayLang=en (Windows Vista Product Guide - Windows Vista Editions Feature Table)
  • http://www.microsoft.com/hk/server/windowsserver2003/evaluation/features/default.mspx
  • http://www.microsoft.com/windowsserver2003/64bit/ipf/datacenter.mspx
  • http://www.microsoft.com/windowsserver2008/en/us/compare-specs.aspx

Architectural limits for 64 bit Windows memory are:

  • 8 TB of shared virtual address space for the system
  • 8 TB of private virtual address space per process
  • 128 GB System PTE storage
  • 128 GB paged pool storage
  • 128 GB non-paged pool storage
  • 1 TB System cache
  • 256 TB pagefile size

From http://support.microsoft.com/?kbid=294418 and http://www.microsoft.com/windowsserver2003/techinfo/overview/x64benefits.mspx.

Here’s some information from various sources about address space implementations in various 64 bit processor architectures from Intel and AMD.

Intel

Not all processors actually have (implement) the same number of physical and virtual address bits. However, all the relatively new processors support larger physical address spaces than are actually supported by any version of Windows, so the actual number of physical address bits implemented is somewhat irrelevant.

For virtual addresses, the operating system must ensure that it does not attempt to allocate virtual memory addresses using un-implemented virtual address bits because there will be application or system failures if it does. The processors provide a way for the operating system to determine the number of virtual address bits and thus the maximum useable virtual address actually implemented (e.g. on Itanium processors, the PAL_VM_SUMMARY "procedure" - see page 2-450 in

  •  (http://download.intel.com/design/Itanium/manuals/24531805.pdf ).
  • Itanium (see http://www.intel.com/design/itanium/itanium/itaniumprodbrief.pdf and http://download.intel.com/design/Itanium/manuals/24531805.pdf section 4.3.2)
  • Physical Address - 44 bits - ~ 17,590 GB
  • Virtual Address - varies by processor model - minimum 51 - ~ 2,250,000 GB Itanium 2 (see http://download.intel.com/design/Itanium/manuals/24531805.pdf)
  • Physical Address 50 Bits - ~ 1,126,000 GB
  • Virtual Address varies by processor model - minimum 51 - ~ 2,250,000 GB Intel Pentium, Xeon, Core 64 bit (see http://download.intel.com/design/processor/manuals/253665.pdf)
  • Physical Address - varies by processor model - minimum 36 - 64 GB for most since 2004 Virtual Address 48 Bits (minimum) - ~ 281,000 GB

AMD

  • Athlon, Opteron, Sempron and Turion:
  • Physical Address 40 Bits - ~ 1,100 GB
  • Virtual Address 48 Bits - ~ 281,000 GB Athlon - http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/24659.PDF)
  • Opteron - http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/23932.pdf
  • Sempron - http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/31805.pdf
  • Turion - http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/32816.pdf

Simple Security with Simple File Sharing

You can apply security effortlessly to your shared folders with Simple File Sharing. As mentioned briefly in the previous section, there are two technologies for applying permissions to shared folders. If you have Windows XP Home Edition, you only have one choice: use Simple File Sharing. If you have Windows XP Professional and your hard drive is formatted with NTFS, you have a second choice: disable Simple File Sharing, configure your own share permissions, and use NTFS advanced permissions.

Simple File Sharing is a security setting that’s either on or off. If it’s on, the folder is shared and you have a few basic choices for how you’ll share it. If it’s off, there’s no sharing of the folder. When you turn off Simple File Sharing, you have access to more options. Specifically, you can state which users or groups of users can do what to the folder and its contents. While this offers a higher level of security and options, it’s easy to mess up. It’s up to you to decide what you’d rather use. I suggest starting with Simple File Sharing enabled, and if you decide later you need more options, disable it and use the advanced security features.

To apply security using Simple File Sharing, you first need to verify that Simple File Sharing is enabled. Of course, this only applies to users of Windows XP Professional, since it is enabled by default on Windows XP Home Edition and is the only choice:

  1. Open Control Panel and, if in Category view, select Appearance And Themes. Select Folder Options.
  2. On the View tab, make sure Use Simple File Sharing (Recommended) is checked. Click OK.

To apply Simple File Sharing permissions:

  1. Locate the folder to share from the Desktop or by using Windows Explorer. To locate a folder in Windows Explorer, right-click Start, choose Explore All Users, expand Documents And Settings, look under your username, and locate the folder to share.
  2. Right-click the folder and click Sharing And Security.
  3. On the Sharing tab, check Share This Folder On The Network. To give permission for other users on the network to change the files in the folder, also check Allow Network Users To Change My Files.
  4. You can also choose to drag the folder selected to the Shared Documents folder. To do that, click Shared Documents, wait for the Shared Documents window to open, and drag the folder into it. After doing so, anyone who logs onto your computer using any user account can access the data as well.
  5. If you did not perform Step 4, click OK to apply the changes in the Properties dialog box.

Monday, April 13, 2009

Printer related Scripts in Windows XP and Server 2003

Using the various functions and parameters of the rundll32 printui.dll,PrintUIEntry command, it is possible to add, delete or configure a printer using a command or script either on the local computer or remotely (for example, see Adding a network printer for all Users).  However, this command and tutorial and tips computer Internet dnd software can not create a new printer port or do some other printer management tasks.

Windows XP and Windows Server 2003 (and later versions) include a set of scripts for manipulating printers and printer ports.  These are located in the %systemroot%\system32 folder (usually c:\windows\system32).

prncnfg.vbs - configures or displays configuration information about a printer
For information about how to use this script see http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/prncnfg.mspx.

 

prndrvr.vbs - adds, deletes, and lists printer drivers
For information about how to use this script see http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/prndrvr.mspx.

prnjobs.vbs - pauses, resumes, cancels, and lists print jobs
For information about how to use this script see http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/prnjobs.mspx.

prnmngr.vbs - Adds, deletes, and lists printers or printer connections, in addition to setting and displaying the default printer
For information about how to use this script see http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/prnmngr.mspx.

prnport.vbs - add, delete or list Standard TCP/IP ports
For information about how to use this script see http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/prnport.mspx.

prnqctl.vbs - prints a test page, pauses or resumes a printer, and clears a printer queue
For information about how to use this script see http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/prnqctl.mspx.

Some of the functions used by these script do not exist in Windows 2000 and earlier Windows versions, so these script will not necessarily work on earlier Windows versions.  For example, prnport.vbs can not add printer ports to computers running Windows 2000 or earlier versions.

Thanks to Alan Morris of the Microsoft Printing team for pointing me at this information.

Sunday, April 12, 2009

Printing to a Print Server Device

"Print Server" is a term used to describe various different kinds of things. Many tutorial and tips computer so called print servers, including those built into some routers, are very simplistic and not much more than LAN adapters with a parallel port.  The internal LAN adapters in many "network" or "network ready" print devices are print servers of this type.  Note that some print servers are more sophisticated and do actually implement the Microsoft Networking protocols required to Microsoft Networking print servers.  Read the documentation to understand the capabilities of the particular print server device you have (or are contemplating acquiring).

If your print device is connected to one of these (type 4) print server devices (or has an internal one), it is not a network printer in Microsoft Networking terms.  Sometimes, the device comes with software that adds a port monitor so it can emulate a Microsoft Networking (type 1) print server and thus enables the print server device to emulate a network printer .  Check the documentation that came with the print server device or the manufacturer's web site for more information about such software.

 

However, with many print servers you have to use either the lpr/lpd or the port 9100 protocol to be able to print to print devices connected to print server devices.  With Windows 2000 or XP, the Standard TCP/IP port monitor supports both of these protocols for print server attached print devices

The instructions on this tutorial and tips computer are for Windows 2000, XP and later Windows versions.  If you have Windows 95, 98 or ME, these do not have the Standard TCP/IP port monitor - check the print server documentation or manufacturer's web site for how to use it with these operating systems.  With Windows NT 4, install the Print Services for Unix component to get the lpr port monitor, or use the DLC protocol, which is supported by most print server devices.

After you have created the Standard TCP/IP port for the print server device and added a printer to use it (as described below), the printer is a normal local printer.  You can then create a share for it and use it as a network printer in the usual way.

The more recent print server devices support both lpr/lpd and port 9100, but check the documentation because some of them only support one or the other of these.

If the print server device supports the port 9100 protocol, this is the easiest to configure and is the default for the Standard TCP/IP port type.  If the print server device doesn't support the port 9100 protocol, you will need to use the lpr/lpd protocol.  In this case, check the documentation to find out what Printer Queue Names (text or text1 are common) the device supports.  Some of the print server devices will accept print for any Printer Queue Name, but some will only accept print for the names they know.

To configure the Standard TCP/IP port for your print server device, you will need to know its IP address.  Check the documentation that came with the print server device (or print device if the print server is internal) or see Find IP address of print server device for some hints.

If the print server device has multiple print device connections (e.g. parallel ports), you will need to create a port for each such connection (i.e. one port for each attached print device).  The IP address will usually be the same for all the print devices (i.e. the print server device itself has only a single IP address).  If you are using the RAW (port 9100) protocol, the Port Number for the second print device will probably be 9101 and for the third, 9102.  If you are using the lpr/lpd protocol, the Printer Queue Name for the second print device will probably be the same as for the first, but with 2 on the end (e.g. text2) and for the third, with 3 on the end (e.g. text3).  If you create the Standard TCP/IP port using the Add Printer wizard as described below, you will need to give each Standard TCP/IP port a unique name and may need to set the Port Number or printer queue name after the Add Printer wizard completes.

To change the configuration of a Standard TCP/IP port:

open the Printers and Faxes folder

click File, Server Properties

select the Ports tab

select the port and click the Configure Port... button

To create a Standard TCP/IP port for a print server device and add a printer to it:

start the Add Printer wizard (e.g. click Start, Control Panel, Printers and Faxes, Add Printer)

on the Welcome panel, click Next

on the Local  or Network Printer panel, select Local Printer..., make sure there is no check mark in Automatically detect and install my Plug and Play printer; click Next

on the Select a Printer Port panel, select the Create a new port radio button, then select Standard TCP/IP Port from the Type of port: drop down list box; click Next

on the Welcome... panel; click Next

on the Add Port panel, in the Printer Name or IP Address: text box, key the IP address of the print server device.

on the Add Port panel, the Port Name: text box is the name that this port is to be known by on this computer.  You can key whatever name you want as long as it is unique on the computer or accept the default name that appears; click Next

at this point, the Add Printer wizard will attempt to communicate with the print server device and determine what make and model it is.  If this communication is successful, the Add Printer wizard will automatically configure the port with default settings - usually the RAW (port 9100) protocol, then display the Completing... panel.  If this happens, click Finish and continue with step 10

  1. if the Additional Port Information Required panel displays, then:
  2. the IP address you supplied is not the one in use by your print server device; click Back and check the IP address against the device's configuration

or

  1. you have the correct IP address, but the print server device did not respond with identifying information appropriately.  In this case:
    1. from the drop down list beside Standard, select the make and model of print server device you have; click Next
    2. if your particular device is not listed, or you want/need to change the port's configuration (e.g to use the lpr/lpd protocol), select the Custom radio button and click Settings...
    3. make the configuration changes you need - for example, to configure the port to use the lpr/lpd protocol:
      1. select LPR in the Protocol frame
      2. in the Queue Name text box, key the Printer Queue Name recognised by the print server device (e.g. text1)
      3. click OK
    4. click Next
    5. click Finish

complete the rest of the Add Printer wizard normally, as you would for a print device on any other type of port

Saturday, April 11, 2009

Printing from DOS with Windows 2000 or XP

In Windows 9x, there was a button in the printer properties to "capture printer port". Windows 2000, XP, 2003, Vista and 2008 don't have this button, so to print from a program running a Command Prompt window or an emulated DOS environment you may have to use a subterfuge,. There are three cases:

  1. the printer is a Local Printer and the print device is connected directly to a parallel port (e.g. LPT1). In this case, you should not have to anything to be able to print from a Command Prompt, from an emulated DOS prompt (command.com) or a DOS (16 bit) program.
  2. the printer is a Local Printer and the print device is connected to a USB or some other kind of port (e.g. a Standard TCP/IP port).
  3. In this case, you need to either:
  • pool the port the printer is on with the LPT1 port (see Pool in Glossary) (thanks to Steven Latus for this suggestion) or
  • create a share for the printer and map the printer to an emulated local port that DOS know about (e.g. LPT1). Do steps 1 through 7 below
  • the printer is a Network Printer or is a Local Printer on a port with a UNC name (see When installing Additional Drivers doesn't work).

Tutorial and tips in this case, map the printer to an emulated local port that DOS know about (e.g. LPT1). Do only steps 6 through 7 below.

If your computer is running Windows XP and you are not an administrator, you may not be able to map the printer to LPT1. In this case, if your DOS program allows you to specify printing to LPT2, do steps 6 through 7 and use lpt2 instead of lpt1 in step 7. If your DOS program will only print to LPT1, ask your administrator or support staff to implement the devcon work around described in the second bullet in the Resolution section of the article at http://support.microsoft.com/kb/313644.

Here's the detailed steps:

(Create a share for the local printer.)

  1. Open the printer's Property Page (see Property Page in Glossary)
  2. Select the Sharing tab
  3. Select the Share this printer radio button
  4. In the Share name: box, key the name you want to use as the printer's share name. The default is the same as the printer's name, but you may want to change it so that it is short and doesn't have any embedded spaces. This will make it easier later.
  5. Click OK (Map the printer share to an emulated local port. If you also have a Local Printer on your parallel port, use a different emulated local port (e.g. LPT2). In step 7, use this other port's name (e.g. lpt2) instead of lpt1.)
  6. Open a Command Prompt (Start, (All) Programs, Accessories)
  7. key: net use lpt1: \\computername\printersharename /persistent:yes and press Enter

for computername, use the name of your computer

for printersharename, use the share name you keyed in step 4

The /persistent:yes parameter makes the mapping of the printer to the emulated lpt1 port persistent, so you don't have to issue this command every time you logon.

Friday, April 10, 2009

Add Printer or Found New Hardware wizard fails for a printer

If the Add Printer or the New Hardware Found wizard consistently fails for a particular printer, there may be an information file on your computer that is causing this.  One way this might happen is if you upgrade from Windows 95, 98 or ME to Windows XP without first deleting the printer.

It's important to only install printer drivers that are designed and built specifically for the Windows version you have.  This is particularly important for Windows XP; many of the CDs and floppy disks distributed with printers (particularly older models) do not have Windows XP drivers - check the printer manufacturer's web site for printer drivers for the version of Windows you have.

The Microsoft Knowledge Base article at http://support.microsoft.com/default.aspx?scid=kb;en-us;298370 has a workaround for a known problem in Windows XP.

If that doesn't help your situation, do the steps below and also have a look at How to clean up printer drivers.

 

open a Windows Explorer window and navigate to %systemroot%\inf (usually c:\windows\inf)

scroll down until you see the files that start with oem

open each oem*.inf file one a time (double click should open it in Notepad, or right click and select Open With...) and see if it relates to the printer causing the problem.  There is usually a comment inside the file that says what model(s) of printer (or other type of device) it pertains to.  When you find one that relates to your problematic printer, delete it and any .pnf file with the same name.  Among other things, these .inf files are used when XP detects a "new printer" on the parallel port.  If the .inf file is for a driver that is not XP compatible, this can cause problems.

Thursday, April 9, 2009

Installing Additional Drivers on an older version of Windows

When you create a network printer, and the printer is shared from a Windows operating system in the NT family (e.g. Windows NT 4, 2000, XP), the printer driver can be automatically installed on the client from the print server. This is part of the feature called Point and Print. In many cases, the operating system version of the client computer is not the same as that of the print server hosting the printer. In these cases, the printer driver for the client operating system must be added to the print server as a Additional Driver.

The dialog for adding Additional Drivers this has a fixed idea about what other operating systems exist. So, if your client is Windows XP and the print server is NT 4.0, you can't add an Additional Drivers for a printer for your client using the dialog on the Windows NT 4.0 print server. However, you can install Additional Drivers for Windows XP clients on the Windows NT 4.0 or Windows 2000 print server from a Windows XP computer.

The same applies to installing Additional Drivers for Windows 2000 clients on a Windows NT 4.0 print server.

Note that it doesn't matter what edition of the various operating systems are on either the client or server (e.g. the client could be Windows 2000 Server and the server could be Windows NT 4.0 Workstation).

Basically, what you do is, on a client workstation that has the "new" OS, temporarily add a local printer on a convenient port (e.g. lpt1) and install the Windows 2000 or XP printer driver. Then you connect to the Printers and Faxes (or Printers) folder on the print server from that same client and install the just installed driver as an Additional Driver.

Here's the details. These instructions are for adding a Windows XP printer driver to Windows NT 4 print server. If the client is Windows 2000 or the print server is Windows 2000, the actual dialogs may be slightly different, but the process is essentially the same.

Logon at a client computer with a user account that has administrative rights and permissions on the print server computer.

Click Start, Printers and Faxes

Right click in an empty space in the right pane and select Add Printer

Click Next

Select the Local Printer… radio button, remove the check mark from Automatically detect and install my Plug and Play printer; click Next

Leave the LPT1: port selected; click Next. You will be adding the printer as if the print device is on the local computer’s parallel port, then deleting the printer later. This is just a way to get the XP driver installed, which is a pre-requisite to adding it as an Additional Driver on the server.

(#) If you are going to use the printer driver delivered with Windows XP, select the appropriate make and model. If you have downloaded a printer driver from a web site or have the driver on a floppy or CD, click Have Disk, Browse and navigate to wherever the driver is. Depending on how the driver is packaged, you may get a list of several printer models; in that case, select the appropriate printer model.

Follow through to the end of the Add Printer wizard (don't share the printer and don't ask for a test print)

Delete the local printer you just added; the printer driver is now installed and will NOT be deleted when you delete the local printer

Click Start, Run

Key \\printservername and press Enter

Scroll down in the left pane and click Printers and Faxes in the Windows Explorer window that opens

Right click on the printer you want to add the Additional Drivers for and select Properties

If you get told that a suitable driver has not been installed on your computer for this printer, click Yes and navigate to the same folder you used in step (#). If there are multiple printer models in the list, select the same you used in step (#)

Select the Sharing tab

Select the Shared radio button

Click the Additional Drivers button

Add a check mark to the Windows 2000 or XP item in the list; click OK

If you get a dialog box asking you to insert disks, click the Browse button and navigate to the same folder you specified in step 7; click OK

If you get a message box saying that “… the operation could not be completed…”. Click OK to clear the message box. Go back to step . For some unknown reason, this process sometimes fails the first time, but succeeds on the second attempt.

Click Close

Wednesday, April 8, 2009

Use the Network Setup Wizard

If you’re setting up the network for the first time or just need to repair the network you have, use the Network Setup Wizard. After your network is set up physically, you can use the Network Setup Wizard to configure it virtually. There are alternate ways to set up the network, but this is by far the fastest and easiest. For the best network performance possible, you should follow the setup directions to the letter.

If you already have a network set up but are having problems with it, running the wizard again may also solve these problems. The Network Setup Wizard locates your shared Internet connection, enables the Internet Connection Firewall, enables and configures a network bridge if the Windows XP computer has more than one NIC, and gives you the opportunity to name (or resolve naming problems for) each computer on the network. (A network will fail if more than one computer has the same name.) Once the network is set up (or  connected), you can then share files and folders, share media, play games on the network, and surf the Web simultaneously on all computers in the house.

The Network Setup Wizard can be run on computers installed with Windows 98, Windows 98SE, Windows Me, and Windows XP Home or Professional. It cannot be run on Windows 2000 or Windows 2003 Server editions. There is information in the help files to add the latter.

Before starting the Network Setup Wizard, verify that you’ve chosen a computer to act as the host and supply the shared Internet connection. The host should be the one connected to the Internet and thus should be a single computer, as detailed in the previous section. Then, do the following:

  • Verify that all hardware is installed on each computer and that it is working properly.
  • Turn on all computers, printers, scanners, etc.
  • At the host computer, connect to the Internet.

With that done, work your way through the wizard. At the host computer:

  1. Choose Start | All Programs | Accessories | Communications | Network Setup Wizard. Click Next to begin.
  2. Read the Before You Continue page, and click Next.
  3. Since you’re configuring the host computer, on the Select A Connection Method page, select This Computer Connects Directly To The Internet. The Other Computers On My Network Connect To The Internet Through This Computer. Click Next.
  4. On the Select Your Internet Connection page, choose the connection that you use to access the Internet. It may be chosen already. In this figure, there are three: an Internet connection that uses a modem, a 1394 FireWire connection for a digital video (DV) camera, and a local area connection using a NIC. Click Next.

  5. If your host computer has multiple connections, you can either let the wizard decide what’s best for you, or configure the settings yourself. It’s wisest to choose Let Me Choose The Connections To My Network. If you’re wary of doing it yourself, though, choose Determine The Appropriate Connections For Me (Recommended) and skip to Step 7.

  6. On the Select The Connections To Bridge page, select the local area connection that connects your host computer to the others on your network. Uncheck the others, the FireWire connection s unchecked because it is not the connection for the LAN; the NIC s. Click Next.

  7. On the next wizard page, type a computer description if desired, and a omputer name. The computer’s name must be distinct on the network. Click Next.

  8. On the Name Your Network page, select a workgroup name. By default, that name is MSHOME. If you’re repairing a network and don’t know the current workgroup name, click Start, right-click My Computer, choose Properties, and then click the Computer Name tab. The workgroup name will be there. Click Next.

  9. Click Next to begin the process of applying your network settings.

Once that’s complete, the next step is to get the appropriate network setup files on the other computers in your network. In my opinion, the easiest and most reliable choice is to create a floppy disk and carry it from computer to computer. You can also use the Windows XP CD, but sometimes that’s not available, especially with computers purchased from retail computer chains, where computers come with “restore disks” instead of the actual Windows XP CD. So, when prompted with the screen, select Create A Network Setup Disk. (If your newer computers don’t have floppy drives, you’ll have to use the Windows XP CD, or choose Create A Network Setup Disk, save the files to your hard drive, burn them onto a CD-R, and use that for the setup disk.)

Depending on the choice you make on the page, the wizard continues in one of various directions. If you’ve chosen to create a floppy disk, you’ll need to choose the drive, format the disk, and make the copy. If you’ve chosen to use the Windows XP CD, there isn’t much left to do but prepare the other computers.

For the other computers on the network:

  1. Insert the network setup disk into the floppy drive.
  2. Click Start | My Computer, and select the disk.
  3. Double-click netsetup.
  4. If you’re using a CD, input the CD, select Perform Additional Tasks and then Set Up A Home Or Small Office Network.
  5. You’ll work your way through the wizard the exact same way as before, except in the dialog box that asks you to define your connection, choose This Computer Connects To The Internet Through Another Computer On My Network Or Through A Residential Gateway.

After all computers have been configured, at each computer, open My Network Places. In the Network Tasks pane, select View Workgroup Computers. Each computer should appear within 15 minutes. If a specific computer does not appear, verify that the connections are secure, and run the Network Setup Wizard again on it. Figure 8-8 shows a successful and functional network setup.

Tuesday, April 7, 2009

Printer Pool

A printer pool is a set of more or less identical print devices that appear to the user a single printer.  Each print device is associated with its own port.  In a printer pool, there are multiple ports associated with a single printer.  Since there is only one (logical) printer, all the print devices in a printer pool use the same printer driver.  Thus, print devices in a printer pool must be identical in the sense that the printer driver for the printer pool works with all the print devices.  Also, they should have the same set of hardware features.  The user doesn't get to select which print device in the pool to use, so, for example, if one has a duplexing unit and one doesn't, double sided printing may or may not work depending on which print device happens to be used.

To enable printer pooling:

Open the Properties of the Printer to be pooled

Select the Ports tab

Add a check mark to the Printer Pooling check box

Click on the port(s) corresponding to the print device(s) that are to be part of the pool to add a check mark to them

Click OK

Monday, April 6, 2009

Avoid a Common Problem: Duplicate Files

Share files, folders, and media so they can be viewed and edited from any computer on the network. One of the main problems with multiple-computer households is duplicate data. Junior creates a movie of his garage band and tweaks it on his computer in Movie Maker 2, then saves it. He then sends the data to a shared folder for all of his family members to see, but does not delete it from its original location. This happens with family photos too, especially vacation pictures.

Everyone has a digital camera, has pictures stored on their own hard drive, and has spread multiple copies all around. This problem is also common with attachments received via e-mail. Instead of saving the funny picture of the dog in the dress to the hard drive in a shared location, the picture is forwarded via e-mail to everyone. It’s then on everyone’s hard drive instead of in a single, shared location.

Because of the massive amount of duplicate data on most home networks, it’s best to take control right away, creating shared folders on each computer or learning how to access the default ones, and put all data to be shared in it. The first step is to create a folder on the host computer that you will use to share data with everyone on the network :

  1. Right-click an empty area of the Desktop, point to New, and click Folder. Name the folder.
  2. Right-click the folder and choose Sharing And Security. You’ll see the folder’s Properties dialog box.
  3. The Properties dialog box shown in Figure 8-9 is the one you’ll see if you have Windows XP Professional and have Simple File Sharing disabled. If that’s the case, check Share This Folder On The Network, and click OK. If you see what’s shown in Figure 8-10, you’re either using Windows XP Home Edition or using Windows XP Professional with Simple File Sharing enabled. If that’s the case, select Share This Folder.
  4. Move what you want to share into this folder.

At each of the networked computers, create a link to this folder (all files stored here by you on your computer can be accessed by anyone on the network) :

  1. Click Start | Control Panel and, if in Category view, select Network And Internet Connections. Select My Network Places. If in Classic view, select My Network Places in the Other Places pane.
  2. In the Network Tasks pane, select Add A Network Place. Click Next to start the wizard.
  3. When prompted, select Choose Another Network Location, and click Next.
  4. In the Add Network Place Wizard, click Browse.
  5. In the Browse For Folder dialog box, expand Entire Network | Microsoft Windows Network. Locate your workgroup name and expand that, and then select the computer that holds the shared folder. Click OK.
  6. Click Next, type a name for the new network place, and click Finish. The file can now be accessed on
    the networked computer.
  7. Repeat these steps for each computer on the network, allowing each user to create one shared folder, and the others to connect to it using the Add Network Place Wizard.

Windows XP comes with shared folders already created, too. To find those, right-click Start, choose Explore All Users, expand Documents And Settings under the Local Disk, expand All Users, and select Shared Documents. Share this folder, and others only need to link to this folder to have access to items you put there.

Sunday, April 5, 2009

Adding a network printer for all Users

HP Officejet 6310 All-in-One PrinterWindows 2000, XP, 2003, Vista, and 2008 have the capability to have a Network Printer so that it is automatically available to any user that logs on at that computer.  Unfortunately, the Add Printer wizard does not expose that capability - it can only add a Network Printer for the currently logged on user.  So to add a printer globally (for all users) you have to a different tool.

The PrintUIEntry function of printui.dll has options for performing most printer management functions.  It can perform these functions either on the same computer that printui.dll is running on or on another computer (i.e remotely).  The general purpose rundll32 command can be used to execute PrintUIEntry function of printui.dll.

Some things to keep in mind:

  1. The function for adding a printer globally is /gaGlobally in this context means that the action applies to all and any users that happen to logon at the target computer. 
  2. The corresponding function for deleting a printer globally is /gd.  If you attempt to delete a global printer by using the Delete function in the printer's context menu, it will appear to delete, but will reappear when the Print Spooler service is restarted. 
  3. Only printers previously added using the /ga function can be deleted using /gd
  4. You have to have administrative rights and permissions on the target computer to use these functions.
  5. If a printer is added remotely using the /ga function, it will not appear to the user until the Print Spooler service is restarted or the user next logs on.  You can restart the print spooler remotely using these commands:
      sc \\targetcomputername stop spooler
        sc \\targetcomputername start spooler
    Like any other commands these commands can be used inside a command file, such as addglobalprinterremotely (see below).

Here's a way of "installing" network printers on workstations so that they are available to all users (remotely).

The file at AddGlobalPrinterRemotely.cmd has the commands for adding a network printer remotely and restarting the print spooler on the target computer.

If you prefer not to download .cmd files, paste (or key) the following into your own .cmd file (e.g. AddGlobalPrinterRemotely.cmd)

     rundll32 printui.dll,PrintUIEntry /ga /c\\%1 /n\\%2
     start /wait sc \\%1 stop spooler
     start /wait sc \\%1 start spooler

Then, at a command prompt key:

addglobalprinterremotely targetcomputername printservername\printersharename

For example to install the printer \\pserver\p1 on the workstation abc:

addglobalprinterremotely abc pserver\p1

To find out more about the rundll32 printui.dll,PrintUIEntry command, key (case sensitive):

rundll32 printui.dll,PrintUIEntry /?

Here's some details:

/c specifies the computer which is to be the target of the requested action.

If /c is not specified, the local computer is assumed.  In other words, the /c option allows you to do printer management things on other computers without actually physically being there (i.e. remotely).

/n specifies which network printer is to be, in this case, added using the printer's UNC name (\\servername\printersharename).

/? is understood by PrintUIEntry to be a request for its Help information, which is displayed in a separate window.

The "start /wait" command runs the command (e.g. sc), then waits until the command actually terminates.  Stopping and starting the print spooler takes a while, so without this, the next command (e.g. sc ... start spooler) may run before the spooler is actually stopped. 

Note : Possibly useful links

http://www.coribright.com/Windows/ some how to do things with printers articles

http://www.practicallynetworked.com/sharing/xp/addxp.htm help on setting up networks

http://h10025.www1.hp.com/ewfrf/wc/genericDocument?lc=en&cc=us&docname=bpl13043
   useful  information about printing in mixed OS version environments (NT 4, 2000, XP etc.)

http://welcome.hp.com/country/us/eng/software_drivers.html place to get HP printer drivers

http://www.lexmark.com/lexmark/sequentialem/home/0,6959,204816596_652569478_0_en,00.html place to get Lexmark printer drivers

http://www.epson.com/cgi-bin/Store/index.jsp?cookies=no place to get Epson printer drivers

http://www.usa.canon.com/html/cprSupportDetail.jsp?minisite=10000&a=b&navfrom=DrivD place to get Canon drivers

Bruce's General Windows Pages

http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/management/gp/default.mspx links to Group Policy related documents

http://support.microsoft.com/?kbid=128345 HOW TO: Troubleshoot Printing Problems in Windows 95, Windows 98, and Windows Millennium Edition

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=bpj02738&locale=en_US&taskId=135&prodSeriesId=27905&prodTypeId=18972 HP Jetdirect Print Servers -How to Determine, Reset, and Configure an IP Address on an HP Jetdirect Print Server

http://support.microsoft.com/kb/555381/en-us How to configure Windows Server 2003 SP1 firewall for a Domain Controller

HP LaserJet P1006 Printer