[Bug 35009] New: Hoshizora no Memoria:"falid open" Dialog after exit

Bug #: 35009 Summary: Hoshizora no Memoria:"falid open" Dialog after exit Product: Wine Version: 1.7.6 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: hibi.sasahara@gmail.com Classification: Unclassified

Created attachment 46664 --> http://bugs.winehq.org/attachment.cgi?id=46664 terminal output

Hoshizora no Memoria(星空のメモリア) is Novel game.

Start menu press "Game start" to start playing story. the scene change, upon dialog to file open error. 「grash_bs/CHR_夢_幼少のオープンに失敗しました」 (meaning: failure open to "grash_bs/CHR_夢_幼少") and exit window and this application.

Free trial version to: http://www.favo-soft.jp/soft/trial/Hoshimemo_Trial.zip sha1sum: 647b9938bac7ad871b19d768f38a82a59a3d24a8 I confirmed that the same error appeared.

note: AppDB is http://appdb.winehq.org/objectManager.php?sClass=application&iId=15676

This game used Retail novel game engine "FAVORITE VIEW POINT SYSTEM". (source(japanese) http://ja.wikipedia.org/wiki/%E3%82%A2%E3%83%88%E3%83%AA%E3%82%A8%E3%81%8B%E...)

Same game engine use game studio "FAVORITE" and "AtorieKaguya P-ch"(アトリエかぐや P-ch) FAVORITE use this game engine all product.

I confirmed that the same error appeared to "Irotoridori no Sekai(いろとりどりのセカイ) WORLD'S END COMPLETE" is latest FAVORITE product. (Free frial version to: http://www.favo-soft.jp/soft/product/world/download/Iroseka_trial.zip sha1sum: c9d127fc96009e8490f45eb3adf7d577e0c56ac6 )

Default is text drawing and other motion very slow, not bug. Debug playing recommend Ctrl key press repeat, fast playing.

When game engine is not top window to become drawing stops. is default, not bug. :)

-- 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.

Show replies by date

wine-bugs＠winehq.org

28 Nov 28 Nov

4:04 p.m.

New subject: [Bug 35009] Hoshizora no Memoria:"falid open" Dialog after exit

hibi.sasahara@gmail.com changed:

wine-bugs＠winehq.org

4:09 p.m.

New subject: [Bug 35009] Hoshizora no Memoria:"falid open" Dialog after exit

hibi.sasahara@gmail.com changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |hibi.sasahara@gmail.com

wine-bugs＠winehq.org

4:22 p.m.

New subject: [Bug 35009] Hoshizora no Memoria:"falid open" Dialog after exit

hibi.sasahara@gmail.com changed:

--- Comment #1 from hibi.sasahara@gmail.com 2013-11-28 10:22:02 CST --- Created attachment 46665 --> http://bugs.winehq.org/attachment.cgi?id=46665 terminal output (winedbg)

46664: terminal output is no "winedbg". This is winedbg out.

wine-bugs＠winehq.org

2 Dec 2 Dec

8:45 p.m.

New subject: [Bug 35009] Hoshizora no Memoria:"falid open" Dialog after exit

--- Comment #2 from Austin English austinenglish@gmail.com 2013-12-02 14:45:08 CST ---

libGL error: failed to load driver: vboxvideo libGL error: Try again with LIBGL_DEBUG=verbose for more details. fixme:d3d:wined3d_guess_card No card selector available for card vendor 0000 (using GL_RENDERER "Gallium 0.4 on llvmpipe (LLVM 3.3, 128 bits)").

can you try on real hardware?

wine-bugs＠winehq.org

10:10 p.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open <invalid path>" dialog after scene change

Anastasius Focht focht@gmx.net changed:

--- Comment #3 from Anastasius Focht focht@gmx.net 2013-12-02 16:10:35 CST --- Hello folks,

the demo has no installer (just unpack). You have to use 'LANG=ja_JP.UTF-8' if non-Japanese default locale.

Paths passed to winmm.mmioOpenA() are indeed strange ... Often an invalid or even garbage path is passed in (letting the first call fail):

--- snip --- $ LANG=ja_JP.UTF-8 WINEDEBUG=+tid,+seh,+relay wine ./Memoria.exe >>log.txt 2>&1 ... 0024:Call KERNEL32.lstrcpyA(007a864d,005997c8 "Z:/home/focht/Downloads/install") ret=0043cb17 0024:Ret KERNEL32.lstrcpyA() retval=007a864d ret=0043cb17 0024:Call KERNEL32.lstrcatA(007a864d "Z:/home/focht/Downloads/install",00457c04 "/") ret=0043cb25 0024:Ret KERNEL32.lstrcatA() retval=007a864d ret=0043cb25 0024:Call KERNEL32.lstrcatA(007a864d "Z:/home/focht/Downloads/install/",005bed88 "graph_bs/CHR_\x96\xb2_\x97c\x8f\xad") ret=0043cb29 0024:Ret KERNEL32.lstrcatA() retval=007a864d ret=0043cb29 0024:Call winmm.mmioOpenA(007a864d "Z:/home/focht/Downloads/install/graph_bs/CHR_\x96\xb2_\x97c\x8f\xad",00000000,00000000) ret=0043cb34 0024:Call ntdll.RtlAllocateHeap(00110000,00000008,00000058) ret=7e80a7c4 0024:Ret ntdll.RtlAllocateHeap() retval=01a3c4a0 ret=7e80a7c4 0024:Call KERNEL32.OpenFile(007a864d "Z:/home/focht/Downloads/install/graph_bs/CHR_\x96\xb2_\x97c\x8f\xad",0033f668,00000000) ret=7e809c94 0024:Ret KERNEL32.OpenFile() retval=ffffffff ret=7e809c94 0024:Call KERNEL32._llseek(ffffffff,00000000,00000001) ret=7e809da5 0024:Ret KERNEL32._llseek() retval=ffffffff ret=7e809da5 0024:Call ntdll.RtlFreeHeap(00110000,00000000,01a3c4a0) ret=7e80a8dd 0024:Ret ntdll.RtlFreeHeap() retval=00000001 ret=7e80a8dd 0024:Ret winmm.mmioOpenA() retval=00000000 ret=0043cb34 ... --- snip ---

Not sure if there is any purpose behind this because another attempt following the (internal) failure succeeds:

--- snip --- ... 0024:Call KERNEL32.lstrcpyA(007a7938,0033f98c "graph_bs.bin") ret=0043cc39 0024:Ret KERNEL32.lstrcpyA() retval=007a7938 ret=0043cc39 0024:Call KERNEL32.lstrcpyA(007a864d,005997c8 "Z:/home/focht/Downloads/install") ret=0043cc49 0024:Ret KERNEL32.lstrcpyA() retval=007a864d ret=0043cc49 0024:Call KERNEL32.lstrcatA(007a864d "Z:/home/focht/Downloads/install",00457c04 "/") ret=0043cc57 0024:Ret KERNEL32.lstrcatA() retval=007a864d ret=0043cc57 0024:Call KERNEL32.lstrcatA(007a864d "Z:/home/focht/Downloads/install/",0033f98c "graph_bs.bin") ret=0043cc5f 0024:Ret KERNEL32.lstrcatA() retval=007a864d ret=0043cc5f 0024:Call winmm.mmioOpenA(007a864d "Z:/home/focht/Downloads/install/graph_bs.bin",00000000,00000000) ret=0043cc6a 0024:Call ntdll.RtlAllocateHeap(00110000,00000008,00000058) ret=7e80a7c4 0024:Ret ntdll.RtlAllocateHeap() retval=01a3c4a0 ret=7e80a7c4 0024:Call KERNEL32.OpenFile(007a864d "Z:/home/focht/Downloads/install/graph_bs.bin",0033f668,00000000) ret=7e809c94 0024:Ret KERNEL32.OpenFile() retval=00000218 ret=7e809c94 0024:Call KERNEL32._llseek(00000218,00000000,00000001) ret=7e809da5 0024:Ret KERNEL32._llseek() retval=00000000 ret=7e809da5 0024:Call KERNEL32._llseek(00000218,00000000,00000002) ret=7e809d82 0024:Ret KERNEL32._llseek() retval=0545747b ret=7e809d82 0024:Call KERNEL32._llseek(00000218,00000000,00000000) ret=7e809da5 0024:Ret KERNEL32._llseek() retval=00000000 ret=7e809da5 0024:Ret winmm.mmioOpenA() retval=000001b6 ret=0043cc6a 0024:Call winmm.mmioRead(000001b6,007a792c,00000004) ret=0043ccc8 0024:Call KERNEL32._lread(00000218,007a792c,00000004) ret=7e809cf8 0024:Ret KERNEL32._lread() retval=00000004 ret=7e809cf8 0024:Ret winmm.mmioRead() retval=00000004 ret=0043ccc8 0024:Call winmm.mmioRead(000001b6,007a7930,00000004) ret=0043ccd5 0024:Call KERNEL32._lread(00000218,007a7930,00000004) ret=7e809cf8 0024:Ret KERNEL32._lread() retval=00000004 ret=7e809cf8 0024:Ret winmm.mmioRead() retval=00000004 ret=0043ccd5 ... 0024:Call winmm.mmioClose(000001b6,00000000) ret=0043cd34 0024:Call KERNEL32._lclose(00000218) ret=7e809cd0 0024:Ret KERNEL32._lclose() retval=00000000 ret=7e809cd0 0024:Call ntdll.RtlFreeHeap(00110000,00000000,01a3c4a0) ret=7e80a8dd 0024:Ret ntdll.RtlFreeHeap() retval=00000001 ret=7e80a8dd 0024:Ret winmm.mmioClose() retval=00000000 ret=0043cd34 --- snip ---

This happens several times during gameplay without any reported failure/exception. Prior to the point of exception the scheme is similar.

Point of failure:

--- snip --- 0024:Call user32.wvsprintfA(012cd5d0,00458534 "%s\x82\xcc\x83I\x81[\x83v\x83\x93\x82\xc9\x8e\xb8\x94s\x82\xb5\x82\xdc\x82\xb5\x82\xbd",0033fb9c) ret=004205a6 0024:Ret user32.wvsprintfA() retval=0000002c ret=004205a6 0024:Call KERNEL32.RaiseException(e06d7363,00000001,00000003,0033fb84) ret=00442caa 0024:trace:seh:raise_exception code=e06d7363 flags=1 addr=0x7b83a8ef ip=7b83a8ef tid=0024 0024:trace:seh:raise_exception info[0]=19930520 0024:trace:seh:raise_exception info[1]=0033fbac 0024:trace:seh:raise_exception info[2]=00468404 0024:trace:seh:raise_exception eax=7b826921 ebx=7b8ba000 ecx=19930520 edx=0033fac4 esi=0033fb70 edi=0033fb30 0024:trace:seh:raise_exception ebp=0033fb08 esp=0033faa4 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00000283 --- snip ---

Besides this 'second-try' scheme there is no obvious problem in trace log (that would explain why it bails here).

Did you really verify that the demo runs successfully in Windows (I have no access to full version)?

$ sha1sum Hoshimemo_Trial.zip 647b9938bac7ad871b19d768f38a82a59a3d24a8 Hoshimemo_Trial.zip

$ du -sh Hoshimemo_Trial.zip 596M Hoshimemo_Trial.zip

$ wine --version wine-1.7.7-262-g30a3e9c

Regards

wine-bugs＠winehq.org

10:59 p.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open <invalid path>" dialog after scene change

--- Comment #4 from hibi.sasahara@gmail.com 2013-12-02 16:59:13 CST --- Created attachment 46706 --> http://bugs.winehq.org/attachment.cgi?id=46706 logfile on real machine.

Yes, play on real machine. But "terminal output" file is guest Ubuntu on Virtualbox4.3 .

New attachment file is take my real machine. command: LANG=ja_JP.UTF-8 wine ./Memoria.exe >>realMachineLog.txt 2>&1 (trial version. wine version to change 1.7.6 to 1.7.7(ubuntu/ppa))

wine-bugs＠winehq.org

3 Dec 3 Dec

11:11 a.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open <invalid path>" dialog after scene change

hibi.sasahara@gmail.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Version|1.7.6 |1.7.7

--- Comment #5 from hibi.sasahara@gmail.com 2013-12-03 05:11:25 CST ---

You have to use 'LANG=ja_JP.UTF-8' if non-Japanese default locale.

I use default locale is Japanese.

Testing change locale $LANG=C wine ./Memoria.exe >>langCLog.txt 2>&1" happen dialog and exit. title is "(character corruption)A-Wish upon a shooti(disappear text)" message is"graph/main_window(character corruption)"

Did you really verify that the demo runs successfully in Windows (I have no access to full version)?

Yes, demo runs succesfully, in Windows7 Home Premium x64 Service Pack 1. (I checked it after your post. sorry.) Playing story and visit opning movie. (some skipping after point of failure.) I have retail package full version (by "COMPLETE EDITION"). I came across this failure for the first time in retail version and on WINE.

$ sha1sum Hoshimemo_Trial.zip 647b9938bac7ad871b19d768f38a82a59a3d24a8 Hoshimemo_Trial.zip

$ du -sh Hoshimemo_Trial.zip 596M Hoshimemo_Trial.zip

$ wine --version wine-1.7.7-262-g30a3e9c

I (re)check now,

$ sha1sum Hoshimemo_Trial.zip 647b9938bac7ad871b19d768f38a82a59a3d24a8 Hoshimemo_Trial.zip

$ du -sh Hoshimemo_Trial.zip 596M Hoshimemo_Trial.zip

$ wine --version wine-1.7.7

Thanks.

wine-bugs＠winehq.org

5:05 p.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open <invalid path>" dialog after scene change

Sagawa sagawa.aki+winebugs@gmail.com changed:

--- Comment #6 from Sagawa sagawa.aki+winebugs@gmail.com 2013-12-03 11:05:14 CST --- Thanks for reporting. I also confirmed the issue.

wine-bugs＠winehq.org

10:23 p.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open <invalid path>" dialog after scene change

http://msdn.microsoft.com/en-us/library/windows/desktop/ms647489%28v=vs.85%2...

--- Comment #7 from Anastasius Focht focht@gmx.net 2013-12-03 16:23:13 CST --- Hello folks,

I think this is another case of incompatibility between Wine's use of unicode.org and Microsoft collation tables.

The culprit is a string array lookup/comparison loop where the app uses lstrcmpiA() which of doesn't work correctly for Wine if you pass in japanese character strings.

string2 (argument on stack, passed in):

--- snip --- Address Hex dump ASCII 0033FA90 43 48 52 5F|96 B2 5F 97|63 8F AD 00|00 00 00 00| CHR_–²_—c --- snip ---

It tries the following string1 values before giving up (I just cut the hexdump at the NULL terminator):

--- snip --- Address Hex dump ASCII 00640341 43 48 52 5F|90 E7 94 67|5F 8A EC 5F|83 70 83 57| CHR_ç”g_Šì_ƒpƒW 00640351 83 83 83 7D|4C 5F 95 5C|8F EE 00 ƒƒƒ}L_•\î --- snip ---

