Re: [Rpcemu] Networking: an interesting discovery (I think)

On 7 Jun 2013, george greenfield <george.greenfield@tiscali.co.uk>
wrote:
> In message <20130604155952.6078224C4A@orac.inputplus.co.uk> you wrote:

[snip]

> > Don't know if this has already been attempted, but how about saving
> > off the log file, rpclog.txt?, after each of these attempts so you
> > or others can see if their differences explain why? If not, it
> > suggests more logging is required in some areas to catch problems in
> > the field.
>
> I attach 2 log files [rpclog_089-402-OK and rpclog_089-402-Fail], made
> from successive attempts to launch 089/402, the first failing to
> network, the second attempt (after PC reboot) succeeding. The only
> difference I can see is the last line in #-Fail, 'Tap-Win32:
> tap_cleanup', which doesn't exist in the, otherwise identical,
> successful log. HTH,

Not having RO 4.02, I launched RPECmu0810/RO439 when the underlying
Windows system was 'busy', causing the network connection to fail, and,
after quitting RPCEmu, copied rpclog.txt elsewhere. I then launched
RPECmu0810/RO439 when Windows appeared to be less busy, resulting in a
successful network connection, and again copied rpclog.txt.

SideDiff shows that the two rpclog.txt files are _identical_, both
ending with the lines, which are the same as George's (apart from the
absence of the last line in rpclog_089-402-OK):

RPCEmu: Machine reset
Tap-Win32: device name: rpcemu
Tap-Win32: device path: \\.\Global\{9E5E57C8-FE40-4391-BA42-4F7C3FBADDA6}.tap
Tap-Win32: File opened
Tap-Win32: version: 9.9.0
Tap-Win32: status set
Tap-Win32: tap_win32_overlapped_init done
Tap-Win32: Thread created
Networking available
RPCEmu: Machine reset complete
Path is \\.\E:
Opening \\.\E:
HostFS: Registration request version 1 accepted
Tap-Win32: tap_cleanup

No error is reported, and rpclog.txt states that 'Networking available',
even when the connection has failed.

I then installed Reporter 2.67a, and set it to log the boot sequence. In
both cases, fail and ok, no errors were reported.

Having set Reporter to monitor the Desktop, it listed the error 'Timed
out while connecting' (when the connection failed), but didn't indicate
what led to it. The error also appears in RO syslogs Errors as:

***Error***
Title : Error
Task : Unknown task
Message : Timed out while connecting

All very puzzling. Can anyone suggest how to identify the culprit?

Tony




_______________________________________________
Rpcemu mailing list
Rpcemu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu