Kisslicer on win7 64 bit

[Temo]

Hello

I doesn't seem to be able to run the 64 bit version on win7 64 sp1. The 32 bit version run without issues. I've tride version 1.1.0 and 1.4.4.6.

I have tried running them from the 64 bit folder and the 32 bit folder, but it always freezes upon opening. I've even tried putting some .ino files in the folders.

Are there any tricks to getting this to run, I have paid for the pro version?

Terje

[Temo]

Hello again

I just tried on my old win7 pc and it works there. This is a brand new pc, are there any libraries or something I have to install before using this?

Terje

[Temo]

Here are the crash report if anyone can help:

Version=1

EventType=AppHangB1

EventTime=130496624323354748

ReportType=3

Consent=1

UploadTime=130496624364850821

ReportIdentifier=46c7e05a-09f0-11e4-8edf-ac220b89a84d

IntegratorReportIdentifier=46c7e05b-09f0-11e4-8edf-ac220b89a84d

Response.BucketId=50

Response.BucketTable=5

Response.type=4

Sig[0].Name=Application Name

Sig[0].Value=KISSlicer64.exe

Sig[1].Name=Application Version

Sig[1].Value=0.0.0.0

Sig[2].Name=Application Timestamp

Sig[2].Value=53bcca41

Sig[3].Name=Hang Signature

Sig[3].Value=e406

Sig[4].Name=Hang Type

Sig[4].Value=0

DynamicSig[1].Name=OS Version

DynamicSig[1].Value=6.1.7601.2.1.0.256.48

DynamicSig[2].Name=Locale ID

DynamicSig[2].Value=1044

DynamicSig[22].Name=Additional Hang Signature 1

DynamicSig[22].Value=e406a6b2af1aa347bde38097a5f98f01

DynamicSig[23].Name=Additional Hang Signature 2

DynamicSig[23].Value=d3b4

DynamicSig[24].Name=Additional Hang Signature 3

DynamicSig[24].Value=d3b48d77ed2efdedc6519ac0d9694641

DynamicSig[25].Name=Additional Hang Signature 4

DynamicSig[25].Value=e406

DynamicSig[26].Name=Additional Hang Signature 5

DynamicSig[26].Value=e406a6b2af1aa347bde38097a5f98f01

DynamicSig[27].Name=Additional Hang Signature 6

DynamicSig[27].Value=d3b4

DynamicSig[28].Name=Additional Hang Signature 7

DynamicSig[28].Value=d3b48d77ed2efdedc6519ac0d9694641

UI[3]=KISSlicer64.exe is not responding

UI[4]=If you close the program, you might lose information.

UI[5]=Close the program

UI[6]=Close the program

UI[7]=Close the program

LoadedModule[0]=C:\Program Files\Kisslicer64\KISSlicer64.exe

LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll

LoadedModule[2]=C:\Windows\system32\kernel32.dll

LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll

LoadedModule[4]=C:\Windows\system32\USER32.DLL

LoadedModule[5]=C:\Windows\system32\GDI32.dll

LoadedModule[6]=C:\Windows\system32\LPK.dll

LoadedModule[7]=C:\Windows\system32\USP10.dll

LoadedModule[8]=C:\Windows\system32\msvcrt.dll

LoadedModule[9]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18201_none_a4d3b9377117c3df\COMCTL32.DLL

LoadedModule[10]=C:\Windows\system32\ADVAPI32.dll

LoadedModule[11]=C:\Windows\SYSTEM32\sechost.dll

LoadedModule[12]=C:\Windows\system32\RPCRT4.dll

LoadedModule[13]=C:\Windows\system32\apphelp.dll

LoadedModule[14]=C:\Windows\AppPatch\AppPatch64\AcGenral.DLL

LoadedModule[15]=C:\Windows\system32\SspiCli.dll

LoadedModule[16]=C:\Windows\system32\SHLWAPI.dll

LoadedModule[17]=C:\Windows\system32\ole32.dll

LoadedModule[18]=C:\Windows\system32\SHELL32.dll

LoadedModule[19]=C:\Windows\system32\sfc.dll

LoadedModule[20]=C:\Windows\system32\sfc_os.DLL

LoadedModule[21]=C:\Windows\system32\USERENV.dll

LoadedModule[22]=C:\Windows\system32\profapi.dll

LoadedModule[23]=C:\Windows\system32\dwmapi.dll

