Issue with software installation on windows 8


#1

i am having a crazy time trying to get the software to run properly on my windows 8 machine. it shows up in the task manager, but no gui and no taskbar icon. any hints?


#2

Check the installation instructions again, and also the troubleshooting. Follow exactly - don't do anything else.
Check runtime is installed correctly as per installation guide.

( it's worked so many times carefully following will work :))

After that, run from command line - see if any error messages.

Trying starting UI without axoloti attached.

If you have issues connecting axoloti ( it's not needed to get UI running) , try different microUSB cable
Again, all in the help installation/troubleshooting guides


#3

Thanks for writing me back. i have installed and uninstalled it many times. it does the same thing. it installs fine on every other machine i have tried. it seems like the installs' configure phase is crazy quick compared to the other machines. i compiled some of the earlier versions of the software on this machine, as well as was running an earlier install based version.


#4

Try deleting the file axoloti.prefs in My Documents/axoloti


#5

that was the magic trick. thanks much for your time!


#6

i am getting a "make not recognized as an internal or external command" error (shell task failed, exit value 1)


#7

"Check runtime is installed correctly as per installation guide."


#8

it is installed as: "C:\Program Files (x86)\axoloti_runtime\platform_win". size is 131,958,015 bytes. could there be junk paths from earlier installs?


#9

What's the runtime dir in the preferences dialog?


#10

"C:\Program Files (x86)\axoloti_runtime"


#11

i got to the bottom of the situation: windows was not unpacking the runtime zip properly, it was only unpacking ~138megs of it. i unpacked with winrar and all was good. Many thanks once again, and a giant apology for eating up your time.


#12

No issues @magneticstripper ... it should have been telling you in the console that it could not find the runtime.
but I guess, if it was half unpacked this might have 'fooled' it.

odd that windows didnt unpack it properly... I tested this with a pretty clean version of windows (as i don't use windows much) and didnt have any issues.

oh well, never mind, most important thing is your up and running....

happy patching smile