Omega 3.0 Autocarve 3D error

[GB2]

I just reconfigured a computer with a new hard drive, a fresh installation of XP Pro with all updates including SP3 and a new installation of Omega 3.0/Autocarve 3D with SP1. This should be running fresh, clean and perfect, which it is except that on my first attempt to fire up my router, I opened a PLT file and tried to assign a prismatic toolpath and I keep getting this error message:

RNBOVDD.DLL. An installable Virtual Device Driver failed DLL initialization. Choose ‘Close’ to terminate the application.

It gives you the option to 'Close' or 'Ignore'. If you close then you get no toolpath and no functionality. I tried ignore and it seems as if it proceeds creating the toolpath but I have not tried outputting it. I should note here also that it only occurs when assigning a prismatic toolpath, it doesn't happen when assigning any 2D toolpaths. I'm doing this in conjunction with a motor replacement on the router so I need to be absolutely confident that there are no software issues to distort my trial run of the router repair.

From my initial research, it seems that that DLL file may be obsolete, has something to do with Virtual Machine and might be able to be removed or disabled but the information I have found is a bit inconsistent and conflicting. Does anyone have any insight into what issues I may have here?

 

[Techman]

given that the dll is properly installed,,,, check your registry entry for the virtual driver.. IF it is bad then make a new one..

 

[Tony Teveris]

Gary, check out

http://support.microsoft.com/default.aspx?scid=kb;EN-US;314452

RNBOVDD.DLL sounds like a Rainbow (now Sentinal) driver. I check one of my XP Pro systems that has Omega on it and it does not have this file anywhere so I'm no sure where it came from. I also performed an Prismatic tool path on that system with no errors. Check the above like and see if it helps.

 

[GB2]

I did see that support notice from Microsoft but I was a little leary of following that procedure without further inquiry because it was so old. I've installed SP3 on this XP OS so I wondered if that solution would still be valid. Do you think I should follow it?

I do have other software installed on this PC too. I have Enroute 4 for one and that operates with a Hasp key. Is it possible that file relates to that? I know you are not an Enroute tech, quite the oposite, but I am not familiar with these type of DLL issues, especially when they relate to those security keys that seem to plaque me all the time.

 

[Tony Teveris]

Let me check about the Hasp / SafeNet devices. Something "rings" a bell.