--- snip --- Address Hex dump ASCII 00640C0B 43 48 52 5F|91 8D 88 EA|98 4E 5F 8A|EE 5F 83 47| CHR_‘ˆê˜N_Šî_ƒG 00640C1B 83 76 83 8D|83 93 00 ƒvƒƒ“ --- snip ---

--- snip --- Address Hex dump ASCII 00640643 43 48 52 5F|90 E7 94 67|5F 8A EE 5F|89 C4 8E 84| CHR_ç”g_Šî_‰ÄŽ„ 00640653 95 9E 5F 90|81 8F 6F 52|5F 95 5C 8F|EE 00 •ž_oR_•\î --- snip ---

--- snip --- Address Hex dump ASCII 00640735 43 48 52 5F|90 E7 94 67|5F 94 DF 5F|83 70 83 57| CHR_ç”g_”ß_ƒpƒW 00640745 83 83 83 7D|5F 95 5C 8F|EE 00 ƒƒƒ}_•\î --- snip ---

--- snip --- Address Hex dump ASCII 006407A8 43 48 52 5F|90 E7 94 67|5F 94 DF 5F|89 C4 8E 84| CHR_ç”g_”ß_‰ÄŽ„ 006407B8 95 9E 5F 90|81 8F 6F 4C|5F 95 5C 8F|EE 00 •ž_oL_•\î --- snip ---

If the comparison results in equality (=0) it bails out to a code path which indicates "found" to caller. If the comparison returns >= it tweaks the lookup to search another array range.

(0x90,0x96) = -1 (0x91,0x96) = 1 (0x90,0x96) = -1 ...

Not sure why the authors chose to use lstrcmpiA() when even MSDN states:

--- quote --- For some locales, the lstrcmpi function may be insufficient. If this occurs, use CompareString to ensure proper comparison. For example, in Japan call with the NORM_IGNORECASE, NORM_IGNOREKANATYPE, and NORM_IGNOREWIDTH values to achieve the most appropriate non-exact string comparison. The NORM_IGNOREKANATYPE and NORM_IGNOREWIDTH values are ignored in non-Asian locales, so you can set these values for all locales and be guaranteed to have a culturally correct "insensitive" sorting regardless of the locale. Note that specifying these values slows performance, so use them only when necessary. --- quote ---

If you want to debug it: the loop starts at 0x0043CD55, lstrcmpiA() at 0x0043CD7E.

So you might hook to one of the already existing lstrcmpi/CompareStringA/W bugs.

Regards

wine-bugs＠winehq.org

7 Dec 7 Dec

4:24 a.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open <invalid path>" dialog after scene change

--- Comment #8 from hibi.sasahara@gmail.com 2013-12-06 22:24:49 CST --- Created attachment 46770 --> http://bugs.winehq.org/attachment.cgi?id=46770 New logfile.

