For daily builds, based on the currect developer version, check this: CVS Builds (once a week)

1. search the forum
2. search the forum
5. search the forum & make an iso | get a 4 speed cdrom drive

3&4 read the readme especially the part about ioctl

Please post your system specs as well as that's quite important when dealing with cdrom problems

OK I had passed about 2 hours reading this forum, and searching, so I was a little tired when I posted my questions. OK I will search the forums. OK OK.

I thought I had read carefully the readme file, but couldn't find out the clue. I love your answers, cubix 😁
Extract from the readme file :

-ioctl
Forces to use ioctl commands. Only valid if mounting a cdrom under
windows which support them (Win2000/XP/NT)

Oh yeah, it's not really crital clear, I wouldn't have asked if it was easy. What is IOCTL ?! 😈

My CD-ROM drive : pionner SCSI 36x
My DVD-RW drive : SONY DRU 510A
Motherboard : ASUS P4P800 Deluxe
CPU : P4 3,3GHz
Sound card : SB512 (crappy, I know)
AGP card : GeForce 4 Ti 4200
OS : WinXP Pro

So, any good idea why the MOUNT.EXE command is launched instead of LOOM.EXE for item #4 ? I'm gonna try tonight to update my ASPI drivers, one never knows.

Oh, I forgot the most important : DosBox version 0.61 🤣

IOCTL: Name of system call (I/O Control).

I only know it from my experience with Unix, so I was surprised to learn that it is an Win32 thing. I suppose the ioctl() function has been promoted to a POSIX function, and that is why it is available under Win32?
--
MiniMax - Not a developer, I haven't even seen the DOSBox source.

I updated my aspi drivers -> no more aspi errors !

But loom still don't want to launch with the -aspi option, grrr. What can I do ? 🙁

CRY

"But loom still don't want to launch with the -aspi option, grrr. What can I do ?"

bah. i got it running just fine using the -ioctl tag for the cdrom-drive and giving it the label LOOM (eg: mount d d:\ -t cdrom -ioctl -label LOOM).
perhaps you could try the same, but in stead of using -ioctl, use -aspi.
i might have a different version than your version of Loom though.

anyway, if you still can't get Loom to work under DosBox, try using ScummVM. (www.scummvm.org)

hope this helps...

Well, let's star over, english is not my mother language, so I'll try to explain again :

I mount my SCSI CD-ROM drive with the command line :
mount d z:\ -usecd 1 -t cdrom
(Z is my CD-ROM drive letter under Windows)

I can launch Loom or any other old dos game from a CD with the -ioctl option. I can't put another CD in the drive after that, no file is listed anymore, with ANY CD.

When I use the -aspi option, I can put another CD and access it, no problem. But I can't launch Loom any more, the program tells me I have to get the Loom CD in order to play the game...

What's bothering me is the following : OK I can play Loom with -ioctl. Fine. But I can't insert another CD after that, it won't be "seen" by dosbox. What if I'd like to play my original Discworld II, which is on 2 CD's ? I will be able to play as long as I don't have to put the 2nd CD in my drive.

(but, if you read carefully my first message, you already know that I also have a real 486, why is it so important to launch Loom under WinXP ? Nope, it's not important, I'm just a little curious you know)

*clears throat*

you still didn't try out my suggestion.
try adding the label LOOM when mounting your cdrom-drive.
so after the "-t cdrom" part, also use "-label LOOM"...
see if that works.

No, it doesn't work with -aspi -label LOOM, in any drive (CD or DVD).

As stated before, it works perfectly with -ioctl and without any label... But I can't eject the CD and put in another one. Now that I have upgraded my ASPI drivers, I get a message about an incorrect label when putting another CD in the drive after having read the first one.

I'm wondering if it's not because I don't have a common CD-ROM drive (IDE). I only have a SCSI CD-ROM or an IDE DVD-RW. One day maybe I'll try to mount an old CD drive lying somewhere in my house... When I have time.

So : no need to specify the label in the MOUNT command line to play Loom. It means also that dosbox reads correctly the first CD label, but can't read a new one after. Maybe a little detection trick would do in the next version of the program ? There must be a flag in the windows system that tells that a CD was ejected or inserted... Or an event... I'm wondering why the path must be specified when using the -usecd option ?

Thanks for the tip, though, even if it didn't work 😀 I think it must be useful when trying to launch a non-genuine CD-ROM game with the wrong label...