Win7 x64
mint4win from Maya 13 Cinnamon 64-bit DVD starts (it is only 32-bit app anyway), I can see it in task manager & then without any error or GUI it just exits
Anybody seen this?
sebus
mint4win starts & then instantly exits on W7 x64
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
mint4win starts & then instantly exits on W7 x64
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Re: mint4win starts & then instantly exits on W7 x64
your description is short.... have you tried to boot the cdrom ? have you used torrent to get the iso ?
Re: mint4win starts & then instantly exits on W7 x64
Sorry, but what difference would getting the linuxmint-13-cinnamon-dvd-64bit.iso via BT would make when downloaded iso is true (correct hash of e0f3dbee947630d1eada01a3583d3b96 , as per http://www.linuxmint.com/edition.php?id=106 )
Boot & install from DVD works perfectly fine
It is only mint4win that does NOT run correctly
On http://www.linuxmint.com/download.php
for Cinnamon it states Windows installer 64-bit only which is obviously not true as mint4win is 32-bit application (ONLY)
mint4win.exe from http://community.linuxmint.com/tutorial/view/687
runs, but obviously does not work (as it was created for v12 specifically)
sebus
Boot & install from DVD works perfectly fine
It is only mint4win that does NOT run correctly
On http://www.linuxmint.com/download.php
for Cinnamon it states Windows installer 64-bit only which is obviously not true as mint4win is 32-bit application (ONLY)
mint4win.exe from http://community.linuxmint.com/tutorial/view/687
runs, but obviously does not work (as it was created for v12 specifically)
sebus
Last edited by sebus on Sun Jun 10, 2012 1:06 pm, edited 1 time in total.
Re: mint4win starts & then instantly exits on W7 x64
Opening min4win.exe in Dependency Walker 2.2 gives:
Error: At least one module has an unresolved import due to a missing export function in an implicitly dependent module.
Error: Modules with different CPU types were found.
Warning: At least one delay-load dependency module was not found.
Warning: At least one module has an unresolved import due to a missing export function in a delay-load dependent module.
Anybody actually managed to run mint4win from 64-bit iso on Win7 x64?
sebus
Error: At least one module has an unresolved import due to a missing export function in an implicitly dependent module.
Error: Modules with different CPU types were found.
Warning: At least one delay-load dependency module was not found.
Warning: At least one module has an unresolved import due to a missing export function in a delay-load dependent module.
Anybody actually managed to run mint4win from 64-bit iso on Win7 x64?
sebus
Re: mint4win starts & then instantly exits on W7 x64
I have this problem too: Windows 7 SP1 build 7601 with Mint (cinnamon) 13, 64bit.
Looking at dependency walker, it shows 4 missing delay-load dlls: ieshims.dll and gpsvc.dll
GPsvc is a security thing and is found using the side-by-side loading I hate so depends will not tell what's up with it (it was never updated to handle side-by-side dlls).
running sxstrace suggests no problems, so I doubt it is anything to do with these dlls. I did notice it was running as a wow32 process, so maybe this is the problem - if I don't have the 32 bit versions of some dlls.
I ran it under processmonitor and nothing exceptional seems to be going on, so I guess it now needs some help with writing debug logs from the application itself.
Looking at dependency walker, it shows 4 missing delay-load dlls: ieshims.dll and gpsvc.dll
GPsvc is a security thing and is found using the side-by-side loading I hate so depends will not tell what's up with it (it was never updated to handle side-by-side dlls).
running sxstrace suggests no problems, so I doubt it is anything to do with these dlls. I did notice it was running as a wow32 process, so maybe this is the problem - if I don't have the 32 bit versions of some dlls.
I ran it under processmonitor and nothing exceptional seems to be going on, so I guess it now needs some help with writing debug logs from the application itself.