On Tue, Mar 17, 2009 at 03:39:48PM +0100, jan rinze wrote: > Ok, so you have the same results. > Does anyone here know why the module hangs? or where?
I've looked into it. EtherRPCEm (IIRC) hangs on a real RO4.39 RPC, so I'm fairly sure the problem is in the module. First I thought it was the callback veneers, but replacing with those in the EtherY module (from which EtherRPCEm is derived, and runs OK on RPCEmu/RO4.39 even if there's no Castle Ethernet hardware) shows it doesn't make any difference. Then I thought there was something up with the service call handler, but service calls seem to be despatching OK. AFAIK it's something happening /after/ a service call is received, but given the DCI4 startup process is replete with service calls this doesn't help that much. What I don't understand is what's changed since 4.02 (and couldn't see anything notable in the logs). Theo _______________________________________________ Rpcemu mailing list [email protected] http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
