Steve (off topic a bit)

Since you seem to have looked at more than one defragger, I'd like to know if you've come across any that either let you leave certain files alone or, better yet, allow you to tell it TO FRAG named files, and how to FRAG them in relation to each other?

I think this could be more valuable than a defragger, and seems to fit in the same domain.

Thanks in advance

Jim Nelson



>Just to throw in my $.02, I think the HP GDI reliance is the reason you're not supposed to use HP printer drivers on Terminal Servers.
>
>And as far as defrag goes, I have just discovered O&O Defragmenter. It's got a nice addition in that you can specify certain files be defragged at boot-time before the OS generally loads and puts them in-use. On a couple of systems I have specified dbc/dbf/cdx/dcx/dct and on another I have specified my MDF/LDFs. Works like a charm. I had been a Diskeeper bigot since 1995, but I finally found a reason to switch and not look back.
>
>
>
>>I know that the 2100 drivers from HP now rely on the GDI for rendering and place a major-league burden on nets and legacy stations alike; we usually treat it as a 4Plus with the MS drivers and leave it at that. In GDI mode, it's a killer for the hosting PC. As mentioned, it does have a (to me) relative unspectacular local rendering engine that supports PCL 5, unlike the never to be sufficiently damned 1100...