Virtualbox and Windows 7

Technical issues/questions of an intermediate or advanced nature.
beny
Full of knowledge
Full of knowledge
Posts: 728
Joined: 02 Jan 2011, 11:33
Location: italy

Re: Virtualbox and Windows 7

Post#46 by beny » 04 Jan 2017, 18:10

well after 550 mb of software installed i do not have qt inside my system, wine there is in, but not want to open i have used the usm list to check the version with no luck.

Jack
Contributor
Contributor
Posts: 1081
Joined: 09 Aug 2013, 14:25
Distribution: Porteus 3.2.rc5 Mate 64 bit
Location: Marysville, OHIO USA

Re: Virtualbox and Windows 7

Post#47 by Jack » 04 Jan 2017, 19:45

beny wrote:hi jack i use usm 3.20 version so the repository is of the 14.2 version you do not have usm? well i think if you use an old porteus version maybe with the packages check you are in trouble
Here is my version I'm using.
Image


I'm running right now the boot up is from v3.2rc5 but the 001 002 and 003 is part of v3.2.2. I'm doing this to test it because I can't just boot up the new release of v3.2.2 Mate it just hang up.
I just like Slackware because I think it teach you about Linux to build packages where Ubuntu is like Windows you just install programs you want.

User avatar
Ed_P
Contributor
Contributor
Posts: 3207
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Virtualbox and Windows 7

Post#48 by Ed_P » 04 Jan 2017, 20:38

The USM version in 3.2.2 is 3.20.

Code: Select all

guest@porteus:~$ su
Password: 

root@porteus:/home/guest# usm -v
 You are using USM version:  3.2.0

root@porteus:/home/guest# ./bootdev.sh
System Memory:   173M
Boot device:   /mnt/sda5
Boot device format: "ntfs" 
Boot folder:   /porteus3.2/
Boot mode:     ISO /ISOs/Porteus-CINNAMON-v3.2.2-x86_64.iso
OS:       Porteus-v3.2.2
ARCH:     x86_64
Kernel:   Linux porteus 4.9.0-porteus

Ed

User avatar
francois
Contributor
Contributor
Posts: 4990
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: Virtualbox and Windows 7

Post#49 by francois » 04 Jan 2017, 22:54

@jack:
To familiarize yourself with vbox would be a first step before installing windows into it. As a first step, I would just install porteus as a guest into porteus as an host. and then install windows when you understand vbox. It is really simple once you understand how it works. As mentioned, it happens that some build of vbox are not functioning well and that then you get an error message.

