monkey Posted November 20, 2007 Share Posted November 20, 2007 i have just installed VW2008, firstly i tried it with my old OS X operating system, and it crashed when i tried to save a file. i then upgraded to leopard OS, have installed all the patches, updated all software on my mac, but still VW crashes when i try to save, sometimes i can save once, but when i try again it crashes, is anyone out there experiencing this same issue, and can anyone help? i know about the issues there have been with the new operating system and VW2008, but thought that was sorted with the new patch. Quote Link to comment
Vectorworks, Inc Employee Robert Anderson Posted November 20, 2007 Vectorworks, Inc Employee Share Posted November 20, 2007 Are you saving to the local HD or to a server? If so, what kind of server? Quote Link to comment
monkey Posted November 20, 2007 Author Share Posted November 20, 2007 im saving to a server, windows 2003 server Quote Link to comment
Guest Posted November 26, 2007 Share Posted November 26, 2007 I too am having the same problem using Tiger and 2008 as well as Leopard and 2008. I am saving to an external USB 2.0 HD (160gb Seagate FreeAgent? Go) formatted as FAT32. I use this drive to shuttle files between my XP PRO machine and my Mac, hence the FAT32. It doesn?t always crash, but it usually does. Quote Link to comment
Erich Lutz Posted November 27, 2007 Share Posted November 27, 2007 (edited) Same problem here. Tiger with 2008. Saving to windows 2003 server. SMB setting. Happens more than not. Forced to save to desktop. Working file saves, but VW2008 quits. File end up with no date info. All dates revert to 01-01-1970? Seems to recall one or two times when the same happened with a file saved on the desktop. Edited November 27, 2007 by Erich Lutz Quote Link to comment
Guest Posted November 27, 2007 Share Posted November 27, 2007 If you are connecting to a network drive via AFP, this is a known issue being worked on. This is included in the release notes of VW 2008 in the VW 2008 folder. Quote Link to comment
Guest Posted November 27, 2007 Share Posted November 27, 2007 Erich, I think your problem is a result of using Windows 2003. There are a few known issues with this configuration. Please contact Tech Support for details. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.