Taskalfa 300i HDD questions

[mrwho]

Good afternoon.

I'm mostly a Ricoh tech with some years back experience on Konica Minolta machines, but I'm fairly green with Kyocera.

I'm trying to fix a 300i with slowdowns and HDD errors. I've replaced the HDD with a not-new but good 160gb spare, but I've got a couple of questions:

Is the U024 hdd format simulation supposed to be instantaneous (as soon as I press the copy button it tells me to cycle the power - same with the U989 scan disk)

The hard disk square on the status screen is blank. Is this normal?

Thanks.

[mrwho]

To add insult to injury, not only the new HD solved the problem (the machine keeps hanging) but I also have a couple more problems to solve.

I'd like to ask for some more help, and as always I'm willing to trade, if needed:

- Would it be possible for someone to supply me with the firmwares for the 300i and 420i (another machine with similar problems at the same customer)?
- There's an error about some "optional font" when I turn on the machines after formating/replacing the HDDs (can't phrase it exactly, as it is not in english) - what should I do to overcome this?

Thanks once again.

[mrwho]

Don't know if anyone is following this, but here's a status update:

- On the 300i I decided to take note of the network settings and then I ran U021. After reboot, for good measure, I reinserted the network info and disabled the unecessary protocols (appletalk, netware, pop3, ftp client, etc). Before I did all of this the machine would hang a couple of minutes after power on - now it (still) didn't hang. Unfortunately everyone near it in the office already went home, so I got nobody to test it atm.

- On the 420i, the operator was trying to print, but the machine panel was irresponsive. Before powering off, I decided to pull out the network cable, and - suprise! - the panel started to respond to input again! I connected the cable again - panel froze. I disconnected the cable - panel responds. Cable on - freeze. Cable off - responds. I tried this several times and the effect was always the same! So I decided not to do the U021 yet, and just disabled the unneeded protocols, which seemed to stop the "panel freeze while network cable is on" situation.

Both of these situations are still under observation.

Never had any of this on Ricoh/KonicaMinolta machines, so I'm learning how to ride a bike again! Any observations from whoever might be reading this?

Thanks again!

[mrwho]

Captain's log 1980 hours, suplemental.

I'm tired of this for today, I'm going home.

The 300i froze once again with F000 (it wasn't visible before because the machine would go into suspension and then would freeze with the screen off and it wouldn't wake up unless we cycled the power.

I can't access the 420i now, but I'm assuming it's in a similar situation, because I can't access it via web but it responds to pings.

Thanks to those who read this.

Over and out.

[blackcat4866]

My guess is that you've got something on the network broadcasting data to all the IP addresses. This non-print data can logic-lock the machine, or give you a variety of CFxxx codes.

What you can do is:
Bring your laptop. Connect the MFP directly to you laptop via crossover cable. Print, scan, whatever. If everything works you've got some data hitting the printer's IP that it doesn't like. Sometimes it helps to change the IP of the printer, and in the driver. I've accidentally created this situation with PrintFleet copy count collection software.

Once you've proved the data source is on their network your part is finished. =^..^=

[mrwho]

My guess is that you've got something on the network broadcasting data to all the IP addresses. This non-print data can logic-lock the machine, or give you a variety of CFxxx codes.

What you can do is:
Bring your laptop. Connect the MFP directly to you laptop via crossover cable. Print, scan, whatever. If everything works you've got some data hitting the printer's IP that it doesn't like. Sometimes it helps to change the IP of the printer, and in the driver. I've accidentally created this situation with PrintFleet copy count collection software.

Once you've proved the data source is on their network your part is finished. =^..^=

Thank you very much for your reply. That thought had ocurred to me, specially because we have two different machines with similar symptoms.

But, with that in mind, yesterday, before I left home, I took out the network cable and asked the IT tech to go there first thing in the morning and tell me if it gave any code - which he told me it did.

Of course there's always the chance someone went and plugged the cable before that - but we placed there two Ricoh loaners in the meantime and I took the 300i to our workshop. I will now plug it to the power outlet and let it sit undisturbed during the rest of the day and see how it fares.

Thanks again. Will update.