Segmentation Violation for Drafting
 

I just had one of my users go through the "official" Win2K > WinXP transition process with his PC (Vectra VL420, 1.7GHz, 1GB RAM, ATI FireGL T2 graphics card). After the transition, he was able to load Modeling without error, but every time he launched Drafting, it would mostly load and then display the error dialog box:

*** SIGNAL RECEIVED: Segmentation Violation

Click OK, Drafting goes away and there is another dialog box on the desktop:

The instruction @ "0x018119d5 referenced memory @ 0x0000000c". The memory could not be read.

Same results after upgrading graphic drivers for the T2 card. He has no problems currently with OSD Modeling. Apparently there have been some technical problems with this OS transition process, enough to put the project on hold. So, last week, since this is a non-R&D box, our PC support subcontractor reimaged the box with XP. The user installed OSDD and voila!, it started working again. Now, today, he is back to the sigsegv error even after a reboot. We have not reinstalled the current drivers for the T2 card which I'm pretty sure were stepped on by the reimage.

Ideas?
__________________

John Westerman
MECAD/EECAD Productivity Engineering
Agilent Technologies - Spokane Site
1-509-921-3658

Re: Segmentation Violation for Drafting
 

Unfortunately, "segmentation violation" is a pretty generic error which can occur due to a lot of different reasons.

Which version of OSDD is this? Did you try to contact CoCreate support about this?

You might want to enable tracing in startup.m to find out how far OSDD gets while starting up before the crash occurs. This may give you some more clues on what to look for.

Claus

Re: Segmentation Violation for Drafting
 

Thanks for the quick reply Claus. This is v13.20A, the only version I have access to. Yes, I sent off an email to CoCreate support. I'll try the 'trace' option like you suggested in startup.m.

Re: Segmentation Violation for Drafting
 

It's pretty rare to see segmentation violations consistently during startup. My best guess would be something in the user configuration files which are automatically saved at exit and loaded at startup. You might try renaming this folder before starting Drafting to see if it helps.

C:\Documents and Settings\user_login\Application Data\CoCreate\ME10\13.20

Re: Segmentation Violation for Drafting
 

Hi,

I'm not sure if it is the solution for your problem, but we had a similar problem a while ago.
This was due to the installed printer driver, when we removed the printer from the system and re-installed it the problem went away.

I have seen this error on a number of occasions and all went away by re-installing the printers. But I haven't found what was wrong with the drivers.


Kind Regards,
John

Re: Segmentation Violation for Drafting
 

Great input, John! This reminds me that certain versions of OSDD indeed had problems on systems which did not have *any* printers installed. I don't recall if 13.20 was affected, but this is certainly something worth checking.

Claus

Re: Segmentation Violation for Drafting
 

Turns out it was a printer driver install as indicated by a post in the CoCreate User Forum. We uninstalled the driver he just loaded, then ran OSDD v13.20 succesfully. Reinstalled printer driver using Start > Run > \\wadm1\rdlj6 (not the wizard), reran OSDD v13.20A successfully. Rebooted, and ran OSDD v13.20A successfully. I can't think of any more ways to validate that it's fixed.

Thanks for the great advice!

Re: Segmentation Violation for Drafting
 

I also faced segmentation violation for drafting but everything was fine after changing the settings from the user menu.