In addition, do you have a functional windows 7 OS disk?
Looks like a bad VirtuBox module. I will check the module on the server. You can rebuild it by activating the 05_devel and crippled sources module and from a root terminal type: update-vbox
Did you followed brokenman`s instructions with the command update-vbox?
Voltaire: Le mieux est l'ennemi du bien.

Jack
Contributor
Contributor
Posts: 1081
Joined: 09 Aug 2013, 14:25
Distribution: Porteus 3.2.rc5 Mate 64 bit
Location: Marysville, OHIO USA

Re: Virtualbox and Windows 7

Post#50 by Jack » 04 Jan 2017, 23:28

I have vbox working on another USB. It get up to this point. Here is a screen shot. I don't think it is a ERROR at this point. It just dose not have anything to do that what I think.
Image
In addition, do you have a functional windows 7 OS disk?
I do have a working copy of Windows 7 32bit of starter and home. I have a working copy Windows 7 64bit of home. With the Key's to Activate them.
As a first step, I would just install porteus as a guest into porteus as an host.
If I knew how to do I would try it. Can anyone help me on this?
I just like Slackware because I think it teach you about Linux to build packages where Ubuntu is like Windows you just install programs you want.

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 880
Joined: 20 Mar 2012, 03:42
Distribution: 3.2.2-64bit xfce/openbox
Location: australia
Contact:

Re: Virtualbox and Windows 7

Post#51 by ncmprhnsbl » 05 Jan 2017, 02:20

random youtube how to use virtualbox tutorial: https://www.youtube.com/watch?v=Dbblu_HVROk
there are many more...
Forum Rules : http://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
francois
Contributor
Contributor
Posts: 4990
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: Virtualbox and Windows 7

Post#52 by francois » 05 Jan 2017, 02:22

The original vbox module would not be operational.
Rebuild by activating the 05_devel and crippled sources module and from a root terminal type:

Code: Select all

update-vbox
Porteus guest on porteus host for a 64bit guest on 64 bit host
Open vbox
Fill info
New
Name: porteus322 #your choice in one word
linux
other linux
next

Memory: 1024 MB #I prefer to double the 512 proposed value
next

Create virtual hard disk now #For porteus 8 gig is good enough, for windows you will need twice depending on how much you want eventually your window virtual hdd to be.
Create
VDI
dynamically allocated
create

Almost there.

Now you have to select porteus iso, or later windows cd when you will make a windows 7 virtual guest.
Settings
Storage
Stortage tree: empty disk Attribute: optical drive (select the disk icon) find porteus.iso
Select iso

Start porteus guest.

Note 1: you can only install a porteus 64 bit guest on a porteus 64 bit host. Same for 32 bit guest and 32 bit host.

Note 2: I get two errors the error one is remediated. The second one is not on my system. Replication is needed:
Use of update-vbox will build a functional vbox module which will issue the following 2 errors:

1.0 error /sbin/vboxconfig
root@porteus:/home/guest# /sbin/vboxconfig
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
***takes much time but eventually works. ***

2,0 Porteus guest will boot until syslinux menu, then error:
viewtopic.php?f=117&t=6519

Code: Select all

... this kernel requires a x86_64 CPU, but only i686 CPU. Unable to boot.
Voltaire: Le mieux est l'ennemi du bien.

Jack
Contributor
Contributor
Posts: 1081
Joined: 09 Aug 2013, 14:25
Distribution: Porteus 3.2.rc5 Mate 64 bit
Location: Marysville, OHIO USA

Re: Virtualbox and Windows 7

Post#53 by Jack » 05 Jan 2017, 07:17

I'm using v3.2rc5 and I have a question.

When I run VBox builder there two ways so I built both. Which to use or both?

1. VirtualBox-5.1.12-porteus-v3.2rc5-x86_64-1prt.xzm

2. vbox-guest-5.1.12-porteus-v3.2rc5-x86_64-1prt.xzm

I can't show you but this is where I receive the two ways.
Image
I just like Slackware because I think it teach you about Linux to build packages where Ubuntu is like Windows you just install programs you want.

User avatar
francois
Contributor
Contributor
Posts: 4990
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: Virtualbox and Windows 7

Post#54 by francois » 05 Jan 2017, 13:47

VirtualBox-5.1.12 is the virtualization program
vbox additions is only some addition to the main program. It is used to adjust the definition of the virtual screen.
Voltaire: Le mieux est l'ennemi du bien.

Jack
Contributor
Contributor
Posts: 1081
Joined: 09 Aug 2013, 14:25
Distribution: Porteus 3.2.rc5 Mate 64 bit
Location: Marysville, OHIO USA

Re: Virtualbox and Windows 7

Post#55 by Jack » 05 Jan 2017, 13:53

francois wrote:VirtualBox-5.1.12 is the virtualization program
vbox additions is only some addition to the main program. It is used to adjust the definition of the virtual screen.
So you can use both of them?
I just like Slackware because I think it teach you about Linux to build packages where Ubuntu is like Windows you just install programs you want.

Jack
Contributor
Contributor
Posts: 1081
Joined: 09 Aug 2013, 14:25
Distribution: Porteus 3.2.rc5 Mate 64 bit
Location: Marysville, OHIO USA

Re: Virtualbox and Windows 7

Post#56 by Jack » 05 Jan 2017, 20:25

I try to start v3.2.2 in Graphics mode but never booted up then I try this. I started v3.2.2 in Always Fresh mode and after 5 minute of boot up time. Here is the output of VBox. I set it up like the YouTube video show me to do it. Here is the screen shot of what I received.
Image
And the ERROR I did received.
Image
These is just a thought.

1. Is it possible that the USB wasn't big enough?
2. It was only a 4gb USB or will I have to use a 16gb or a 32gb?
3. Do you think that Mint Linux has to be on a DVD to install?
I just like Slackware because I think it teach you about Linux to build packages where Ubuntu is like Windows you just install programs you want.

donald
Full of knowledge
Full of knowledge
Posts: 1175
Joined: 17 Jun 2013, 13:17
Distribution: Porteus 3.2.2 XFCE 32bit
Location: Germany

Re: Virtualbox and Windows 7

Post#57 by donald » 05 Jan 2017, 21:44

Look if you can enable it in vbox.
settings > system > Acceleration-Tab > check "Enable VT-x/AMD-V"

If it is greyed out
you may have virtualization disabled on the host computer. To enable:
Go to your host computer's BIOS (press F12, or Delete, or F2, ... depends on computer).
Find some options regarding virtualization.
https://i.stack.imgur.com/5x3YW.png
If there is such an option, enable it, save it
and switch the PC off and on again.

beny
Full of knowledge
Full of knowledge
Posts: 728
Joined: 02 Jan 2011, 11:33
Location: italy

Re: Virtualbox and Windows 7

Post#58 by beny » 05 Jan 2017, 22:59

Code: Select all

guest@porteus:~$ wine /home/guest/Scaricati/mSetup.exe
fixme:winediag:start_process Wine Staging 1.9.23 is a testing version containing experimental patches.
fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org.
fixme:nls:GetThreadPreferredUILanguages 00000038, 0x329760, 0x329770 0x329764
fixme:nls:get_dummy_preferred_ui_language (0x38 0x329760 0x329770 0x329764) returning a dummy value (current locale)
fixme:module:load_library unsupported flag(s) used (flags: 0x00000060)
fixme:module:load_library unsupported flag(s) used (flags: 0x00000060)
fixme:process:RegisterApplicationRestart (L" /RestartByRestartManager:D6131C4E-6409-4c22-8E73-37EAD27CB880",0)
fixme:shell:InitNetworkAddressControl stub
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000002 lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000003 lp=0078888b
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000000 lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000002 lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000003 lp=0078888b
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000000 lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000002 lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000003 lp=0078888b
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000000 lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000002 lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000003 lp=0078888b
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000000 lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000002 lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000003 lp=0078888b
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000000 lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000002 lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000003 lp=0078888b
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000000 lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000002 lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000003 lp=0078888b
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000000 lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000002 lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000003 lp=0078888b
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000000 lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000002 lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000003 lp=0078888b
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000000 lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000002 lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000003 lp=0078888b
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000000 lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000002 lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000003 lp=0078888b
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000000 lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000002 lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000003 lp=0078888b
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000000 lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000002 lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000003 lp=0078888b
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000000 lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000002 lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000003 lp=0078888b
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000000 lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000002 lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000003 lp=0078888b
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000000 lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000002 lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000003 lp=0078888b
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=00000000 lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
err:trackbar:TRACKBAR_WindowProc unknown msg 0466 wp=000000ff lp=00000000
fixme:ver:GetCurrentPackageId (0x133e9d8 (nil)): stub
fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_DATA_RECEIVE_TIMEOUT (4000): STUB
fixme:wininet:InternetSetOptionW INTERNET_OPTION_SEND/RECEIVE_TIMEOUT/DATA_SEND_TIMEOUT 4000
fixme:wininet:InternetSetOptionW INTERNET_OPTION_SEND/RECEIVE_TIMEOUT/DATA_SEND_TIMEOUT 4000
fixme:wininet:InternetSetOptionW INTERNET_OPTION_SEND/RECEIVE_TIMEOUT/DATA_SEND_TIMEOUT 4000
fixme:wininet:InternetSetOptionW INTERNET_OPTION_CONNECT_RETRIES 4
ALSA lib seq_hw.c:466:(snd_seq_hw_open) open /dev/snd/seq failed: File o directory non esistente
fixme:secur32:schannel_get_mac_algid unknown algorithm 200
fixme:secur32:schannel_get_mac_algid unknown algorithm 200
fixme:wininet:set_cookie secure not handled
fixme:wininet:set_cookie secure not handled
fixme:wininet:set_cookie secure not handled
fixme:wininet:set_cookie secure not handled
fixme:wininet:set_cookie secure not handled
fixme:wininet:set_cookie secure not handled
fixme:wininet:set_cookie secure not handled
fixme:wininet:set_cookie secure not handled
fixme:wininet:set_cookie secure not handled
fixme:wininet:set_cookie secure not handled
fixme:wininet:set_cookie secure not handled
hi jack to start wine you need also the multilib set by alienbob,i have installed also virtualbox with a windows 7 OVA from microsoft legal site 90 day trial but my usb key isn't enough to fit it.

fred08155
Black ninja
Black ninja
Posts: 56
Joined: 22 Apr 2016, 07:11
Distribution: Porteus 3.2.2 xfce
Location: Germany

Re: Virtualbox and Windows 7

Post#59 by fred08155 » 12 Jan 2017, 22:13

I also got a little problem with virtualbox.

I have set up porteus 3.2.2 xfce with devel module and virtualbox module downloaded from server.
Virtualbox works fine so far. I imported OVA image from Microsoft with IE11 and Win7.
I´d like to use USB 2.0 in the VM but it tells me it needs extension pack for this. So i downloaded extension pack from USM. When i change setting from USB 1.1 to 2.0 it still says incorrect settings - need to install extension pack.
Where is the problem???

donald
Full of knowledge
Full of knowledge
Posts: 1175
Joined: 17 Jun 2013, 13:17
Distribution: Porteus 3.2.2 XFCE 32bit
Location: Germany

Re: Virtualbox and Windows 7

Post#60 by donald » 12 Jan 2017, 22:54

@ fred08155

The virtualbox module on server = 5.1.10
extension-pack via usm = 5.0.14
this does not match.

try the Vbox-builder to get the newest vbox and guest addons
menu > system > vbox builder (in XFCE)

info at
https://www.virtualbox.org/wiki/Downloads

Vielleicht auch hilfreich:
http://www.pcwelt.de/tipps/Windows-7-8- ... 26088.html

Post Reply