Page 1 of 1

How To - Install Corel Draw Plugin

Posted: Mon Mar 04, 2019
by Gene Uselman
How to install RDWORKS Corell Plugin.pdf
For use of CorelDraw x8 and RDWORKS 8.01.19 (or Later) you will need to create a missing
folder called GMS. Previous versions of CorelDraw have this folder but CorelDraw x8 does not
include it.

Go to
C:\Program Files\Corel\CorelDRAW Graphics Suite X8\Draw
and make a new folder: GMS
Then install RDWORKS as normal.
---------------------
Post by Alexis Tzoulis » Sat Nov 12, 2016 11:24 am
I have created a color palette for corel draw x8 witch supports the 20 colors of rdworks v8.01.19 .
To install it go to: Window -> Color Palettes -> Open Palette
RDworks_color_palette.xml

Re: How To - Install Corel Draw Plugin

Posted: Wed Jan 01, 2020
by Dave Vigness
Gene,

Having a bit of trouble with the macro install into CorelDraw 2017. It has the GMS directory, and RDWorks thinks it's installing correctly. But when Corel starts it gives out a Visual Basic error for the RDWorks plug in saying 'Object not found in collection'. Any thoughts? I have plug ins for other programs and they installed and function no problem. Installing RDWorks V8.01.00-191015

Re: How To - Install Corel Draw Plugin

Posted: Sat May 02, 2020
by Dave Vigness
UPDATE :

It is a problem between Corel and RDWorks. If I rename the gms file, Corel boots up with no errors. Wit the gms put back, I get the error. I do not get this on the other three computers, and all were installed, both Corel and RDWorks, from the same files.

Hooeson over on the Reddit lasercutting page posted a 'fix', but it's not working for me... go figure. Is there any way to open / edit a gms file so I could tweak it and maybe get rid of my error?

Re: How To - Install Corel Draw Plugin

Posted: Sun May 03, 2020
by Gene Uselman
Hi Dave- I have never used Corel personally- I think the post was done after we were recovering as much of the old forum after it was vandalized/deleted. I tried to attribute the original posts but I guess I did not on this one.

Re: How To - Install Corel Draw Plugin

Posted: Sun May 03, 2020
by Pete Cyr
Dave Vigness wrote: Sat May 02, 2020 UPDATE :

It is a problem between Corel and RDWorks. If I rename the gms file, Corel boots up with no errors. Wit the gms put back, I get the error. I do not get this on the other three computers, and all were installed, both Corel and RDWorks, from the same files.

Hooeson over on the Reddit lasercutting page posted a 'fix', but it's not working for me... go figure. Is there any way to open / edit a gms file so I could tweak it and maybe get rid of my error?
viewtopic.php?f=104&t=3720&hilit=remove+rdworks

go to link above - remove RDWORKS as shown in youtube vid - reinstall

Re: How To - Install Corel Draw Plugin

Posted: Sun May 03, 2020
by Dave Vigness
I don't believe it's a before and after thing. I had the original Corel and single RDWorks, I think it was a .29, installed. Installed the bad copy of .44, installed the good copy of .38 from Russ, Installed the good copy of .41 from Ruida, and then installed five more copies of .41 after you told I had to do it that way to open 'multiple' windows. All through it I've had the same problem.

I'm not sure if it's the gms or the dll though. The guy on Reddit says he's installed his fix on several computers with no problem. I installed just his gms and still have the problem. Going to install his dll and give that a try. Failing that I'll go for the .40 with his fix.

The thing that bugs me is that the same copy of .41 and Corel are installed on three other computers with no problem. I have two 32 bit and two 64 bit, all running Win7. But this computer is the only one that is giving me problems. And it's not that the macro doesn't' work, it works just fine. It's just the annoying little pop up because the MVB is throwing a tantrum it can't find what it wants. And it's typical Microsoft, throw a tantrum but not give any real clue a normal human could understand what it's problem is.

I've installed and removed enough programs on this computer that I'm hoping a corrupted dll is the problem. Will try and find time to delve into it later. Will let you guys know.