VOGONS


First post, by ErikGG

User metadata
Rank Member
Rank
Member

Whenever I start DOSBox and open the mounted diskdrive before Fallout starts I get the following error, see the screenshot.

This happens in DOSBox 0.65, 0.70 and 0.71.

After pressing cancel "Annuleren" then fallout starts without any problem.

Erik.

Read the new FAQ.doc

Reply 1 of 7, by Qbix

User metadata
Rank DOSBox Author
Rank
DOSBox Author

opening a mounted drive ? Is that actually possible in windows ?
In linux the tray won't open.

Water flows down the stream
How to ask questions the smart way!

Reply 2 of 7, by ErikGG

User metadata
Rank Member
Rank
Member

Seems so,

Just tried it again in 0.71 and it can be opened.

Erik

Read the new FAQ.doc

Reply 3 of 7, by ErikGG

User metadata
Rank Member
Rank
Member

Might be interresting in this situation :
Windows 2000 SP4

Tried IOCTL and no options for the CDRom device.

Erik.

Read the new FAQ.doc

Reply 4 of 7, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Windows doesn't lock the CD drives as Linux does.

1+1=10

Reply 5 of 7, by ErikGG

User metadata
Rank Member
Rank
Member

I'm using the folowing function to lock the cdrom drive while extracting the audio from a game disk in my experiental Audio extractor.

procedure NTStyleTrayLock(Device: THandle; Lock: Boolean);
var
Dummy : Cardinal;
PMR : TPREVENT_MEDIA_REMOVAL;
begin
if Lock then
PMR.PreventMediaRemoval := 1
else
PMR.PreventMediaRemoval := 0;
DeviceIoControl(Device, IOCTL_STORAGE_MEDIA_REMOVAL, @PMR,
sizeof(PMR), nil, 0, Dummy, nil);
end;

Erik.

Read the new FAQ.doc

Reply 6 of 7, by Qbix

User metadata
Rank DOSBox Author
Rank
DOSBox Author

not sure if that is a good idea. Under linux it is quite hard to change cdroms when in dosbox, because of this locking.

Water flows down the stream
How to ask questions the smart way!

Reply 7 of 7, by ErikGG

User metadata
Rank Member
Rank
Member

I wouldn't lock it too as I would like to keep this functionality, freedom over the CD-Rom (Swapping disks using CTRL-F4).

Read the new FAQ.doc