$ wine ./Memoria.exe >~/MemoriaLog.txt 2>&1 Ubuntu 13.10 amd64, Wine1.7.7 from ubuntu-ppa.

in "logfile on real machine."

fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)

is ~/.wine directory erase miss. (I use "$ rm -rf ~/.wine/*" but find "$ ls -a ~/.wine/" remaining file '.update-timestamp'.)

wine-bugs＠winehq.org

4:38 a.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open <invalid path>" dialog after scene change

--- Comment #9 from hibi.sasahara@gmail.com 2013-12-06 22:38:08 CST --- Created attachment 46771 --> http://bugs.winehq.org/attachment.cgi?id=46771 change to no japanese path.

"New logfile", change to path name.

$ wine ./Memoria.exe >~/MemoriaLog_noJpPath.txt 2>&1 Ubuntu 13.10 amd64, Wine1.7.7 from ubuntu-ppa.

$ cd /home/hibi/rep/ $ mv 星空のメモリア　プロローグ体験版/ hoshimemo_trial

Change to last line.

fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet

but window closing issue is not change.

wine-bugs＠winehq.org

1:58 p.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open <invalid path>" dialog after scene change

--- Comment #10 from Anastasius Focht focht@gmx.net 2013-12-07 07:58:09 CST --- Hello folks,

