Development for LHC@home

v1.27 contains a very minor change to pass information from the bootstrap script to the wrapper script.

The last four or five with squid 5.5, no problems seen.
https://lhcathomedev.cern.ch/lhcathome-dev/show_host_detail.php?hostid=4639

I had two errors this morning.
https://lhcathomedev.cern.ch/lhcathome-dev/result.php?resultid=3162937
https://lhcathomedev.cern.ch/lhcathome-dev/result.php?resultid=3162961
I found in VBox media the parent VDI with a connected child with a yellow rectangle and exclamation mark.
The child however already left the home from his slot #1 last night at 1:15:58 UTC, but the shadow was still there.
I remove the shadow from VBox media and the next first task went fine.
Part of an error result:

2022-12-08 11:29:45 (15424): Adding virtual disk drive to VM. (ATLAS_vbox_1.27_image.vdi)
2022-12-08 11:29:52 (15424): Error in deregister parent vdi for VM: -2135228404
Command:
VBoxManage -q closemedium "D:\Boinc1/projects/lhcathomedev.cern.ch_lhcathome-dev/ATLAS_vbox_1.27_image.vdi" 
Output:
VBoxManage.exe: error: Cannot close medium 'D:\Boinc1\projects\lhcathomedev.cern.ch_lhcathome-dev\ATLAS_vbox_1.27_image.vdi' because it has 1 child media
VBoxManage.exe: error: Details: code VBOX_E_OBJECT_IN_USE (0x80bb000c), component MediumWrap, interface IMedium, callee IUnknown
VBoxManage.exe: error: Context: "Close()" at line 1862 of file VBoxManageDisk.cpp

This will happen occasionally.
It is caused by VirtualBox's vdi handling which moves the media entry back and forth between different configuration files.
Version 7.x makes it even worse compared to v6.1 as it violates it's own rule not to allow the multiattach attribute within the global media registry.

So far the only solution is to manually clear orphaned media entries.