Only work with 64MB card

[GoogleCodeExporter]

I did all steps, but hack only an old 64MB card works. All 1GB, 2GB and 8GB 
don't works. I formated cards using camera and PC (Windows XP) with FAT and FAT 
32, follow instructions (EOSCard, copy files) but hack don't work with all 
others card, only with 64MB. Someone can help? I am using last version 
400plus-20120415-11.

Original issue reported on code.google.com by gbom...@gmail.com on 3 Jul 2012 at 2:28

[GoogleCodeExporter]

All advice I can give is to repeat all the steps again, it is a delicate 
process and any mistake may go unnoticed; most people use large cards, and it 
works for them. If that fails, please post here all what you are doing, step by 
step, and the results.

Changing the issue to a support request.

Original comment by eduardo....@gmail.com on 3 Jul 2012 at 5:22

• Added labels: Type-Support
• Removed labels: Type-Defect

[GoogleCodeExporter]

May be you are preparing a FAT32 card with FAT16 procedure, or vice versa. 
Please use the procedure for the correct filesystem.

Original comment by fired...@gmail.com on 3 Jul 2012 at 8:32

[GoogleCodeExporter]

First I changed fiwmware version to 1.1.1 and install testfir using 64MB card.

Steps to hack:
1. insert CF card PQI Hi-Speed 2GB on camera;
2. format card using camera format;
3. insert card on card reader slot;
4. run EOSCard with both first and second checkbox checked, then Save button;
5. copy autoexec.bin and language.ini to CF;
6. out card on camera slot;
7. turn on camera;
8. blue light don't blink, menu don't appear with print button.

The same steps on all cards, only 64MB card works. I tried with cards PQI 2GB, 
San Disk 1GB and Trancend 8GB,

I did the same with all cards. The same. There is no space to error, format, 
prepare card, copy files. Maybe problem with all large cards? Maybe problem 
with formating cards?

Original comment by gbom...@gmail.com on 3 Jul 2012 at 8:45

[GoogleCodeExporter]

Fired, do you know how I change it at camera? Because I formated using camera.

Original comment by gbom...@gmail.com on 3 Jul 2012 at 8:47

[GoogleCodeExporter]

I have a 2GB card (formated to FAT16) and a 4GB card (formated to FAT32), and 
400plus works on both of them; so I would say that neither card size nor FAT 
type are a problem here.

First think I would try now is to format the card in the computer.

Original comment by eduardo....@gmail.com on 3 Jul 2012 at 10:59

• Changed state: Started

[GoogleCodeExporter]

You do not change it on the camera, the camera chooses the right FAT size for 
the card, that's why this is the preferred method for formting the card in the 
FirmwareHackInstallation wiki.
I said you may be preparing for wrong FAT size because I did not know the 
method you were using for preparing the card, in some methods (like the DD 
method) it is very important to use  the correct offsets for the FAT size. With 
EOSCard it is done automatically for you.

When you enable the both checkboxes in EOSCard, you also need to ensure the 
inputs for each checkbox is correct, like in the picture: 
http://chdk.wikia.com/wiki/EOScard

Original comment by fired...@gmail.com on 3 Jul 2012 at 11:29

[GoogleCodeExporter]

So, I don't know what is happen. I do the steps on a new 16GB Kingston ElitePro 
133x  card now, formating on camera, use EOSCard with two first options 
checked, then copy autoexec.bin and language.ini to card, they are at root, 
insert card on camera and nothing, blue light don't blink, menu don't appear 
with print button. It only works with 16MB card. Someone have any ideas? There 
are some mambo jambo to do this? Thank you in advantage.

Original comment by gbom...@gmail.com on 11 Jul 2012 at 3:33

Attachments:

• EOSCard.JPG

[GoogleCodeExporter]

This is very strange indeed. Just to confirm, you did the "Hack-activation 
firmware" (400plus-testfir-1.bin.zip) update right ?

Original comment by fired...@gmail.com on 11 Jul 2012 at 4:44

[GoogleCodeExporter]

Just some thoughts:

* I always assumed that our camera cannot format cards larger than 4GB; is 
yours working properly?

* Is the old 16MB card still working? Perhaps the booting has been somehow 
disabled?

* Speaking of that, have you followed the "Prepare the camera" procedure more 
that once maybe?

Original comment by eduardo....@gmail.com on 11 Jul 2012 at 8:40

[GoogleCodeExporter]

