How to get AutoCAD 2002 .PC3 files to work in both Win2000 and XP?

Discussion in 'AutoCAD' started by David Allen, Jul 15, 2004.

  1. David Allen

    David Allen Guest

    Got a Win2003 server
    Got a Xerox large format printer, 2 HP LaserJet's and Lanier Color Copier
    Got 2000 and XP workstations
    Using AutoCAD 2002

    I setup the PC3 files with a Win2000 machine.
    One of the LaserJet's and the Lanier PC3 files work on the XP box,
    but the Xerox and the other LaserJet do not work.

    I setup a PC3 for the Xerox on a XP machine and it does work on the
    2000 computer.

    Why is this? The driver and the print que server are the same? T

    David
     
    David Allen, Jul 15, 2004
    #1
  2. David Allen

    Chip Harper Guest

    PC3 files are system specific .... the ctb's and stb's can be shared
     
    Chip Harper, Jul 15, 2004
    #2
  3. David Allen

    David Allen Guest

    why then do they work sometimes and sometimes they do not?

    What am I supposed to do, maintain PC3 files for each OS?
    If I have a Xerox_8825.PC3 for Windows 2000 and another Xerox_8825.PC3 for XP
    What do I do, put them in separate folders and then point each workstation to a different network folder?
    I cannot name them 2 different names.

    "Chip Harper" <>
    |>PC3 files are system specific .... the ctb's and stb's can be shared


    David
     
    David Allen, Jul 15, 2004
    #3
  4. David Allen

    jonesr Guest

    Really?
     
    jonesr, Jul 15, 2004
    #4
  5. David Allen

    Joel Guest

    It's system dependent because the name of the printer tied to the PC3 may be
    different on each machine.

    It can work where you save one PC3 and copy them to other workstations on a
    network as long as the same drivers are loaded on all machines, all Acad hdi
    drivers are all the same and the network port name that the drivers are are
    calling to are all the same. All that info is saved in the PC3.

    We actually do have a mix of Win2000 and XPPro macines. All the Win2000
    machines can share the same PC3, but I have to remake them on the XP
    machines.
     
    Joel, Jul 15, 2004
    #5
  6. Just create different folders for each OS.
    In Options-files-printer support files-printer config files point out to the
    correct folder.
    YES, you may need different profiles for each OS.

    Jan
     
    Jan van de Poel, Jul 16, 2004
    #6
  7. David Allen

    David Allen Guest

    what go around to each workstation to configure them individually and maintain 2 different pc3 files?
    I'd rather not, that is the easy way out

    "Jan van de Poel" <>
    |>Just create different folders for each OS.
    |>In Options-files-printer support files-printer config files point out to the
    |>correct folder.
    |>YES, you may need different profiles for each OS.
    |>
    |>Jan
    |>
    |>"David Allen" <*@*.com> schreef in bericht
    |>|>> why then do they work sometimes and sometimes they do not?
    |>>
    |>> What am I supposed to do, maintain PC3 files for each OS?
    |>> If I have a Xerox_8825.PC3 for Windows 2000 and another Xerox_8825.PC3 for
    |>XP
    |>> What do I do, put them in separate folders and then point each workstation
    |>to a different network folder?
    |>> I cannot name them 2 different names.
    |>>
    |>> "Chip Harper" <>
    |>> |>PC3 files are system specific .... the ctb's and stb's can be shared
    |>>
    |>>
    |>> David
    |>


    David
     
    David Allen, Jul 20, 2004
    #7
  8. David Allen

    David Allen Guest

    As I stated in my email the printer name is identical on every machine because
    its connected to a network que such as \\server\printer. There is no way to
    have different names. There is also no way to install different drivers since you
    double click on a printer on a network server and it gets installed. I am using
    windows system drivers, no hdi.

    Again as I have stated before, I am using a mix of 2000 and xp. Sometimes it
    works and sometimes it does not.

    "Joel" <>
    |>It's system dependent because the name of the printer tied to the PC3 may be
    |>different on each machine.
    |>
    |>It can work where you save one PC3 and copy them to other workstations on a
    |>network as long as the same drivers are loaded on all machines, all Acad hdi
    |>drivers are all the same and the network port name that the drivers are are
    |>calling to are all the same. All that info is saved in the PC3.
    |>
    |>We actually do have a mix of Win2000 and XPPro macines. All the Win2000
    |>machines can share the same PC3, but I have to remake them on the XP
    |>machines.
    |>


    David
     
    David Allen, Jul 20, 2004
    #8
  9. David Allen

    John Schmidt Guest

    What we did is create specific Win2K and WinXP .pc3 files, but used the same
    name for both of them. Then, it's a one-time deal to set them up on the
    specific users' computers. We do this automatically via Windows logon
    scripts, so that if we make changes/updates to the .pc3 files, users get the
    updated versions the next time they log on to Windows.

    John
     
    John Schmidt, Jul 20, 2004
    #9
  10. David Allen

    David Allen Guest

    you know, this is a really old pain in the a$$ issue that has been rehashed over and over again over the years.
    Yes I know I could do separate pc3 files, but that's not what I asked.

    I asked why its not working properly when there is one driver on one server. When the workstation connects
    to the server only one possible driver gets downloaded and installed. Its impossible that all XP machines regardless
    of age have an "old" driver. I do not install drivers locally, they always go through a print que server. Again as I
    stated in the original post, some devices it works and some it does not. Does it really make sense that I can create
    a pc3 file for one printer in win2k and it works in xp. Then another printer created in 2k does not work in xp. But
    then I can create that same pc3 in xp and it works in 2k? It makes no sense why creating it on one OS works while
    creating it on another os it does not.

    If it was consistent then it would not be frustrating. But there is really no reason why PC3 files cannot be shared
    between OS's. It works most of the time. When it does not work, that is the frustrating part.

    I just wish I could edit the actual internals of a PC3 file to figure out what is wrong with it.

    "Dean Saadallah" <info from pendean>
    |>Need a helmet to go with that brick wall ;)
    |>
    |>I suspect somewhere you installed an 'old' driver in WinXP on those machines
    |>where it does work, and 'newer' WinXP drivers on the other machines perhaps?
    |>Short of a group of us dropping by your office and tearing up your systems
    |>to investigate, you will probably have to just wait until someone guesses at
    |>something that will work.
    |>
    |>In the meantime, the one working solution is being repeated often in this
    |>thread, if you got better things to do.. .
    |>
    |>--
    |>Dean Saadallah
    |>Add-on products for LT
    |>http://www.pendean.com/lt


    David
     
    David Allen, Jul 22, 2004
    #10
Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.