Clean install of Windows 95 OSR 2.5 displays black screen when booting to normal mode after restarting

[gingusScringus]

Describe the bug

I recently installed Windows 95 OSR 2.5 using DOSBox-X. I had a successful install with no problems when I was at version 2024.07.01 or earlier I think. I followed the official guide to install this.

When I try to shut down or restart to add some commands and parameters to the .conf file, it displays a black screen instead after the Windows 95 bootup screen, which my previous install did not do.

I don't think me adding some commands to the .conf has anything to do with this, as reverting them gives off the same result. The only way I could enter the OS is with Safe Mode. And the newly mounted directories seem to be working in safe mode too.

Though the log might have something that causes this, I saw some errors on the CPU and IDE, maybe. I don't know.

Steps to reproduce the behaviour

1. Install Windows 95 normally through the guide.
2. After installing, wait for the OS to install miscellaneous things (such as IE 4.0). Then wait for it to finish.
3. Restart the OS.

Expected behavior

No response

What operating system(s) this bug have occurred on?

Windows 11 24H2 OS Build 26100.1882 64-bit

What version(s) of DOSBox-X have this bug?

DOSBox-X 2024.10.01 Visual Studio 64-bit SDL2

Used configuration

[sdl]
autolock=true

[dosbox]
title=Windows 95
memsize=480

[video]
vmemsize=8
vesa modelist width limit=0
vesa modelist height limit=0

[dos]
# Set 'ver=7.1' if using Win95 OSR2 (95B) or later
ver=7.1
hard drive data rate limit=0
floppy drive data rate limit=0

[cpu]
cputype=pentium_mmx
core=normal

[sblaster]
sbtype=sb16vibra

[fdc, primary]
int13fakev86io=true

[ide, primary]
int13fakeio=true
int13fakev86io=true

[ide, secondary]
int13fakeio=true
int13fakev86io=true
cd-rom insertion delay=4000

[render]
scaler=none

[autoexec]
IMGMOUNT 0 empty -fs none -t floppy
IMGMOUNT 1 empty -fs none -t floppy -size 512,15,2,80
IMGMOUNT C "C:\ShetDOS\DosBOX HDDs and ISOs\Win95\hdd.img" -ide 1m
IMGMOUNT D empty -t iso -ide 2m
mount T "C:\ShetDOS\Tracker Modules" -label TRAKMUS
mount H "C:\ShetDOS\MS-DOS or Windows Programs" -label DOSPROG
mount G "C:\ShetDOS\Drivers" -label DRVR
mount J "C:\ShetDOS\Windows-only Programs" -label WINPROG
BOOT C:

Output log

