the name of PS.FI2 on the card is actually not really PS.FI2.
I tried awhile ago to just make the whole 8 gig card formatted FAT32 and copy all of the files over, but it didn't work. Should it? If it ought to work I could try it again.
But there's that other part of the directions that involves copying the boot sector over and using a Hex editor, and my guess is that that's the part that's going wrong? Should I have to do that part at all if I don't care about autoboot?
Quotethe name of PS.FI2 on the card is actually not really PS.FI2. Wait, then what is the name?
perhaps you can have a look at the root directory with CHDK (with the file browser in misc. stuff) and see what kind of files are in there. (I just got DISKBOOT.BIN, PS.FI2, vers.req and readme.txt.)
I understand how creating partitions works and stuff, and its easy in disk utility to make sure you are only modifying the SD card and not any other drive. But I don't know much about the Terminal code. The code given worked just fine, and I think its unrealistic to expect anyone who wants to try the CHDK to know how to program in linux or unix or whatever that is.
I did read the known issues on that FAQ but I don't think any of them apply to me. Since the installation worked on my 4 gig card, I don't think there are any problems with unarchiving or permissions.
Did you actually check with ls -la@ ? It would be unsurprising if mac did slightly different things between FAT32 and FAT12 or different partition types.
The firmware update method is known to work. All you have to do is have a copy of the correct FI2 file in the root directory of the first partition on the card, without any special attributes or anything.
Whether you think it should be easier or not is irrelevant.
QuoteDid you actually check with ls -la@ ? It would be unsurprising if mac did slightly different things between FAT32 and FAT12 or different partition types.I'm not sure who/what that is, so no
That's what I've done and it doesn't work. Are you sure its "known to work" on a mac?
Also, I think that asking people to learn an entire programming language rather than just giving clear instructions for this one step would discourage a lot of potential CHDK users, and I'm thinking that in the long run its more advantageous to have more people interested in CHDK, learning to use it, able to answer questions, etc.
It's known to work on any system that can just copy a file in the standard manner without doing some bizarre extra garbage you didn't ask for behind the scenes.
... although I've yet to try editing a wiki, maybe I'll try to put in the lack of a Firm Update menu as a particular problem that can occur with the Mac installation.
Having read through the Mac FAQ again, I don't think its clear what the -la@ is referring to. Is it a command to type into Terminal? It just says "here's what I got" and gives some sample results. I guess it might be clearer to people who have more experience with this context. Anyway, I ended up just trying the commands to remove the flags without using the -la@ (which I think was some sort of test to see if the flags were there?) and it did work successfully, so I guess it doesn't really matter.
Edit: The reason all my posts are edited is that apparently when I type in the quote code by hand it doesn't work, and when I use the quote button it does. Even though as far as I can tell its producing the same text each time...
It's probably your Mac.
Started by antitax
Hello, I'm a NEWBIE - HELP!! (Newbies assistance, User Guides and thank you notes)
Started by Kraz
Started by reyalp
Started by CanonBlue
General Discussion and Assistance
Started by 74prof
General Discussion and Assistance