Hacking Wad2Nand OS X v1.4 (Final?)

[XarcusEater]

Wad2Nand mac os x v1.4 is here. Many, many bug fixes, it should work for everyone now. Other changes: creates wad2nand-install.log on desktop, now you will be able to tell where it failed. Max wads still 60, I think that's enough for everyone.
Feedback is appreciated.

 

[terminal_illness]

still not working for me. all my wads have .wad extention. when it asks me for my wad they are all greyed out. i have common-key.bin in the home folder and still no go.

10.5.8
powermac g5 dual core.

 

[XarcusEater]

this should work. still must be in /Applications. will allow any filetype selection.

 

[terminal_illness]

i get an error on selecting wad

""cant make "macintosh HD:applications:wad2nand.app:contents:resources:" into type

 

[XarcusEater]

even when it's in the Applications folder?
Is your startup disk called "Macintosh HD"?

 

[terminal_illness]

yes its in applications and no my startup volume is not called that. i am creative and i name all of my drives something different. i guess i need it to be named Macintosh HD while im using this?

edit: still doesnt work. the 1.4 all my wads are greyed out, and the version you posted gives me the error,

"cant make "macintosh HD:applications:wad2nand.app:contents:resources:ticket" into an item.

 

[XarcusEater]

yes, ill try to make it work with any name tomorrow, I chose that name because its the default for a newly bought mac.

 

[terminal_illness]

check my edit.

 

[XarcusEater]

there should be a file caled "wad2nand-install.log" on the desktop. copy and paste it's contents here.
also, go to the wad2nand app in finder, right-click, show package contents, then go to /contents/resources, and tell me what files and folders are there after it quits. Thanks

 

[joda]

Using hardcoded paths is just plain stupid and bad programming. (Since it won't work on anything but your exact configuration.)

Use the proper class methods for this instead.

ÂÂÂÂ// bundlePath points to @"[...]/Bundle.app"
NSString *bundlePath = [[NSBundle mainBundle] bundlePath];
ÂÂÂÂ// ticketPath points to @"[...]/Bundle.app/Contents/Resources/ticket"
NSString *ticketPath = [[[bundlePath stringByAppendingPathComponent:@"Contents"]
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ stringByAppendingPathComponent:@"Resources"]
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂstringByAppendingPathComponent:@"ticket"];

 

[joda]

You could of course add all in one go, and/or use the general

- (NSString *)stringByAppendingString:(NSString *)aString

method to append the end of the path. This is however also bad practice since the

- (NSString *)stringByAppendingPathComponent:(NSString *)aString

method makes sure that there are no surplus slash-characters, and adds any if needed.

 

[joda]

Also --- I'm on a flow here

--- you shouldn't really do work in your bundle directory, but in the system default temporary directory. Simplest way to get that is by:

NSString * tempDir = NSTemporaryDirectory();
if (tempDir == nil)
ÂÂÂÂtempDir = @"/tmp";

[*]Then create a subdir to work in.[*]Do your shitz in that dir.[*]Move the end product somewhere useful.[*]Clean up by removing your entire dir.

 

[XarcusEater]

@joda: this doesn't apply, I'm using applescript to choose file(s), then using applescript to put the in my directory, then using shell to install them.
so the user gets to choose whatever files first, then the directory is hardcoded. I wanted to create some sort of GUI, but I didn't know cocoa.
look at the shell and the scpt in the /src folder of the .dmg

 

[terminal_illness]

still not working for me, i tested it on 4 different macs.

 

[XarcusEater]

can you do what I asked you to in post #9?
also, select one of your wads, and hit command-i (get info). then look at the full filename. it might have a second extension. ex: example.wad.txt
remove the extension if there is one. then try release 1.4

 

[XarcusEater]

outdated, look at the new thread