Marietto

May 9

Hello to everyone.

I would like to install Windows 7 x64 bit on my mobo Aorus pro based on the Z390 platform. I want to explain what I did,because at the end it failed giving a BSOD that I want to fix.

I've followed the tutorial on this page :

and I've reached the stage where I see the disks where to install Windows 7. Unfortunately I have one only disk that I can use and it is an USB disk,model : WD 3200BMV External but Windows refuses to install on a USB disk.

At this point I've used But there is another problem on the stage 2 : it won't be installed on a USB disk. And unfortunately I have only one spare USB disk to use.

Anyway I found a method to achieve the goal. The method explained here :

https://github.com/vavrecan/usb-boot-watcher

ok. This is what I did :

C:\Users\virtu\Downloads\GetWaikTools\Waik_3\amd64>imagex /apply I:\Backup\Windows\en_windows_7_professional_x64_dvd_24.4.10\sources\install.wim 1 g:

ImageX Tool for Windows

Copyright (C) Microsoft Corp. All rights reserved.

Version: 6.1.7600.16385

[ 100% ] Applying progress

Successfully applied image.

C:\Users\virtu\Downloads\GetWaikTools\Waik_3>bcdboot f:\Windows /s f: /v

BFSVC: ServiceBootFiles MuiOnly:n Res:y Fonts:y BootMgrOvw:n BootStatOvw:n DbgTrn:y SuspendBDE:n

BFSVC: Unable to open file f:\Windows\boot\Resources\BOOTRES.DLL for read because the file or path does not exist

BFSVC Warning: Failed to determine source OS version.

BFSVC: Copying boot files CopyBootManager(Yes) f:\Windows\boot\EFI -> \\?\GLOBALROOT\Device\HarddiskVolume42\EFI\Microsoft\Boot

BFSVC: Updating \\?\GLOBALROOT\Device\HarddiskVolume42\EFI\Boot\bootx64.efi

BFSVC: Creating Recovery directory.

BFSVC: Logging boot file servicing to bootstat log \\?\GLOBALROOT\Device\HarddiskVolume42\EFI\Microsoft\Boot\BOOTSTAT.DAT.

BFSVC Warning: Failed to log servicing event to bootstat \\?\GLOBALROOT\Device\HarddiskVolume42\EFI\Microsoft\Boot\BOOTSTAT.DAT. Status: 0x80000005

BFSVC: Copying font files from f:\Windows\boot\Fonts to \\?\GLOBALROOT\Device\HarddiskVolume42\EFI\Microsoft\Boot\Fonts...

BFSVC: Copying resource files from f:\Windows\boot\Resources to \\?\GLOBALROOT\Device\HarddiskVolume42\EFI\Microsoft\Boot\Resources...

BFSVC: SetNamedSecurityInfo failed! Error code = 0x2

BFSVC Warning: Resource files missing from f:\Windows\boot\Resources. These files are required for some editions of Windows. If you are servicing older versions of Windows, you can ignore this message.

BFSVC: Servicing debugger files

BFSVC Warning: ServiceDebuggerFiles: f:\Windows\boot\BootDebuggerFiles.ini does not exist

BFSVC: System partition is not in a space

BFSVC: BfsInitializeBcdStore flags(0x0000001c) RetainElementData:n DelExistinObject:n

BFSVC: VolumePathName for f:\Windows is f:\

BFSVC: SystemRoot is \Windows

BFSVC: Opening template from \Device\HarddiskVolume42\Windows\System32\config\BCD-Template.

BFSVC: Opening store from \Device\HarddiskVolume42\EFI\Microsoft\Boot\BCD

BFSVC: System BCD store does not exist, creating.

BFSVC: Creating General objects.

BFSVC: Creating Resume object.

BFSVC: Creating MemTest object.

BFSVC: Creating OsLoader object.

BFSVC: OsLoader identifier: {f1a07f02-0ddc-11ef-af3b-e0d55ee21f22}

BFSVC: Removing duplicate entries.

BFSVC: Create BOOTMGR object RetainBootDefault:n

BFSVC: Setting {default} to {f1a07f02-0ddc-11ef-af3b-e0d55ee21f22}

BFSVC: Cleaning up debugger settings.

BFSVC: Cleaning up hypervisor settings.

BFSVC: Opening recovery store from \Device\HarddiskVolume42\EFI\Microsoft\Recovery\BCD

