Letters from the VisualCADD User’s Forum:

 

This section of the Visual CADD Group’s WEB site is devoted to the publication of letters of mutual interest copied from the VisualCADD Forum.  Letters are published at the discretion of the WEB Master.  Content may be edited for punctuation, spelling and grammar.  Political, religious or slanderous comments will not be published.  Only letters with a valid e-mail return address will be published. 

 

This is not a forum so; if you have a comment about an e-letter published here, please write to the originator.

 

 Disclaimer:

The Visual CADD Group assumes no liability for the content herein.  Opinions expressed are those of the submitters and not necessarily The Visual CADD Group.

---

SUBJECT: Visual CADD backwards compatibility

 

---

From: Carl Thomas [mailto:crlthomasjr@sbcglobal.net]

Sent: Tuesday, July 20, 2004 02:54 PM

To: visualcadd@yahoogroups.com

Subject: Past to Present

 

Hi All:

 

I just had the pleasure to go into my archive vault to find and replace a set of drawings for a customer done in 1987 with Generic CADD 1.x.  Found them, changed *.DWG to *.GCD loaded them into Visual CADD 15 minutes editing and faxed the new copies to the customer.  Got a phone call from customer telling me I was the only vender able to respond with usable drawings not excuses.

 

Another unsolicited testimonial for Visual CADD.

 

Best regards,

Carl L. Thomas, Jr.

 

From: Matt Pobursky  [mailto:vcadduser@mps-design.com]

Sent: Tuesday, July 20, 2004 05:05 PM

To: visualcadd@yahoogroups.com

Subject: Re: Past to Present

 

A few years ago, a long time client of mine had their building burn to the ground.  They lost everything, including all their "fireproof" storage and, of course, they didn't have all their data in off-site storage.  They called me and asked for "anything you have" on a major military project I'd done for them about 5 years previous -- they just had gotten a new order and had virtually no documentation to produce it!  Thankfully, I had made copies of *all* their Ottocad mechanical component/assembly drawings and converted to Generic CADD for my own use as working drawings.  I also had all the electronic hardware and software design files safely archived away.  I converted the mechanical drawings back to .dwg and .dxf files using Visual CADD then I made them a CDROM of everything I had and delivered it that day.

 

They were astonished.  I had delivered everything except a few electronic manufacturing process drawings required to completely build and test the units.  I didn't ask them for any money and wished them well on their recovery from the fire.

 

That Christmas I received a $1000 check in the mail from them with a nice card thanking me for being so helpful.

 

So... it pays to backup your data and it pays to use Visual CADD (well, that's my opinion at least ;-))

 

Matt Pobursky

Maximum Performance Systems

---

 

SUBJECT: Visual CADD crashes when attempting to print

---

 

-----Original Message-----

From: Bob Morrison [mailto:bob@rlmorrisonengr.com]

Sent: Friday, July 30, 2004 01:05 PM

To: visualcadd@yahoogroups.com; visualcadd@yahoogroups.com

Subject: Re: Crashes when trying to print

 

At 08:27 PM 7/29/2004, David Lee wrote:

This printer/system crash problem comes up every month or so.  For the benefit of all users, please post a detailed explanation of the problem and the fix so that I can post it on the group's WEB site.

 

David:

 

The problem occurs when a person goes to print and VCADD crashes.  The cause is a corrupted "Presets.cfg" file.  This file can get corrupted through normal use or if a person regularly adds and removes printers from their system.  Older operating systems (Win 95/98) seem more prone to this problem than Win2K or Win XP.  However, the latter are not immune.

 

The solution is to delete the "presets.cfg" file or restore an older version of the file from a backup.  This is one of those files that is customized by the user.  Like the menu files and toolbar and tool.pal files, it is a good idea to keep backups of known "good" versions.  Then one simply has to restore the good version by overwriting the corrupt version.

 

Short of keeping a backup, the next best option is to close VCADD, delete the "Presets.cfg" file which is located in the "[drive:] \ [VCadd path] \Programs" older.  When the user next opens VCADD a new "Presets.cfg" will be created.

 

BTW, this problem occasionally arises with VC5 as well.  It seems to have more to do with the operating system than with VCADD itself.  For example, I run Win2K and have had a problem with this file only once and that was because I had changed some printers that are on a network.  The network path to the printers got goofed up and VCADD crashed.  The simple solution was to delete "Presets.cfg" and start over again with known printers and known network paths.

 

Finally, you can edit the "Presets.cfg" file with a text editor, but you better make certain you know what you are doing.  Making a backup before editing is always a good idea.

 

Does that help?

 

 

 

Bob Morrison

Vice President Visual Cadd Group (VCG)

R L Morrison Engineering Co

Structural and Civil Engineering

Poulsbo WA

---

SUBJECT: Recommended Visual CADD files to backup

---