From owner-freebsd-questions Sun May 21 10:59:11 2000 Delivered-To: freebsd-questions@freebsd.org Received: from blues.jpj.net (blues.jpj.net [204.97.17.146]) by hub.freebsd.org (Postfix) with ESMTP id AB09D37BAB2 for ; Sun, 21 May 2000 10:59:02 -0700 (PDT) (envelope-from trevor@jpj.net) Received: from localhost (trevor@localhost) by blues.jpj.net (right/backatcha) with ESMTP id e4LHwsk26629; Sun, 21 May 2000 13:58:54 -0400 (EDT) Date: Sun, 21 May 2000 13:58:54 -0400 (EDT) From: Trevor Johnson To: Cliff Rowley Cc: freebsd-questions@FreeBSD.ORG Subject: Re: VMWare 2, then VMWare 1 - Ack! In-Reply-To: <20000521182756.A10530@onsea.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > When starting vmware2, I get the following: > > ----------- > Error: > Cannot open vmware executable file. > Possibly an installation error? > Cannot create splash screen > ----------- > > And when trying to run a vm: > > Could not open /usr/local/lib/vmware/lib/vmm > > I guessed vmware2 may be broken under 4.0-STABLE as it stands, so I deinstalled that and reinstalled vmware1. > > Exactly the same thing happens. I've deinstalled and reinstalled a few times, and I've cleaned up everything I've found relating to vmware, and still it doesnt work. > > Any ideas? I've searched the archives, and noone seems to answer these questions. You didn't mention whether you were using the port. If you were, and your system wasn't suitable for running vmware, "make" would warn you: .if ${OSVERSION} < 400013 BROKEN= "Systems prior to 400013 is out of support" .endif .if !defined(HAVE_LINPROCFS) && !exists(/modules/linprocfs.ko) && !exists(${PREFIX}/modules/linprocfs.ko) BROKEN= "This software absolutely requires Linux procfs support" .endif -- Trevor Johnson http://jpj.net/~trevor/gpgkey.txt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message