I'm trying to run the Ardis Cutting Optimizer under wine but it uses a Rainbow Sentinel driver to detect a parallel port dongle for copy protection. I have the dongle and I've installed the sentinel driver, but when I run wine COWIN.exe I get the following: fixme:vxd:VXD_Open Unknown/unsupported VxD L"sntnlusb.vxd". Try setting Windows version to 'nt40' or 'win32'. At that point the program pops up a window telling me that I need to install the sentinel driver. I've tried changing the version and it produces the same error. I've looked up the file and it's the usb sentinel driver, which shouldn't apply here, but it apparently checks for both usb and parallel. The other modules run just fine under wine, but without the primary executable, they won't work. Any ideas? Vince~ ____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs
>>>>> "Vince" == Vince <uberneen@yahoo.com> writes:Vince> I'm trying to run the Ardis Cutting Optimizer under wine but it Vince> uses a Rainbow Sentinel driver to detect a parallel port dongle Vince> for copy protection. I have the dongle and I've installed the Vince> sentinel driver, but when I run wine COWIN.exe I get the Vince> following: Vince> fixme:vxd:VXD_Open Unknown/unsupported VxD L"sntnlusb.vxd". Try Vince> setting Windows version to 'nt40' or 'win32'. Vince> At that point the program pops up a window telling me that I need Vince> to install the sentinel driver. Vince> I've tried changing the version and it produces the same error. Vince> I've looked up the file and it's the usb sentinel driver, which Vince> shouldn't apply here, but it apparently checks for both usb and Vince> parallel. The other modules run just fine under wine, but Vince> without the primary executable, they won't work. Wine can't load hardware drivers running in Ring 0. A .vxd or .sys needs to run in Ring 0 to access the Hardware. Either the programm also runs on win9x, without a driver doing direct hardware access, which wine can "emulate". Or you have a access to the driver interface definition and you reprogram it with unix means. However "sntnlusb.vxd" seems to do something USB related, not related to the parallel port access, so you are not even at the source of the problem. You will get to the next problem if you fake a successfull sntnlusb.vxd loading and then reply to all calls to sntnlusb.vxd in a way that the application gets told that there is no USB hardware. But these things are not for the faint harted Bye -- Uwe Bonnes bon@elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
Hello Vince, we've got the same problem with some of our applications using Sentinel SuperPro dongles. Our investigations showed, that there might be a way for running theses applications unter wine, as the sentinel dongle protection is technically realized as TCP/IP communication between the application and a "dongle server" (part of the dongle driver provided by safenet). Atleast for our applications the dongle server is the reason for all "evil". Safenet provides linux drivers (and daemons) for parallel port und USB dongle on thier web-site for download (http://www.safenet-inc.com/support/tech/sentinel.asp). As there is currently not support for RedHat Linux 4 we could not test this approach ourselves. But we beliefe, that this is a promissing approach. Maybe you've got more luck. Thomas>I was afraid something like that would be the case, >however I wasn't aware of the specifics. Right now we >have it on a windows server so I guess it will stay >there. >Thank you for the information. > >Vince~ > >> Wine can't load hardware drivers running in Ring 0. >> A .vxd or .sys needs to >> run in Ring 0 to access the Hardware. Either the >> programm also runs on >> win9x, without a driver doing direct hardware >> access, which wine can >> "emulate". Or you have a access to the driver >> interface definition and you >> reprogram it with unix means. >> However "sntnlusb.vxd" seems to do something USB >> related, not related to the >> parallel port access, so you are not even at the >> source of the problem. You >> will get to the next problem if you fake a >> successfull sntnlusb.vxd loading >> and then reply to all calls to sntnlusb.vxd in a way >> that the application >> gets told that there is no USB hardware. >> >> But these things are not for the faint harted >> >> Bye-- Dr. Thomas Serries LVM Versicherungen Abteilung DV-Infrastruktur Tel.: +49-251-702-2561 Fax: +49-251-702-99-2561 mailto: t.serries@lvm.de http://www.lvm.de