virtualbox.org

I have successfully used vbox on many pc's for several years now and LOVE the product.

I am running it on windows to host linux and running uit on linux to host windows!

as a matter of fact at home I have my wifes PC (a duo core home brew) running Mandriva 2009.1 kde4 with VBOX all day and all night.

somewhere i9 did something (or a LOT of somethings) wrong on MY pc.

I have an amd quad core home brew with Mandriva 2009.1 as well.

I went to install the OSE from the mdv repos since i was in a hurry and something went wrong (been so long i dont remember exactly what)

so i removed OSE (or thought I did) and downloaded it straight from here and ran into a series of issues, the guys in the MDV forums have been helping me out a LOT.

Currently I have the OSE completely uninstalled, BUT during my attempts at resolution one suggestion was that I use the "all distros version which is run from the cli as: everything said it went fine, i went to perform the setup and it failed.

so now I have 2 options.

completely scrub all evidence of vbox and start over again, or scrub the OS and start the pc from scratch.

I have a seperate /home partition so I'm not completely adverse to that, but would rather it be a last resort.

however (and this is my Linux CLI ignorance) how does one UNINSTALL a xxxx.run file?

I tried: only to be told that -uninstall is an invalid switch

so please if ANYONE can tell me how to uninstall that I would DEEPLY appreciate it.

I've tried urpme but since it didnt go through the typical RPM install that has no record of it.

all suggestions gratefully attempted!

j

Double dash. You can find out what options are available through --help. Usually, parameters with single dash use single character, double dash is whole word. When I'm not sure, I always run --help, that at least works or shows how to get some help .

wow now i do feel stupid

thanks

How long have you been using Linux? If it's more than a year, then yeah, you should feel stupid . Else, beginners error.

unfortunately, off and on for over 5 years.

thing is that although I venture out into other distros on a regular basis, 90% of my time is in Mandriva/mandrake and their repos are so full their isnt a whole lot of xxx.run packages out there that i have needed to use.

But thanks for that one, i looked through 5 different linux reference books (including 1 on bash and 1 on CLI) and found zero references.

but I do have to remember the --help

interesting was, my "error" actually gave me a screenful of "options" but --uninstall wasnt one of them

well thats what i like about Linux, always learning!

now if you have LOTS of spare time and wanted to look here:

http://forum.mandriva.com/viewtopic.php?t=116370

at my challenges installing vbox on my pc, i am open to any ideas.

shame is I have it successfully installed on 3 different windows pc's (2k,xp,w7) in my house, Fedora and another MDV2009.1

my personal pc however, bah why would it want to work THERE!

Ok, just a question, which architecture are you running? 32 bit or 64 bit? And which architecture package did you install? You can't run 32 bit VB on 64 bit Host.

straight 32bit on an amd 9950

i know I could/should move to 64, but having worked w/ MDV's 64 bit versions in the past I havent ever found any benefits

ALTHOUGH if my employer starts moving more towards VM (already our 3rd largest app is moving to a Linux server) I may need to just to stay current

j

I tried to get Mandriva to install inside VB, to test the installation of VB inside MDV, but that darn thing didn't even want to boot the installer. The one time that it did boot into the installer, it hung before it could do any installer things. Just the basic questions about keyboard, language, time were done, then bam, 100% cpu usage and nothing. I don't like MDV, and from what I've heard, there are too many issues with it (too buggy). Figure this is the same kind of situation now.

Guys which version of Mandriva are you using?
I know that mine had the VBox Client installed by default and that might be causing some problems. See Screen shot of the version that I am using.

Same ISO as you Perry. It won't even install, right after I select the keyboard, it goes to CPU overload. I can still switch between TTY's (1, 7 and 12 are the only ones that have something), but the installer stays with a white screen. I'm never gonna touch Mandriva again. Wiping the ISO from my hard drive now.

Wow. I must be blessed. Install for me went easy and I was finally impressed with the way they have it working. Still AFAIAC they do have a ways to go. I even installed the VB OSE program inside to see if it confused anything. It asked which kernel I wanted and then finished the install. Oh well I will enjoy what I have for now.

I use the KDE vesion for the US.

Although as I said, my wifes PC (other than the HW) mirrors mine, so its not MDV, I'm sure its just something I did in the setup.

as for the OSE, I'm specifically trying NOT to use that one, because I need to install the guest additions for file sharing

My wifes MDV pc will run VBOX all day long with everything from puppy linux to windows as Guest OS's

Mine on the other hand?

well vbox loads, it even lets me setup a new guest s, but on execution I get the 1908 error

and then the fun begins!

well now i dont feel so bad

--uninstall didnt work either

[root@localhost mindwave]# sh VirtualBox-3.0.4-50677-Linux_x86.run --help
Makeself version 2.1.5
1) Getting help or info about VirtualBox-3.0.4-50677-Linux_x86.run :
VirtualBox-3.0.4-50677-Linux_x86.run --help Print this message
VirtualBox-3.0.4-50677-Linux_x86.run --info Print embedded info : title, default target directory, embedded script ...
VirtualBox-3.0.4-50677-Linux_x86.run --lsm Print embedded lsm entry (or no LSM)
VirtualBox-3.0.4-50677-Linux_x86.run --list Print the list of files in the archive
VirtualBox-3.0.4-50677-Linux_x86.run --check Checks integrity of the archive

2) Running VirtualBox-3.0.4-50677-Linux_x86.run :
VirtualBox-3.0.4-50677-Linux_x86.run [options] [--] [additional arguments to embedded script]
with following options (in that order)
--confirm Ask before running embedded script
--noexec Do not run embedded script
--keep Do not erase target directory after running
the embedded script
--nox11 Do not spawn an xterm
--nochown Do not give the extracted files to the current user
--target NewDirectory Extract in NewDirectory
--tar arg1 [arg2 ...] Access the contents of the archive through the tar command
-- Following arguments will be passed to the embedded scrip

Then a simple "uninstall". It was one of the two.