not sure if you have read/understood my comment #7 ... There is no need to further attach output and/or trying to interpret terminal messages. They are harmless and have nothing to do with the actual problem.

The issue has been identified and it will probably take some time (months, maybe years) to resolve that. Check all the other unicode/collation related bugs for reference.

Regards

wine-bugs＠winehq.org

2:33 p.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open <invalid path>" dialog after scene change

--- Comment #11 from hibi.sasahara@gmail.com 2013-12-07 08:33:08 CST --- Dear Anastasius Focht. Thank you reply.

My mind excitement and hurried. I am very sorry that my language and skills are poor.

wine-bugs＠winehq.org

10 Sep 10 Sep

12:58 p.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open <invalid path>" dialog after scene change

hibi.sasahara@gmail.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Version|1.7.7 |1.7.50

-- 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.

wine-bugs＠winehq.org

16 Aug 16 Aug

2:32 p.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open < invalid path>" dialog after scene change

zaplo00@mailfence.com changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |zaplo00@mailfence.com

-- 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.

wine-bugs＠winehq.org

20 Aug 20 Aug

1:02 a.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open < invalid path>" dialog after scene change

Fabian Maurer dark.shadow4@web.de changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de

--- Comment #12 from Fabian Maurer dark.shadow4@web.de --- Download link is dead. Is this still an issue with current wine? If so, mind adding a working link?

-- 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.

wine-bugs＠winehq.org

1:01 p.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open < invalid path>" dialog after scene change

hibi.sasahara@gmail.com changed:

-- 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.

wine-bugs＠winehq.org

1:05 p.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open < invalid path>" dialog after scene change

--- Comment #13 from hibi.sasahara@gmail.com --- Official Download link is dead.

other download link: http://holyseal.homeip.net:8000/mirror2/favorite/hoshizoranomemoia/20090227t... in http://holyseal.net/cgi-bin/mlistview.cgi?prdcode=8187 and links: http://eroge.jp/demo/favorite/

-- 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.

wine-bugs＠winehq.org

5:31 p.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open < invalid path>" dialog after scene change

--- Comment #14 from zaplo00@mailfence.com --- This is still an issue. I did some testing in windows 8.1, with JP non-unicode locale.

I put conditional breakpoint to loop at 0x0043CD7E to break when something starting CHR_ is tested (so it happens only at error place). Before them are these:

CMP: &"BG054_020" and &"BG033_021b" CMP: &"BG040_110" and &"BG033_021b" CMP: &"BG037_010b" and &"BG033_021b" CMP: &"BG034_010b" and &"BG033_021b" CMP: &"BG033_021b" and &"BG033_021b"

Then it tries different values against str2 (CHR_夢_幼少)

1. 079DA017 43 48 52 5F 90 E1 8D D8 5F 8A EC 5F 93 7E 90 A7 CHR_雪菜_喜_冬制 079DA027 95 9E 4C 5F 95 5C 8F EE 00 服L_表情

2. 079DA544 43 48 52 5F 94 F2 92 B9 5F 8A EE 5F 90 85 92 85 CHR_飛鳥_基_水着 00

3. 079D8CBD 43 48 52 5F 96 BE 93 FA 95 E0 5F 8A EE 5F 83 81 CHR_明日歩_基_メ 079D8CCD 83 43 83 68 95 9E 00 イド服

