Sarah C. Sarnelli

Katie, I tried the OIP-Esc combination but could not get that to bring up the plug-in error. I asked the user if she thought she may be doing this, and she worked until it happened again. She said she definitely had not used the escape key at all nor gone into the OIP while using a tool. She and I both use the OIP a lot, but no esc. I have replaced her VW10.1 with a "fresh" copy off our server, replaced her workspace, and replaced her prefs on Friday. It still happens. The problem progressed today to crashing VW when she tried to use her trim tool. NOTE: she says it only happens when using the trim tool or offset tool. I know that I and the other users with the problem had the error only with those tools, too. We are ordering the VW10.1 CD upgrade today. Hopefully the download was the problem. Sarah

Go to HP's website. This is an OS related bug that has to do with presets made before version 10.2.3 or 4. We get this error message on several of or laser printers. Sarah

We have also had this problem, and like everyone else we notice it only on VW10.1. My users were all running 10.2.4 until yesterday when I began to update to 10.2.5. It started with one user, but has now shown up with 5 of the 12 users that I have on VW10.1 (the rest of the office is still running 10.0 because of this and a few other annoying bugs found in VW10.1). For each afflicted user, we replaced their workspace with their back-up copy on the server. For all but one this has fixed the problem. Yes, restarting VW fixes the problem, but it just shows up again. ALL of my users created their custom workspaces from the Architect workspace which comes with VW10.0. The plug-in error seems random at this point (I have gotten once myself, but it has never shown up again even though I am runnign the same files and using the same tools). Any suggestions other than buying the CD? Is the CD the full VW10.1 version or just an update? I downloaded the updates to VW10.0.1 and VW10.1 myself and updated a clean version of VW10.0. This is the version that has been copied to all the computers in the office. Sarah

Katie, What ever became of this? We used to have this problem in some VW9 files, but we thought it went away in VW10. We were wrong. We have a file (admittedly converted from VW9) in which a group causes force quit. Long version: File made in VW10, copied an elevation from another file which was converted from VW9. Group(s) in elevation can be opened and edited, but when closing the group the parametric constraint dialogue appears and loops -- must force quit VW. The only way around the bug (which we found in VW9) was to ungroup the objects, edit, then regroup. We do not use parametric contraints since we first found this bug over a year ago in VW9. The user is running VW10.1 on Mac OS X 10.2.4. Any ideas? Sarah

I have several users (on VW10.0 Mac) that have complained about their inability to snap to objects. They try to snap to the end of a line or the corner of a rectangle or polygon (with all the proper snaps turned on), and they either cannot get the cursor to snap to the point or they think it snapped but the line is obviously not at the preferred snap location. We first tried LOWERING the snap radius below 5 pixels, but we found it's actually better to RAISE it above 10 pixels. We're still experimenting, though. I will let you know if VW10.1 fixes the problem for them. Sarah

Katie, Per his request, I just sent the file to Paul Pharr and the bugsumbit. Since reading about fixing permissions on some websites, he have begun to run it on all our machines. The 10.2.4 machines that the file crashed on have all had their permissions fixed in the last week (because I did one myself over the weekend and another was wiped clean, updated, and fixed on Tuesday). So, looks like permissions ain't gonna do it here. It has fixed issues with other users' crahes, though! I also dealt with a file this morning where the batt insulation (done using the b.a. tool) duplicated itself randomly all over a page when the file was first opened in VW10.1. The file was orginally drawn in VW9.5.2, converted to VW10 a few weeks ago, and the user was upgraded to VW10.1 yesterday. Any ideas? Sarah

We have a file which crashes in OSX 10.2.4 only: Machines running 10.2.4 with VW10.0 OR VW10.1 -- crash. Machines running 10.2.1, 10.2.2, or 10.2.3 with VW10.0 -- opens just fine. The file has a lot of freehand tool work. Could this be the culprit? As I mentioned on a similar topic, our office is very anal about all the machines running the same software configurations. Our users do not have admin privledges, so changes to the configuration have to be OKed by the techies. Sarah

Confusing description, but I guess you're saying that you want to be able to move a base reference file from one location to another and the files referenced to it would keep the refs? Well, this is actually how it works already. Did I misunderstand? Sarah VW10.1 OSX 10.2.4

First, Katie I am sending you a file which I have not yet fixed. It could be a combination of drawing label selections (we use config 7 with 24 pt title, 60pt bubble, and 10pt scale; I have custom scales in these files). Second, rosebud, you need to run Font Doctor on your fonts. We have some MM fonts that we have gotten to work by running Font Doctor. I believe Katie, though, that these fonts are about to die on the Mac. The only MM font we have left is Graphite, and we discourage its use now. Sarah Sarnelli Jackson & Ryan Architects Houston, Texas

I hate replies like this, but.... I have 25 users running VW10.0 (with only me currently on VW10.1) on OS X 10.2.2-4, and we have not had any frequent crashes. Our users are not allowed to admin their computers, so very few are running anything other than "standard" programs (OS X Mail client, iCal, Address Book, AppleWorks, FileMaker, Netscape, Exploder...). Even the three people playing with widgets have not reported problems. Sarah

Have you tried "Set Print Area..." in the Page menu? Sometimes the print area in VW9 gets stuck (instead of being on "One Page", it shifts to a specific size). We encountered this problem a lot in VW9.5.2 -- we even had it progress to crashing VW when Page Setup or Print was inititated. The solution there was to export a VW8 file and reimport. Sarah Sarnelli Jackson & Ryan Architects Houston, Texas

