Calling all Windows 7 x64 host users

Discussions related to using VirtualBox on Windows hosts.
wyeknott
Posts: 11
Joined: 1. Jan 2011, 21:33
Primary OS: MS Windows 7
VBox Version: OSE Debian
Guest OSses: ubuntu

Re: Calling all Windows 7 x64 host users

Post by wyeknott »

I have a Win7 64-bit host running VBox 4.08 and it works -- sort'a.

My HOST is home-built using an AMD Phenom II X6 1075T CPU (6 cores), 8 GB RAM, Gigabyte 870A-UD3 Mobo, 2x 1TB HDDs.

I have the following guests:

64-bit Windows SBS 2011 (Demo, boots properly);
32-bit UBuntu 11.04 (mouse click is unreliable);
32-bit Windows 2000 SP4, (fully functional);
32-bit Windows XP SP3, (fully functional);
16-bit MS-DOS 6.22, (no shared folders, diskette doesn't work, can't connect to host)
16-bit MS-DOS 6.20, (no shared folders, diskette doesn't work; haven't tried to network)

The Win7 Host is part of a Win SBS 2003 Domain and that works just fine.
I haven't gotten into SBS 2011 very much at all but it boots properly.
UBuntu has a flakey mouse click but otherwise seems to work.
Windows 2000 and Windows XP work perfectly.

The MS-DOS VMs are badly crippled because the diskette support is non-existent, and no shared folders are available since there's no VMadditions under VBox, and I've yet to get MS-DOS Client 3.0 connect to a WIn7 Share. The only work-around I've found for this issue is to build a 100MB Virtual Disk that I pass around like a diskette between MS-DOS and Windows XP in order to swap files of any size. It works but it's a major PITA.

The only recourse I have to run MS-DOS 6.xx with shared folders is to use MS Virtual PC. That has VM Additions for MS-DOS that work.
BUT, I don't think I can run VBox and VPC at the same time which limits its utility.

Ain't we got fun?
wa4zlw
Posts: 19
Joined: 9. Jun 2015, 19:20

Re: Calling all Windows 7 x64 host users

Post by wa4zlw »

My problem (post down below in another thread) is I can not reinstall either an old version or the latest virtualbox on my W7 Professional with dual quad core and 32 gb ram. Previous laptop had same CPU but only 8gb ram. I'm wondering if high ram I now have is the issue. other difference in this vs the other is the old had a 512mb hybrid drive; this one has a 512GB SSD and a 512GB HD.

install starts and then rolls back for an unknown reason that is not displayed.


any ideas?

thanks leon
wa4zlw
Posts: 19
Joined: 9. Jun 2015, 19:20

Re: Calling all Windows 7 x64 host users

Post by wa4zlw »

BTW I have Windows Virtual PC loads and it works. the old laptop did not have VPC loaded. I do need both if possible.

thanks leon
wa4zlw
Posts: 19
Joined: 9. Jun 2015, 19:20

Re: Calling all Windows 7 x64 host users

Post by wa4zlw »

found how to generate a log and here's a snippet:

Code: Select all

vboxDrvCfgInfQueryFirstPnPId: vboxDrvCfgInfQueryModelsSectionName returned lpszModels = (BROADCOM)
vboxDrvCfgInfQueryFirstPnPId: vboxDrvCfgRegQueryKeyValue for models (BROADCOM) returned lpszPnPId (PCI\VEN_14E4&DEV_4320&REV_03) 

vboxDrvCfgInfEnumerationCallback: vboxDrvCfgInfQueryFirstPnPId returned lpszPnPId = (PCI\VEN_14E4&DEV_4320&REV_03)
vboxDrvCfgInfEnumerationCallback: pContext->InfInfo.lpszPnPId = (sun_VBoxNetFltmp)
vboxDrvCfgInfEnumerationCallback: lpszFileName (oem7.inf)

vboxDrvCfgInfEnumerationCallback: pContext->InfInfo.lpszClassName = (Net)
vboxDrvCfgInfEnumerationCallback: lpszFileName (oem70.inf)

vboxDrvCfgInfEnumerationCallback: pContext->InfInfo.lpszClassName = (Net)
vboxDrvCfgInfQueryFirstPnPId: vboxDrvCfgInfQueryModelsSectionName returned lpszModels = (Intel)
vboxDrvCfgInfQueryContext: SetupFindFirstLine failed WinEr (-536870654) for Section(Intel), Key((null))

vboxDrvCfgInfQueryFirstPnPId: vboxDrvCfgInfQueryContext for models (Intel) failed, hr=0xe0000102

