add deepseek and gemma results

1 files changed, 0 insertions, 58 deletions

diff --git a/results/classifier/deepseek-2-tmp/output/boot/2235 b/results/classifier/deepseek-2-tmp/output/boot/2235
deleted file mode 100644
index 9cb2e586..00000000
--- a/results/classifier/deepseek-2-tmp/output/boot/2235
+++ /dev/null
@@ -1,58 +0,0 @@
-
-Hiren's Bootcd PE LiveCD not booting in windows qemu
-Description of problem:
-Hiren's Bootcd PE LiveCD not booting up in windows qemu.  
-PE stands for pre-execution environment which is like a minimal boot environment like windows-recovery.  
-The ram drive it makes is about 3.5 GiB.  
-Being able to boot something like Hiren BootCD PE is like a simple test of qemu.   
-
-I've tried many things, but I can't figure out if it's because I can't get the arguments right or if it is because of something else.
- 
-So far, using windows-qemu, I have not tried to boot a win10-guest-OS on win10 host-OS.
-Steps to reproduce:
-1. Try to start qemu as per command. Try figure out what the right arguments/options are.
-
-The live cd boot process is as follows
-1. First the livecd bootloader loads files from the cdrom and unpacks them into a ramdrive
-   During this phase, in the taskmgr it can be seen that the memory of the qemu process grows to about 1.5 GiB
-2. Then the boot process should transfer to the unpacked OS in the ramdrive.  
-   In the center of the screen, if one is doing efi-boot, then one can see the tianocore logo, else if one is doing legacy boot, then one can see the windows logo.  
-   The windows loading animation, dots in circle, does not start. In some boot attempts, it seems to have put only 1 dot, in other boot attempts nothing at all.  
-   Even after the expansion phase, the qemu process in the taskmgr shows a 11% use (which 1 cpu in a hyperthreading i7 quadcore cpu).  
-   This means emulator is doing something. But, despite waiting for a long time, nothing seems to happen in the guest-display-window.  
-
-```
-PS F:\> dir D:\bootable\hb*.iso
-
-    Directory: D:\bootable
-
-Mode                 LastWriteTime         Length Name
-----                 -------------         ------ ----
--a---           9/17/2021  7:29 PM     3099203584 HBCD_PE_x64_v1.0.2_20210701.iso
--a---           3/13/2024  4:45 PM     3291686912 HBCD_PE_x64_v1.0.8_20240305.iso
-
-PS F:\> Get-FileHash -Algorithm SHA256 D:\bootable\HBCD_PE_x64_v1.0.2_20210701.iso
-
-Algorithm       Hash                                                                   Path
----------       ----                                                                   ----
-SHA256          8281107683E81BE362AFD213026D05B2219BC6A7CA9AF4D2856663F3FFC17BFD       D:\bootable\HBCD_PE_x64_v1.0.2_…
-
-PS F:\> Get-FileHash -Algorithm SHA256 D:\bootable\HBCD_PE_x64_v1.0.8_20240305.iso
-
-Algorithm       Hash                                                                   Path
----------       ----                                                                   ----
-SHA256          8C4C670C9C84D6C4B5A9C32E0AA5A55D8C23DE851D259207D54679EA774C2498       D:\bootable\HBCD_PE_x64_v1.0.8_…
-
-PS F:\> Get-Content D:\bootable\HBCD_PE_x64_v1.0.2_20210701.iso.sha256
-8281107683E81BE362AFD213026D05B2219BC6A7CA9AF4D2856663F3FFC17BFD  HBCD_PE_x64_v1.0.2_20210701.iso
-PS F:\> Get-Content D:\bootable\HBCD_PE_x64_v1.0.8_20240305.iso.sha256
-8c4c670c9c84d6c4b5a9c32e0aa5a55d8c23de851d259207d54679ea774c2498  HBCD_PE_x64_v1.0.8_20240305.iso
-```
-Additional information:
-- https://www.hirensbootcd.org/download/
-- method to create the bios file is explained in #2233 
-- I have booted into v1.0.2 in native, so I know v1.0.2 works.  
-- I have tried qemu with and without EFI bios. 
-- The more recent v1.0.8 released on 20240305 is Win11 PE based (>22621)
-- Virtualbox-7.0.14 is able to boot HBCDPE as normal, but with EFI disabled, and not when enabled.  
-- As of this issue creation, not yet checked whether under Linux if qemu-kvm can boot HBCDPE.