This is running the following Windows version:
Windows 10 Home
OS Build 18362.418
For some reason it thinks it was installed on 10/12/2019, but it's a lot,
lot, older than that.
On Mon, Nov 4, 2019 at 5:26 AM RakshithM_16 <firstname.lastname@example.org>
Some additional information -
The Windows instance that this does work on is running Windows 10 Home version 1803. I'd give you the build, but since I forgot and left the laptop on during the day Microsoft is currently updating it to 1903, so we'll have to see what happens.
Regardless of the Windows version, I keep the source and workspace files on a shared drive on my Linux machine. Up until now that hasn't been an issue. However...
Just for the heck of it, I copied the workspace directory over to the local directory of my Windows virtual guest. It essentially moved from Y:\soandso to C:\Users\Scott\Documents\soandso. Once I copied the files from the shared drive to the C: drive, then it started working.
At this point I'm guessing that it has something to do with the Oracle Virtualbox extensions that provide the access to the shared drive. I have been able to duplicate this with multiple workspaces. So...
Running PSoC Creator 4.2 works on the virtual guest as long as the workspace files are considered local to the guest Windows OS. If the files are on a shared drive, they can be accessed, edited, etc., but the Code Outliner has issues with them and PSoC Creator crashes. So I'll just have to copy the files back and forth when I update Github or if I want to use one machine for programming the firmware on the PSoC and another for editing/compiling the code.
It seems to work without issue using a network share over WiFi. Just the Virtualbox share fails. It looks like this question can be closed out, as the prompt to obtain the Windows version made me think about just how I am accessing these files.