You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 17, 2024. It is now read-only.
$ ls -lh floppy/bginfo/Bginfo.exe
-rwxr-xr-x@ 1 user staff 2.9M Jan 17 2018 floppy/bginfo/Bginfo.exe
I will try a workaround by commenting out anything relating to setting background and do a build then, but thought you must have run into the issue yourself and that I should report it.
Full output of running packer build (some paths redacted for privacy):
$ packer build -only=virtualbox-iso -force -on-error=ask template-output/MSEdge-Win10.json
virtualbox-iso output will be in this color.
==> virtualbox-iso: Downloading or copying Guest additions
virtualbox-iso: Downloading or copying: file:///path/to/VirtualBox.app/Contents/MacOS/VBoxGuestAdditions.iso
==> virtualbox-iso: Downloading or copying ISO
virtualbox-iso: Downloading or copying: file:///path/to/dev.microsoftedge.com-vms/scripts/iso/15063.0.170317-1834.RS2_RELEASE_CLIENTENTERPRISEEVAL_OEMRET_X64FRE_EN-US.iso
==> virtualbox-iso: Deleting previous output directory...
==> virtualbox-iso: Creating floppy disk...
virtualbox-iso: Copying files flatly from floppy_files
virtualbox-iso: Copying file: floppy/common/setautologon.ps1
virtualbox-iso: Copying file: floppy/build.cfg
virtualbox-iso: Copying file: floppy/openssh/openssh.ps1
virtualbox-iso: Copying file: floppy/updates/win-updates.ps1
virtualbox-iso: Copying file: floppy/common/post-win-updates.ps1
virtualbox-iso: Copying file: floppy/common/finish-actions.ps1
virtualbox-iso: Copying file: floppy/updates/microsoft-updates.bat
virtualbox-iso: Copying file: floppy/common/preprovisioner.ps1
virtualbox-iso: Copying file: floppy/bginfo/Bginfo.exe
==> virtualbox-iso: Error adding file from floppy_files : floppy/bginfo/Bginfo.exe : FAT FULL
==> virtualbox-iso: Step "StepCreateFloppy" failed
==> virtualbox-iso: [c] Clean up and exit, [a] abort without cleanup, or [r] retry step (build may fail even if retry succeeds)? c
==> virtualbox-iso: Deleting output directory...
Build 'virtualbox-iso' errored: Error adding file from floppy_files : floppy/bginfo/Bginfo.exe : FAT FULL
==> Some builds didn't complete successfully and had errors:
--> virtualbox-iso: Error adding file from floppy_files : floppy/bginfo/Bginfo.exe : FAT FULL
==> Builds finished but no artifacts were created.
Configuration:
packer: 1.2.5
Build host: macOS 10.3.6
For the record, the full MSEdge-Win10.json (which I merged from template-parts by hand (and adding one line to the vagrant post-processor to test a fix for #21) to avoid building packermerge since I am on a Mac):
@dusek I switched to using a cdrom and EFI for windows 10. I haven't uploaded the code yet because there are some parts that arent fully automated. Another option is to dig an older version of that file that's smaller.
@molant Thanks for the tips. In the end, I managed to work around this by removing BGinfo.exe from the floppy and commenting out copying and execution of BGinfo.exe in install.vbs.
Technically there were 2.88MB floppies in the past and as a virtual floppy the size shouldn't matter unless it is hardcoded to a certain size somewhere.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Bginfo.exe (downloaded today from the site linked in README using the Download BgInfo link) is 2.9MB, twice more than 1.44MB floppy max size:
I will try a workaround by commenting out anything relating to setting background and do a build then, but thought you must have run into the issue yourself and that I should report it.
Full output of running
packer build
(some paths redacted for privacy):Configuration:
For the record, the full MSEdge-Win10.json (which I merged from template-parts by hand (and adding one line to the
vagrant
post-processor to test a fix for #21) to avoid building packermerge since I am on a Mac):The text was updated successfully, but these errors were encountered: