Okay, eStudio 232 won't print ... I find out the NIC part of the SYS board is bad so I order a new SYS board.
Customer is anxious and wants the machine running NOW.
I find a freight damaged eStudio 232 in our shop that only has damage to the scanner section. I remove the SYS board and take it to the customer's location.
I install the new SYS board. I take the NVRAM, HDD, memory module, and cabling from the "old" SYS board and put it on the "new" SYS board I just installed.
I put firmware version 329 on my USB thumbdrive, do the 4 9 thing, select total update, and let it rock and roll. Firmware update completes without a hitch.
NOW FOR THE GOOD PART
I now need to initialize the NIC with 08 1119 and 947. I hold down 0 and 8 while powering on ... hear the little beep and let go of the keys. I get the usual 100% in the upper left corner, but just below it is the message:
machine type load ERROR
long press ENERGY SAVER key
At this point I turned the machine off and went into 05 mode with no problem. I turned the machine off and back on without any mode and it came to READY. I made copies, it received faxes, but the network will not initialize because I have not been able to get into 08 mode to initialize it.
I tried reloading the firmware again ... same result.
Okay ... I've had enough, so I call Toshiba tech support and talk to Brent (who is my favorite operator there). He suggest that I regress back to version 300, do NVRAM reset, then bring the copier back up to version 329. Sounds good to me.
I load version 300 on my USB thumb drive, but when the display comes up it only gives me the option for SYS and HDD. I know something is amiss, so call tech support back.
This time I get Russel (he's pretty helpful most of the time). He tells me that, no, all the options should be available if you are regressing the firmware. He suggest that maybe my firmware files are bad, corrupted, or whatever and that I should download the firmware again. So I do ... same result
I ran out of time at the customer's office, so I am now at a bit of a loss as where to go from here. I will call tech support again if I have to, but I'd like to be armed with some better ideas if anyone has any.
Thanks
Customer is anxious and wants the machine running NOW.
I find a freight damaged eStudio 232 in our shop that only has damage to the scanner section. I remove the SYS board and take it to the customer's location.
I install the new SYS board. I take the NVRAM, HDD, memory module, and cabling from the "old" SYS board and put it on the "new" SYS board I just installed.
I put firmware version 329 on my USB thumbdrive, do the 4 9 thing, select total update, and let it rock and roll. Firmware update completes without a hitch.
NOW FOR THE GOOD PART
I now need to initialize the NIC with 08 1119 and 947. I hold down 0 and 8 while powering on ... hear the little beep and let go of the keys. I get the usual 100% in the upper left corner, but just below it is the message:
machine type load ERROR
long press ENERGY SAVER key
At this point I turned the machine off and went into 05 mode with no problem. I turned the machine off and back on without any mode and it came to READY. I made copies, it received faxes, but the network will not initialize because I have not been able to get into 08 mode to initialize it.
I tried reloading the firmware again ... same result.
Okay ... I've had enough, so I call Toshiba tech support and talk to Brent (who is my favorite operator there). He suggest that I regress back to version 300, do NVRAM reset, then bring the copier back up to version 329. Sounds good to me.
I load version 300 on my USB thumb drive, but when the display comes up it only gives me the option for SYS and HDD. I know something is amiss, so call tech support back.
This time I get Russel (he's pretty helpful most of the time). He tells me that, no, all the options should be available if you are regressing the firmware. He suggest that maybe my firmware files are bad, corrupted, or whatever and that I should download the firmware again. So I do ... same result
I ran out of time at the customer's office, so I am now at a bit of a loss as where to go from here. I will call tech support again if I have to, but I'd like to be armed with some better ideas if anyone has any.
Thanks
Comment