Hi there

I had created some CD image with a software called Alcohol 120% under Windows. Those image have a .mds/.mdf extention.

Now I'm migrating to linux and would like to mount them. I had google for it and search some linux forums but haven't find a answer yet.

Anyone know how can I mount .mds file under linux? I don't want to convert them back to ISO as there're many of them.

Thanks!

http://mark.foster.cc/kb/tips.html

sorry, do you see some reference in that url link to something related to .mdf/.mds?? because i dont

im having trouble with this too. did you find a solution?

im prepared to convert them to iso though. what program could do that?

Yeah, i need to know how to do that too...

How far did you get?

nowhere - luckily i was doing it on a windows box so i could download magiciso i think, which i used to convert it to an iso.

hmm, looks like im gonna have to find a box to install win onto =\

Cheers

you could do it with vmware (or bochs if you a) can be bothered and b) will need to do it outside a 30 day period) and save trouble probably.

Yeah, i'm installing vmware on my box now. I'm running slack 9.1 with 2.6.6 kernel and I get an error when building the module. (I see you run slack9.1 so i'm guessing you might have installed vmware on there?)

Anyway, i get this output -

Thanks for any help

Stopping VMware services:
Virtual machine monitor done

Trying to find a suitable vmmon module for your running kernel.

None of VMware Workstation's pre-built vmmon modules is suitable for your
running kernel. Do you want this program to try to build the vmmon module for
your system (you need to have a C compiler installed on your system)? [yes]

Using compiler "/usr/bin/gcc". Use environment variable CC to override.

What is the location of the directory of C header files that match your running
kernel? [/lib/modules/2.6.6/build/include]

Extracting the sources of the vmmon module.

Building the vmmon module.

Building for VMware Workstation 4.0.x.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config1/vmmon-only'
make -C /lib/modules/2.6.6/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.6'
CC [M] /tmp/vmware-config1/vmmon-only/linux/driver.o
/tmp/vmware-config1/vmmon-only/linux/driver.c:144: warning: initialization from incompatible pointer type
/tmp/vmware-config1/vmmon-only/linux/driver.c:148: warning: initialization from incompatible pointer type
/tmp/vmware-config1/vmmon-only/linux/driver.c: In function `Panic':
/tmp/vmware-config1/vmmon-only/linux/driver.c:2994: warning: implicit declaration of function `_exit'
CC [M] /tmp/vmware-config1/vmmon-only/linux/hostif.o
CC [M] /tmp/vmware-config1/vmmon-only/common/vmx86.o
CC [M] /tmp/vmware-config1/vmmon-only/common/memtrack.o
CC [M] /tmp/vmware-config1/vmmon-only/common/phystrack.o
CC [M] /tmp/vmware-config1/vmmon-only/common/cpuid.o
gcc -Wall -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=pentium4 -Iinclude/asm-i386/mach-default -O2 -fomit-frame-pointer -DMODULE -Wall -Wstrict-prototypes -DVMWARE__FIX_IO_APIC_BASE=FIX_IO_APIC_BASE_0 -DVMW_HAVE_EPOLL -DVME_DEFAULT=VME_V4 -DVMW_USING_KBUILD -I/tmp/vmware-config1/vmmon-only/./include -I/tmp/vmware-config1/vmmon-only/./common -I/tmp/vmware-config1/vmmon-only/./linux -fno-exceptions -c -o /tmp/vmware-config1/vmmon-only/common/task.o /tmp/vmware-config1/vmmon-only/common/task.C
LD [M] /tmp/vmware-config1/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST
*** Warning: "_exit" [/tmp/vmware-config1/vmmon-only/vmmon.ko] undefined!
CC /tmp/vmware-config1/vmmon-only/vmmon.mod.o
LD [M] /tmp/vmware-config1/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-2.6.6'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-config1/vmmon-only'
Unable to make a vmmon module that can be loaded in the running kernel:
insmod: error inserting '/tmp/vmware-config1/vmmon.o': -1 Unknown symbol in module
There is probably a slight difference in the kernel configuration between the
set of C header files you specified and your running kernel. You may want to
rebuild a kernel based on that directory, or specify another directory.

For more information on how to troubleshoot module-related problems, please
visit our Web site at "http://www.vmware.com/download/modules/modules.html" and
"http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html".

Execution aborted.

im using hte same stuff as you and it worked fine. if you can be bothered, just try recompiling the kernel and making sure the /usr/src/linux symlink is pointing in the right place. it should work after that.

yay my 200th post

hmm, i tried that... it should point to /usr/src/linux-2.6.6 right?

yeh, and also make sure that /lib/modules/`uname -r`/build points to /usr/src/linux-`uname -r`

yeah, i just checked that and that seesm fine.
however, my /lib/modules/2.6.6/kernel/drivers/net is completley empty... could this be why it is not building the modules, and if so why is it empty?

Cheers

id just go with the kernel recompile if i was you - it only takes about 10 mins to configure and then waiting for about 1/2 an hours on 1ghz - less if you have a faster comp.

Did anyone ever find a reasonable way to mount MDF/MDS files created with alcohol? I would really appreciate a reply.