LoadedModule[24]=C:\Windows\system32\MPR.dll

LoadedModule[25]=C:\Windows\system32\IMM32.DLL

LoadedModule[26]=C:\Windows\system32\MSCTF.dll

LoadedModule[27]=C:\Windows\system32\comdlg32.dll

LoadedModule[28]=C:\Windows\system32\OPENGL32.dll

LoadedModule[29]=C:\Windows\system32\GLU32.dll

LoadedModule[30]=C:\Windows\system32\DDRAW.dll

LoadedModule[31]=C:\Windows\system32\DCIMAN32.dll

LoadedModule[32]=C:\Windows\system32\SETUPAPI.dll

LoadedModule[33]=C:\Windows\system32\CFGMGR32.dll

LoadedModule[34]=C:\Windows\system32\OLEAUT32.dll

LoadedModule[35]=C:\Windows\system32\DEVOBJ.dll

LoadedModule[36]=C:\Windows\system32\CRYPTBASE.dll

LoadedModule[37]=C:\Windows\system32\uxtheme.dll

LoadedModule[38]=C:\Program Files (x86)\ATI Technologies\HydraVision\HydraDMH64.dll

LoadedModule[39]=C:\Windows\system32\CLBCatQ.DLL

LoadedModule[40]=C:\Windows\system32\msimtf.dll

LoadedModule[41]=C:\Windows\system32\VERSION.dll

LoadedModule[42]=C:\Windows\system32\atig6pxx.dll

LoadedModule[43]=C:\Windows\system32\atio6axx.dll

LoadedModule[44]=C:\Windows\system32\winmm.dll

LoadedModule[45]=C:\Windows\system32\atiadlxx.dll

LoadedModule[46]=C:\Windows\system32\PROPSYS.dll

LoadedModule[47]=C:\Windows\system32\WTSAPI32.dll

LoadedModule[48]=C:\Windows\system32\PSAPI.DLL

LoadedModule[49]=C:\Windows\system32\WS2_32.dll

LoadedModule[50]=C:\Windows\system32\NSI.dll

LoadedModule[51]=C:\Windows\system32\IPHLPAPI.DLL

LoadedModule[52]=C:\Windows\system32\WINNSI.DLL

LoadedModule[53]=C:\Windows\system32\WINTRUST.dll

LoadedModule[54]=C:\Windows\system32\CRYPT32.dll

LoadedModule[55]=C:\Windows\system32\MSASN1.dll

LoadedModule[56]=C:\Windows\system32\atig6txx.dll

State[0].Key=Transport.DoneStage1

State[0].Value=1

State[1].Key=DataRequest

State[1].Value=Bucket=50/nBucketTable=5/nResponse=1/n

FriendlyEventName=Stopped responding and was closed

ConsentKey=AppHangXProcB1

AppName=KISSlicer64.exe

AppPath=C:\Program Files\Kisslicer64\KISSlicer64.exe

ReportDescription=A problem caused this program to stop interacting with Windows.

kl. 18:10:07 UTC+2 lørdag 12. juli 2014 skrev Temo følgende:

[lonesock (Jonathan)]

Hi, Temo.

The only time I have seen this behavior, the KISSlicer executable was in a directory where it did not have write access (the Downloads folder, sometimes in Program Files, depending on settings), or with the INI files write protected.  If it runs OK in a completely different directory, or when run as administrator (not that I recommend that, in general), that's most likely the problem.  Can you edit a text file in that directory using notepad or similar?

thanks,

Jonathan

[Temo]

Hello

Thank you for the answer, yes I can edit ini-files.

I've tried different folders, different drives and running as an administrator. 

Can it matter that I have a SSD -drive as a system drive, wouldn't think so myself?

Are there any reg settings for Kisslicer or any other directories where the settings are stored, and where are the ini-files supposed to be stored?

Terje

[Temo]

So I've been working on this straight 8 hours, this must be a either a windows 7 issue or a missing app-data folder/reg settings. 

Do I need a app-data folder if I have the ini files in the same directory  as the exe file, and are there supposed to be any reg settings?

And I can not, whatever I do get the read only settings altered for the Kisslicer directory, but the files are write-able.

Terje

kl. 18:10:07 UTC+2 lørdag 12. juli 2014 skrev Temo følgende:

[Temo]

So I restored the computer to an earlier state, but before I try one more time:

- any tips or tricks to get the 64 bit version to run on win7 64 bit?

