What does "shared drive in booted images" mean?

I'm guessing cdrom drive/image access after booting DOS or Win9x. I think an ATA/ATAPI emulation is required to support the device drivers in DOS (e.g. DEVICE=OAKCDROM.SYS), and the ATAPI drivers in Win9x. If the OP is referring to local drive access after booting, ugh, don't know how that could be done.

As for sharing a drive image between different instances of DOSBox, well, that doesn't really seem like it would work. I mean, can two computers use the same physical hard drive simultaneously? (N.B. a fileserver is ONE computer using the PHYSICAL drive).

ripsaw8080 wrote:

I'm guessing cdrom drive/image access after booting DOS or Win9x. I think an ATA/ATAPI emulation is required to support the device drivers in DOS (e.g. DEVICE=OAKCDROM.SYS), and the ATAPI drivers in Win9x. If the OP is referring to local drives, ugh, don't know how that could be done.

Maybe via networking adapter emulation or something 🤣

do you have games that need it ? (DOS games to be precise)

Maybe you could use hal's megabuild with network support, boot a server, boot some clients, get them connected to one another. Didn't think that's what was being asked for, but it might be a challenge to kill time with.

Wouldn't hooking Int 13 work? I would guess stuffing the DOSBox handler inside a DOS TSR that hooks Int 13 would be what's needed.

Squishing a folder-mount into a sector based int13 device may of course work,
but that creates certainly so many problems that you won't even start coding that.

I am pleased to see a booted image that can communicate with the host (outside world), that's it... Thanks
Jack

not enough reason to add it.