(09-16-2018, 04:19 PM)mothered Wrote:

(09-16-2018, 12:17 PM)vex. Wrote:

(09-16-2018, 11:13 AM)mothered Wrote: The latest version of VMware Workstation.

Although I'm quite confident you do not require assistance, If you decide to make the switch and are In need of help (example bridged connections/networking, mapping network drives etc), let me know.

You may also wish to checkout "Hyper-V", which Is a native VM on supported Windows operating systems- server versions & editions Inclusive. However, the CPU of your Host (physical machine) must support SLAT (Second Level Address Translation). It will not function without a supported OS & CPU.

I got it all installed, I'll play with the VMs a bit after my exams this week, see if ParrotOS works this time. Thank you for the link!

Just going to mention, I just Googled a key, and out of curiosity, VMware don't check a database to see if a key has been used? I saw comments on a 40 thousand viewed video and they were certain the key would work. I had to try it, and what you know, it worked...  I'm not advocating piracy,  but 10 serial keys were shown, Why would they still allow these keys to be used?   How can these keys still be functional? I'm so confused

You're welcome.

It's good to read you have It all up and running. As with MBAM (Malwarebytes), VMware's EULA does not allow you to use the same license key on another Workstation, but It doesn't (obviously) prevent you from doing so. As opposed to Adobe, VMware's activation servers do not check the reuse of keys, hence there's an abundance floating around the net. I'm not aware of how they operate Internally, but I assume sooner or later they'll catch on and start cracking down on the distribution of keys.

(09-17-2018, 11:10 AM)mothered Wrote:

(09-17-2018, 07:53 AM)darkninja1980 Wrote:

(09-17-2018, 07:19 AM)mothered Wrote: Generally, 32GB sticks. But 128GB Is also available.

Of course, the MOBO has to accommodate It.

which motherboards do support 128 GB?

I've yet to look Into It.

There's no reason to. 128GB Is hardly used In a personal environment.

(09-17-2018, 04:09 PM)vex. Wrote: Also, I saw you use ParrotOS on another post. How did you get it installed? Im always getting install errors (they love to give no error codes) I am using the 64bit, were you using it as 32bit or just using live desktop?

(09-17-2018, 09:21 PM)mothered Wrote:

(09-17-2018, 04:09 PM)vex. Wrote: Also, I saw you use ParrotOS on another post. How did you get it installed? Im always getting install errors (they love to give no error codes) I am using the 64bit, were you using it as 32bit or just using live desktop?

It's not a Live OS, I Installed Parrot and It Is the 64 bit.

Exactly what errors are you experiencing, and at what stage of the Installation?

Spoiler:

(09-18-2018, 07:00 AM)vex. Wrote:

(09-17-2018, 09:21 PM)mothered Wrote:

(09-17-2018, 04:09 PM)vex. Wrote: Also, I saw you use ParrotOS on another post. How did you get it installed? Im always getting install errors (they love to give no error codes) I am using the 64bit, were you using it as 32bit or just using live desktop?

It's not a Live OS, I Installed Parrot and It Is the 64 bit.

Exactly what errors are you experiencing, and at what stage of the Installation?

Spoiler:

I'm not sure why, tried both 32bit and 64, both VMware and Virtual Box, both had the same problem. I'm currently at collage and used their Virtual Machines to be sure it wasen't my own hardware.

(09-18-2018, 07:00 AM)vex. Wrote:

(09-17-2018, 09:21 PM)mothered Wrote:

(09-17-2018, 04:09 PM)vex. Wrote: Also, I saw you use ParrotOS on another post. How did you get it installed? Im always getting install errors (they love to give no error codes) I am using the 64bit, were you using it as 32bit or just using live desktop?

It's not a Live OS, I Installed Parrot and It Is the 64 bit.

Exactly what errors are you experiencing, and at what stage of the Installation?

Spoiler:

I'm not sure why, tried both 32bit and 64, both VMware and Virtual Box, both had the same problem. I'm currently at collage and used their Virtual Machines to be sure it wasen't my own hardware.

(09-18-2018, 08:40 AM)mothered Wrote:

(09-18-2018, 07:00 AM)vex. Wrote:

(09-17-2018, 09:21 PM)mothered Wrote: It's not a Live OS, I Installed Parrot and It Is the 64 bit.

Exactly what errors are you experiencing, and at what stage of the Installation?

Spoiler:

I'm not sure why, tried both 32bit and 64, both VMware and Virtual Box, both had the same problem. I'm currently at collage and used their Virtual Machines to be sure it wasen't my own hardware.

Given you've tried both architectures (separate ISOs), I doubt they're causing the Issue.

I assume you're trying the same ISOs at your college.
Please advise of the outcome.

(09-18-2018, 08:59 AM)vex. Wrote:

(09-18-2018, 08:40 AM)mothered Wrote:

(09-18-2018, 07:00 AM)vex. Wrote:

Spoiler:

I'm not sure why, tried both 32bit and 64, both VMware and Virtual Box, both had the same problem. I'm currently at collage and used their Virtual Machines to be sure it wasen't my own hardware.

Given you've tried both architectures (separate ISOs), I doubt they're causing the Issue.

I assume you're trying the same ISOs at your college.
Please advise of the outcome.

Yes, figured out how to get the ISO installed today.
So, this is for VirtualBox. The three things I changed were: I disconnected the Floppy Disk then added the network in settings. Then when creating space for the ISO, I made the virtual machine to have 20GB instead of the default 8GB. This must've caused an overflow of cache and expanding uncompressed files for the installation, this explains crashes happening at around 75%,

I'll replicate this when I get home with VMware, but I'm now certain this is why it was happening.

(09-18-2018, 09:41 AM)mothered Wrote:

(09-18-2018, 08:59 AM)vex. Wrote:

(09-18-2018, 08:40 AM)mothered Wrote: Given you've tried both architectures (separate ISOs), I doubt they're causing the Issue.

I assume you're trying the same ISOs at your college.
Please advise of the outcome.

Yes, figured out how to get the ISO installed today.
So, this is for VirtualBox. The three things I changed were: I disconnected the Floppy Disk then added the network in settings. Then when creating space for the ISO, I made the virtual machine to have 20GB instead of the default 8GB. This must've caused an overflow of cache and expanding uncompressed files for the installation, this explains crashes happening at around 75%,

I'll replicate this when I get home with VMware, but I'm now certain this is why it was happening.

Good to read. You should be good to go.

I always set the VHD on the VM to 20GB at the minimum (depending on what I plan to Install), and Increase the Ram anywhere between 3-4GB. I have the hardware to well and truly run maximum specs on quite a few simultaneous VMs.