Jump to content

jhutchison

Member
  • Posts

    84
  • Joined

  • Last visited

    Never

Everything posted by jhutchison

  1. Many times when I startuo VWA 9.5 in OSX, my workspace pallettes disappear. I have to then spend time re-activiting them in the pallette scroll down window. Anyone have any idea what is causing this?
  2. oh---and I forgot to mention---yes we print out of Acrobat and Preview natively in OS X. In fact, all of our client machines no longer use classic to print. We just send the print files to the OS9 print server and let it do the rest.
  3. As I mentioned in my original post, our network consists of 6 client macs (all running OSX and VW 9.5), a file server (running osX) a print server (running OS 9.2 and HP 455CA Rip software) and an HP 455CA plotter connected to the network via an external HP jet direct. With the HP RIP software running in OS 9.2 on the preint server, all client macs running OSX can see the 455CA in the Print Center under "Appletalk" connection. All you do to get the PPD file is copy the HP455 CA PPD file from the System folder of the OS9 Print Server to the Mac OS X client Hard Drive. Once you do that, you can select the ppd file in Print Center by clicking on "Printer Model", scroll to the bottom of the list, choose "Other" and find the HP 455CA PPD file which you copied to the OSX client. That's it---you're done.
  4. Problem solved. I found that if I print the pdf to the plotter using Preview, everything prints correctly.
  5. Problem solved. I found that if I print the pdf to the plotter using Preview, everything prints correctly.
  6. Problem solved. I found that if I print the pdf to the plotter using Preview, everything prints correctly.
  7. There have been many posts about printing to a plotter using pdf's in OSX. The following are results and problems that occur in our office. If anyone has reccomendations for the problems, we would greatly appreciate it. Our network consists of 6 client macs (all running OSX and VW 9.5), a file server (running osX) a print server (running OS 9.2 and HP 455CA Rip software) and an HP 455CA plotter connected to the network via an external HP jet direct. As many people w/ the 455CA plotter have discovered, we are not able to print to the plotter directly out of VW without getting PS errors. We CAN print to the plotter natively in OSX by generating PDF files and printing directly out of Acrobat. However, the following problems are occurring with our physical output: 1. Fills with lines in them print as a solid grey even though they appear correct in the pdf file. Hatches print correctly. 2. Images imported into VW print out as solid grey even though they appear correct in the pdf file. We are so close to having a completely native OSX network---if only we could only resolve these glitches. Recommendations much appreciated.
  8. There have been many posts about printing to a plotter using pdf's in OSX. The following are results and problems that occur in our office. If anyone has reccomendations for the problems, we would greatly appreciate it. Our network consists of 6 client macs (all running OSX and VW 9.5), a file server (running osX) a print server (running OS 9.2 and HP 455CA Rip software) and an HP 455CA plotter connected to the network via an external HP jet direct. As many people w/ the 455CA plotter have discovered, we are not able to print to the plotter directly out of VW without getting PS errors. We CAN print to the plotter natively in OSX by generating PDF files and printing directly out of Acrobat. However, the following problems are occurring with our physical output: 1. Fills with lines in them print as a solid grey even though they appear correct in the pdf file. Hatches print correctly. 2. Images imported into VW print out as solid grey even though they appear correct in the pdf file. We are so close to having a completely native OSX network---if only we could only resolve these glitches. Recommendations much appreciated.
  9. There have been many posts about printing to a plotter using pdf's in OSX. The following are results and problems that occur in our office. If anyone has reccomendations for the problems, we would greatly appreciate it. Our network consists of 6 client macs (all running OSX and VW 9.5), a file server (running osX) a print server (running OS 9.2 and HP 455CA Rip software) and an HP 455CA plotter connected to the network via an external HP jet direct. As many people w/ the 455CA plotter have discovered, we are not able to print to the plotter directly out of VW without getting PS errors. We CAN print to the plotter natively in OSX by generating PDF files and printing directly out of Acrobat. However, the following problems are occurring with our physical output: 1. Fills with lines in them print as a solid grey even though they appear correct in the pdf file. Hatches print correctly. 2. Images imported into VW print out as solid grey even though they appear correct in the pdf file. We are so close to having a completely native OSX network---if only we could only resolve these glitches. Recommendations much appreciated.
  10. The following sloution works perfectly for us: The Epson 1520 printer is connected to a computer (our print server) running OS 9.2 via usb. The Epson Stulus RIP software runs continuously on that computer. All client running OSX simply setup a new printer using print center. First, copy the 1520 ppd file to your OSX computer. Then select Appletalk printer in print center, and choose the 1520 ppd file. Works beautifully for all computers on the network
  11. We are running the new 9.5 on Mac OS 10.1.2. Our plotter is an HP 455CA on an ethernet network. Because the HP RIP software that came with the plotter no longer works with VW9 and later, we purchased the Microspot Graphic Pak, which works beautifully with the HP plotter. However, Microspot does not work in OS X. Does anyone have a printing solution so they can plot in OS X?
  12. surprisingly, I am having far fewer problems in 9.5 running natively on os X.1 than I did with 9 on os 9. Come to think of it, no problems whatsoever---other than the maddening issues of postscript errors on our 455CA plotter. (We've had ps errors ever since upgrading to VWA 9) I think we are about to purchase an HP 500ps instead.
  13. OS 10.1 has been released, and it appears to fix many bugs, speed, and classic compatibility issues. In a word, it's magnificent. Most of the big software packages will have OS X compatible versions out by November. Our office feels it's finally time to upgrade. When is Nemetschek going to release the OS X version of VectorWorks. I understand they do not want the same disaster to happen as when they released VW9.0, but they need to give an accurate time table so the rest of us can start to consider implementation procedures. Nemetschek---do you have a date targeted?
  14. I am having trouble printing images to ps files (via a plotter) within 9.01. The images either are incomplete, or vectored. If I exporet file to version 8, images print fine. Anyone else have this problem? Any suggestions?
  15. Sean ? that was my original guess as well. I tested that theory out last week and made sure my network was connecting via TCP/IP in OS 9, but it did not work. I posted the same issue on the Apple discussion board, and got the following reply regarding the path structure differences between OSX and OS9: All paths stem from the root '/' and a partition is mounted under this in the directory Volumes. Try prepending '/Volumes/' to your path. For example, if you have a partition called 'OS9' and a file 'myfile.txt' in a particular directory you would use this: /Volumes/OS9/some/path/myfile.txt Does this make sense to your tech guy working on this isssue? It appears that OS X uses a different path because of the Unix code. Please let me know what you find out---or have your tech guy call me directly. Until we get this issue resolved, OSX and OS 9.1 cannot run simultaneously on a network while using VectorWorks.
  16. A know bug in version 9 (computer crashes while exporting files with references to version 8) is still not fixed in update 9.01. Does anyone else have this problem? I am using Architect 9.01 on a Mac G3 466 using OS 9.1.
  17. In the last dispatch newsletter, Nemetschek indicated there would be a downloadable beta version of Vectorworks for OS X users, late spring or early summer. Has anyone seen this?
  18. OS X is now shipping on all new Macs. We are having a problem with Vectorworks references in a server environment. When I try to open a file while using OS X (OS 9.1 in classic mode), I get a message that says my server does not support the IP protocols required by OS X. I have no problem opening a non-referenced file under the same conditions. My server is running OS 9.1. It appears that the problem is that (Vectorworks) references files by remembering the path of the referenced file. Apparently OS X and 9.1 have different directory path structures. In OS 9.1, the path from a server which has 2 disks (partitions), is remembered by "computer name/partition name,........". In OS X, the path of the same server is remembered by "partition name/........". Hence, OS X does not include the computer name in the path, whereas OS 9.1 does. Any idea how I can get the paths to read the same between the 2 different OS's? Has anyone else run into this issue?
  19. OS X is now shipping on all new Macs. We are having a problem with Vectorworks references in a server environment. When I try to open a file while using OS X (OS 9.1 in classic mode), I get a message that says my server does not support the IP protocols required by OS X. I have no problem opening a non-referenced file under the same conditions. My server is running OS 9.1. It appears that the problem is that (Vectorworks) references files by remembering the path of the referenced file. Apparently OS X and 9.1 have different directory path structures. In OS 9.1, the path from a server which has 2 disks (partitions), is remembered by "computer name/partition name,........". In OS X, the path of the same server is remembered by "partition name/........". Hence, OS X does not include the computer name in the path, whereas OS 9.1 does. Any idea how I can get the paths to read the same between the 2 different OS's? Has anyone else run into this issue?
  20. I have figured out the problem of a message I posted earlier. That message is as follows: So far VA9 is working fine with Mac OS X (aside from all the problems and bugs VA9 already has under OS 9.1). However, when I try to open a file while using OS X (OS 9.1 in classic mode), I get a message that says my server does not support the IP protocols required by OS X. I have no problem opening a non-referenced file under the same conditions. My server is running OS 9.1, as I am testing OS X on only one machine for a few months before I install it over our entire network. Has anyone else ran into these issues? The problem is that (Vectorworks) references other files by remembering the path of the referenced file. In OS 9.1, the path from a server which has 2 disks (partitions), is remembered by "computer name/partition name,........". In OS X, the path of the same server is remembered by "partition name/........". Hence, OS X does not include the computer name in the path, whereas OS 9.1 does. Any idea how I can get the paths to read the same between the 2 different OS's? Since Apple is now shipping all new macs with OSX, Vectorworks compatibility between 9.1 and X is pretty essential.
  21. I have figured out the problem of a message I posted earlier. That message is as follows: So far VA9 is working fine with Mac OS X (aside from all the problems and bugs VA9 already has under OS 9.1). However, when I try to open a file while using OS X (OS 9.1 in classic mode), I get a message that says my server does not support the IP protocols required by OS X. I have no problem opening a non-referenced file under the same conditions. My server is running OS 9.1, as I am testing OS X on only one machine for a few months before I install it over our entire network. Has anyone else ran into these issues? The problem is that (Vectorworks) references other files by remembering the path of the referenced file. In OS 9.1, the path from a server which has 2 disks (partitions), is remembered by "computer name/partition name,........". In OS X, the path of the same server is remembered by "partition name/........". Hence, OS X does not include the computer name in the path, whereas OS 9.1 does. Any idea how I can get the paths to read the same between the 2 different OS's? Since Apple is now shipping all new macs with OSX, Vectorworks compatibility between 9.1 and X is pretty essential.
  22. I have figured out the problem of a message I posted earlier. That message is as follows: So far VA9 is working fine with Mac OS X (aside from all the problems and bugs VA9 already has under OS 9.1). However, when I try to open a file while using OS X (OS 9.1 in classic mode), I get a message that says my server does not support the IP protocols required by OS X. I have no problem opening a non-referenced file under the same conditions. My server is running OS 9.1, as I am testing OS X on only one machine for a few months before I install it over our entire network. Has anyone else ran into these issues? The problem is that (Vectorworks) references other files by remembering the path of the referenced file. In OS 9.1, the path from a server which has 2 disks (partitions), is rememebered by "computer name, partition name,........". In OS X, the path of the same server is rememebered by "partition name,........". Hence, OS X does not include the computer name in the path, whereas OS 9.1 does. Any idea how I can get the paths to read the same between the 2 different OS's?
  23. What is the time line for a carbonized version of Architect 9 for OS X?
  24. So far VA9 is working fine with Mac OS X (aside from all the problems and bugs VA9 already has under OS 9.1). However, when I try to open a file while using OS X (OS 9.1 in classic mode), I get a message that says my server does not support the IP protocols required by OS X. I have no problem opening a non-referenced file under the same conditions. My server is running OS 9.1, as I am testing OS X on only one machine for a few months before I install it over our entire network. Has anyone else ran into these issues?
×
×
  • Create New...