- what are the preferred directory to install into?

- does it matter where you extract to, and then just copy to the dir that you run it from?

- is it better to copy the 4 ini files from the 32 bit dir to the 64 bit dir before you install and run for the first time?

- do you manually have to set write permissions for the Kisslicer?

Terje

[lonesock (Jonathan)]

Hi, again.  Sorry this is such a problem!

KISSlicer does not need to be run in any special directory, as long as it can write files there.  You can use the same INI files from 32- or 64-bit installs.  (It is even supposed to handle cross-platform stuff now, so opening INI files generated on a Mac should work too.)

KISSlicer doesn't use the registry, but it does save preferences in a file in the directory "C:\Users\USERNAME\AppData\Roaming\lonesock software", in a file named "KISSlicer.prefs".  If that folder is write protected it could cause the problem.

I also wonder if this might be a problem if there are unicode characters in the username?  KISSlicer tries to be unicode aware for handling STL and G-code files, but the internals of the preferences code may have some problems.  Could that be the case?

Jonathan

[funBart]

Hello Temo, 

I have installed KS on Mac and Windows machines. Now I'm running the latest beta (1.4.4.6) on a Windows 8, 64 bit system, but I have it running on another Win 7 x64 system as well. You have downloaded and extracted that same Beta?

The only time I had that kind of trouble, is when installed on the Program folder without sufficient rights. 

To avoid changing of permissions, I suggest to copy the Kisslicer.exe (you have unzipped it, haven't you?) to a directory on your Desktop. You can start the exe first, to see it generates the standard ini files in that directory and if it runs.

If so, you can copy your tweaked ini files to that directory of course.

AFIK isn't Kisslicer doing anything to your registry / putting dll's somewhere or so. It seems to run directly without dependencies.

The only exception is the PRO key, that is stored in your USER/Appdata/roaming/Lonesock software directory.

Maybe your UAC is set to a too high level / is your virus scanner blocking somehow? 

Hope it helps.

Bart

[funBart]

Jonathan! What's the point when we post about the same message at the same time ;-)

Go play with your kids man!

Bart

[Temo]

Thank you both  for helping my trying to fix this.

I just don't get it, I created a folder on the desktop"TestKiss" and unzipped the 64 bit version there, started it and it asked me about the expert level, I clicked on expert and it reported that it would use default ini files, but it did not create it. I had turned UAC and virus control off. I then copied the ini files from my other win7 computer and started it again, but no luck just freezes up.

I then unzipped the 32 bit version to the same folder and it runs just fine, I'm thinking it can not have any thing to do with permissions then?

I also checked the Lonesock folder. Can it help if I edit it with my pro key?

Terje

[Temo]

I don't know if it matters, but just to test, I downloaded Slic3r 64 bit and installed it to Program Files and it worked right away.

[Temo]

Last post before bedtime!

I uninstalled AVG Antivirus 2014, restarted but same same.

Then I started the computer in diagnostic start-up mode, same same.

Then I started in safe mode, voila it worked.

Then I started in normal mode, same same did not work.

I attach a screen dump to show how it looks when it freezes up.

Terje

[Temo]

Hello


Before I do any more work on trying to get this 64 bit version working, can some skilled people read anything out out the attached err report so I know where to start looking?

Also, what would I miss out on not using the 64 bit version?
I'm running a self built rig with: Asus P9X79-WS motherboard, Intel I7-4930, 16 gig of 2400 ram(kit of four), AMD FirePro W7000 workstation graphics cards, Samsung SSD 250 startup-disk, 2T 7200 storage-disk and the dreadful windows 7. 

I have good cooling so the the CPU is running in range of 30-40 C with daily use, inside air-temp this summer about 25C

Mainly made this for work-use, but have just started installing software(Kisslicer64bit), but want to resolve this issue before putting in more software.


Terje

[lonesock (Jonathan)]

Running Win32 will limit you to just under 4GB of RAM, and can be a bit slower (depending on the actual processor).  I can use it just fine unless I do crazy-big models, or ultra-fine oversample resolution.

I may have missed it, but did running it as administrator work?

Jonathan

[Temo]

Hello

No, I have tried running as an admin, does not help.

I forgot to ask, you can see that it has taken the setting from the 32 bit version in the lonesock dir and applied the pro name that I registered with the 32 bit version, so it can read there when opening. 

But why is not the graphic with the visual print bed showing up before it crashes(see the attached photo on the earlier post). I'm I missing a graphic file or something, that represent the print-bed?

Terje

[Temo]

No sorry, it's bedtime for me, it did show up in safe mode, sorry!

[Timmay]

Try updating your ATI drivers?  It looks like it freezes just as it's trying to render the (I'm assuming) OpenGL window. 

