Importing 2005 LT Hatch Patterns to 2007 LT

[jstorrie]

I just upgraded to 2007 Lt from 2005 LT. I followed the migration process for the upgrade, but my hatch patterns for 2005 LT (aclt.pat & acltiso.pat) did not cross over. I need these because there are some custom hatching patterns included in these.

I noticed that the 2007 LT files are named differently (acadlt.pat & acadltiso.pat).

When I upgraded from 2002 LT to 2005 LT, all i had to do was open the files with notepad and merge them together.

I do not want to attempt this at this point because of the different file names.

Will merging them this way hurt? Is there another way to import them so that they can be used?

Thanks

[Mike.Perry]

Hi

Try the following...

* Make back-up copies of your custom AutoCAD LT 2005 Hatch Pattern files - aclt.pat & acltiso.pat

* Make back-up copies of your original AutoCAD LT 2007 Hatch Pattern files - acadlt.pat & acadltiso.pat

* Now rename your custom AutoCAD LT 2005 Hatch Pattern files aclt.pat & acltiso.pat to acadlt.pat & acadltiso.pat respectively.

* Place the newly created ( renamed ) Hatch Pattern files in your AutoCAD LT 2007 Support Search Path.

Do they work ?

Did your original AutoCAD LT 2005 Hatch Pattern files contain the following text in their headers...


;; Note: in order to ease migration of this file when upgrading
;; to a future version of AutoCAD, it is recommended that you add
;; your customizations to the User Defined Hatch Patterns section at the
;; end of this file.Does your original AutoCAD LT 2007 Hatch Pattern files contain the above text in their headers...

Have a good one, Mike

[jstorrie]

Mike,

Thank you for the reply.

I did as you instructed, it worked for one exception. When I go to select a hatch pattern from "Other Predefined Patterns" I get two error messages, both saying "Error in Pattern File".

Two patterns show up blank on the palette. I checked the coding and compared it to the original file coding and they are the same. For some reason 2005 reads it, but 2007 doesn't.

Any thoughts on this? The two that are coming up as an error are two of the ones that I needed.

Also, in answer to your question on the migration note - it does appear.

John

[hugh.69031]

Check the patterns to make sure every line is terminated with a carriage return and linefeed pair (hex 0d 0a) - or post the custom patterns as an attachment.