BFSVC: Creating new recovery store \Device\HarddiskVolume42\EFI\Microsoft\Recovery\BCD

BFSVC: Creating General objects.

BFSVC: Create BOOTMGR object RetainBootDefault:y

Boot files successfully created.

The final stage :

C:\Users\virtu\Downloads\usb-boot-watcher-master\bin\amd64>UsbBootWatcher /prepare f:\Windows\System32

Copy from C:\Users\virtu\Downloads\usb-boot-watcher-master\bin\amd64\UsbBootWatcher.exe

To f:\Windows\System32\UsbBootWatcher.exe

Copy from UsbBootWatcher.conf

To f:\Windows\System32\UsbBootWatcher.conf

Copy from f:\Windows\System32\config\system

To f:\Windows\System32\config\system.backup20240509083357

Registry hive loaded HKLM\USBBOOT

Target control set ControlSet001

Updating USBBOOT\ControlSet001\Services\usbstor

Updating USBBOOT\ControlSet001\Services\usbehci

Updating USBBOOT\ControlSet001\Services\usbohci

Updating USBBOOT\ControlSet001\Services\usbuhci

Updating USBBOOT\ControlSet001\Services\usbhub

Creating service USBBOOT\ControlSet001\Services\Usb Boot Watcher Service

Registry hive unloaded HKLM\USBBOOT

It didn't work. You want to see well whats happened ?

https://ibb.co/v4Bg4jC
https://ibb.co/Qcpkysg

How to fix this error ?

May 8

Hello to everyone.

What I would like to understand if why,when I try to passthru my RTX 2080 ti from FreeBSD to Windows 11,it won't do it,causing the error 12. It says that it generates a resource conflict and requires additional installation).

I'm trying to debug the error. Below you see the IOMMU group of my Nvidia Geforce RTX 2080 ti passed in a Windows 11 / bhyve VM and of Windows 11 installed physically. I'm not able to understand if there are inconsistencies.

VM :

Group: 30.0.15.1123 - Device: NVIDIA GeForce RTX 2080 Ti (Device ID: PCI\VEN_10DE&DEV_1E04&SUBSYS_250319DA&REV_A1\3&61AAA01&0&48)

Group: 4.39.0.0 - Device: NVIDIA Virtual Audio Device (Wave Extensible) (WDM) (Device ID: ROOT\UNNAMED_DEVICE\0000)

Group: 1.46.831.832 - Device: NVIDIA USB Type-C Port Policy Controller (Device ID: PCI\VEN_10DE&DEV_1AD7&SUBSYS_250319DA&REV_A1\3&61AAA01&0&4B)

Group: 10.0.22000.2360 - Device: Controller host NVIDIA USB 3.10 eXtensible - 1.10 (Microsoft) (Device ID: PCI\VEN_10DE&DEV_1AD6&SUBSYS_250319DA&REV_A1\3&61AAA01&0&4A)

Physical installation :

Group: 31.0.15.5222 - Device: NVIDIA GeForce RTX 2080 Ti (Device ID: PCI\VEN_10DE&DEV_1E04&SUBSYS_250319DA&REV_A1\4&94764DC&0&0009)

Group: 4.49.0.0 - Device: NVIDIA Virtual Audio Device (Wave Extensible) (WDM) (Device ID: ROOT\UNNAMED_DEVICE\0000)

Group: 1.50.831.832 - Device: NVIDIA USB Type-C Port Policy Controller (Device ID: PCI\VEN_10DE&DEV_1AD7&SUBSYS_250319DA&REV_A1\4&9476 4DC&0&0309)

Group: 10.0.22000.2360 - Device: NVIDIA USB 3.10 eXtensible Host Controller - 1.10 (Microsoft) (Device ID: PCI\VEN_10DE&DEV_1AD6&SUBSY S_250319DA&REV_A1\4&94764DC&0&0209)

As an experiment I've passed only this device from FreeBSD to WIndows 11 :

pptdevs="2/0/0"

I have excluded "2/0/1 ; 2/0/2 ; 2/0/3". I want to show you what means these addresses :

02:00.0 VGA compatible controller: NVIDIA Corporation TU102 [GeForce RTX 2080 Ti] (rev a1)

02:00.1 Audio device: NVIDIA Corporation TU102 High Definition Audio Controller (rev a1)

02:00.2 USB controller: NVIDIA Corporation TU102 USB 3.1 Host Controller (rev a1)

