If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
I'm based in Surrey too so not far!
if you have formated the HDD using the SST you you will definatley need to install the system software or the copier wont boot!
One thing you could do is remove the HDD & fit it to a pc or caddy see if windows will format it etc, if not then the hdd has failed. (It is a standard 3.5" desktop type 40GB if I remember)
Let us eat, drink, and be merry, because tomorrow we may die!
For all your firmware & service manual needs please visit us at:
Yes it is a standard 3.5", specifically a Deskstar in mine, HDS722540VLAT20, the only problem is at the moment none of my built computers actually physically have an IDE controller! I guess technology has officially moved on..
I do have plenty of old kit lying around so I'll build a system to try out the drive when I get a chance, in fact I'm pretty sure I can see a PCI IDE card sitting in an old motherboard, I'll see if it works, but might be a bit of a delay as I have deadlines coming up.
However it does seem like when it is claiming to have been successful it really has been - It claims to have successfully applied
and if I run the batch job again with it set to "Same Ver: Skip / Downgrade: Confirm" it skips them so it must be finding them.
However the troublesome one, iRC3200N_Boot_XXxx0606, which it wants to apply first, before iRC3200_Boot_XXxx7001, warns me that I have 70.01 so I'm trying to replace with the "older" 06.06, and if I say to proceed that's when it tries and throws Error Code 124.
I don't really understand what it's trying to achieve though, with these different versions of the Boot firmware:
The 'N' batch job first tries to apply this 'N' version of Boot v0606, then restarts, then applies a standard Boot v7001 which is the same for both C and N.
The 'C' batch job does the same thing, applies the 'C' version of Boot v0606, then restart, then the same Boot v7001 - Obviously this one stops immediately as it can see my device is an 'N' model.
Is the v0606 some sort of 'resetting' step? How come the v7001 doesn't have different 'N' and 'C' versions?
So now I'm thinking.. Does anybody have alternative firmware that I could try?
The N boot rom is if the machine has print, the C boot rom is if you either have a non print machine version (copier only) or you have the firery rip attached.
If you're using the firmware I sent you? then it's 100% good, I use it all the time.
Let us eat, drink, and be merry, because tomorrow we may die!
For all your firmware & service manual needs please visit us at:
Yeah that's the only firmware I have, what I was thinking was if I could get hold of another version I could see if it will accept it - then if it does, after that from a different starting point it might then accept the one you sent, I don't doubt the firmware is fine, if my damn machine would take it!
I get the difference between 'N' and 'C', what I don't understand is what it's aiming to achieve by installing the 'N' specific v0606 followed by an apparently non specific v7001, the SST seems to think they are just different versions of the same thing and one simply replaces the other but presumably that is not entirely accurate otherwise installing both would be pointless? Should the SST be treating them differently?
To be honest all you need to install to get the machine to boot is the system firmware, all the others are not needed, so rather than choose ALL, simply just tick the system check box, if that installs ok the machine should boot up OK!
So ignore language, boot, fax, etc etc for the time being
Let us eat, drink, and be merry, because tomorrow we may die!
For all your firmware & service manual needs please visit us at:
Oh also, forgot to mention, before trying any of this I removed and reseated the two memory sticks, the boot ROM, and the HDD ribbon cable. No change in behaviour, but nothing visually wrong at least (so hopefully didn't get damp after all)..
-------------------------------- a new HDD can only/& must be formatted inside the Printer with the SST> using iRC3200-XXxx0022-HDFormat.ift/
u can not format outside of the iR printer the ALL-HDF is used only when installing a new HDD--------I never try formatting on a old HDD that has/had error codes or HDD issues- best to buy a new HDD or a refurbished one
then u select ALL-HDF_C or N > after doing the HDFormat
if the iR3200 only needs to be updated or just re-loading firmware(overwrite all) > u select ALL_C or ALL_N on a iR3220 model u don't have to select a "C" or "N" firmware/ SST will automatically know> BOOT uses same ver. for "C & "N"
**Knowledge is time consuming, exhausting and costly for a trained Tech.**
Thanks teckat, I am aware (thanks to reading through many, many of your detailed and informative posts advising others) that the drive must be formatted inside the machine as you describe.
Can I confirm - if I remove the drive and connect to my desktop PC I can perform diagnostics and if it passes presumably I can blank it to an 'as factory' state then install in copier with the procedure as if it has been purchased new?
I am loathe to replace hdd at this point, partly because I am not at all convinced that the hdd is to blame and partly because even if it is, there is still potentially too much else wrong with the machine to justify spending the money until I know it can be fixed. I do also have a few old drives lying around which are potential candidates for adding to .ift file (or may even already be on it, I haven't checked yet)
At the moment my prime candidate (ok hunch) is boot rom.. What are your thoughts? Is this behaviour likely with a fried boot rom?
Initially it was booting, then it started with boot loop, has this error 124 on that specific firmware, and now doesn't even boot loop - screen doesn't light up at all when switched on unless going into 2 8.
I have never done a format outside the printer_
Guess it should be no issue
U will still need to format that HD inside 3200 with the 3200's firmware format file or printer will not see HD\ it's a Canon thing/ it prepares HD for receiving the printer firmware-
That Canon format file is written with language developed by Canon.
What is your Boot Rom - C or N .
I have seen where if one of those two memory sticks are bad, the printer will not boot all the way (,progress bar stalls at 3/4 way. This sometimes simulates a bad HD with no error codes/ learned this the hard way ,when i was bringing HD to customers & SST would not go into download mode to format,- made me carry back up memory sticks for 3200 series.
**Knowledge is time consuming, exhausting and costly for a trained Tech.**
The boot was stopping way earlier than 3/4, more like 1/10, and was then going blank and restarting over and over, rather than stalling. Machine enters 2 8 download mode fine and accepts some firmware, just not the v0606 boot, also 1 9 completes successfully and then enters download mode. Now a normal boot (and 1 7 boot) doesn't even get as far as progress bar. So probably not memory?
Are they as fussy about memory as they are hdd? If not I'm sure I will have something around I could test with..
The boot was stopping way earlier than 3/4, more like 1/10, and was then going blank and restarting over and over, rather than stalling. Machine enters 2 8 download mode fine and accepts some firmware, just not the v0606 boot, also 1 9 completes successfully and then enters download mode. Now a normal boot (and 1 7 boot) doesn't even get as far as progress bar. So probably not memory?
Are they as fussy about memory as they are hdd? If not I'm sure I will have something around I could test with..
Error 124= displays in the Service Support Tool when flashing the boot ROM
= that means No Boot ROM DIMM is inserted or Boot Rom is defective
"N" BOOT ROM is only available in the Multi PDL Print Kit- A1 i believe. did u check if the Kits UFR BOARD is inserted into it's slot
Do u have the original "C" Boot Rom / techs are supposed to leave it taped inside printer near bottom of Main Board FG3-3130-000 = "C"opier version Boot Rom
Just remembered this >>NOTE: A blown fuse or a low voltage fuse on the Fuse Pcb will sometimes mimic a bad BOOT UP ISSUE
Fuse Pcb is cheap & FUSE PCB in this model is notorious for causing issues--
Error 124= displays in the Service Support Tool when flashing the boot ROM
= that means No Boot ROM DIMM is inserted or Boot Rom is defective
Ahhhhhhhhh, there it is!
Now why couldn't I have found that when I was searching it like crazy?!
Brilliant thanks teckat, so I'll check all the contacts in the socket and give it another reseat first, but sounds like I'm going to be in the market for a replacement boot rom, anyone know my best bet for this in the UK?
Now why couldn't I have found that when I was searching it like crazy?!
Brilliant thanks teckat, so I'll check all the contacts in the socket and give it another reseat first, but sounds like I'm going to be in the market for a replacement boot rom, anyone know my best bet for this in the UK?
Thanks all
Anthony
----------------------------------------
hope u can find a N Boot to test it first / expensive to purchase KIT online ( 1,500>2,000)/
Maybe from a junker printer wholesaler shop
u could test with a C BOOT> just to see if Main board & HDD is good (remove UFR Board) when testing with "C" BOOT
**Knowledge is time consuming, exhausting and costly for a trained Tech.**
Comment