Early LOG Init complete
"" is not a valid value for variable: configuration tool theme.
It might now be reset to the default value: 
DOSBox-X's working directory: C:\DOSBox-X
Logging init: beginning logging proper. This is the end of the early init logging
Logging: No logfile was given. All further logging will be discarded.
DOSBox-X version 2024.10.01 Commit d93a20f (Visual Studio SDL2 64-bit)
Prevent capture: 0
SDL: version 2.30.4, Video windows, Audio directsound
Windows keyboard layout ID is 0x0409
Host keyboard layout is now us (US English)
Mapper keyboard layout is now us (US English)
SDL2 reports desktop display mode 1920 x 1080
The default output for the video system: direct3d
Configured windowposition: -
SDL: Current window pixel format: SDL_PIXELFORMAT_RGB888
SDL: You are running in 24 bpp mode, this will slow down things!
SDL: Windows 11 round corners will be disabled.
Screen report: Method 'Win98base' (1920.000 x 1080.000 pixels) at (0.000 x 0.000) (508.000 x 285.750 mm) (20.000 x 11.250 in) (96.000 x 96.000 DPI)
ISA BCLK: 8333333.333Hz (25000000/3)
monopal: green, 
Active save slot: 1 [Empty]
USING AVI+ZMBV
Max 3670016 sz 65536
Final 65536
MIDI:Opened device:win32
Pentium CMPXCHG8B emulation is enabled
VOODOO LFB now at d0000000
Serial1: BASE 3f8h
Serial2: BASE 2f8h
Parallel1: BASE 378h
MPU-401 Registering I/O ports as if IBM PC MPU-401 at base 330h
Memory I/O complexity optimization enabled aka option 'memory io optimization 1'. If the game or demo is unable to draw to the screen properly, set the option to false.
The 'scanline render on demand' option is available and may provide a modest boost in video render performance if set to true.
Screen report: Method 'Win98base' (1920.000 x 1080.000 pixels) at (0.000 x 0.000) (508.000 x 285.750 mm) (20.000 x 11.250 in) (96.000 x 96.000 DPI)
Allocated APM BIOS pm entry point at f000:ce40
Writing code to fce40
Writing code to fce60
Screen report: Method 'Win98base' (1920.000 x 1080.000 pixels) at (0.000 x 0.000) (508.000 x 285.750 mm) (20.000 x 11.250 in) (96.000 x 96.000 DPI)
Windows: IID_ITaskbarList3 is available
ISA Plug & Play BIOS enabled
VGA ROM BIOS init callback
Screen report: Method 'Win98base' (1920.000 x 1080.000 pixels) at (0.000 x 0.000) (508.000 x 285.750 mm) (20.000 x 11.250 in) (96.000 x 96.000 DPI)
pixratio 1.000, dw false, dh false
Aspect ratio: 640 x 480  xToY=1.333 yToX=0.750
Screen report: Method 'Win98base' (1920.000 x 1080.000 pixels) at (0.000 x 0.000) (508.000 x 285.750 mm) (20.000 x 11.250 in) (96.000 x 96.000 DPI)
WARNING: No translation support (to host) for code page 0
pixratio 1.350, dw false, dh false
Aspect ratio: 720 x 540  xToY=1.333 yToX=0.750
Screen report: Method 'Win98base' (1920.000 x 1080.000 pixels) at (0.000 x 0.000) (508.000 x 285.750 mm) (20.000 x 11.250 in) (96.000 x 96.000 DPI)
***| TYPE HELP (+ENTER) TO GET AN OVERVIEW OF ALL COMMANDS |***
DOS keyboard layout loaded with main language code US for layout us
XMS: 50 handles allocated for use by the DOS environment
EMS page frame at 0xe000-0xefff
COMMAND.COM env size:             720 bytes
COMMAND.COM environment block:    0xcc01 sz=0x002d
COMMAND.COM main body (PSP):      0xcc2f sz=0x009a
COMMAND.COM stack:                0xcc49
Mounted empty C/H/S/sz 80/2/18/512 1440KB
Updating floppy type to 8 BIOS type 0x02
Mounted empty C/H/S/sz 80/2/15/512 1200KB
FAT: Partition type is MBR (IBM PC)
Mounted FAT volume is FAT16 with 64439 clusters
Mapping BIOS DISK C/H/S 1023/64/63 as IDE 4092/16/63
IMGMOUNT: HDD image mounted to drive no. 2 (IDE Primary Master)
Empty ISO
IMGMOUNT: CD-ROM image mounted to drive D (IDE Secondary Master)
Converting drive G: to FAT...
Mapping BIOS DISK C/H/S 61/255/63 as IDE 0/16/63
IMGMOUNT: HDD image mounted to drive no. 3 (IDE Primary Slave)
Converting drive H: to FAT...
Mapping BIOS DISK C/H/S 147/255/63 as IDE 0/16/63
IMGMOUNT: HDD image mounted to drive no. 4 (IDE Secondary Slave)
Converting drive J: to FAT...
IDE: WARNING: IDE controller Secondary Master already occupied, specify another slot.
Booting guest OS stack_seg=0x7000 load_seg=0x07c0
Removing UMB block 0xcc00-0xdfff
Alright: DOS kernel shutdown, booting a guest OS
  CS:IP=0000:7c00 SS:SP=7000:0100 AX=0000 BX=7c00 CX=0001 DX=0080
    292975 ERROR BIOS:INT15:Unknown call ax=4101
pixratio 1.200, dw true, dh false
Aspect ratio: 640 x 480  xToY=1.333 yToX=0.750
Screen report: Method 'Win98base' (1920.000 x 1080.000 pixels) at (0.000 x 0.000) (508.000 x 285.750 mm) (20.000 x 11.250 in) (96.000 x 96.000 DPI)
pixratio 1.350, dw false, dh false
Aspect ratio: 720 x 540  xToY=1.333 yToX=0.750
Screen report: Method 'Win98base' (1920.000 x 1080.000 pixels) at (0.000 x 0.000) (508.000 x 285.750 mm) (20.000 x 11.250 in) (96.000 x 96.000 DPI)
pixratio 1.200, dw true, dh false
Aspect ratio: 640 x 480  xToY=1.333 yToX=0.750
Screen report: Method 'Win98base' (1920.000 x 1080.000 pixels) at (0.000 x 0.000) (508.000 x 285.750 mm) (20.000 x 11.250 in) (96.000 x 96.000 DPI)
  19067744 ERROR BIOS:INT15:Unknown call ax=D800
  19067758 ERROR BIOS:INT15:Unknown call ax=D800
  19067772 ERROR BIOS:INT15:Unknown call ax=D800
  19067786 ERROR BIOS:INT15:Unknown call ax=D800
  19067800 ERROR BIOS:INT15:Unknown call ax=D800
  19067814 ERROR BIOS:INT15:Unknown call ax=D800
  19067828 ERROR BIOS:INT15:Unknown call ax=D800
  19067842 ERROR BIOS:INT15:Unknown call ax=D800
  19067856 ERROR BIOS:INT15:Unknown call ax=D800
  19067870 ERROR BIOS:INT15:Unknown call ax=D800
  19067884 ERROR BIOS:INT15:Unknown call ax=D800
  19067898 ERROR BIOS:INT15:Unknown call ax=D800
  19067912 ERROR BIOS:INT15:Unknown call ax=D800
  19067926 ERROR BIOS:INT15:Unknown call ax=D800
  19067940 ERROR BIOS:INT15:Unknown call ax=D800
  19067954 ERROR BIOS:INT15:Unknown call ax=D800
Limit check 7fb50+4-1 = 7fb53 > ffff DS:SI
Segment limit violation
DOSBox-X has switched to max cycles, because of the setting: cycles=auto.
If the game runs too fast, try a fixed cycles amount in DOSBox-X's options.
  19167668 ERROR CPU:Illegal Unhandled Interrupt Called 68
  20504710 ERROR CPU:Illegal Unhandled Interrupt Called 68