02:00.3 Serial bus controller: NVIDIA Corporation TU102 USB Type-C UCSI Controller (rev a1)

What happened when I launched the vm using these parameters ?

bhyve -S -c sockets=2,cores=2,threads=2 -m 4G -w -H -A \

-s 0,hostbridge \

-s 1,ahci-hd,/mnt/$vmdisk0'p2'/bhyve/img/Windows/Windows11.img,bootindex=1 \

-s 9:0,passthru,2/0/0 \ -s 11,hda,play=/dev/dsp,rec=/dev/dsp \

-s 13,virtio-net,tap18 \ -s 29,fbuf,tcp=0.0.0.0:5918,w=1600,h=950,wait \

-s 30,xhci,tablet \ -s 31,lpc \ -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI_CODE.fd \

vm0:18 < /dev/null & sleep 2 && vncviewer 0:18

this error :

Assertion failed: (!err), function hda_init, file /usr/corvin-src-releng-140/usr.sbin/bhyve/pci_hda.c, line 353.

The error is caused by this parameter :

-s 11,hda,play=/dev/dsp,rec=/dev/dsp \

I have excluded it and Windows 11 booted. Now,inside it I still see the error 12 :

The device PCI\VEN_10DE&DEV_1E04&SUBSYS_250319DA&REV_A1\3&61aaa01&0&48 generates a resource conflict and requires additional installation.

If I pass to the vm only -s 9:0,passthru,2/0/0 \ ; it does not work anyway,because AFAIK,MAYBE there is one and only IOMMU group,so I should pass everything ? But if I pass everything,the error 12 is there anyway.

I would like to understand if there is a problem with the IOMMU thing,if there is maybe there is the needing to develop a patch like this one : GitHub - benbaker76/linux-acs-override for FreeBSD.

For an experienced developer should not be so hard to understand which devices conflict. I want to ask some help to understand how to debug the error. If we will be able to understand which devices conflict,maybe I can explain this to the bhyve developer with which I'm in contact and he can develop a patch. So,we will be able to use every modern nvidia gpus inside a Windows VM with bhyve under FreeBSD ! That's a nice goal,isn't it ? So,please ask me more informations that you need to understand the origin of the error.

Windows Build/Version : 10.0.22000.2538

April 24

Hello to everyone.

I've installed Windows XP 32 and 64 bit as virtual machine with VMware 17 on my Ubuntu 23.10. The goal is to be able to boot them in UEFI mode.

At a certain point of the video,he changes the boot mode from BIOS to UEFI (I can't attach urls). I did the same,but In my case it won't change. The button is greyed out.

I've also converted those xp virtual machines from vmdk to img and I tried to boot them with bhyve (the hypervisor used on FreeBSD),but they didn't boot.

So,I can't check if the vmdk images are able to boot with VMware because I'm not able to enable the UEFI option and I can't check if they don't boot with bhyve because they don't boot with UEFI in VMware.

October 6, 2010

you said : you can't burn your own install DVDs : can you explain better what it means ?

October 4, 2010

Hello to everybody,

I'm trying to start the unattended installation of Windows 7 using GRUB4DOS with a different approach.

My first hard disk is partitioned like this :

(hd0,0) : Windows 7 100 MB hidden partition

(hd0,1) : partition where is installed Windows 7

This is what I did on (hd0,0) from Linux :

a) mv Boot Boot_

b) mv bootmgr bootmgr_

c) copied here the file autounattend.xml

c) copied here grldr

d) copied here menu.lst with this content inside :

title : Start the installation of Windows 7

root (hd0,1)

chainloader /bootmgr

on (hd0,1) I copied all the files and folder located on the Windows 7 DVD,so here I have these files and folders :

$Recycle.Bin

Documents and Settings

Program Files

ProgramData

Users

Windows

boot

bootmgr

efi

setup.exe

sources

support

upgrade

After having done this,I have installed the GRUB4DOS bootloader on sda from Linux,with this command :

./bootlace.com /dev/sda

and I rebooted the computer. At the boot time it asks to me to press a special key if I want to load the old bootmgr. I don't do it and the grub4dos menu appears on the screen,showing the message :

Start the installation of Windows 7

When I press a key,the installation of Windows 7 starts correctly,but the autounattend.xml file is not detected. I don't understand why,because I have copied it on the root of (hd0,0) and of (hd0,1). I read somewhere that it should be copied o the root of the disk,is this right ? What's the root in my scenario,(hd0,0)/ or (hd0,1)/ ?

