I've been playing MC for 2 years now, so installing mods has never given me trouble until 1.4.6 came out.
The MC jar has a file named aux.class, that my archiver is unable to handle, leading to corrupted jars.
I use AlZip (which recognizes jar files as archives) to extract the jar into a new folder.
I could drag file directly into the jar, but it occasionally fails and the jar is lost, so I just
save time by extracting to a folder from the start.
I then drag the forge files into the folder and delete the meta-inf folder.
after re-compressing the folder I'm ready to go.
But every since 1.4.5, i get an overwrite confirmation dialogue, when performing the initial extraction,
asking me if i want to overwrite file (filename is blank) (size is zero bytes) (no other info provided)
with file (no file info of any sort is provided), if i select "Yes" , the program freezes for 1 minutes the finnishes.
If I select "No", it doesnt freeze, it just finnishes, and in both cases the file aux.class is not extracted.
If I try to manually extract aux.class, I get the same dialogue, even there is no other file present is that folder,
and the extraction fails, silently.
I know that "AUX" is an illegal filename in windows ( im using XP), and the few copies of previous versions of the jar, that i have don't have aux.class in them, so this is a new issue.
How is everyone else getting around it?
Why are so few people having this trouble?
How can I get around it? I don't to have to Hex edit every jar from now on out.
I would suggest using a different archiver, winrar or 7zip.
You shouldn't get corrupted archives dragging and dropping the forge files into the unextracted jar. So that what leads me to believe the program you are using is the problem.
Alternately you could use MultiMC and never have to worry about opening the jar yourself to add mods in.
I then drag the forge files into the folder and delete the meta-inf folder.
after re-compressing the folder I'm ready to go.
Also, forge now has it's own meta-inf folder that needs to be in place after forge is installed, so you should delete the meta-inf folder prior to moving forge in.
The MC jar has a file named aux.class, that my archiver is unable to handle, leading to corrupted jars.
I use AlZip (which recognizes jar files as archives) to extract the jar into a new folder.
I could drag file directly into the jar, but it occasionally fails and the jar is lost, so I just
save time by extracting to a folder from the start.
I then drag the forge files into the folder and delete the meta-inf folder.
after re-compressing the folder I'm ready to go.
But every since 1.4.5, i get an overwrite confirmation dialogue, when performing the initial extraction,
asking me if i want to overwrite file (filename is blank) (size is zero bytes) (no other info provided)
with file (no file info of any sort is provided), if i select "Yes" , the program freezes for 1 minutes the finnishes.
If I select "No", it doesnt freeze, it just finnishes, and in both cases the file aux.class is not extracted.
If I try to manually extract aux.class, I get the same dialogue, even there is no other file present is that folder,
and the extraction fails, silently.
I know that "AUX" is an illegal filename in windows ( im using XP), and the few copies of previous versions of the jar, that i have don't have aux.class in them, so this is a new issue.
How is everyone else getting around it?
Why are so few people having this trouble?
How can I get around it? I don't to have to Hex edit every jar from now on out.
-
View User Profile
-
View Posts
-
Send Message
Retired StaffYou shouldn't get corrupted archives dragging and dropping the forge files into the unextracted jar. So that what leads me to believe the program you are using is the problem.
Alternately you could use MultiMC and never have to worry about opening the jar yourself to add mods in.
Also, forge now has it's own meta-inf folder that needs to be in place after forge is installed, so you should delete the meta-inf folder prior to moving forge in.