Sophie: opencbm-0.4.2a-5mdv2010.0 i586

opencbm-0.4.2a-5mdv2010.0.i586.rpm

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
 <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
 <TITLE>OpenCBM 0.4.2 Users Guide: Known bugs and problems</TITLE>
 <LINK HREF="opencbm-31.html" REL=next>
 <LINK HREF="opencbm-29.html" REL=previous>
 <LINK HREF="opencbm.html#toc9" REL=contents>
</HEAD>
<BODY>
<A HREF="opencbm-31.html">Next</A>
<A HREF="opencbm-29.html">Previous</A>
<A HREF="opencbm.html#toc9">Contents</A>
<HR>
<H2><A NAME="knownbugs"></A> <A NAME="s9">9.</A> <A HREF="opencbm.html#toc9">Known bugs and problems</A></H2>

<P>There are some known problems in OpenCBM:</P>
<P>
<UL>
<LI><I>cbmcopy</I> is still known to have some protocol races, especially with
1581 drives; thus, it does not always work reliably.</LI>
<LI><I>cbmctrl detect</I> as well as <I>cbmcopy</I> and <I>d64copy</I> do not
recognize the drive type if some custom ROM is used.</LI>
<LI>Windows: If you have any other devices connected to your parallel port,
you cannot use them as long as cbm4win is installed. In this case, either
remove OpenCBM whenever you want to access that other device, or install
OpenCBM with <I>instcbm --lock=no</I> and make sure to issue <I>cbmctrl lock</I>
before accessing the drive, and <I>cbmctrl unlock</I> afterwards.</LI>
<LI>Windows: Third party PCI parallel port cards are problematic.
In fact, I tried several, but none of them did work with
OpenCBM on Windows currently. Anyway, I have had at least one positive
report that this is possible.
It seems the drivers for such parallel port cards do not specifically
allow the interrupt to be routed to the PC, as most parallel devices
nowadays do not need the interrupt. Unfortunately, this is not true
for OpenCBM, which actually needs it!</LI>
</UL>
</P>

<HR>
<A HREF="opencbm-31.html">Next</A>
<A HREF="opencbm-29.html">Previous</A>
<A HREF="opencbm.html#toc9">Contents</A>
</BODY>
</HTML>