vboxDrvCfgInfEnumerationCallback: vboxDrvCfgInfQueryFirstPnPId returned lpszPnPId = (C:\Windows\inf\oem*.inf)
vboxDrvCfgInfEnumerationCallback: pContext->InfInfo.lpszPnPId = (sun_VBoxNetFltmp)
vboxDrvCfgInfEnumerationCallback: lpszFileName (oem71.inf)

vboxDrvCfgInfEnumerationCallback: pContext->InfInfo.lpszClassName = (Net)
vboxDrvCfgInfEnumerationCallback: lpszFileName (oem72.inf)

vboxDrvCfgInfEnumerationCallback: pContext->InfInfo.lpszClassName = (Net)
vboxDrvCfgInfEnumerationCallback: lpszFileName (oem73.inf)

vboxDrvCfgInfEnumerationCallback: pContext->InfInfo.lpszClassName = (Net)
vboxDrvCfgInfEnumerationCallback: lpszFileName (oem74.inf)

vboxDrvCfgInfEnumerationCallback: pContext->InfInfo.lpszClassName = (Net)
vboxDrvCfgInfEnumerationCallback: lpszFileName (oem75.inf)

vboxDrvCfgInfEnumerationCallback: pContext->InfInfo.lpszClassName = (Net)
vboxDrvCfgInfEnumerationCallback: lpszFileName (oem76.inf)

vboxDrvCfgInfEnumerationCallback: pContext->InfInfo.lpszClassName = (Net)
vboxDrvCfgInfEnumerationCallback: lpszFileName (oem77.inf)

vboxDrvCfgInfEnumerationCallback: pContext->InfInfo.lpszClassName = (Net)
vboxDrvCfgInfEnumerationCallback: lpszFileName (oem78.inf)

vboxDrvCfgInfEnumerationCallback: pContext->InfInfo.lpszClassName = (Net)
vboxDrvCfgInfEnumerationCallback: lpszFileName (oem79.inf)

vboxDrvCfgInfEnumerationCallback: pContext->InfInfo.lpszClassName = (Net)
vboxDrvCfgInfEnumerationCallback: lpszFileName (oem8.inf)

vboxDrvCfgInfEnumerationCallback: pContext->InfInfo.lpszClassName = (Net)
vboxDrvCfgInfEnumerationCallback: lpszFileName (oem80.inf)

vboxDrvCfgInfEnumerationCallback: pContext->InfInfo.lpszClassName = (Net)
vboxDrvCfgInfEnumerationCallback: lpszFileName (oem81.inf)

vboxDrvCfgInfEnumerationCallback: pContext->InfInfo.lpszClassName = (Net)
vboxDrvCfgInfEnumerationCallback: lpszFileName (oem82.inf)

vboxDrvCfgInfEnumerationCallback: pContext->InfInfo.lpszClassName = (Net)
vboxDrvCfgInfEnumerationCallback: lpszFileName (oem83.inf)

vboxDrvCfgInfEnumerationCallback: pContext->InfInfo.lpszClassName = (Net)
vboxDrvCfgInfEnumerationCallback: lpszFileName (oem84.inf)

vboxDrvCfgInfEnumerationCallback: pContext->InfInfo.lpszClassName = (Net)
vboxDrvCfgInfEnumerationCallback: lpszFileName (oem85.inf)

vboxDrvCfgInfEnumerationCallback: pContext->InfInfo.lpszClassName = (Net)
vboxDrvCfgInfEnumerationCallback: lpszFileName (oem86.inf)

vboxDrvCfgInfEnumerationCallback: pContext->InfInfo.lpszClassName = (Net)
vboxDrvCfgInfEnumerationCallback: lpszFileName (oem87.inf)

vboxDrvCfgInfEnumerationCallback: pContext->InfInfo.lpszClassName = (Net)
vboxDrvCfgInfEnumerationCallback: lpszFileName (oem88.inf)

vboxDrvCfgInfEnumerationCallback: pContext->InfInfo.lpszClassName = (Net)
vboxDrvCfgInfEnumerationCallback: lpszFileName (oem89.inf)

vboxDrvCfgInfEnumerationCallback: pContext->InfInfo.lpszClassName = (Net)
vboxDrvCfgInfEnumerationCallback: lpszFileName (oem9.inf)

vboxDrvCfgInfEnumerationCallback: pContext->InfInfo.lpszClassName = (Net)
vboxDrvCfgInfEnumerationCallback: lpszFileName (oem90.inf)

vboxDrvCfgInfEnumerationCallback: pContext->InfInfo.lpszClassName = (Net)
vboxDrvCfgInfEnumerationCallback: lpszFileName (oem91.inf)

