• First you have to setup the printer on a server or workstation.
• Share printer from this location. In this case LJ2300
• Then use the NET USE Command to connect to this share.
• net use lpt1: \\sharename\share
• Then install the printer as lpt1

Issue: 
Error or blue screen on PCI.SYS when loading OS or XP Pro CD cannot see a bootable device or partition.

Requirements:
• Download Dell driver for RAID controller.
• Slipstreamed CD with SP2 (Without this you will never boot the SP2 drivers are needed.)
• USB Floppy Disk (Could not figure out how to get USB stick working)
• Change BIOS RAID to Combination not AHCI.

Backup Exec Error:
Storage device “EXABYTE 1″ reported an error on a request to write data to media. Error reported: The I/O bus was reset.V-79-57344-34027 - The storage device was reset.
Fix:
This error is caused when the controller cannot handle having two devices access information on one another at the same time. You will need to have the tape drive and the disk drives holding the data on separate controllers

Multilink Modems To Increase Your Connection Speed

If a slow network connection is your issue and high speed internet is not an option then you should try multiliking. A multilink connection is a way you could double your connection speed when other alternatives are not available. A multilink connection is when you connect two modems together and allow them to work synchronously with each other giving you double the effective speed.  Unlike many Internet speed-enhancement techniques that employ a software utility to tweak an existing modem or connection, multilinking is a hardware-based solution. It uses multiple dial-up modems that piggyback duplicate Internet connections, one behind the other. The most common configuration involves two modems. 

I decided that when a sales-department laptop passed through IT’s hands for a regular backup, we would configure the laptop with a local policy that did nothing but stop the AIM executable from running. By default, security restrictions apply to all users on a computer. Typically, you’d exempt local administrators from such restrictions because they have access to the local security policy editor and can change whatever they like. But because the local security policy editor isn’t obvious to a typical user, I decided that hiding the AIM-blocking policy in plain sight was a workable plan.