In article <CAJjzs2Cvz3RE6WGHHj9eAALmDc5gJQLDM62YiJV-sfBB8H=o...@mail.gmail.com>, Matthew Howkins <[email protected]> wrote: > On 5 December 2015 at 06:40, Dave Symes <[email protected]> wrote:
> > Win 7 Pro 64 bit SP-1 > > RPCEmu 0.8.13 and RISC OS 6.20 > > The cmos.ram file that resides in the RPCEmu appdir has become > > corrupted twice in the recent few days and I have no idea why. > > > > I've saved a copy of the corrupted cmos.ram file and after putting it > > and the good version in Zap... There are differences, but to be honest > > I have no idea what the differences mean, except Corrupted. > > > > Any kind person able to read this stuff and say "Ah your grommet was > > not configured correctly" or whatever? > > > > They are in an archive on http://www.triffid.co.uk/dstuff/Seemoss.zip > > > I have downloaded your CMOS ram files, and tested them. I found I could > succesfully boot RISC OS 6.20 with both of them - i.e. including the > 'corrupt' file. > You'll need to explain what you mean by 'corrupted', how these files came > about, and what problem(s) you're getting with them. > Please include a copy of your rpclog.txt file which will help us > reproduce your set-up more accurately. > Thanks > Matthew Oh yes, I'd forgotten about that... Thanks for the note Matthew. It appears, an app I was testing for someone (Sorry NDA) was causing some unusual difficulties. App now sorted, and difficulties gone. Thanks Dave -- Dave Triffid _______________________________________________ Rpcemu mailing list [email protected] http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
