Full Version: Corel 10.0 Timing Prob
From: Mike (BIGPIXEL) [#1]
19 Jul 2006
To: ALL
I am having a problem with CorelDraw v10.0 on a PC running XP pro. I have plenty of processing power and RAM on this machine.
Occasionally when working on a file for a few minutes, I get a message that says Corel must shut down due to a timing error. I am not allowed to save the current state of any work open before Corel needs to be shut down.
No other programs I use are affected the same way. I routinely work in PhotoShop CS for hours at a time, no timing error.
What's going on and can I fix it?
Thanks
From: Stunt Engraver (DGL) [#2]
20 Jul 2006
To: ALL
Just bringing Mike's discussion back into view.
Anyone heard of of Corel 10 "Timing Error" ?
EDITED: 20 Jul 2006 by DGL
From: cindy (ROBERTM) [#3]
20 Jul 2006
To: Stunt Engraver (DGL) [#2] 20 Jul 2006
Yes, it use to happen to me on a regular basis. I have found that (I guess I'm right) it happens when I'm typing and clicking around faster than it has time to respond.
Hope this helps some.
Cindy
From: Stunt Engraver (DGL) [#4]
20 Jul 2006
To: cindy (ROBERTM) [#3] 20 Jul 2006
From Mike's description of his computer system, it sounds as if there's enough power, hard drive space and memory.
Seems like it would be difficult to outrun.
So, you actually got a "Timing Error" message on your monitor?
Thanks for the response.
From: cindy (ROBERTM) [#5]
20 Jul 2006
To: Stunt Engraver (DGL) [#4] 20 Jul 2006
Mine would say something like corel 10 has experenced a problem and will shut down. Any unsaved dated will be lost. Do you want to send a report to corel about this problem. Then it would have a box to check that said send report or end now.
Cindy
From: Mike (BIGPIXEL) [#6]
20 Jul 2006
To: cindy (ROBERTM) [#5] 20 Jul 2006
Thanks for the bump Dave.
Cindy/RobertM,
Yes, I got that message also.
I should mention that I also have version 9.0 on the same computer. When I received an OEM copy of 10.0 from a customer I decided not to overwrite 9.0, I have both 9.0 and 10.0 on the same computer. I haven't received this warning on 9.0 and so it must be a bug in 10 or perhaps Corel doesn't like having an older brother on the same machine. Conflict of some kind maybe..... Just wondering if there's a work around.
One thing I have done is to lower my 'auto save' to a 2 minute interval.
PS: One thing I do accidentally sometimes is scroll out beyond Corel's limits with the thumb wheel. I get a warning that I've exceded limits. Maybe this causes the crash.
Actually I wish there was a way to purge histories like in CS. That would free whatever buffer is getting choked....I think.
EDITED: 20 Jul 2006 by BIGPIXEL
From: laserman (MIKEMAC) [#7]
21 Jul 2006
To: Mike (BIGPIXEL) [#6] 24 Jul 2006
From: Pedaler (ROYBREWER) [#8]
23 Jul 2006
To: Mike (BIGPIXEL) [#1] 24 Jul 2006
I'm confirming what Laserman has suggested, but with a few warnings.
I don't recall ever having the "timing error" during the long time we worked with Corel 10; but, *all* problems I was having (including several that no one else ever had) were cleared after installing *both* patches.
Caution: many people had a lot of problems patching 10 (only 10, don't bother with the extra work below on newer or older Corel versions when patching).
The best way to avoid any problems when upgrading:
1. Shut the system completely down
2. Restart your PC
3. *immediately* run 1st patch (d10sp1en.exe)
4. *immediately* shut system completely down
5. *immediately* run 2nd patch (D10SP2.EXE)
Notes:
1. You'll have no fear of any issues if you follow these instructs recommended by the official Corel news group.
2. Numerous posters on the official Corel news group did not do this and never could get Corel 10 up & running again! Sometimes requiring complete re format of the hard disk.
3. Above patches are available on official Corel support web site.
4. For laser engravers still using Corel 10 (why anyone would be, I have no idea), the biggest reason to run these patches is to allow proper setting of line widths in inches.
5. The main reason for the above steps is to be sure *nothing* with the string "corel" is running in memory.
6. The experts are divided on whether both patches are really necessary; while I never took the time to confirm that patch two includes all the things corrected it patch one, I took the "JIC" approach.
From: Mike (BIGPIXEL) [#9]
31 Jul 2006
To: Pedaler (ROYBREWER) [#8] 1 Aug 2006