Cant open atBios

[Jānis Kangarooo]

Binary package hint: wine1.2

clean 10.10 xubuntu
installed wine
atBios dl from http://www.gigabyte.de/Support/Motherboard/HowToReflashBIOS.aspx
opened->extracted
in extrated folder setup.exe
error in picture

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: wine 1.1.42-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.35-9.14-generic 2.6.35-rc5
Uname: Linux 2.6.35-9-generic i686
Architecture: i386
Date: Wed Jul 21 00:06:56 2010
EcryptfsInUse: Yes
InstallationMedia: Xubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100701)
PackageArchitecture: all
ProcEnviron:
 LANG=lv_LV.utf8
 SHELL=/bin/bash
SourcePackage: wine1.2

[Jack Leigh (leighman)]

Created an attachment (id=29734)
Picture from OP

From https://bugs.edge.launchpad.net/ubuntu/+source/wine1.2/+bug/607970:

clean 10.10 xubuntu
installed wine
atBios dl from http://www.gigabyte.de/Support/Motherboard/HowToReflashBIOS.aspx
opened->extracted
in extrated folder setup.exe
error in picture

Not sure how wise it is to use a BIOS tool through wine but it may at least provide info about current version.
I can confirm this problem.
In the terminal I get:
err:ole:TLB_ReadTypeLib Loading of typelib L"C:\\Program Files\\Common Files\\InstallShield\\Professional\\RunTime\\IsProBE.tlb" failed with error 2
fixme:storage:create_storagefile Storage share mode not implemented.

[Jack Leigh (leighman)]

and:
err:ole:dispatch_rpc no apartment found for ipid {ffffffff-ffff-ffff-1e00-00001b000000}
err:rpc:I_RpcReceive we got fault packet with status 0x80010108
err:ole:dispatch_rpc no apartment found for ipid {ffffffff-ffff-ffff-1e00-00001b000000}
err:rpc:I_RpcReceive we got fault packet with status 0x80010108
when dismissing the error

[Arethusa26 (arethusa26)]

The installer is doing:

001c:Call KERNEL32.CreateFileA(00324f24 "\\\\.\\GIO",c0000000,00000001,00000000,00000003,00000080,00000000) ret=0a221173
001c:Ret KERNEL32.CreateFileA() retval=00000100 ret=0a221173
001c:Call KERNEL32.DeviceIoControl(00000100,c3502004,00324f70,00000020,00324f9c,00000004,00324f94,00000000) ret=0a2222d9
...
0028:Call ntdll.RtlInitUnicodeString(0053e69c,00540bde L"\\Device\\PhysicalMemory") ret=00540c66
0028:Ret ntdll.RtlInitUnicodeString() retval=0053e69c ret=00540c66
0028:Call ntdll.ZwOpenSection(0053e6d0,000f001f,0053e67c) ret=00540c96
0028:Ret ntdll.ZwOpenSection() retval=c0000034 ret=00540c96
0028:Ret driver dispatch 0x540388 (device=0x11a568,irp=0x53e768) retval=c000000d
001c:Ret KERNEL32.DeviceIoControl() retval=00000000 ret=0a2222d9
...
001c:trace:seh:raise_exception code=c0000005 flags=0 addr=0x9ff11ae ip=09ff11ae tid=001c
...

I imagine implementing the \Device\PhysicalMemory object is going to be hard, if not impossible.

[Jack Leigh (leighman)]

I don't think it's wise to use Wine for BIOS tasks but I've upstreamed the bug since I can confirm.
You can follow it at http://bugs.winehq.org/show_bug.cgi?id=23739

[Frédéric Delanoy (frederic-delanoy)]

Confirmed in 1.5.30, although it's probably unlikely to be fixed soon...

[Super-man-i (super-man-i)]

still fails 1.7.54

[Michael Müller (mqchael)]

Implementing \Device\PhysicalMemory is not so as hard as it might sound. Linux for example offers /dev/mem which is basically the same as \Device\PhysicalMemory. The problem is only that you need to have root rights in order to access this device. This is not really surprising as you can read the data of all mapped processes which is a major security risk. On Windows you also need admin rights in order to access \Device\PhysicalMemory. However, Wine is not intended to be run as root, so this is most probably not going to be implemented.

[Scott Ritchie (scottritchie)]

Closing ancient wine1.2 bugs

[Gijsvrm (gijsvrm)]

Still present in 6.15.

Adding stable download.

$ sha1sum motherboard_utility_gbttools_gbt_atbios.exe
03a137b1cef5ad1c37984672cde0dc46f5ef2e9e motherboard_utility_gbttools_gbt_atbios.exe

$ du -sh motherboard_utility_gbttools_gbt_atbios.exe
5.2M motherboard_utility_gbttools_gbt_atbios.exe