VMWare Player

[mike_ekim]

The installation iso doesn't work for me, it just hangs on the bootup flower screen. Can someone provide a VMWare image of the latest version compatible with the VMWare Player? This is an awesome tool that lets people try applications without installing or configuring anything.

Mike

[sblevin]

Kris has said that he would be happy to host a VMWare player image if someone wants to make and upload one.

If someone with the full VMware wants to do it, or has any questions about how they should create a default image, I'd be happy to make some suggestions. I've got a whole SLEW of vmware installs of PC-BSD running here and they are great. Maintaining the public download is just the "one more thing" I don't want to get involved with right now.

A VMware PC-BSD install, with a 10GB hd image should zip up to about the same size as the ISO download. My rc1 install with 10GB HD image (not fully allocated at creation) zips to 548 MB.

[Aaron2]

A clean vmware image would be great to use for testing pbi's too.

[AlphaX]

Ive got Vmware Workstation and have made a virtual machine image of pcbsd if anybody wants it, its about 385 mb compressed bz2.

I dont have a server to host it though, so if someone has a dedicated server who is willing to host it I will upload it.

[erik]

I have vmware5 up and going as well. Let me know what I can do to help.

[Romerican]

So, who is Kris? Maybe someone who knows Kris can tap Kris on the shoulder... and get these folks a place to upload their images.

I'd like to play with one. =]

[AlphaX]

Kris is the founder and creater of PC-BSD, I just sent him an email the other day, so I should here something before to long. Unless he has something in the works on it himself...

[SunnyB]

VMware images are easy to setup if you have the HDD space.

I have just reloaded PCBSD 1.0rc2 in VMware 5.5.1 with a 10Gb
vhdd. I tried the 1.0rc2 patch and it hosed my 1.0rc1 install so
i started anew.

I would hesitate to share a working image because it would contain
my root and user password. In order to use a shared image it
could only have the most generic info in the setup and this would
need to be altered by the new user before it was usable.

Like the .vmdk and the .vmx files would need to be altered to reflect
the correct file and pathname on the new system. Then the username
and passwords would need to be changed by the enduser.

Also, the 5.5.1 images are not compatible with earlier versions so these
shared images would need to be made with VMware 4.5 or earlier
then the enduser would need to upgrade it to his version.