Yes, the first thing, and only once time. The 64MB card still working by the 
way. All the others, 1GB, 2GB, 8GB and now 16GB don't. The mystery is why 64MB 
(FAT) works. =(

Original comment by gbom...@gmail.com on 11 Jul 2012 at 8:57

Attachments:

• 64mb.JPG
• 16gb.JPG

[GoogleCodeExporter]

Can you try formatting one of the <= 4GB CF cards with FAT16 and try it (dont 
forget to prepare it) ?

Original comment by fired...@gmail.com on 11 Jul 2012 at 9:03

[GoogleCodeExporter]

My camera formated the 16GB card without problems. The old card has 64MB, and 
still working. I formated 1GB now with FAT (under Windows), prepare with 
EOScard and copy files. Did you think that run testfir again can solve 
something?

Original comment by gbom...@gmail.com on 11 Jul 2012 at 9:19

Attachments:

• 1gb.JPG

[GoogleCodeExporter]

> I formated 1GB now with FAT (under Windows), prepare with EOScard and copy 
files.

Does it work ?

Running the testfir again should not make any difference, but wont hurt to try.

Original comment by fired...@gmail.com on 11 Jul 2012 at 9:26

[GoogleCodeExporter]

No, don't work. I will put testfir on both 1GB and 64MB and try again. I am 
reading FirmwareHackInstallation again to see if I jump something. Can cluster 
size affect something?

Original comment by gbom...@gmail.com on 11 Jul 2012 at 9:30

[GoogleCodeExporter]

Using 1GB card the message was "Update file cannot be found".

Original comment by gbom...@gmail.com on 11 Jul 2012 at 9:33

[GoogleCodeExporter]

I do not think the cluster size is the problem, but I'm not sure on that.
BTW it doesn't matter from which card you run the testfir.
It sounds like a camera specific problem... I do not understand what is 
happening and why it's not working... very strange problem. Though it runs from 
64MB card, which is even more strange.
Anyway, try running the testfir from 1GB card or larger. Let's see if it helps.

Original comment by fired...@gmail.com on 11 Jul 2012 at 9:34

[GoogleCodeExporter]

Using 64MB card works, it is updating now.

Original comment by gbom...@gmail.com on 11 Jul 2012 at 9:34

[GoogleCodeExporter]

hmm... the 1GB card shows the FW update menu, but doesn't update actually 
because of the error message ?

Original comment by fired...@gmail.com on 11 Jul 2012 at 9:36

[GoogleCodeExporter]

reach me at firedust@gmail.com (GTalk)

Original comment by fired...@gmail.com on 11 Jul 2012 at 9:36

[GoogleCodeExporter]

It's sound like no MBR program on 1GB card boot record.

Original comment by gbom...@gmail.com on 11 Jul 2012 at 9:38

[GoogleCodeExporter]

MBR should not be the case here, MBR is not used by the camera...

Original comment by fired...@gmail.com on 11 Jul 2012 at 9:40

[GoogleCodeExporter]

More guesses: I see you always write "autoexec.bin" instead of "AUTOEXEC.BIN"; 
could that be the cause?

Original comment by eduardo....@gmail.com on 11 Jul 2012 at 9:44

[GoogleCodeExporter]

in FAT the case does not matter, but who knows.

Original comment by fired...@gmail.com on 11 Jul 2012 at 9:47

[GoogleCodeExporter]

Okay, not exactly a MBR, but some kind of boot record. I just unpack to card, 
autoexec.bin is in uppercase, but languages.ini in in lowercase in both cards.

Original comment by gbom...@gmail.com on 11 Jul 2012 at 9:52

[GoogleCodeExporter]

there is no boot record for the camera, the MBR is only for the BIOS of x86 
systems (historically), the ARM architecture does not use BIOS, neither MBR... 
that's why we use the EOScard utility to set the volume label of the card and 
the BOOTDISK flag, which the camera checks on start and then looks for 
AUTOEXEC.BIN in the root folder. If it exists, the camera loads it.

Original comment by fired...@gmail.com on 11 Jul 2012 at 9:56

[GoogleCodeExporter]

Well, this appear to be a body problem, it can't load autoexec.bin nor upgrade 
firmware file from card greater than 64MB. Thanks for everyone.

Original comment by gbom...@gmail.com on 11 Jul 2012 at 10:10

[GoogleCodeExporter]

Just to spread some more lights from my chat with gbomfim, it seems the camera 
cannot start firmware update from >64mb card, which i believe is the problem 
with the hack too.
The camera gives error message when he try to update the FW from >64mb (but 
still see the FW file and shows the menu for FW update)

Another disturbing thing is that the FW version of the camera was 1.0.4 before 
update to 1.1.1 (with 64mb card)

IIRC my camera was with FW version 1.0.9 or 1.1.0 before updating it to 1.1.1. 
I bought my camera in April 2007 and it was relatively new to the market, the 
FW 1.1.1 came out few months after that IIRC.
FW version 1.0.4 sounds like a experimental/prototype camera, and may have 
different hardware somehow (though i doubt it).

gbomfim, if you send it to the service and they somehow fix the problem (or you 
find a way to fix the problem), please drop a message here.

For now I will close the issue as Unfixable.

Original comment by fired...@gmail.com on 11 Jul 2012 at 10:18

• Changed state: Unfixable

[GoogleCodeExporter]

I just saw a message, at a Spanish forum, from someone who had a similar 
problem; and this is the solution that he found:

* Format card (SanDisk Extreme III 4GB) in the camera.
* With HxD, write EOS_DEVELOP at row=00000040 column=07 and BOOTDISK at 
row=00000050 column=0C.
* Copy files to card.
* Enjoy 400plus.

May be worth giving it a try...

Original comment by eduardo....@gmail.com on 12 Jul 2012 at 6:23

[GoogleCodeExporter]

He actually did what EOSCard does. 0x47 and 0x5C are the addresses for FAT32. 
But who knows, it may be a problem with EOSCard, though I doubt it.

Original comment by fired...@gmail.com on 12 Jul 2012 at 8:22

[GoogleCodeExporter]

EOScard save and read this values, so I don't think that EOScard has a problem. 
I formated 1GB card with FAT32, redo all steps and nothing.

Original comment by gbom...@gmail.com on 12 Jul 2012 at 1:00