i downloaded the subscription to 22/23 corel graphics suite (doesn't look much different than my X8) i thought the trace feature had been improved....looks and performs the same as my X8?
I don't think there is an actual problem with Xeon processors David, you just notice an apparent problem and log it in your head as being down to the processor, because that was the memorable difference to all other systems.
I have had more crashes (proportionally) with my new i10 processor than I had with the dual Xeon previously. Draw has just disappeared twice, gone, no trace. And this is the same version of Draw 2018, same workspace and the bugs that I logged against 2018 when I was beta testing are mostly still there in the trial of 2023 that I downloaded, including one that crashes the program reliably every time (so that bug was demonstrably not Xeon based, but you probably have it in your memory database as being due to the Xeon)
I have not tested i10 systems. What I did was keep a log of repeated issues and system/Draw re-install and AMD and Xeon lead the pack by a wide margin. In the case of Xeon due to so few systems it was way ahead of everyone else.
When I build a system I stay a bit down from latest generation gear.
I know that my clients using Xeon servers build systems that have $1,000 main boards, I suspect that CorelDRAW users do not. I've seen Xeon main boards for under $400, they can't be much.
The RIP software is running on the design machine due to the cost of building another box to just run RIP. The company I work for currently is a small Mom/Pop franchise sign shop in south Florida (I used to work for a much larger sign company until it changed hands due to the owner getting divorced). We don't have thousands to invest in IT equipment, so we make due with what we have and stretch our resources accordingly. In a perfect world, the RIP would be a purpose built machine that only did RIP, but we just cannot afford that luxury. Everything serves multiple purposes here, from computers and tools to work spaces and vehicles.
As far as why use Xeons... uptime, reliability, multitasking performance, higher memory capacity and ECC ram. That's why. I have a Xeon workstation at home that has had a 99.99% uptime for the last 15 years. I can count on one hand the number of times I have needed to reboot the machine over that time. I once had it hit 2 years of 100% constant uptime with me using it every single day for at least 5 hours per day...never needed a reboot, never crashed, never had any software issues. 2 bloody years being on and under heavy usage...no issues at ALL. You just cannot replicate that with an i-series non-ECC ram computer. You just can't. Also, my systems have gobs of RAM. The machine I am typing this on has 128GB ECC in quad channel (yes, I really do need that much RAM). The most I could slap on my i-9 VR rig is 64GB non-ECC (I was very dissappointed by that). Not even close to the same thing. Also, while single core performance may be a tick lower on a Xeon compared to an i-9, it's multicore performance leaves the i-9 in the dust. Most of my software is heavily multithreaded and benefits from the added cores and hyperthreading available on Xeons. Xeons also handles large files better since it has better memory handling. An average bus wrap nears 4 GB in size. Doing even a simple operation on a file that size is painful on an i-series, but on a xeon it slaps.
So, bottom line is that Xeons are superior for doing real work, while i-series are better for games and wasting time.
Glad to hear that. I still have CGS12 disk at home. I didn't think I would be able to install Trace to my Windows 11 machine. I wasn't looking forward to creating a Windows 7 virtual machine just to run Trace. I'll load it up tonight.
One thing I find its its a bit buggy, was even in WIn7, try to load your trace settings before loading the image, especially if its a big image. Then Trace and save trace result.
BTW when you come to save it the file name field will be blank, which is annoying, but if you just hit enter/save it will save as the image name but with a .cmx suffix. Be careful though as it will overwrite any file with the same name.