[Temo]

Yes I will, see there is a new version out now, or I've been thinking to try different resolution. I have it set to 2560x1600 by displayport, maybe it doesn't support this, but a bit strange that the 32 bit version does. 

This is what that is pusseling me, why does the 32bit version run without issues?

Terje

[lonesock (Jonathan)]

The video drivers will have a 64-bit and a 32-bit version.  Under Windows it is a bit confusing...here's a quote from http://opengl3.org/downloads.

64 bits Windows versions

If you are running a 64 bit version of Windows, you might be wondering if there is a OpenGL64.dll file. The answer is no, there isn't. On all versions of Windows, Windows\System32 contains all the 64 bit DLLs. It contains the OpenGL32.dll which is actually a 64 bit dll.

For 32 bit programs, Windows detects the exe as a 32 bit program and instead of using System32 files, it uses Windows\SysWOW64 which actually contains the 32 bit DLLs. WOW means Windows On Windows which is a backwards-compatibility layer.

To find your Windows' System32 directory, go to: Start, Run... and type in %WINDIR%\System32. The system will redirect you to the default System32 directory automatically; this is also true for the 32 bits versions of Windows.

So yep, that might do it!

thanks,

Jonathan

[Temo]

Hello

Sorry, you lost me!

I got the file in four places:

- C:\windows\system32 opengl32.dll 0.99 MB

- C:\Windows\winsxs\amd64_microsoft-windows-opengl_31bf3856ad364e35_6.1.7600.16385_none_6ab9e7b9a318b3e8 opengl32.dll 0.99 MB
- C:\windows\sysWOW64 opengl32.dll 733 KB

- C:\Windows\winsxs\x86_microsoft-windows-opengl_31bf3856ad364e35_6.1.7600.16385_none_0e9b4c35eabb42b2 opengl.dll 773 KB

All of the same date 14.7.2009

And as you said no opengl64.dll

So where do I go from here? Can I redirect or something?

Terje

[lonesock (Jonathan)]

This one is the 64-bit version.

C:\windows\system32\opengl32.dll 0.99 MB

I know, it has '32' in it (we all know it should be '42', right?! [8^)  But that is the 64-bit version of OpenGL.  It is a different driver from the 32-bit version, which is this one:

C:\windows\sysWOW64 opengl32.dll 733 KB

Note the size difference.  I would definitely try updating to the latest video card drivers (from the AMD website, not via Microsoft).  The main video driver installation package will update all those for you.  ATI (who was bought out by AMD) used to have horrible OpenGL driver support, but they have come a long way...hopefully this will fix the issue!

Jonathan

[Temo]

OK, I will try

[Temo]

Wow, what a nice picture!

Uninstalled Hydravision, CCC with all drivers etc. run CCleaner, rebooted two times, installed CCC with drivers and all, no Hydravision as I only run one 30 inch screen. 

Rebooted, run CCleaner, check driver version. Old driver 13.352.1009, new driver 13.352.1014. 

Reboot one time, shut down(take a Scotch for the nerves).

Started win764, and then Kiss64Pro, viola chrimas time.

Now I just need a good profile for my Aluminatus!

Thank for all help.

Terje

ps. forgot to say, I tried running it after I uninstalled the ATI-drivers, it did run fine on win7 stock drivers.

[lonesock (Jonathan)]

Awesome!  Good job, and thanks for not giving up!

Jonathan

[Temo]

Thanks to you to, haven't check the .dll version yet but will check it and give you a feedback.

Terje

[Riccardo Fezza]

Hi have a problem when lunch a slice operation:

[funBart]

You mean you have trouble to slice some bread at lunchtime ;-) But I have that too sometimes, most of the time it's solved when adjusting the oversample resolution on the PRO tab  to a higher number.

Bart

[Robert Eaton]

I know you will get those errors if you have the RAM warning level set too high and slice a large model.

[Riccardo Fezza]

After lunch :-P with a oversample 0.06->0.1 the slice run but with a wrost result :-(
There are some triks for run in 64 mode ?

[funBart]

Can you post the stl?