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

RPCEmu 0.8.9 [DYNAREC NO_DEBUG]
Build: 32-bit binary
Compiler: GCC version 4.6.1
OS: Microsoft Windows
OS: PlatformId = 2
OS: MajorVersion = 6
OS: MinorVersion = 1
OS: ProductType = 1
OS: SuiteMask = 0x300
OS: ServicePackMajor = 1
OS: ServicePackMinor = 0
OS: ProcessorArchitecture = 9
OS: SystemMetricsServerR2 = 0
OS: ProductInfoType = 3
Allegro version ID: Allegro 4.4.2, MinGW32
Host Colour Depth: 32
loadconfig: bridgename = "rpcemu"
loadconfig: cpu_idle = "1"
loadconfig: mouse_twobutton = "0"
loadconfig: network_type = "ethernetbridging"
loadconfig: mouse_following = "1"
loadconfig: cdrom_type = "72"
loadconfig: cdrom_enabled = "1"
loadconfig: blit_optimisation = "0"
loadconfig: refresh_rate = "60"
loadconfig: stretch_mode = "0"
loadconfig: sound_enabled = "1"
loadconfig: vram_size = "2"
loadconfig: cpu_type = "SA110"
loadconfig: mem_size = "256"
romload: Loaded 'ROM402' 4194304 bytes
romload: Total ROM size 4 MB
initpodulerom: Successfully loaded 'hostfs,ffa' into podulerom
initpodulerom: Successfully loaded 'hostfsfiler,ffa' into podulerom
initpodulerom: Successfully loaded 'SyncClock,ffa' into podulerom
RPCEmu: Machine reset
Tap-Win32: device name: rpcemu
Tap-Win32: device path: \\.\Global\{F8178C2D-0346-4469-A93A-BF05583FFF95}.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
RPCEmu 0.8.9 [DYNAREC NO_DEBUG]
Build: 32-bit binary
Compiler: GCC version 4.6.1
OS: Microsoft Windows
OS: PlatformId = 2
OS: MajorVersion = 6
OS: MinorVersion = 1
OS: ProductType = 1
OS: SuiteMask = 0x300
OS: ServicePackMajor = 1
OS: ServicePackMinor = 0
OS: ProcessorArchitecture = 9
OS: SystemMetricsServerR2 = 0
OS: ProductInfoType = 3
Allegro version ID: Allegro 4.4.2, MinGW32
Host Colour Depth: 32
loadconfig: bridgename = "rpcemu"
loadconfig: cpu_idle = "1"
loadconfig: mouse_twobutton = "0"
loadconfig: network_type = "ethernetbridging"
loadconfig: mouse_following = "1"
loadconfig: cdrom_type = "72"
loadconfig: cdrom_enabled = "1"
loadconfig: blit_optimisation = "0"
loadconfig: refresh_rate = "60"
loadconfig: stretch_mode = "0"
loadconfig: sound_enabled = "1"
loadconfig: vram_size = "2"
loadconfig: cpu_type = "SA110"
loadconfig: mem_size = "256"
romload: Loaded 'ROM402' 4194304 bytes
romload: Total ROM size 4 MB
initpodulerom: Successfully loaded 'hostfs,ffa' into podulerom
initpodulerom: Successfully loaded 'hostfsfiler,ffa' into podulerom
initpodulerom: Successfully loaded 'SyncClock,ffa' into podulerom
RPCEmu: Machine reset
Tap-Win32: device name: rpcemu
Tap-Win32: device path: \\.\Global\{F8178C2D-0346-4469-A93A-BF05583FFF95}.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_cleanupIn message <20130604155952.6078224C4A@orac.inputplus.co.uk> you wrote:

> Hi George,
[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.
>
> Cheers, Ralph.

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,

George

--
george greenfield