When opening Minecraft, the launcher proceeds to reverse LZMA and then goes to unpack.
That's the problem, it doesn't unpack. The catch is that I'm working with the computer technician here in the library to get this to work on the network of computers. Minecraft has worked on the computers before on the same network, but there was a crash when the computer tech set up a backup server and everything had to be restored. Now, Minecraft will not unpack.
The problem, I think, is that it is unpacking to a shared network folder and not a local folder like the C:\ drive, yet I do not know how or if it's even possible to change the path of the unpack.
This is what the bizns looks like:
Bootstrap (v5)
Current time is Sep 26, 2014 1:49:32 PM
System.getProperty('os.name') == 'Windows 7'
System.getProperty('os.version') == '6.1'
System.getProperty('os.arch') == 'x86'
System.getProperty('java.version') == '1.7.0_67'
System.getProperty('java.vendor') == 'Oracle Corporation'
System.getProperty('sun.arch.data.model') == '32'
Looking for update
Downloading: https://s3.amazonaws.com/Minecraft.Download/launcher/launcher.pack.lzma
Got reply in: 538ms
No update found.
Reversing LZMA on \\WIN-BDQALMTMB7H\Network\Users\Library\AppData\Roaming\.minecraft\launcher.pack.lzma to \\WIN-BDQALMTMB7H\Network\Users\Library\AppData\Roaming\.minecraft\launcher.pack
Unpacking \\WIN-BDQALMTMB7H\Network\Users\Library\AppData\Roaming\.minecraft\launcher.pack to \\WIN-BDQALMTMB7H\Network\Users\Library\AppData\Roaming\.minecraft\launcher.jar
It does not get past that no matter how long I wait.
Things I've tried:
-Went into AppData\Roaming\.minecraft and deleted the folder and re-installed it.
-Checked to see if the appropriate files have the permissions required to write, read, change files on the computer and such. (They do)
Funny thing is, I logged into the administrator account for a computer and ran Minecraft and it worked just fine only because it was unpacking the necessary files to the C:\ drive, not the network folder.
The computer tech has done all he can do and knows for a fact that he has allowed Java on the network to do things.
There are many kids here in the library that yearn for their Minecraft back, along with myself on occasion. I hope this guilt instills within you all the urgency of my request: is there a way to change the path that the launcher unpacks to?
Comments 4
I have run into this same problem, but in a different sort of manner.
a week ago i had installed a functional Minecraft entirely within a portable USB drive. With two lines in a batch file
set APPDATA=%CD%\Data
java -jar Launcher/Minecraft.jar
((previously i had tried it with the old "alternative" .exe that ends in the same results))
needless to say i have deleted, reinstalled, changed installers... and yet the result always concludes in the launcher getting stuck "unpacking"
Before i decided last night to reformat my thumb drive everything worked fine. Now it is reformatted exFAT and this problem arises. Unsure if there is causation.
I'm not sure if this is an issue with java in general, or with the launcher. A possible alternative though would be to use the alternate launcher, which does not perform any installations or unpacking like installation-based one. It's possible to change the working directory with the -workDir argument (if I'm not mistaken) through a batch script.
Can confirm on Minecraft 1.8.1 and Launcher version 1.6.11:
I have the same problem, thought first it was my NAS but seeing this report it is identical to my problem. (NAS works fine otherwise)
I've tried Symlink, Minecraft Portable application, modded, vanilla, all the same.
However, using symlink i managed to make it unpack, but at an incredibly slow speed (link 15kB/s) and after unpack the game would not launch (probably due to the slow transfer speed).
Using the Minecraft portable application (which unpacks directly to the NAS and not via symlink) It stopped when the launchar.jar reached 274KB.
I've tried Java 7 and latest Java 8 (2015-02-02).
Using Windows 8.1 Pro x64,Laptop, Intel i7 Ivy Bridge, Nvidia Kepler, 8GB DDR3 RAM.
However, using resourcepacks and saves on the Network drive works fine, it seems only be related to Unpacking and launching the game itself.