Hi there! Apologies for not providing more details. Host OS: Windows 10 64-Bit (Intel i5 CPU) Emulated OS: RiscOS 3.71 Settings: Default (2MB VRAM, 32MB RAM)
After more in-depth testing, it appears to be an issue with the UniBoot2 archive from https://www.retro-kit.co.uk/user/custom/Software/Acorn/RISCOS/UniBoo2.zip when !Boot or !Run gets executed whether it be at boot time, via display of the directory or directly. To reproduce: Install fresh copy of RPCEmu 0.8.100 and add RO3.71 ROM Add UniBoot2 to the root of HostFS Run !Boot or !Run by any method Behaviour for each HW configuration (apart from Phoebe) is as follows: Interpreter -------------- ARM610/710/StrongARM/A7000/A7000+: Works ARM810: RPCEmu Fatal Error - Bad LDRH/STRH opcode 0000ADB8 Recompiler ---------------- StrongARM: Works ARM610/710/A7000/A7000+: RiscOS locks up (although the mouse pointer *usually* remains working) ARM810: Some garbled RiscOS error box that just recurs if you try to cancel it - rpc.cfg - =============================================================== [General] bridgename=rpcemu cdrom_enabled=1 cdrom_iso= cdrom_type=0 cpu_idle=0 ipaddress=172.31.0.1 macaddress= mem_size=32 model=RPC610 mouse_following=1 mouse_twobutton=0 network_type=off refresh_rate=60 sound_enabled=0 stretch_mode=1 username= vram_size=2 =============================================================== - rpclog.txt - =============================================================== localtime: 2018-01-02 01:07:31 gmtime: 2018-01-02 01:07:31 RPCEmu 0.8.100 VERY SECRET EDITION [DYNAREC NO_DEBUG] Build: 32-bit binary Compiler: GCC version 4.9.2 OS: Microsoft Windows OS: PlatformId = 2 OS: MajorVersion = 6 OS: MinorVersion = 2 OS: ProductType = 1 OS: SuiteMask = 0x100 OS: ServicePackMajor = 0 OS: ServicePackMinor = 0 OS: ProcessorArchitecture = 9 OS: SystemMetricsServerR2 = 0 OS: ProductInfoType = 48 QT5: 5.6.2 Number of screens: 1 Primary screen: \\.\DISPLAY1 Information for screen: \\.\DISPLAY1 Resolution: 1920 x 1080 Colour depth: 32 Working Directory: D:\Emu\Acorn\RPCEmu_Test Host CD/DVD Drive (F:)romload: Loaded 'risocs-3.71.rom' 4194304 bytes romload: Total ROM size 4 MB romload: ROM patch applied: 8MB VRAM RISC OS 3.71 plt_sound: qt5 Audio Device: Speakers (Realtek High Definition Audio) plt_sound: qt5 Audio Codecs Supported: 1 0: audio/pcm plt_sound: qt5 Audio SampleRates Supported: 10 0: 8000 1: 11025 2: 16000 3: 22050 4: 32000 5: 44100 6: 48000 7: 88200 8: 96000 9: 192000 initpodulerom: Successfully loaded 'hostfs,ffa' into podulerom initpodulerom: Successfully loaded 'hostfsfiler,ffa' into podulerom RPCEmu: Machine reset RPCEmu: Machine reset complete HostFS: Registration request version 3 accepted =============================================================== Kind Regards, James On 1 January 2018 at 15:59, Peter Howkins <[email protected]> wrote: > On Sun, Dec 31, 2017 at 02:05:45PM +0000, J Percival wrote: > > Also just noticed that HostFS access crashes the recompiler except for > > CPU=StrongARM but it's not a regression as it does so in 0.8.15 as > well. > > Erm, this doesn't happen here, as such let's try to reproduce it. > > - What do you mean by crash? Emulator exits? with or without error > message? emulator stops running (lock up)? Error reported in RISC OS? > something else? > - At which point does the 'crash' happen, on boot? on accessing a > particular file? something else? > - Which version of RISC OS are you running? > - What files have you put in HostFS, a boot sequence? which? something > else? > - What settings are you using for, memory, vram? > > Can you also post your rpc.cfg and rpclog.txt files. > > > Think you must already be aware of it > > This isn't directed at you particulaly, but to all users of rpcemu. > > We really really need people to report all the bugs they find, there are > so many potential configurations and pieces of software out there that we > can't run everything, as such the chances are that we're not aware of it. > > But every good bug report stands a very good chance of being fixed which > makes everyone's life a little better. > > Even if you figure out a workaround (e.g. change setting to something > else) please still report the original issue. > > > is there a list of known issues somewhere? > > There isn't at the moment, I'll look into adding one. > > Peter > > -- > Peter Howkins > [email protected] > > _______________________________________________ > Rpcemu mailing list > [email protected] > http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu >
_______________________________________________ Rpcemu mailing list [email protected] http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
