search

dosemu2 / comcom64

64bit command.com
https://github.com/dosemu2/comcom32/
GNU General Public License v3.0
32 stars 5 forks source link

Using comcom32 breaks custom setup with 'drive_c' #3

Closed bolle732 closed 5 years ago

bolle732 commented 5 years ago

When I have activated comcom32 (together with fdpp), I cannot start anymore my custom setup, which has the files too in a folder named drive_c, as the default under ~/.dosemu.

Error message: ERROR: Bootable drive not found, exiting

Renaming either ~/.dosemu/drive_c or ~/<CUSTOM>/drive_c to another name makes it work again.

The custom setup use this to start DOSEMU2: /usr/local/bin/dosemu.bin --Fimagedir $G_DOSEMU_HOME -f $G_DOSEMU_HOME/dosemurc $@

Would it be better to check for boot files in the provided paths first and then if not found check in the default paths ?

bolle732 commented 5 years ago

In dosemurc I have specified:

$_hdimage = "./drive_c"

stsp commented 5 years ago

Yes, but its better to have this ticket in dosemu2. comcom32 does not define the boot sequence.

bolle732 commented 5 years ago

Ok, I'll close this ticket and open another one in dosemu2.