Apache OpenOffice (AOO) Bugzilla – Issue 7455
Fatal error: vxd symvxd occurred while in Writer
Last modified: 2003-11-07 04:28:15 UTC
I have Windows 98SE and I downloaded the current version of Open Source, it loaded ok but after I started to use it I started to get " Fatal Error ... vxd symvxd ... ". Can anyone reproduce the error to supply a fix. I hope someone can give me answer as to what to do.
An error containing vxd may be telling you there is an error with your video driver. You might try visiting the website of your video card manufacturer, and attempt to obtain an updated video driver.
Hi Jeffrey, Thanx for submitting your issue. I am hoping that you found updated display drivers that will solve your issue. But if not, would it be possible for you to provide a little more information about your failure? Did you just load version 1.0.1? What platform are you using? Would it be possible for you to quote the entire error message that you received (or is that the entire error message that you quoted)? What part of OOo were you using when you received the error message? Are you able to reproduce the error on your system? If so, could you provide us with the steps you took to reproduce the error? Are you able to provide any data from any error logs on your system? Sorry to bombard you with so many questions, but perhaps we can provide some useful answers to you if we can get a bit more info about your circumstance. thanx, diane
Here is what I found out. The error containing " vxd symvxd " is caused by Nortons AntiVirus and/or any Nortons product (" sym " = Symantec). The information I found says to uninstall the program and then reinstall it under the Safe Mode screen. I am testing to see if I can or will get any error messages. I was considering on buying StarOffice to see if this would have corrected the problem. Does anyone if there are any templates like those in StarOffice? Win98 OO 1.0.1 Error occurred while in Writer
Hi Jeffrey, Thanx for the additional information. I saw the email that suggested that sym possibly means symantec. It was also prosed as a question. I have heard that sym could possibly mean symbol too. I have not found anything to substantially back that thought, but there are some emails out there in the newsgroups that point to that possibility as well. In my research I have also noticed that this error tends to be tied to users of Norton and win98, who are using html type docs. I am not sure whether this issue should be placed under the writer or the installation component. It also may not be an OOo issue, as I saw similar errors tied to other programs as well. I saw one suggestion to totally remove the Norton product, because its drivers sometimes interrupt the normal flow of data somehow. That may be another avenue to pursue. I do not have access to Norton, so I am not able to test any of these thoughts. Is it possible that a font change or something like that in Writer could have caused the error? Do you remember what you were doing in the Writer program when the error occurred? If the error is somehow tied to symbology, there could be a clue there. Admittedly, this issue is outside my field of knowledge, and I am not sure of the best way to direct it with the flags, so many of them have been left as they were when they arrived. I set the oooqa keywd. Hopefully others will review this and help this issue to find its proper path...I altered the summary slightly to add the description of the fatal error that you witnessed.
I have been trying to make the error come up after the reinstallation but so far all is working. I use Writer for word processing with no or very little graphics or html. If I do, the link it is done as a cut and paste and usually that of a web link.
That is a bonus! If all is ok for you now, should we close this issue? We may want to tie it to the installation component as well, because a reinstallation seems to have been the fix.
I agree. At least for now I would say OK. For now lets mark this as fixed.
Issue was appears to be fixed after a reinstallation.
Should have commented that I closed the issue in my previous entry. :)
closed.