https://bugs.winehq.org/show_bug.cgi?id=42424
Bug ID: 42424
Summary: Error occurs while installing
Renesas_Flash_Programmer_Package_V30201_free.exe.
Product: Wine
Version: 2.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kiwamu(a)debian.or.jp
Distribution: ---
Created attachment 57250
--> https://bugs.winehq.org/attachment.cgi?id=57250
Screen shot when the error occurs
The issue is reproduced by following:
1. Download Renesas_Flash_Programmer_Package_V30201_free.exe from following:
https://www.renesas.com/ja-jp/software/D4000308.html
2. Run the Renesas_Flash_Programmer_Package_V30201_free.exe with following:
$ wine Renesas_Flash_Programmer_Package_V30201_free.exe
3. You should see attached screen shot named "shot.png".
Could you support this issue?
Best regards,
--
Kiwamu Okabe
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47588
Bug ID: 47588
Summary: AmiKitXE crashes on PlayOnLinux 4.3 with Wine
3.21-staging
Product: Wine-staging
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mortenweb43(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 64993
--> https://bugs.winehq.org/attachment.cgi?id=64993
AmiKitXE crashes on PlayOnLinux 4.3 with Wine 3.21-staging
AmiKitXE crashes on PlayOnLinux 4.3 with Wine 3.21-staging
Please help make it work again :-)
Error log is attached.
Thanks
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=41395
Bug ID: 41395
Summary: CreateFile returns a wrong LastError Code when you
pass an invalid path
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: Christoph(a)ApiViewer.de
Distribution: ---
CreateFile returns a wrong LastError Code when you pass an invalid path.
Testcase:
CreateFileA("C:C:\\Windows", GENERIC_READ, FILE_SHARE_READ,
NULL, OPEN_EXISTING, FILE_ATTRIBUTE_NORMAL, NULL);
todo_wine ok( GetLastError() == ERROR_INVALID_NAME, "Wrong LastError %d,
expected ERROR_INVALID_NAME\n", GetLastError() );
Which also means the code in cryptnet_main:1025 to line 1048 must be wrong.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=55332
Bug ID: 55332
Summary: 00d8:fixme:setupapi:CM_Get_Device_Interface_List_SizeW
000000000011F5B8 0000000180045FD8 (null) 0x00000000:
stub
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: usb
Assignee: wine-bugs(a)winehq.org
Reporter: alois.schloegl(a)gmail.com
Distribution: ---
Created attachment 74926
--> https://bugs.winehq.org/attachment.cgi?id=74926
log about trying to run "wine usbip.exe attach ..."
Trying to run
wine usbip.exe attach -r <USBIB_SERVER> -b 1-1.2.4.2
fails with the attached error. The same command on linux
usbip attach -r <USBIB_SERVER> -b 1-1.2.4.2
is working fine. In order to reproduce this, you need
- an usbip server running some linux with hostname or IP-ddress <USBIP-SERVER>,
with some usb-device attached,
- start the usbip deamon with this command:
usbipd -D
- check the busid of the usb device with
usbip list --local
- bind the usb device,
usbip bind --busid=1-1.2.4.2
This provides remote access (port 3240 by default).
Next you install usbip-win2 from
https://github.com/vadimgrn/usbip-win2/releases
in wine, and try to connect to the usbip server with
usbip list --remote=<USBIB_SERVER>
This should show the exported USB devices.
However, the command
wine usbip.exe attach -r <USBIB_SERVER> -b 1-1.2.4.2
will fail with the attached error.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34529
Bug #: 34529
Summary: Game attempts to create and read from root Z:\ drive
instead of C:\ (c_drive) directory.
Product: Wine
Version: 1.7.1
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: nemstar(a)zoho.com
Classification: Unclassified
When running the PC version of the game Shadowgun: Deadzone
(http://www.madfingergames.com/deadzone/) which is free to download and play,
I encounter a problem. The game is attempting to write to the root directory
which is the Z:\ drive by default in wine. It attempts to create a directory
named /users/<player name> with data files that pertain to the game. I know
this because I set up a test bed and used root and the directory /users/<player
name> and files within it were created successfully and the game ran as
intended.
If the Z:\ drive is removed using winecfg (as none root user) and the file is
placed or created in ~/.wine/c_drive/users/<player name>, then the game will
read the correct file on the C: drive and run as intended. If the Z:\ drive is
re-enabled, then the game will try to read from the root file system on Z: and
can not find /user/<player name> so it will not connect to a match or save
settings.
This is the case when ran as any user.
Obviously the game should not be trying to create a new directory under
C:\users in any circumstance, or as Z:\users if root is mounted as Z:\.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=55355
Bug ID: 55355
Summary: My Tally prime server application crashes after some
time
Product: Wine
Version: 6.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winsock
Assignee: wine-bugs(a)winehq.org
Reporter: vikasy.enjay(a)gmail.com
Distribution: ---
Following installation, the application launches when I run tallyserver.exe,
however after a while it fails and displays the message "Tallygateway server
not found" as seen below in the logs:
02d8:fixme:dbghelp_dwarf:dwarf2_parse_variable Unsupported constant (parameter)
"pEncodePara" in function
02d8:fixme:dbghelp_dwarf:dwarf2_parse_variable Unsupported constant (parameter)
"dwFlags" in function
02d8:fixme:dbghelp:MiniDumpWriteDump NIY MiniDumpWithHandleData
02d8:fixme:dbghelp:MiniDumpWriteDump NIY MiniDumpScanMemory
02d8:fixme:dbghelp:x86_64_fetch_minidump_module RunTime_Function outside
IMAGE_DIRECTORY_ENTRY_EXCEPTION unimplemented yet!
02d8:fixme:dbghelp:x86_64_fetch_minidump_module RunTime_Function outside
IMAGE_DIRECTORY_ENTRY_EXCEPTION unimplemented yet!
01dc:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFFFFFFFFFA,
000000000326EBD0
02e0:err:service:process_send_command service protocol error - failed to write
pipe!
02e8:err:service:process_send_command service protocol error - failed to write
pipe!
02f0:err:service:process_send_command service protocol error - failed to write
pipe!
0308:err:service:process_send_command service protocol error - failed to write
pipe!
0310:err:service:process_send_command service protocol error - failed to write
pipe!
0318:err:service:process_send_command service protocol error - failed to write
pipe!
0320:err:service:process_send_command service protocol error - failed to write
pipe!
0328:err:service:process_send_command service protocol error - failed to write
pipe!
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=55368
Bug ID: 55368
Summary: NtCreateFile broken for non-ASCII with RootDirectory
Product: Wine
Version: 8.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: novae.harpist06(a)icloud.com
Distribution: ---
Created attachment 74950
--> https://bugs.winehq.org/attachment.cgi?id=74950
Reproducer
Output on Windows:
00000000
Output on Wine:
C000003B
relevant logs with +file:
0114:trace:file:NtCreateFile handle=0x11fd38 access=00100001
name=L"\\??\\C:\\test" objattr=00000040 root=(nil) sec=(nil) io=0x11fd40
alloc_size=(nil) attr=00000080 sharing=00000003 disp=3 options=00204021
ea=(nil).0x00000000
0114:trace:file:nt_to_unix_file_name_no_root L"\\??\\C:\\test" ->
"/root/.wine/dosdevices/c:/test"
0114:trace:file:NtCreateFile handle=0x11fd18 access=c0110000 name=L"\0171.txt"
objattr=00000040 root=(nil) sec=(nil) io=0x11fd40 alloc_size=(nil)
attr=00000080 sharing=00000000 disp=3 options=00000020 ea=(nil).0x00000000
0114:warn:file:NtCreateFile L"\0171.txt" not found (c000003b)
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=55370
Bug ID: 55370
Summary: ddraw:ddraw4 - test_clipper_blt() sometimes gets an
unexpected bounding rect on Windows and Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
ddraw:ddraw4 - test_clipper_blt() sometimes gets an unexpected bounding rect in
Wine:
ddraw4.c:1115: Test failed: Got unexpected count 0.
ddraw4.c:1116: Test failed: Got unexpected bounding rect (0,0)-(0,0), expected
(18,41)-(642,482).
See https://test.winehq.org/data/patterns.html#ddraw:ddraw4
This is happening on both Windows and Wine and, so far, seems to only happen
during full WineTest runs:
* 2022-12-01 linux_lastestmaster
* 2022-12-03 linux_fgtb-debian11-wow32
* 2022-12-07 win81_newtb-w8
* 2023-01-07 linux_fgtb-debian11-wow32
* 2023-01-13 linux_fg-deb64-t32
* 2023-01-13 linux_fg-deb64-wow64
* 2023-02-02 linux_fgtb-debian11-win32
* 2023-02-11 linux_fgtb-debian11-win32
* 2023-02-28 linux_fgtb-debian11-win32
* 2023-04-13 win22H2_fgtb-w10pro64-rx550-64
* 2023-07-27 win81_newtb-w8
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=55369
Bug ID: 55369
Summary: Halo Online / Eldewrito - Dedicated Server errors and
fast upcount
Product: Wine
Version: 8.0.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bogdan17(a)garglob.com
Distribution: ---
When you run the DedicatedServer.bat in Wine, the bat files open in a Wine CMD
window and shows the following...
ElDewrito dedicated server is running! (xxxx)
Can't reconize 'timeout 10 / nobreak ' as an internal or external command, or
batch script
On Windows when you run the DedicatedServer.bat, command prompt will open up
and only display this...
ElDewrito dedicated server is running! (xxxx)
Also the (xxxx) in the brackets are an upcount, on Windows this upcount is slow
and seems to increase by 1 every 10 seconds, on Linux in Wine, it is counting
up raipidly fast.
How it looks in the terminal when I run DedicatedServer.bat and its output...
$ env WINEPREFIX="/path/to/wine/prefix/" "wine "C:\windows\command\start.exe"
/Unix "/path/to/wine/prefix/drive_c/HaloOnline/mods/server/DedicatedServer.bat"
002c:err:wineboot:process_run_key Error running cmd
L"C:\\windows\\system32\\winemenubuilder.exe -a -r" (2).
0074:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0074:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0074:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0074:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0074:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0074:fixme:xinput:pdo_pnp IRP_MN_QUERY_ID type 5, not implemented!
0074:fixme:xinput:pdo_pnp IRP_MN_QUERY_ID type 5, not implemented!
0074:fixme:xinput:pdo_pnp IRP_MN_QUERY_ID type 5, not implemented!
0074:fixme:xinput:pdo_pnp IRP_MN_QUERY_ID type 5, not implemented!
0024:fixme:exec:SHELL_execute flags ignored: 0x00000100
don@homepc:~$ 00e0:fixme:imm:ImeSetActiveContext (00010026, 0): stub
00e0:fixme:imm:ImmReleaseContext (00010020, 00010026): stub
00d8:fixme:imm:ImeSetActiveContext (00010052, 1): stub
00d8:fixme:imm:ImmReleaseContext (0002004A, 00010052): stub
And then the terminal spits out the following output over and over again at a
rapid pase...
012c:fixme:tasklist:wmain stub: L"tasklist" L"/v" L"/fi" L"IMAGENAME eq
eldorado.exe" L"/fi" L"STATUS eq Running"
0134:fixme:findstr:wmain stub: L"findstr" L"eldorado.exe"
013c:fixme:tasklist:wmain stub: L"tasklist" L"/v" L"/fi" L"IMAGENAME eq
eldorado.exe" L"/fi" L"STATUS eq Running"
0144:fixme:findstr:wmain stub: L"findstr" L"eldorado.exe"
014c:fixme:tasklist:wmain stub: L"tasklist" L"/v" L"/fi" L"IMAGENAME eq
eldorado.exe" L"/fi" L"STATUS eq Running"
012c:fixme:tasklist:wmain stub: L"tasklist" L"/v" L"/fi" L"IMAGENAME eq
eldorado.exe" L"/fi" L"STATUS eq Running"
0134:fixme:findstr:wmain stub: L"findstr" L"eldorado.exe"
013c:fixme:tasklist:wmain stub: L"tasklist" L"/v" L"/fi" L"IMAGENAME eq
eldorado.exe" L"/fi" L"STATUS eq Running"
0144:fixme:findstr:wmain stub: L"findstr" L"eldorado.exe"
014c:fixme:tasklist:wmain stub: L"tasklist" L"/v" L"/fi" L"IMAGENAME eq
eldorado.exe" L"/fi" L"STATUS eq Running"
012c:fixme:tasklist:wmain stub: L"tasklist" L"/v" L"/fi" L"IMAGENAME eq
eldorado.exe" L"/fi" L"STATUS eq Running"
0134:fixme:findstr:wmain stub: L"findstr" L"eldorado.exe"
013c:fixme:tasklist:wmain stub: L"tasklist" L"/v" L"/fi" L"IMAGENAME eq
eldorado.exe" L"/fi" L"STATUS eq Running"
0144:fixme:findstr:wmain stub: L"findstr" L"eldorado.exe"
014c:fixme:tasklist:wmain stub: L"tasklist" L"/v" L"/fi" L"IMAGENAME eq
eldorado.exe" L"/fi" L"STATUS eq Running"
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.