vboxDrvCfgInfEnumerationCallback: pContext->InfInfo.lpszClassName = (Net)
vboxDrvCfgInfEnumerationCallback: lpszFileName (oem92.inf)

vboxDrvCfgInfEnumerationCallback: pContext->InfInfo.lpszClassName = (Net)
vboxDrvCfgInfEnumerationCallback: lpszFileName (oem93.inf)

vboxDrvCfgInfEnumerationCallback: pContext->InfInfo.lpszClassName = (Net)
vboxDrvCfgInfEnumerationCallback: lpszFileName (oem94.inf)

vboxDrvCfgInfEnumerationCallback: pContext->InfInfo.lpszClassName = (Net)
vboxDrvCfgInfEnumerationCallback: lpszFileName (oem95.inf)

vboxDrvCfgInfEnumerationCallback: pContext->InfInfo.lpszClassName = (Net)
vboxDrvCfgInfEnumerationCallback: lpszFileName (oem96.inf)

vboxDrvCfgInfEnumerationCallback: pContext->InfInfo.lpszClassName = (Net)
vboxDrvCfgInfEnumerationCallback: lpszFileName (oem97.inf)

vboxDrvCfgInfEnumerationCallback: pContext->InfInfo.lpszClassName = (Net)
vboxDrvCfgInfEnumerationCallback: lpszFileName (oem98.inf)

vboxDrvCfgInfEnumerationCallback: pContext->InfInfo.lpszClassName = (Net)
vboxDrvCfgInfEnumerationCallback: lpszFileName (oem99.inf)

vboxDrvCfgInfEnumerationCallback: pContext->InfInfo.lpszClassName = (Net)
UninstallNetFlt: VBoxNetCfgWinUninstallComponent failed, error = 0x1
Converting unhandled HRESULT (0x1) to ERROR_GEN_FAILURE   <<<=========
Uninstalling NetFlt done, error = 0x1f
MSI (s) (88:20) [22:06:09:691]: Executing op: ActionStart(Name=ca_InstallBranding,,)
MSI (s) (88:20) [22:06:09:693]: Executing op: ActionStart(Name=ca_CreateHostOnlyInterface,,)
MSI (s) (88:20) [22:06:09:695]: Executing op: ActionStart(Name=PublishProduct,Description=Publishing product information,)
MSI (s) (88:20) [22:06:09:697]: Executing op: RegOpenKey(Root=-2147483646,Key=Software\Classes\Installer\Products\CB18BB8EC76E057448EE21D85A7ADA5A\SourceList\Net,SecurityDescriptor=BinaryData,BinaryType=1,,)
MSI (s) (88:20) [22:06:09:699]: Executing op: RegOpenKey(Root=-2147483646,Key=Software\Classes\Installer\Products\CB18BB8EC76E057448EE21D85A7ADA5A\SourceList,SecurityDescriptor=BinaryData,BinaryType=1,,)
MSI (s) (88:20) [22:06:09:701]: Executing op: RegRemoveValue(Name=LastUsedSource,Value=#%n;1;C:\Users\leonz\AppData\Local\Temp\VirtualBox\,)
MSI (s) (88:20) [22:06:09:703]: Executing op: RegCreateKey()
MSI (s) (88:20) [22:06:09:706]: Executing op: RegOpenKey(Root=-2147483646,Key=Software\Classes\Installer\Products\CB18BB8EC76E057448EE21D85A7ADA5A,SecurityDescriptor=BinaryData,BinaryType=1,,)
MSI (s) (88:20) [22:06:09:708]: Executing op: RegRemoveValue(Name=Clients,Value=[~]:,)
MSI (s) (88:20) [22:06:09:710]: Executing op: RegCreateKey()
any assistance is greatly appreciate.

thanks leon
Attachments
tooracle.zip
log file from failed install on x64 8cpu 32gb
(58.4 KiB) Downloaded 22 times
Last edited by noteirak on 12. Jun 2015, 15:57, edited 1 time in total.
Reason: Added code tag
wa4zlw
Posts: 19
Joined: 9. Jun 2015, 19:20

Re: Calling all Windows 7 x64 host users

Post by wa4zlw »

heres the logs from the windows\inf subdir

leon
Attachments
tooracle2-INF.zip
INF logs
(49.51 KiB) Downloaded 12 times
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: Calling all Windows 7 x64 host users

Post by mpack »

Don't wake the dead. Please create your own topic and provide Minimum information needed for assistance.

Read the instructions carefully, since the logs you provided above are not the ones we need.
Locked