October 4, 2010

This is a solution that I have already thought,but since I'm creating a system that I want to sell to my customers,it is against the Microsoft EULA to re-distribuite Windows files,so I can do what you suggest only if I can take the necessary files from the customer's Windows Seven 32 or 64 bit DVD. Can you confirm that I can do it ?

October 4, 2010

Hello to everybody,

I'm trying to make an unattended installation of Windows 7 over a pre-existing installation of Windows 7. This is the autounattend.xml file I'm using :

<?xml version="1.0" encoding="utf-8"?>

</SetupUILanguage>

</component>

<WillWipeDisk>false</WillWipeDisk>

</Disk>

</DiskConfiguration>

</InstallTo>

</OSImage>

</ImageInstall>

<AcceptEula>false</AcceptEula>

<FullName>Windows</FullName>

<Organization>Windows</Organization>

</UserData>

</component>

</settings>

<ComputerName>Windows</ComputerName>

</component>

</settings>

<CommandLine>c:\reinstallazione\fase4.bat</CommandLine>

</SynchronousCommand>

</FirstLogonCommands>

</component>

</settings>

</unattend>

Now this is the problem I need to fix : Usually Windows 7 creates a 100 MB hidden partition instead to install itself in one only single partition. For this reason,the autounattend.xml file I created can't be valid everytime. Plus,I need to make the unattended re-installation of Windows 7 64 bit,and this is another reason why I need to use al least 4 different kinds of autounattend.xml files :

version n. 1) can be used if the old installation of Windows 7 32 bit hadn't created a 100 MB hidden partition. In this case :

<?xml version="1.0" encoding="utf-8"?>

....

</InstallTo>

</OSImage>

</ImageInstall>

version n. 2) the old installation of Windows 7 64 bit hadn't created a 100 MB hidden partition. In this case :

<?xml version="1.0" encoding="utf-8"?>

....

</InstallTo>

</OSImage>

</ImageInstall>

version 3) the old installation of Windows 7 32 bit had created a 100 MB hidden partition. In this case :

<?xml version="1.0" encoding="utf-8"?>

....

</InstallTo>

</OSImage>

</ImageInstall>

version n. 4) the old installation of Windows 7 64 bit had created a 100 MB hidden partition. In this case :

<?xml version="1.0" encoding="utf-8"?>

....

</InstallTo>

</OSImage>

</ImageInstall>

Since I can start the autounattended re-installation of Windows 7 only copying the autounattend.xml file in one only place,the root of the CD/ROM,because it is the only place where it is detected and because whe whole system will be loaded from there,my question is : how can I configure the file autounattend.xml to avoid the problem that I have explained above ?

September 27, 2010

Hello,

I'm trying to create a bootable CD with FreeDOS and without the long file names limitation. Inside the ISO image I've included the FreeDOS files and a lot of files contain files longer than 31 chars as for example these :

activedirectory-webservices-replacement.man

application-experience-program-compatibility-assistant-replacement.man

and so on.

I make the ISO image using mkisofs with the following parameters :

-o fdoem.iso -b isolinux/isolinux.bin -no-emul-boot -boot-load-size 4 -boot-info -table -N -r -iso-level 4 -J -l -D -joliet-long -relaxed-filenames CDROOT

this is what happens when I make the ISO image.

Using "mkisofs.rc"

Warning: creating filesystem that does not conform to ISO-9660.

Warning: Creating ISO-9660:1999 (version 2) filesystem.

Warning: ISO-9660 filenames longer than 31 may cause buffer overflows in the OS.

Size of boot image is 4 sectors -> No emulation

2.83% done, estimate finish Mon Sep 27 14:11:58 2010

5.66% done, estimate finish Mon Sep 27 14:11:58 2010

99.00% done, estimate finish Mon Sep 27 14:12:01 2010

Total translation table size: 2048

Total rockridge attributes bytes: 113522

Total directory bytes: 319488

Path table size(bytes): 3142

Max brk space used 14a68b0

176773 extents written (345 MB)

Created cdrom imagefile fdoem.iso out of directory CDROOT

as you can see,there are no problems.

After having created the ISO image,I've burnt it using NERO with the following parameters :

Mod Data : Mode 1

File System : ISO 9660 + Joliet

Name File Lenght (ISO) : Max 31 chars (lev.2 )

Charset : ISO 9660 (standard CD/ROM ISO)

