https://bugs.winehq.org/show_bug.cgi?id=45357
--- Comment #10 from Silvan s.jegen@gmail.com --- (In reply to Anastasius Focht from comment #8)
Hi Silvan
--- quote --- The program used to generate the machine-specific ID for Solid also crashes in Wine. I wonder if that indicates that getting the machine ID is what crashes our program in wine as well...
... Thanks for having a look. I sent you an email. --- quote ---
Thanks for the app. Easy one, I didn't even need to debug it.
--- snip --- $ WINEDEBUG=+seh,+relay wine ./SolidMachineID.exe >>log.txt 2>&1 ... 002e:Call KERNEL32.GetVolumeInformationA(004155e4 "C:\",0033fb90,00000104,0033fb78,00000000,00000000,00000000,00000000) ret=004017e0 002e:Ret KERNEL32.GetVolumeInformationA() retval=00000001 ret=004017e0 002e:Call KERNEL32.GetLastError() ret=004068f1 002e:Ret KERNEL32.GetLastError() retval=00000042 ret=004068f1 002e:Call KERNEL32.GetLastError() ret=004068f1 002e:Ret KERNEL32.GetLastError() retval=00000042 ret=004068f1 002e:Call ntdll.RtlAllocateHeap(00110000,00000000,00000018) ret=00404e86 002e:Ret ntdll.RtlAllocateHeap() retval=0015fbf8 ret=00404e86 002e:Call KERNEL32.RaiseException(e06d7363,00000001,00000003,0033fa88) ret=00403c96 002e:trace:seh:raise_exception code=e06d7363 flags=1 addr=0x7b446fba ip=7b446fba tid=002e 002e:trace:seh:raise_exception info[0]=19930520 002e:trace:seh:raise_exception info[1]=0033faa4 002e:trace:seh:raise_exception info[2]=00415cd8 002e:trace:seh:raise_exception eax=7b4356b1 ebx=0033fb44 ecx=00000000 edx=0033fa6c esi=0033fa6c edi=0033fa30 002e:trace:seh:raise_exception ebp=0033fa08 esp=0033f9a4 cs=330023 ds=33002b es=f7be002b fs=f7be0063 gs=f7be006b flags=00000212 002e:trace:seh:call_stack_handlers calling handler at 0x40fdef code=e06d7363 flags=1 002e:Call KERNEL32.GetLastError() ret=004068f1 ... 002e:Call KERNEL32.IsDebuggerPresent() ret=004055f4 002e:Ret KERNEL32.IsDebuggerPresent() retval=00000000 ret=004055f4 002e:Call KERNEL32.SetUnhandledExceptionFilter(00000000) ret=0040781d 002e:Ret KERNEL32.SetUnhandledExceptionFilter() retval=004065f2 ret=0040781d 002e:Call KERNEL32.UnhandledExceptionFilter(0033f158) ret=00407826 wine: Unhandled exception 0x40000015 in thread 2e at address 0x4065da (thread 002e), starting debugger... 002e:trace:seh:start_debugger Starting debugger "winedbg --auto 45 92" 002e:Ret KERNEL32.UnhandledExceptionFilter() retval=00000000 ret=00407826 002e:Call KERNEL32.GetModuleHandleExW(00000000,0041112c,0033f41c) ret=00404f17 002e:Ret KERNEL32.GetModuleHandleExW() retval=00000000 ret=00404f17 002e:Call KERNEL32.ExitProcess(00000003) ret=00404f4b --- snip ---
The app expects a non-empty serial number for drive 'C:' -> bug 17823
You could use Wine-Staging (prefix update!) or manually assign a serial in 'winecfg' to the virtual drive.
I used 'winecfg' to change the serial of C:\ to "78A1" which is half of the serial number that the command "vol C:" was showing me on my Windows dev machine. The "vol" command on my Windows dev machine returns "78A1-8192" which 'winecfg' truncates to only the part before the dash. Maybe dashes are not allowed there?
After that, the ID generating program worked fine, thanks for that!
Please check if it helps the main app too.
On the negative side, the main program still didn't work. I attached a new WINEDEBUG=+seh,+relay debug output.
When I used a Mac-specific license key on our Windows dev machine by mistake I didn't get some helpful warning but some kind of exception as well. I am now wondering if I just see the same happening in Wine.
Next I will try to generate a machine-ID-specific license for the machine ID that is returned in Wine and use that license to run the program. I will report my findings afterwards.