Hi, I use wine to run an application, the app needs to install a driver, but the app failed with following information. Would you please tell me the meaning of "..failed. Error code: 0x80070002". Thank you very much! Following is the end part of the error messages. ... CertMgr Succeeded Current full path - C:\windows\temp\~ndtmp~\ndisrd.inf Current miniport full path - C:\windows\temp\~ndtmp~\ndisrd_m.inf Trying to install 'nt_ndisrd'... ...C:\windows\temp\~ndtmp~\ndisrd.inf was copied to C:\windows\inf\oem0.inf ...C:\windows\temp\~ndtmp~\ndisrd_m.inf was copied to C:\windows\inf\oem1.inf fixme:advapi:CheckTokenMembership ((nil) 0x1220c8 0x33f1a4) stub! ..failed. Error code: 0x80070002
On 9/5/11 7:58 PM, pzr wrote:> Hi, I use wine to run an application, the app needs to install a driverWine cannot support Windows drivers and most likely will not. The questions I have are: What is the program name you are trying to install? What is the name of the product you are trying to install Windows drivers for? Thank you. James
The program is freegate 7.16, the app itself will install a driver of its own, not a hardware driver, maybe a network filter. Just now, I tried to put the app under directory drive_c, and starts the app use command: wine start 'C:\fg716p.exe' Seems no previous error, but the driver still can't be installed. Any idea? Following is the end part of the log. fixme:advapi:CheckTokenMembership ((nil) 0x129b38 0x33ec30) stub! fixme:crypt:CertAddEncodedCTLToStore (0x12ab60, 00010001, 0x460000, 1666, 00000004, (nil)): stub fixme:crypt:CertAddEncodedCTLToStore (0x12ab60, 00010001, 0x12b390, 1169, 00000004, (nil)): stub fixme:crypt:CertEnumCTLsInStore (0x12ab60, (nil)): stub fixme:crypt:CertEnumCTLsInStore (0x12af40, (nil)): stub fixme:advapi:CheckTokenMembership ((nil) 0x122130 0x33f1a4) stub!
Would you please tell me use which command to gather entire log? More information, the app shows a dialog to reboot Windows after it finished the installation. I don't know how to make wine to reboot. Is this the possilble reason?
I checked just now. On Windows, the application can put a .sys file under windows\system32\drivers before the appearing of the dialog to reboot the Windows. So, on wine, maybe issues exist.
On Mon, Sep 5, 2011 at 9:33 PM, pzr <wineforum-user at winehq.org> wrote:> I checked just now. On Windows, the application can put a .sys file under windows\system32\drivers before the appearing of > the dialog to reboot the Windows. So, on wine, maybe issues exist.This is a Windows driver file and Wine cannot support them. James