After having burnt the CD,I see that the long file names are read correctly by Windows,but not by FreeDOS. Here they are truncated with the 8+3 format. As I read,FreeDOS does not support long file names,so I'm using the DOSLFN driver.

The DOSLFN.TXT file,says :

c (CDROM support): Enables CDROM support, i.e. DOSLFN uses much more memory

to keep code for CDROM initialization and CDROM access. This switch defaults

to the state whether SHSUCDX v3.01 is loaded or not (this version of DOSLFN

does not work with MSCDEX or earlier versions of SHSUCDX). You must include

a c+ switch if you load DOSLFN before SHSUCDX, and you want long file names

on CDROM!

Since I load DOSLFN after SHSUCDX,I don't need to use the -c+ switch. But I see that the 8+3 chars limitation is not removed when FreeDOS has been loaded,so,I have removed the old version of SHSUCDX that I used before (2.1) and I have changed it with the new version (3.01) suggested and I started the DOSLFN driver from the command line with the -c+ switch,but this has not helped me at all,because every file and folder are still truncated at 8+3 chars. Do you have any suggest ? Thanks in advance.

September 13, 2010

nothing...

August 25, 2010

fixed. Autounattend.xml should be copied on the root of the DVD/ROM.

August 25, 2010

Hello to everyone,

I want to start the unattended installation of Windows 7 from FreeDOS (it runs in LIVE mode on the DVD/ROM) using Grub4dos. This is the partition scheme of the disk with which I work :

(hd0) : 300 GB

(hd0,0) : NTFS (hidden partition,it contains the boot folder and the file bootmgr)

(hd0,1) : NTFS (This is the installation partition)

Since the boot files of Windows 7 are located on (hd0,0),to start the unattended installation of Windows 7 I have :

1) renamed bootmgr to bootmgr_ on (hd0,0) to prevent booting Windows 7 from there

2) copied all the installation files of 7 on the root of partition (hd0,1)

3) copied Autounattend.xml on the root of the partition (hd0,1)

4) created menu.lst :

title Start the installation of Windows Vista/7 32/64 bit

find --set-root --ignore-floppies --ignore-cd /bootmgr

chainloader /bootmgr

5) grub.exe and menu.lst are located on the root of the DVD/ROM,because Freedos runs in Live mode.

grub4dos detects the correct bootmgr and the installation of Win 7 starts correctly. The problem is that Autounattend.xml is not detected at all,even if it is on the root of (hd0). Why ?

April 22, 2009

Hello,

I'm trying to create a Windows 7 Slipstream Installation DVD with vLlite 1.2 and WAIK for Windows 7 beta. I've copied the file wimgapi.dll from C:\Program Files\Windows AIK\Tools\x86 to C:\Program Files\vLite because I know about the bug,but it doesn't works,vLlite 1.2 doesn't recognize WAIK anyway.

April 21, 2009

Hello,

my name's Mario. I come from Italy. I'm trying to create a Windows 7 Italian Language pack Slipstream Installation DVD. I've built the iso image correctly using Vlite. During the installation process I can choose between italian and english,but If I choose the italian language the installation stops with the following error message :

It's not possibile to setup informations related to the offline local settings. Informations saved during the installation cannot be saved.

update :

I'm using WAIK for Windows 7 beta. I've copied the file wimgapi.dll from C:\Program Files\Windows AIK\Tools\x86 to C:\Program Files\vLite because I know about the bug,but it doesn't works,vLlite 1.2 doesn't recognize WAIK anyway. why ?

Thanks.

Sign In

Marietto

Posts

Joined

Last visited

Donations

Country

Content Type

Profiles

Forums

Events

Posts posted by Marietto

Windows 7 on the Aorus Pro / Z390 mobo...

Trying to passthru my RTX 2080 ti from FreeBSD (14) to a Windows 11 vm (it generates a resource conflict and requires additional installation)

I can't boot a modified and patched installation of XP in UEFI mode.

How to configures partitions inside autounattend.xml file

Unattended installation of Win 7 installing the Grub4DOS bootloader

How to configures partitions inside autounattend.xml file

How to configures partitions inside autounattend.xml file

ISO image creation with mkisofs makes files name truncated.

unattend.txt file not detected

Autounattend.xml file is not detected by grub4dos

Autounattend.xml file is not detected by grub4dos

vLlite 1.2 doesn't works with Windows Automated Installation Kit f

Windows 7 Italian Language pack Slipstream Installation DVD

Activity

Browse