INT13: Check Extensions Present for drive: 0x80
INT13: Check Extensions Present for drive: 0x81
INT13: Check Extensions Present for drive: 0x82
INT13: Check Extensions Present for drive: 0x83
APM BIOS: Connected to 32-bit protected mode interface
APM BIOS: OS disconnected
  37994673 ERROR CPU:Illegal Unhandled Interrupt Called 68
  44463917 ERROR CPU:Write 0 to rom at e00a0
  44463918 ERROR CPU:Write ffff to rom at e00a2
  44463939 ERROR CPU:Write ffff to rom at e00a2
  44463941 ERROR CPU:Write ffff to rom at e00a0
  44463957 ERROR CPU:Write 0 to rom at e08a0
  44463958 ERROR CPU:Write ffff to rom at e08a2
  44463979 ERROR CPU:Write ffff to rom at e08a2
  44463981 ERROR CPU:Write ffff to rom at e08a0
  44464098 ERROR CPU:Write 0 to rom at e10a0
  44464099 ERROR CPU:Write ffff to rom at e10a2
  44464120 ERROR CPU:Write ffff to rom at e10a2
  44464122 ERROR CPU:Write ffff to rom at e10a0
  44464138 ERROR CPU:Write 0 to rom at e18a0
  44464139 ERROR CPU:Write ffff to rom at e18a2
  44464160 ERROR CPU:Write ffff to rom at e18a2
  44464162 ERROR CPU:Write ffff to rom at e18a0
  44464279 ERROR CPU:Write 0 to rom at e20a0
  44464280 ERROR CPU:Write ffff to rom at e20a2
  44464301 ERROR CPU:Write ffff to rom at e20a2
  44464303 ERROR CPU:Write ffff to rom at e20a0
  44464319 ERROR CPU:Write 0 to rom at e28a0
  44464320 ERROR CPU:Write ffff to rom at e28a2
  44464341 ERROR CPU:Write ffff to rom at e28a2
  44464343 ERROR CPU:Write ffff to rom at e28a0
  44464460 ERROR CPU:Write 0 to rom at e30a0
  44464461 ERROR CPU:Write ffff to rom at e30a2
  44464482 ERROR CPU:Write ffff to rom at e30a2
  44464484 ERROR CPU:Write ffff to rom at e30a0
  44464500 ERROR CPU:Write 0 to rom at e38a0
  44464501 ERROR CPU:Write ffff to rom at e38a2
  44464522 ERROR CPU:Write ffff to rom at e38a2
  44464524 ERROR CPU:Write ffff to rom at e38a0
  44464641 ERROR CPU:Write 0 to rom at e40a0
  44464642 ERROR CPU:Write ffff to rom at e40a2
  44464663 ERROR CPU:Write ffff to rom at e40a2
  44464665 ERROR CPU:Write ffff to rom at e40a0
  44464681 ERROR CPU:Write 0 to rom at e48a0
  44464682 ERROR CPU:Write ffff to rom at e48a2
  44464703 ERROR CPU:Write ffff to rom at e48a2
  44464705 ERROR CPU:Write ffff to rom at e48a0
  44464822 ERROR CPU:Write 0 to rom at e50a0
  44464823 ERROR CPU:Write ffff to rom at e50a2
  44464844 ERROR CPU:Write ffff to rom at e50a2
  44464846 ERROR CPU:Write ffff to rom at e50a0
  44464862 ERROR CPU:Write 0 to rom at e58a0
  44464863 ERROR CPU:Write ffff to rom at e58a2
  44464884 ERROR CPU:Write ffff to rom at e58a2
  44464886 ERROR CPU:Write ffff to rom at e58a0
  44465003 ERROR CPU:Write 0 to rom at e60a0
  44465004 ERROR CPU:Write ffff to rom at e60a2
  44465025 ERROR CPU:Write ffff to rom at e60a2
  44465027 ERROR CPU:Write ffff to rom at e60a0
  44465043 ERROR CPU:Write 0 to rom at e68a0
  44465044 ERROR CPU:Write ffff to rom at e68a2
  44465065 ERROR CPU:Write ffff to rom at e68a2
  44465067 ERROR CPU:Write ffff to rom at e68a0
  44465184 ERROR CPU:Write 0 to rom at e70a0
  44465185 ERROR CPU:Write ffff to rom at e70a2
  44465206 ERROR CPU:Write ffff to rom at e70a2
  44465208 ERROR CPU:Write ffff to rom at e70a0
  44465224 ERROR CPU:Write 0 to rom at e78a0
  44465225 ERROR CPU:Write ffff to rom at e78a2
  44465246 ERROR CPU:Write ffff to rom at e78a2
  44465248 ERROR CPU:Write ffff to rom at e78a0
  44465365 ERROR CPU:Write 0 to rom at e80a0
  44465366 ERROR CPU:Write ffff to rom at e80a2
  44465387 ERROR CPU:Write ffff to rom at e80a2
  44465389 ERROR CPU:Write ffff to rom at e80a0
  44465405 ERROR CPU:Write 0 to rom at e88a0
  44465406 ERROR CPU:Write ffff to rom at e88a2
  44465427 ERROR CPU:Write ffff to rom at e88a2
  44465429 ERROR CPU:Write ffff to rom at e88a0
  44465546 ERROR CPU:Write 0 to rom at e90a0
  44465547 ERROR CPU:Write ffff to rom at e90a2
  44465568 ERROR CPU:Write ffff to rom at e90a2
  44465570 ERROR CPU:Write ffff to rom at e90a0
  44465586 ERROR CPU:Write 0 to rom at e98a0
  44465587 ERROR CPU:Write ffff to rom at e98a2
  44465608 ERROR CPU:Write ffff to rom at e98a2
  44465610 ERROR CPU:Write ffff to rom at e98a0
  44465727 ERROR CPU:Write 0 to rom at ea0a0
  44465728 ERROR CPU:Write ffff to rom at ea0a2
  44465749 ERROR CPU:Write ffff to rom at ea0a2
  44465751 ERROR CPU:Write ffff to rom at ea0a0
  44465767 ERROR CPU:Write 0 to rom at ea8a0
  44465768 ERROR CPU:Write ffff to rom at ea8a2
  44465789 ERROR CPU:Write ffff to rom at ea8a2
  44465791 ERROR CPU:Write ffff to rom at ea8a0
  44465908 ERROR CPU:Write 0 to rom at eb0a0
  44465909 ERROR CPU:Write ffff to rom at eb0a2
  44465930 ERROR CPU:Write ffff to rom at eb0a2
  44465932 ERROR CPU:Write ffff to rom at eb0a0
  44465948 ERROR CPU:Write 0 to rom at eb8a0
  44465949 ERROR CPU:Write ffff to rom at eb8a2
  44465970 ERROR CPU:Write ffff to rom at eb8a2
  44465972 ERROR CPU:Write ffff to rom at eb8a0
  44466089 ERROR CPU:Write 0 to rom at ec0a0
  44466090 ERROR CPU:Write ffff to rom at ec0a2
  44466111 ERROR CPU:Write ffff to rom at ec0a2
  44466113 ERROR CPU:Write ffff to rom at ec0a0
  44466129 ERROR CPU:Write 0 to rom at ec8a0
  44466130 ERROR CPU:Write ffff to rom at ec8a2
  44466151 ERROR CPU:Write ffff to rom at ec8a2
  44466153 ERROR CPU:Write ffff to rom at ec8a0
  44466270 ERROR CPU:Write 0 to rom at ed0a0
  44466271 ERROR CPU:Write ffff to rom at ed0a2
  44466292 ERROR CPU:Write ffff to rom at ed0a2
  44466294 ERROR CPU:Write ffff to rom at ed0a0
  44466310 ERROR CPU:Write 0 to rom at ed8a0
  44466311 ERROR CPU:Write ffff to rom at ed8a2
  44466332 ERROR CPU:Write ffff to rom at ed8a2
  44466334 ERROR CPU:Write ffff to rom at ed8a0
  44466451 ERROR CPU:Write 0 to rom at ee0a0
  44466452 ERROR CPU:Write ffff to rom at ee0a2
  44466473 ERROR CPU:Write ffff to rom at ee0a2
  44466475 ERROR CPU:Write ffff to rom at ee0a0
  44466491 ERROR CPU:Write 0 to rom at ee8a0
  44466492 ERROR CPU:Write ffff to rom at ee8a2
  44466513 ERROR CPU:Write ffff to rom at ee8a2
  44466515 ERROR CPU:Write ffff to rom at ee8a0
  44466632 ERROR CPU:Write 0 to rom at ef0a0
  44466633 ERROR CPU:Write ffff to rom at ef0a2
  44466654 ERROR CPU:Write ffff to rom at ef0a2
  44466656 ERROR CPU:Write ffff to rom at ef0a0
  44466672 ERROR CPU:Write 0 to rom at ef8a0
  44466673 ERROR CPU:Write ffff to rom at ef8a2
  44466694 ERROR CPU:Write ffff to rom at ef8a2
  44466696 ERROR CPU:Write ffff to rom at ef8a0
