For the record I found the solution to the problem I
described earlier.
Basically, the dos 16-bit ( or real mode?) cd driver that
one specifies in the config.sys on the win95 boot install
floppy cannot be just any old cd driver (vide-cdd.sys,
or whatever) that might have
come with your cd drive. These will work on a normal bare
pc but will not always work on a boot disk used to boot a
virtual machine.
A `good' cd driver can be found at http://www.mitsumi.com
Click on the US link and look for `Drivers and Documentation'
The file was called ide158.exe, a self-extractor that contains
the good mitsumi cd driver.
This info is available at http://www.vmware.com - search for `atapi'
-Josh
On Sun, May 06, 2001 at 05:34:43AM +0000, Joshua Burvill wrote:
> I was wondering if anyone might be able
> to give me a pointer with this.
>
> When I boot the vm from a windows/dos
> boot up floppy with the dos cd driver,
> most of the time it says that no cdrom
> drive can be found. There are no kernel
> messages associated with this.
>
> On two occasions the dos cd driver actually loaded but the speed
> when accessing the cdrom was exceedingly slow - it took about a minute
> to do a dir listing of the cd.
>
> BTW, the cd drive works perfectly well except within the vm
>
> ** Using debian 2.2r2, kernel 2.2.15, vmware workstation 2.0.1
>
> TIA, Josh
>
> PS When running with kernel 2.4.3, I also
> had a lot of errors trying to read
> the floppy drive from the vm, which is
> why I am currently using an older kernel,
> which has improved the situation quite a
> bit, although I still get the occasional
> error:
> kernel: end_request: I/O error, dev 02:00 (floppy), sector 0
>
> --
> SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
> More Info: http://slug.org.au/lists/listinfo/slug
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