4. 079D85B3 43 48 52 5F 96 B2 5F 94 DF 5F 83 70 83 57 83 83 CHR_夢_悲_パジャ 079D85C3 83 7D 4C 5F 95 5C 8F EE 00 マL_表情

5. 079E8AFF 43 48 52 5F 96 BE 93 FA 95 E0 5F 8A EC 5F 89 C4 CHR_明日歩_喜_夏 079E8B0F 90 A7 95 9E 5F 90 81 8F 6F 4C 00 制服_吹出L

6. 079D8932 43 48 52 5F 96 BE 93 FA 95 E0 5F 8A EC 5F 83 81 CHR_明日歩_喜_メ 079D8942 83 43 83 68 95 9E 4C 00 イド服L

7. 079D8550 43 48 52 5F 96 B2 5F 97 63 8F AD 00 CHR_夢_幼少

So seventh one is match and then it starts looking for different things without failure:

str1 079EA017 43 48 52 5F 90 E1 8D D8 5F 8A EC 5F 93 7E 90 A7 CHR_雪菜_喜_冬制 079EA027 95 9E 4C 5F 95 5C 8F EE 00 服L_表情

str 2 0018FC18 43 48 52 5F 96 B2 5F 97 63 8F AD 5F 95 5C 8F EE CHR_夢_幼少_表情

-- 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.

wine-bugs＠winehq.org

21 Aug 21 Aug

4:14 p.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open < invalid path>" dialog after scene change

--- Comment #15 from zaplo00@mailfence.com --- Wine compares against str2

0033FA80 43 48 52 5F 96 B2 5F 97 63 8F AD 00 CHR_夢_幼少

these strings:

005E9F5F 43 48 52 5F 90 E1 8D D8 5F 8A EC 5F 93 7E 90 A7 CHR_雪菜_喜_冬制 005E9F6F 95 9E 4C 5F 95 5C 8F EE 00 服L_表情

005E726C 43 48 52 5F 82 B1 82 E0 82 E0 5F 94 DF 5F 9B DE CHR_こもも_悲_巫 005E727C 8F 97 95 9E 00 女服

005E982A 43 48 52 5F 88 DF 97 E9 5F 8A EE 5F 93 7E 8E 84 CHR_衣鈴_基_冬私 005E983A 95 9E 5F 95 5C 8F EE 00 服_表情

005E970C 43 48 52 5F 88 DF 97 E9 5F 8A EC 5F 89 C4 8E 84 CHR_衣鈴_喜_夏私 005E971C 95 9E 5F 90 81 8F 6F 52 5F 95 5C 8F EE 00 服_吹出R_表情

005E74DC 43 48 52 5F 83 81 83 41 5F 8A EE 5F 8E 80 90 5F CHR_メア_基_死神 005E74EC 83 4A 83 7D 4C 00 カマL

005E7623 43 48 52 5F 83 81 83 41 5F 94 DF 5F 8E 80 90 5F CHR_メア_悲_死神 005E7633 83 4A 83 7D 5F 95 5C 8F EE 00 カマ_表情

005E764E 43 48 52 5F 83 8C 83 93 5F 8A EE 5F 8E 80 90 5F CHR_レン_基_死神 005E765E 4C 00 L

005E96BC 43 48 52 5F 88 DF 97 E9 5F 8A EC 5F 89 C4 8E 84 CHR_衣鈴_喜_夏私 005E96CC 95 9E 5F 90 81 8F 6F 4C 00 服_吹出L

005E7660 43 48 52 5F 83 8C 83 93 5F 8A EE 5F 8E 80 90 5F CHR_レン_基_死神 005E7670 4C 5F 95 5C 8F EE 00 L_表情

10.

005E967C 43 48 52 5F 88 DF 97 E9 5F 8A EC 5F 89 C4 8E 84 CHR_衣鈴_喜_夏私 005E968C 95 9E 00 服

Then shows error popup.

-- 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.

wine-bugs＠winehq.org

23 Aug 23 Aug

3:34 p.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open < invalid path>" dialog after scene change

--- Comment #16 from zaplo00@mailfence.com --- Wine fails in first of these compares in 0x0043CD7E, windows returns -1 but wine returns 1.

CompareStringA(0x411, 0x1, CHR_雪菜_喜_冬制服L_表情, -1, CHR_夢_幼少, -1)

-- 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.

wine-bugs＠winehq.org

3:45 p.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open < invalid path>" dialog after scene change