APM BIOS: Connected to 32-bit protected mode interface
APM BIOS negotiated to v1.2
Unknown APM BIOS call AX=5312
enable APM for device    1
engage APM for device    1
enable APM for device    1
Plug & Play OS reports itself active
PNP OS changed I/O read port to 0x277 (from 0x20B)
  66655678 ERROR SBLASTER:DSP:Unhandled (undocumented) command  3
VOODOO LFB now at ff000000
VOODOO LFB now at d0000000
C/H/S 0/0/33 out of bounds 0/16/63
IDE abort dh=0xb0 with error on 0x1f0
C/H/S 0/0/33 out of bounds 0/16/63
IDE abort dh=0xb0 with error on 0x170
  71660797 ERROR CPU:Illegal Unhandled Interrupt Called 20
  71661074 ERROR CPU:Illegal Unhandled Interrupt Called 20
  75113907 ERROR BIOS:INT15:Unknown call ax=F963
INT 15h mouse initialized to 3-byte protocol
INT 15h mouse reset
INT 15h reporting mouse device ID 0x00
pixratio 1.350, dw false, dh false
Aspect ratio: 720 x 540  xToY=1.333 yToX=0.750
Screen report: Method 'Win98base' (1920.000 x 1080.000 pixels) at (0.000 x 0.000) (508.000 x 285.750 mm) (20.000 x 11.250 in) (96.000 x 96.000 DPI)
C/H/S 0/0/1 out of bounds 0/16/63
IDE abort dh=0xb0 with error on 0x1f0
C/H/S 0/0/1 out of bounds 0/16/63
IDE abort dh=0xb0 with error on 0x170
Fast Forward ON
Fast Forward OFF

Additional information

No response

Have you checked that no similar bug report(s) exist?

• I have searched and didn't find any similar bug report.

Code of Conduct & Contributing Guidelines

• I agree to follow the code of conduct and the contributing guidelines.

[rderooy]

I see that your using some folder mounts. Note that still has quite some issues when used with something like Win9x, and I would not recommend using it. Do you also have issues without it?

I just tried to boot up Win95 OSR2.5 twice in a row, and did not have any problems with the startup or shutdown. Same for a Win98SE image.

This was on a Linux host with DOSBox-X 2024-10-01

[gingusScringus]

I see that your using some folder mounts. Note that still has quite some issues when used with something like Win9x, and I would not recommend using it. Do you also have issues without it?

