US VORTECHS

PCL or Postscript, That is the question

Wednesday, 03 February 2010 07:16 |

Author: Shawn Levin |

PCL vs Postscript

Have you ever wondered why there are three different print drivers for your printer? PCL5, PCL6 and Postscript. Well in just a few words it will all be clearer. Bottom line, PCL is good for text, speed and compatibility whereas Postscript is your ticket to consistency and graphic quality.

PCL

Printer Control Language or PCL is a common printing language used widely by many different printer manufacturers. PCL is supported by many different Operating Systems which allows for the same printer to work in many different environments. PCL is device dependent. This means that the drivers for this language utilize the printer hardware for creating some of the printed data, usually graphics data such as fill areas, underlines or fonts. This allows the computer to process the print job quickly and efficiently. The printer is then responsible to complete the creation and processing of page data. Individual printers may perform these tasks differently giving you a slightly different output.

Pros:

Fast print processing.

Widely supported in many different Operating System platforms.

Cons:

The same print job on two different printers may vary slightly.

Quality of graphics is dependent on the print device.

Not supported in most Macintosh environments

Postscript:

Postscript language or PS is a common printing language also used widely by many different printer manufacturer. It is used heavily in Macintosh platforms and for graphic applications in several platforms. Unlike PCL, Postscript is device independent. This means that the Postscript language creates all of the print data and does not rely on the printer for print data. This allow the output to be consistent when printed on more than one type of printer or print device. Specifically, the graphic objects will be consistent and in some cases of higher quality than PCL.

Pros:

Graphical objects are often more detailed

The same print file should print identically on two or more different print devices. (This most beneficial when used for printing drafts on one printer then sending out to a printing company for production)

Cons:

Print processing can be slow

Not found in as many platforms as PCL

Print file and memory requirements are larger.

Please conserve...only print when you need to, and be sure to share!

Some information found at http://www.laserquipt.com/support/idx/0/063/article/PCL-vs-Postscript.html Thanks!

Bart PE Boot Disk Creation

Tuesday, 02 February 2010 06:34 |

Author: Shawn Levin |

BartPE on USB Drive (UFD) - Build Bootable BartPE USB Drive

1. Download and install PEBUILDER

2. http://www.nu2.nu/pebuilder/

3. Ensure pe2usb.cmd and pe2usb.bin are in the <pebuilder> directory

4. Get a flash USB Drive with at least 256MB total capacity

5. Download Server 2003 SP2 at http://www.microsoft.com/downloads/details.aspx?FamilyId=95AC1610-C232-4644-B828-C55EEC605D55&displaylang=en

6. Rename the downloaded file to sr1sp.exe

7. Unpack the files

a. open command prompt

b. navigate to file location

c. type sr1sp.exe -x

d. extract to c:\server2003sp1

8. Copy the file c:\server2003sp1\i386\setupldr.bin to <pebuilder>\srsp1 folder

9. Expand the file c:\server2003sp1\i386\ramdisk.sy_ to <pebuilder>\srsp1

a. type "expand -r c:\server2003sp1\i386\ramdisk.sy_" in cmd

b. move ramdisk.sys to <pebuilder>\srsp1

10. You can now remove/delete the c:\server2003sp1 folder

11. Build BartPE using pebuilder as normal

a. Set the output folder to "BartPE"

b. generating an ISO image not needed

12. Run "pe2usb -f <drive:>" formats and installs the files to your UFD.

a. Formatting is only needed the first time, so next time you can run
"pe2usb <drive:>" (without -f) to update the BartPE files.

13. Will prompt "For successful booting BartPE from a USB flash disk you need:
"A PC that is capable of booting from a USB flash disk with 256MB memory or more..."

Thank you - http://www.911cd.net/forums/index.php?showtopic=10806