--- Comment #17 from zaplo00@mailfence.com --- Created attachment 59006 --> https://bugs.winehq.org/attachment.cgi?id=59006 test program

Returns 1 on windows 3 in wine

-- 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.

wine-bugs＠winehq.org

25 Aug 25 Aug

8:45 a.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open < invalid path>" dialog after scene change

--- Comment #18 from zaplo00@mailfence.com --- If you use comparestring.cpp from other bug it shows sortkey is wrong.

str1 0x96EA, str2 0x5922

(win 8.1) locale is 0x411 CompareStringW: string1 is less lstrcmpW: string1 is less LCMapStringW result: 7 0xca 0x92 0x1 0x1 0x1 0x1 0x0

char: 0x96ea, sortkeys: 0xca 0x92 0x1 0x1 0x1 0x1 0x0 char: 0x0, sortkeys: 0x1 0x1 0x1 0x1 0x0

(wine) locale is 0x411 CompareStringW: string1 is greater lstrcmpW: string1 is greater LCMapStringW result: 9 0xff 0xfe 0x96 0xea 0x1 0x1 0x1 0x1 0x0

char: 0x96ea, sortkeys: 0xff 0xfe 0x96 0xea 0x1 0x1 0x1 0x1 0x0 char: 0x0, sortkeys: 0x1 0x1 0x1 0x1 0x0

-- 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.

wine-bugs＠winehq.org

9:22 a.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open < invalid path>" dialog after scene change

https://www.microsoft.com/en-us/download/confirmation.aspx?id=1175

--- Comment #19 from zaplo00@mailfence.com --- Maybe this table is of help? It contains these characters which fail.

Won't be updating this anymore, or it will become too spammy.

-- 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.

wine-bugs＠winehq.org

30 Dec 30 Dec

12:50 p.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open < invalid path>" dialog after scene change

--- Comment #20 from zaplo00@mailfence.com --- This bug happens in wine 3.0-rc4

-- 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.

wine-bugs＠winehq.org

12 May 12 May

3:53 p.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open < invalid path>" dialog after scene change

--- Comment #21 from zaplo00@mailfence.com --- Still happens in wine 3.7, this patchset (not committed as of today) does not help either https://source.winehq.org/patches/data/144624

-- 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.

wine-bugs＠winehq.org

13 May 13 May

1:58 p.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open < invalid path>" dialog after scene change

tokktokk fdsfgs@krutt.org changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |fdsfgs@krutt.org

-- 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.

wine-bugs＠winehq.org

10 Jul 10 Jul

5:32 p.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open < invalid path>" dialog after scene change

--- Comment #22 from zaplo00@mailfence.com --- Just a little heads up, wine 3.11 with update to unicode 11 doesn't help. Compare is still broken.

-- 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.

wine-bugs＠winehq.org

24 Jan 24 Jan

9:33 p.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open < invalid path>" dialog after scene change

--- Comment #23 from zaplo00@mt2015.com --- wine 4.0-rc7 it doesn't work. I beg you, please do look at the possible causes. Thank you very much for your attention.

-- 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.

wine-bugs＠winehq.org

9 Feb 9 Feb

10:58 a.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open < invalid path>" dialog after scene change

--- Comment #24 from Rafał Mużyło galtgendo@o2.pl --- (In reply to zaplo00 from comment #23)

wine 4.0-rc7 it doesn't work. I beg you, please do look at the possible causes. Thank you very much for your attention.

See bug 10767 - begging is not enough, a correct solution of the problem is far from trivial.

-- 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.

WineHQ Bugzilla

8 Jan 8 Jan

2:17 a.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open <invalid path>" dialog after scene change

--- Comment #25 from Fabian Maurer dark.shadow4@web.de --- Still relevant as of wine(-staging)-5.0rc4 Their latest title has the same issue: http://suezou.dyndns.org/dl2018/favorite/sakuramoyu/Sakuramoyu_trial_v101.zi...

-- 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.

WineHQ Bugzilla

13 Feb 13 Feb

2:28 p.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open <invalid path>" dialog after scene change

--- Comment #26 from Fabian Maurer dark.shadow4@web.de --- I'm currently working on a proper solution for this. Just need to get it upstreamed, which will probably take some time still.

-- 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.

WineHQ Bugzilla

14 Feb 14 Feb

8:08 p.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open <invalid path>" dialog after scene change

--- Comment #27 from zaplo00@mt2015.com --- (In reply to Fabian Maurer from comment #26)

I'm currently working on a proper solution for this. Just need to get it upstreamed, which will probably take some time still.

This is the best message I've seen in few years, and also created a donation to wine foundation ^^.