I just tried to boot up Win98 OSR2.5 twice in a row, and did not have any problems with the startup or shutdown. Same for a Win98SE image.

This was on a Linux host with DOSBox-X 2024-10.01

Actually, that WOULD be an issue for me.

The folders I've mounted other than the hdd.img for Windows 95 are commonly used for normal DOSBox usage with DOS, which I usually add things like programs, games, tracker modules, etc, which I probably do a lot. Using .imgs would be a hassle for me to just add a single file, since I have to use an external program to do this instead of just using Windows Explorer.

Also, uh... I don't think a Windows 98 OSR 2.5 ever exists? I'll take that as a typo.

[rderooy]

Sorry, that was indeed a typo.

[gingusScringus]

Sorry, that was indeed a typo.

It's okay. 👍

Also, I want to note that I have a Windows 3.1 and ME install with my own folder directory set like in the config above (minus the -label parameter), which I don't see any problems with it... But that's probably because I installed them already before this problem happens.

You also mentioned about Windows 98SE, which I just realized that I haven't tried out installing 98 ever on DOSBox-X, and I'm curious if this problem also happens on other fresh installs of Windows 9x (98, ME). Going to try this now.

[rderooy]

Folder mounts are only an issue when booting a guest OS, if your Win 3.1 is run directly from the DOSBox-X shell, you would not have the issue.

But Win9x/ME can only be run from their own OS, so you must boot them.

More recent versions of DOSBox-X indeed now have limited support for folder mounts when booting a guest OS, but the support has not been extensively tested, and for instance do not support persistent writes. So any writes will be lost when you reboot.

[gingusScringus]

Folder mounts are only an issue when booting a guest OS, if your Win 3.1 is run directly from the DOSBox-X shell, you would not have the issue.

But Win9x/ME can only be run from their own OS, so you must boot them.

More recent versions of DOSBox-X indeed now have limited support for folder mounts when booting a guest OS, but the support has not been extensively tested, and for instance do not support persistent writes. So any writes will be lost when you reboot.

Alright, so... after installing Windows 98SE for what it feels like 2 years, I booted into the OS after the setup, shut it down, add my folder mounts, but it booted again with no black screens and my folder mounts are there! (except for the Tracker Modules directory which didn't show up because of the T: drive letter, but this was fixable by changing it).

As for the writing problem... you're right, it did not save any writes I've done. I tried modifying or adding a file (in this case, a .txt file) but after a restart, the modifications were gone.

I suppose that's not really a huge problem? Since usually what I do with DOSBox-X is just playing tracker modules on a tracker, or playing DOS games which I could probably move to the C: drive itself? Maybe it is a problem for me in the future...

But what about that problem with Windows 95? I believe there's SOME workaround on this, as I said, my first Win95 install was back in 2024.07.01, and this problem already appeared on that same version before I upgraded to 2024.10.01 today. Maybe this problem is due to a faulty configuration on my host computer?

[rderooy]

I don't know what the issue is with your Win95 setup. As I said, my Win95 installation seems fine. But then it was not uncommon for Win95 to get corrupted, especially when installing additional software even back in the day. Again, did you try without the folder mounts? You may also want to remove drives like the empty A: and B: drives. Support for empty drives is also very recent and there are still some issues with it.

[gingusScringus]

I don't know what the issue is with your Win95 setup. As I said, my Win95 installation seems fine. But then it was not uncommon for Win95 to get corrupted, especially when installing additional software even back in the day. Again, did you try without the folder mounts? You may also want to remove drives like the empty A: and B: drives. Support for empty drives is also very recent and there are still some issues with it.

I found the problem, it's because of this: IMGMOUNT D empty -t iso -ide 2m

I was prodding around the .conf file by firstly commenting out the folder mount commands, including the emptied out drive D:. It booted with no problem.

Just to make sure, I uncommented the folder mount commands EXCEPT the IMGMOUNT D empty -t iso -ide 2m command. There's the problem.

Screen.Recording.2024-10-06.002857.mp4

Screen.Recording.2024-10-06.003548.mp4

I hope you get what I'm trying to do in both videos. I was recording frantically by the Snipping Tool recorder feature from crashing for no god damn reason if I recorded too long. I don't feel like using OBS just to record a simple footage.

[maron2000]

Booting guest OSs with empty disks mounted are not yet mature such as already reported in #4988.
If you need to swap floppy or CD disks, mount a dummy image instead which should have no problems.