I totally concur with everyone who has said that the rung with the MUL on it is not getting executed, or there is a condition on the rung which makes it false.
You say that when your F70:35 is zero, and you type a number into the destination address N300:3, it stays there.
That tells me that the MUL is not writing to it, so the rung is either false, or it is not being scanned.
If we assume that the MUL rung has Logic Continuity (i.e. it evaluates as true), then here's some other things to look for.....
Is it in a subroutine that stops being called when your F70:35 is zero? (the subroutine code will not be scanned)
Is it in a subroutine that has (above it) a RET instruction that gets enabled when your F70:35 is zero? (anything after a true RET will not get scanned)
Is it in a subroutine that has (above it) a TND instruction that gets enabled when your F70:35 is zero? (anything after a true TND will not get scanned)
Is the rung skipped by a JMP instruction when your F70:35 is zero?
Is the rung inside an MCR zone that is activated when your F70:35 is zero?
In PLC5 there are no restrictions on data-types in the math instructions.
Yes, you can have 0 as Source A (either an address or a literal).
Yes, you can have 0 as Source B (either an address or a literal).
Yes, you can mix data-types (eg. float and integer) in any of the Source or Destination fields. The processor performs the maths at the highest level of the data-types, then (if it needs to) converts the result for storage into the destination.