-- 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.

WineHQ Bugzilla

16 Feb 16 Feb

3:13 p.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open <invalid path>" dialog after scene change

--- Comment #28 from hibi.sasahara@gmail.com --- Thank you good post. I need try, but ubuntu wine repository is broken... I setup a wine build environment later and try.

-- 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.

WineHQ Bugzilla

7:25 p.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open <invalid path>" dialog after scene change

--- Comment #29 from Fabian Maurer dark.shadow4@web.de --- Try what exactly? There is nothing to try, the full patchset is not public yet.

-- 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.

WineHQ Bugzilla

17 Feb 17 Feb

12:57 p.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open <invalid path>" dialog after scene change

--- Comment #30 from hibi.sasahara@gmail.com --- ow... Thanks I am looking forward to it.

-- 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.

WineHQ Bugzilla

27 Feb 27 Feb

9:30 p.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open <invalid path>" dialog after scene change

--- Comment #31 from zaplo00@mt2015.com --- (In reply to Fabian Maurer from comment #29)

Try what exactly? There is nothing to try, the full patchset is not public yet.

Was the problem that windows has custom code pages?

-- 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.

WineHQ Bugzilla

9:42 p.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open <invalid path>" dialog after scene change

--- Comment #32 from Fabian Maurer dark.shadow4@web.de --- Not really, the problem is that windows sorts unicode different from the official unicode standard. Still waiting for my patch to be reviewed.

-- 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.

WineHQ Bugzilla

4 Aug 4 Aug

6:37 a.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open <invalid path>" dialog after scene change

joaopa jeremielapuree@yahoo.fr changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr

--- Comment #33 from joaopa jeremielapuree@yahoo.fr --- Fabian, any news for your patch?

-- 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.

WineHQ Bugzilla

5:49 p.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open <invalid path>" dialog after scene change

--- Comment #34 from Fabian Maurer dark.shadow4@web.de --- I've reworked it a few times and then got pretty busy with work. I'll come back to working on it in a few days, I hope. Not sure when it's ready to send in though, it's pretty complex.

-- 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.

WineHQ Bugzilla

16 Jan 16 Jan

2:12 p.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open <invalid path>" dialog after scene change

--- Comment #35 from Fabian Maurer dark.shadow4@web.de --- Essentially the same reason as bug 10767 - different collation tables. This should be fixed in staging, can you retest please? Also, should we merge those bugs?

-- 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.

WineHQ Bugzilla

29 Mar 29 Mar

6:40 a.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open <invalid path>" dialog after scene change

Harold felineswift+wine@gmail.com changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |felineswift+wine@gmail.com

--- Comment #36 from Harold felineswift+wine@gmail.com --- (In reply to Fabian Maurer from comment #35)

Essentially the same reason as bug 10767 - different collation tables. This should be fixed in staging, can you retest please? Also, should we merge those bugs?

Can confirm the bug is fixed in wine-staging 6.5

-- 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.

WineHQ Bugzilla

2 Jan 2 Jan

9:01 p.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open <invalid path>" dialog after scene change

Fabian Maurer dark.shadow4@web.de changed:

--- Comment #37 from Fabian Maurer dark.shadow4@web.de --- Marking dupe.

*** This bug has been marked as a duplicate of bug 10767 ***

-- 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.

WineHQ Bugzilla

4 Jan 4 Jan

12:15 a.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open <invalid path>" dialog after scene change

https://web.archive.org/web/20101222035026/http://suezou.dyndns.org/dl2009/f...

Anastasius Focht focht@gmx.net changed:

--- Comment #38 from Anastasius Focht focht@gmx.net --- Hello folks,

adding stable download links via Internet Archive for documentation.

$ sha1sum Hoshimemo_Trial.zip 647b9938bac7ad871b19d768f38a82a59a3d24a8 Hoshimemo_Trial.zip

$ du -sh Hoshimemo_Trial.zip 596M Hoshimemo_Trial.zip

====

https://web.archive.org/web/20200110095131/http://suezou.dyndns.org/dl2018/f...

$ sha1sum Sakuramoyu_trial_v101.zip 3c3bc5aadb305e2fe12e2c5f20bbcd237aa0403d Sakuramoyu_trial_v101.zip

$ du -sh Sakuramoyu_trial_v101.zip 2.0G Sakuramoyu_trial_v101.zip

Regards

-- 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.

WineHQ Bugzilla

5 Jan 5 Jan

7:12 a.m.

New subject: [Bug 35009] Hoshizora no Memoria (visual novel) shows "failure to open <invalid path>" dialog after scene change