installed on virtual machine in VBox
installed on virtual machine in VBox
I installed Everything from within a virtual machine running 64-bit Windows 8 Pro. It appears to be running fine when I give it the privilege of running as administrator. However, it sees the Host machine's hard drive only and does not see the VM's hard drive. Nor can I change what it sees by browsing from within its menu options. Is there something I can do to make it look at the hard drive of the guest, which is Windows 8? If this has been discussed and solved properly, please point me in the right direction because I did not see anything adequate. Thanks.
Re: installed on virtual machine in VBox
What virtual machine are we talking about here?
Re: installed on virtual machine in VBox
The VirtualBox by Oracle: https://www.virtualbox.org/
Re: installed on virtual machine in VBox
At this point I am inclined to say that the way I am trying to use Everything search tool does not work on a 64-bit Windows 8 Pro under the circumstances I have described. I have it installed in a folder that is on a network share mapped to a drive letter accessible to the VM's operating system. This drive is made accessible to the OS fine, and other programs on this same drive do run properly. However, the Everything Search tool appears to have issues when I try to run it. When I tried running it in the Windows compatibility troubleshooter while installed on the share, it said it was not a compatible program. When I try running it, a window opens saying that the path is not valid.
Re: installed on virtual machine in VBox
I haven't had much luck getting VirtualBox going, anything I run on it atm is just blue-screening..
It is odd that Everything can see the hosts hard drive and not the virtual machines hard drive.
This sounds like an issue with VirtualBox?
What type of Virtual hard disk did you use?
I have added support VirtualBox to my "things to do" list.
It is odd that Everything can see the hosts hard drive and not the virtual machines hard drive.
This sounds like an issue with VirtualBox?
What type of Virtual hard disk did you use?
I have added support VirtualBox to my "things to do" list.
Re: installed on virtual machine in VBox
I think there is some confusion in communication, and I am partly to blame if not completely. I tried to clarify the discussion in my last post, but I might not have done so adequately. I want to try again so not to create any unnecessary work for you, even though your last statement indicated that you may have found some other unrelated issues with Virtual Box.
In my first post I was wrong in saying "It appears to be running fine ...". It was installed in a shared folder, meaning of course that it was accessible to both the host and the guest (i.e., shared). When I was running it, I must have been doing so from the host, not from the guest, even though my intention was to make use of it only from the guest while it runs. However, since I was running it from the host inadvertently, it properly saw the host's directory because while running in a folder in the host, it is just a regular program and a regular drive. However, later, as I was trying to indicate in my last post, when I do in fact start it up within the guest while in this same folder, in this case the folder is now being accessed by the guest as a network share. And in this situation the program was not running at all. As I think about it more, I am of the opinion that Everything was not intended to be run over a network share remotely.
So the question , therefore, is whether Everything is supposed to be run from a network share? If I was trying to run the program in a way that it was not designed to be used, then there is not a problem with it, but there is a problem with my attempted method for using it. If this hunch is correct, then what I should be doing is installing it directly into the guest while somehow getting access to the file system on a network share, i.e., the shared folder's files. Does this make sense to you?
In my first post I was wrong in saying "It appears to be running fine ...". It was installed in a shared folder, meaning of course that it was accessible to both the host and the guest (i.e., shared). When I was running it, I must have been doing so from the host, not from the guest, even though my intention was to make use of it only from the guest while it runs. However, since I was running it from the host inadvertently, it properly saw the host's directory because while running in a folder in the host, it is just a regular program and a regular drive. However, later, as I was trying to indicate in my last post, when I do in fact start it up within the guest while in this same folder, in this case the folder is now being accessed by the guest as a network share. And in this situation the program was not running at all. As I think about it more, I am of the opinion that Everything was not intended to be run over a network share remotely.
So the question , therefore, is whether Everything is supposed to be run from a network share? If I was trying to run the program in a way that it was not designed to be used, then there is not a problem with it, but there is a problem with my attempted method for using it. If this hunch is correct, then what I should be doing is installing it directly into the guest while somehow getting access to the file system on a network share, i.e., the shared folder's files. Does this make sense to you?
Re: installed on virtual machine in VBox
Sorry for the misunderstanding.
I would recommend installing Everything directly on the virtual machine.
You can run "Everything" from a remote folder..
However, if Everything does not have write access to this folder no settings or database will be saved.
You can override the ini location with -config <filename.ini> and the database with -db <database location>
I would recommend installing Everything directly on the virtual machine.
You can run "Everything" from a remote folder..
However, if Everything does not have write access to this folder no settings or database will be saved.
You can override the ini location with -config <filename.ini> and the database with -db <database location>