|
From: Peter on 7 May 2008 15:48 Hi, On WXP 64 installation of x64 driver from 32-bit utility fails with error 0x4a020 . This utility uses setupapi.lib functions and error code 0x4a020 is result of function: INetCfgClassSetup* -> Install(...) Is possible to install x64 driver from 32-bit app on Windows 64, or what do you recommend ? Peter
From: Gianluca Varenni on 7 May 2008 16:59 Actually, 0x0004a020 is not an error, it is #define NETCFG_S_REBOOT MAKE_HRESULT(SEVERITY_SUCCESS, FACILITY_ITF, 0xA020) and it means that you need to reboot in order for the changes to be effective. However, if I remember well, you need to use a 64bit application to install a network driver on a 64bit machine (but I might be wrong). Is the driver installed correctly after a reboot? Have a nice day GV -- Gianluca Varenni, Windows DDK MVP CACE Technologies http://www.cacetech.com "Peter" <Peter(a)discussions.microsoft.com> wrote in message news:510C2DB6-4586-4922-8800-8027CE5CAF29(a)microsoft.com... > Hi, > > On WXP 64 > installation of x64 driver from 32-bit utility fails with error 0x4a020 . > This utility uses setupapi.lib functions and error code 0x4a020 is result > of > function: > > INetCfgClassSetup* -> Install(...) > > Is possible to install x64 driver from 32-bit app on Windows 64, or what > do > you recommend ? > > Peter > >
From: Maxim S. Shatskih on 8 May 2008 05:09 > However, if I remember well, you need to use a 64bit application to install > a network driver on a 64bit machine (but I might be wrong). It is better to always do this way, not all important 64bit registry keys are mirrored to the 32bit registry space. -- Maxim Shatskih, Windows DDK MVP StorageCraft Corporation maxim(a)storagecraft.com http://www.storagecraft.com
From: Peter on 8 May 2008 07:06 Thank for answers, installation with 32-bit utility was not successful even restart was done. I built 64-bit utility for this and all is ok now. Peter "Maxim S. Shatskih" wrote: > > However, if I remember well, you need to use a 64bit application to install > > a network driver on a 64bit machine (but I might be wrong). > > It is better to always do this way, not all important 64bit registry keys are > mirrored to the 32bit registry space. > > -- > Maxim Shatskih, Windows DDK MVP > StorageCraft Corporation > maxim(a)storagecraft.com > http://www.storagecraft.com > >
|
Pages: 1 Prev: Accessing files on FAT32 partition at boot time Next: MiniportHalt() function |