[Virtualacorn-list] Incompatible host

[T.O.M.S.]

Hello Folks

I've been following the most recent posts on this thread and I hope y'all 
won't mind if I stick my hooter in. What has already been said has made good sense since the early days of VirtualRPC - BUT can I stress that there have been several important changes/updates in recent years. Having discussed these topics very recently with Aaron (when Jim Nott'num 
and I were updating both the VirtualPPC booklets in late-2018). Aaron wished us 
to spell out the current situation.

In brief, there was a significant change to the 'official' location of 
VirtualRPC in the 2014 update (when the silver discs were replaced by white 
discs). This is covered in detail in Support Article No. 133 on 
http://www.virtualacorn.co.uk/support/articles/133/index.htm  

Most importantly, please note that, at the bottom (under 
'Change to VirtualRPC default installation path'), the article specifies that 
VirtualRPC should no longer be installed in the 'old' C:\Program 
Files\VirtualAcorn\VirtualRPC-xxx  folder but in the 'new' location at 
C:\VirtualAcorn\VirtualRPC-xxx 

That was and still is the 'official' line from VirtualAcorn. Aaron asked us to 
stress this as 
it's clear he is having to spend considerable time and effort helping punters sort out problems due to the location of their *working* installation not being as specified, for example putting it in the root of drive C:  At least some of these later problems arise from the way Window 10 does things. 

If you want further details on the above. please refer to the very latest info in the 2 red boxes on page 29 in the VirtuallRPC In Use companion *Supplements* booket (Edition 3 dated December 2018) available for download on http://www.virtualacorn.co.uk/support/vrpcinuse/index.htm

Another point of concern to Aaron is that several punters have run into major problems by separating the main 'HardDisc4' folder from the rest of their VirtualRPC installation folder and putting it elsewhere. It took a while to suss out why they felt the need to do this but certainly in 2 cases (there may be more) this was a simple misunderstanding between Megabytes and Gigabytes. Specifically, their host PCs contained a 128/256 *GB* SSD as drive C;: - and they didn't 
want the drive to be swamped by RISC OS user-documents etc. When it was pointed 
out that even a very busy VirtualRPC installation was unlikely to exceed 10-20 
GB, the penny dropped.

So to summarise: To avoid problems, DO NOT SEPARATE the main HardDisc4 folder 
from the main VirtualRPC folder.  
  
I hope that helps to clarify the updated sitch.

Steve Johnson


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus