Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!vsi1!ubvax!weitek!weitek.com!robert
From: robert@hemingway (Robert Plamondon)
Newsgroups: comp.windows.ms
Subject: Re: beware of Micrografx Designer 3.0!!!!
Message-ID: <1990Sep25.170549.24963@hemingway>
Date: 25 Sep 90 17:05:49 GMT
References: <615@ncratl.Atlanta.NCR.COM> <2365@lectroid.sw.stratus.com> <1990Sep20.114534.27982@pdn.paradyne.com> <1990Sep21.204055.6132@amd.com>
Reply-To: robert@hemingway.WEITEK.COM (Robert Plamondon)
Organization: WEITEK, Sunnyvale CA
Lines: 27

I had similar problems, and I cleverly called Micrografx Technical
Support.  They quickly traced the problem to my WIN.INI file; I had
kept my Windows 2.0 WIN.INI file and edited in the new 3.0 lines,
rather than letting Windows start over with a new WIN.INI.  This
causes mysterious problems.  I deleted my Windows directory structure
and reinstalled Windows (I wanted to be absolutely sure any weirdness
was gotten rid of).  Everything now works fine.

There's also a bug somewhere in Designer.  If I understand correctly,
somebody goofed and, rather than reading the TEMP environment
variable, refers to C:\TEMP explicitly somewhere in the program.
Some problems will apparently clear up if you create a C:\TEMP
directory and put:

set TEMP=C:\TEMP
set TMP=C:\TEMP

in your AUTOEXEC.BAT file.

Finally, if you have any problems, call Micrografx Technical Support!
They put the phone number on the first page of all their manuals.

	-- Robert

-- 
    Robert Plamondon
    robert@weitek.COM