I updated to VW10.1 yesterday, and opening my files this morning I discover that all my drawing labels are displaying incorrectly. When I click on one, all the settings are correct in the Object Info. I changed a text size field, and the screen regenerated and displayed the drawing label correctly. Saving the file and opening on a computer still running VW10.0, the drawing labels display correctly -- "changed" ones and originals. VW10.1 Architect with RenderWorks installed running on Mac OS X 10.2.4 Sarah Sarnelli Jackson & Ryan Architects Houston, Texas

In our office, we have created one "master" VW prefs file which contains all of our serial numbers -- in other words, we do not assign serial numbers to each work station. Call us lazy. Fine. When the 10.0.1 install came out, we noticed that it never updated the VW application -- Finder "get info" and "About VW" both said the app was version 10.0.0. Two of us even had the 10.0.1 installer "update" software on our iPods instead of our hard drives (what's up with that????). So, we never bothered with the update and went back to 10.0. In the last two days, we have been 0 for 4 installing the 10.0.1 and 10.1 updates. Today we tried installing VW 10.0 all over again from scratch from the CD. Without opening the app or adding serial numbers, we successfully updated to VW 10.0.1 and then 10.1. THE DIFFERENCE: Note that the second time we did the installs all in a row which means that the preference file had only ONE serial number in it. Obviously the 10.0.1 updater screws up with multiple serial numbers, thus users with more than one serial number in their preference file are going to have problems. We are running VW Architect with RenderWorks installed (combo serial numbers) on Mac OS X 10.2.4. Sarah Sarnelli Jackson & Ryan Architects Houston, Texas

Oops. Forgot: we tried both dwg and dxf(text) in r2000 and r14. Sarah

We are using Palatino (similar to Times New Roman) and Helvetica. Both fonts disappear. We send our consultants equivalent PC fonts. When we open the good or bad files in AutoCAD Lite in Virtual PC, the fonts simply map to Simplex. The text is simple, top level, text. No worksheets. No record formats. We use record formats in our titleblock, but in this case we converted the symbols to groups and ungrouped them to leave the text "exposed." The file that I exported via VW9 worked just fine. The consultant did not have any problems. Sarah

I am using VW10 in OSX 10.2.2. I exported a file as an AutoCAD r2000, and my consultants reported that all the text had disappeared. We opened the file ourselves in Virtual PC, and the consultants were right! No text. Not even text blocks. Exporting the file as r14: same thing. Exporting the file as r12: text is upside down and backwards. We resorted to recreating the file (luckily a simple titleblock) in VW9 and then exporting. Just fine (as we knew it would be). This is a bug -- a SERIOUS BUG!!! Sarah Sarnelli Jackson & Ryan Architects Houston, Texas

We have found OS 9 very stable, and we have few to no printing problems. OS X is another issue... Anyway, I agree with Katie that OS 9 is an important upgrade, and OS 9.2.2 is running just fine on *all* of our machines. Sarah

VulcanGrip, We have seen this problem in the past ONLY on our original G4 towers (purchased almost 2 years ago). We think it was a video memory issue (since you had to reboot to fix it). Not all of our G4 towers experienced it, but we though it was an OS or firmware issue. The machines are now running OS 9.2.1 or 9.2.2. I don't think we've seen the problem since pre OS 9. I don't remember which firmware version is installed. Which OS are you using? Sarah Sarnelli

Sorry, forgot to mention that we are running VW9.5 on the Mac. Sarah

A symbol contains primitive objects, group(s), and other symbol(s). Everything is on the same class. Run a saved sheet which does *not* have this class turned on. Now run the saved sheet that will bring up your symbol: only the group(s) and primitive objects display. Run the same saved sheet again, and the nested symbols appear. Bug!?! Sarah

Katie, The export/import solution to our missing layer problem seems to be working. Two teams have now done this, and their drawings are no longer corrupted; I have a third team exporting/importing this morning. It's a fix, but not a permanent one -- considering the first drawings exported/imported were pure VW9. Thanks for the help, and keep me posted on your progress with the drawings we sent you last week. Sarah P.S. -- In case anyone else has to do this, we have noticed that you have to *completely* break all the references to your drawing -- including deleting the referenced layers. Once you have exported/imported *all* of your drawings, you have to recreate all your referencing. Painful, but less painful than constant corruption!

Katie, I have just sent you four files for your use. Sorry for the delay; we had to wait for someone to return from a business trip. All of the files were created in VW Architect 9.0, and now are used in VW Architect 9.5. We are going to try the export/import on some of the files. Thanks. Sarah

Katie's 2.11.02 post: quote: ... or it's creating this extra corrupted layer....An alternative is to copy and paste the drawing into a new blank document, disregarding the offending layers that are mysteriously being created. We do not have mysterious layers appearing. We will try thr export/reimport option, though. Thanks. BTW: We are on a wholly Mac system. All of our computers are operating on OS9.2.1 except for three of us testing OS X. Sarah

I would say yes, except that we have several projects that have been entirely created in VW9 that have the problem.

Yes, we realize that referencing previous versions is not supported. That was the point of the first part of the posting. ALL of our files are on VW 9. The second part of the posting describes the problem. Thanks for your help!Sarah