Hugh Adamson
Cadro Pty Ltd
www.cadro.com.au/hatchkit (http://www.cadro.com.au/hatchkit)

[jstorrie]

Hugh,

Not being that adept at deciphering the coding for the hatch patterns, I decided to defer to your expertise.

Here are the two hatch patterns in question:

*bricks,Grouted bricks
0, 0,0, .25,.2, .47,-.03
0, 0,.17, .25,.2, .47,-.03
90, 0,0, .2,.25, .17,-.23
90, -.03,0, .2,.25, .17,-.23

*endcedar,Cedar shake with ends shown
0, 0,0, 1,.2, 1
0, 0,.02, 1,.2, 1
90, 0,0, 1,1, .2,-.4,.2,-.2
90, .05,.4, 1,1, .2,-.2,.2,-.4
90, .1,.2, 1,1, .2,-.2,.2,-.4
90, .15,0, 1,1, .2,-.8
90, .2,.2, 1,1, .2,-.4,.2,-.2
90, .25,0, 1,1, .2,-.2,.2,-.4
90, .3,.6, 1,1, .2,-.8
90, .35,.2, 1,1, .2,-.4,.2,-.2
90, .4,0, 1,1, .2,-.2,.2,-.4
90, .45,.2, 1,1, .2,-.2,.2,-.4
90, .5,.4, 1,1, .2,-.2,.2,-.4
90, .55,0, 1,1, .2,-.8
90, .6,.2, 1,1, .2,-.4,.2,-.2
90, .65,0, 1,1, .2,-.4,.2,-.2
90, .7,.4, 1,1, .2,-.8
90, .75,.2, 1,1, .2,-.2,.2,-.4
90, .8,.4, 1,1, .2,-.2,.2,-.4
90, .85,0, 1,1, .2,-.4,.2,-.2
90, .9,.4, 1,1, .2,-.2,.2,-.4
90, .95,.2, 1,1, .2,-.8

I could not discern any difference between how these ended and the others that worked. They all ended with a small "square" character which did not copy over on the above.

Thank you for your reply and help on this.

John

[hugh.69031]

Cutting and pasting text can sometimes fix line termination problems :) (There's an "Attach Files" feature in the "Additional Options" panel just below the "Reply to Thread" panel if you want to upload a file as an attachment).

I suggest you make a backup copy of acadlt.pat, then delete the two patterns. Test the two attached custom hatch pattern files by copying them to a directory that is on the Support Files Search Path (Tools/Options) and test both in a new drawing.

If they prove ok, add them to the end of your acadlt.pat, move them out of the Support Files Search Path and test again.

hth
Hugh Adamson
Cadro Pty Ltd
www.cadro.com.au/hatchkit/ (http://www.cadro.com.au/hatchkit/)

[jstorrie]

I followed your instructions and now the "endcedar" shows up and works within the program. Unfortunately I am still not having any luck with "bricks". Not sure why.

Do you have any other suggestions?

Thank you for your help.

[Mike.Perry]

Hi

If possible, post your custom acadlt.pat & acadltiso.pat files here in this thread, we can then take a look at the issue / problem first-hand...

Have a good one, Mike

[hugh.69031]

Select either the Quote or Post Reply buttons to gain access to the Attach Files functionality in the Additional Options box.


Hugh Adamson
Cadro Pty Ltd
www.cadro.com.au/hatchkit/ (http://www.cadro.com.au/hatchkit/)

[jstorrie]

Thanks Guys,

Here is the acadlt.pat file that is currently running.

[Mike.Perry]

Here is the acadlt.pat file that is currently running.Hi

Ok! I carried out the following tasks...

* Downloaded the above ZIP file ( acadlt.zip ).

* Extracted file acadlt.pat

* Renamed acadlt.apt to acad.pat ( just so I could use it within AutoCAD, I do not have access to AutoCAD LT ).

* acad.pat loaded without a problem.

* Was able to successful use all Hatch Patterns defined within ( including bricks,Grouted bricks ).

Therefore I was unable to recreate the problem you are currently experiencing at your end.

What happens when you try to use Hatch Pattern bricks,Grouted bricks ?

Do you receive any ( error ) message(s) when loading / using acadlt.pat ?

Give the attached file a try. I have cleaned up acadlt.pat a little ( removed duplicate Hatch Pattern definitions ).

Have a good one, Mike

[hugh.69031]

John,

The file you posted contains two versions of the standard hatch patterns (SOLID through to ZIGZAG) followed by some custom patterns. This could be the result of adding a customised earlier version of ACAD.PAT or ACLT.PAT to the end of a newer version, going on the copyright dates shown in each portion.

The lines within the first set of standard hatch patterns were teminated with CRLF pairs (DOS mode) and those in the remainder of the file were terminated with LF characters only (UNIX mode).

I'm a bit of a fan of the PSPad editor which can readily convert line termination modes. Open the file with PSPad then click in the box at the bottom of the window that displays DOS, UNIX or MAC depending on the current line terminator mode setting. Save the file when it shows the mode you want (which I suspect should be DOS).

Link to PSPad: http://www.pspad.com/en/

(PsPAD has a hex file display function to view these normally invisible characters, a visual file compare, and quite a lot more to tempt you away from Notepad.)

hth
Hugh Adamson
Cadro Pty Ltd
www.cadro.com.au/hatchkit/ (http://www.cadro.com.au/hatchkit/)

[jstorrie]

Thank you both for help and advice. My problem now stands corrected and I am once again fully functional. Although a small issue it was very aggravating, once your use to having something it's hard to do without. Thanks again.

[basport]

I upgraded from AutoCAD 2006 to 2007, and I am having the exact same problem. Let me know if you figured something out. I have several custom hatch patterns that are giving me the "error in pattern file" as well. It would be not be good if I had to go in and edit code in the acad.pat file. (It might take awhile)
We have two other CAD users that upgraded as well, and this part of the migration went just fine for them. The only difference when we loaded 2007 is that they chose the standard upgrade, and I chose the custom upgrade. We selected all the same features, but I wonder if this had anything to do with it??? Did you do the standard upgrade or the custom upgrade?

Thanks in advance.

[jstorrie]

I followed the standard upgrading procedures. My issue occurred with two of my pattern files.

I followed what Hugh and Mike had suggested and got one to work right away, the second did not until I downloaded the program Hugh had suggested and followed his suggestion on converting it through it.Make sure you reboot and restart the program though, mine didn't change until I did that.

Good Luck.