Clearly it used to load or I would not have an OS/2 installation.

But now, it loads when booting E: and fails when booting A: and D: on the same
box with the same file.

I tried jjscdrom.dmd without success although it works on another box.

I compared the config.sys files for the 3 partitions but nothing jumped out at
me.

What might be happening here?

On Thu, 24 Nov 2005 07:03:49 UTC in comp.os.os2.misc, johnsuth@nospam.com.au
wrote:

It doesn't load when it can't find any CD drives for it to operate. Probably
it's other drivers that are different and os2cdrom.dmd is just a symptom not the
cause.

--
Trevor Hemsley, Brighton, UK.
Trevor-Hemsley at dsl dot pipex dot com

Trevor Hemsley wrote:
Couldn't it be the IBM1S506.add that needs updating??

Rich W

In <c1.2c.2ywXky$0L7@PC1.ACENET.COM.AU>, johnsuth@nospam.com.au writes:

Well one solution is to replace the DVD writer (slave on IDE0) with a CD reader
(master on IDE0). This enabled me to reinstall Warp on D:

Another solution is to change the DVD to master. This enabled D: to boot as E:
always booted using the same driver version.

I guess Trevor was right in that the Sony DVD writer did not look sufficiently
like a CD ROM, but why does the view change according to the drive I am booting
from?

On Fri, 25 Nov 2005 04:44:37 UTC, johnsuth@nospam.com.au wrote:

Well, first of all, having a SLAVE, without a MASTER, is not correct,
and it really shouldn't work, at all, ever (but, usually does,
especially with windows). If you have a single drive, it should be a
master, if you have a second drive, on tha same interface, it must be
a slave. If you don't follow that simple rule, you will, eventually,
have a problem.

Other considerations (although new devices don't necessarily, have the
problems):

Never use a CD drive, as a master to anything other than another CD
drive.

Always use the newer drive as the master (unless it conflicts with the
previous rule).

Don't mix CD, or DVD. drives, on the same interface as a hard disk
(performance problems).

Always connect a single drive to the end of the cable (not the
center), if the cable has more than one connector on it.

Hope this helps...
--
From the eComStation 1.2 of Doug Bissett
doug dot bissett at attglobal dot net
(Please make the obvious changes, to e-mail me)

Doug Bissett wrote:
Except for those drives which have a jumper setting for single.

if you have a second drive, on tha same interface, it must be
If you have an appropriate cable, it is also possible to jummper all drives as
cable select; then the master/slave status of each drive is determined by which
connector is plugged into it.

Does it help to have a CD in the drive?

On Thu, 24 Nov 2005 07:03:49 UTC, johnsuth@nospam.com.au wrote:


--
Chuck McKinnis
mckinnis@sandia.net
Covenant Solutions
http://7cities.net/~mckinnis/

In <J4Lhf.170132$Io.159769@clgrps13>, "James J. Weinkam" <jjw@cs.sfu.ca> writes:
There was a master drive on the DVD cable; I just did not mention it.

I assume that the master/slave concept is tied to the flat ribbon daisy chain
cable, which is all I had ever seen until the recent arrival of point to point
cables sheathed in pretty colours. (how do they handle crosstalk, or is
reflection the limiting factor for data rate?) And what selection should I make
for these cables?

I recall that drives come out of the box with the jumper on cable select, but I
have never tried it. What might happen?

On Sat, 26 Nov 2005 05:45:02 UTC, johnsuth@nospam.com.au wrote:

It will work, if you have the proper cable, and if all of the drives
(1, or 2) are jumpered to use cable select, and if the controller has
that capability. Personally, I have never tried cable select, but I
have no doubt that it works. You can change the master/slave
relationship by simply changing the jumpers, and not changing the
relative position on the cable. It really doesn't matter which of the
two devices is master, and which is the slave (other than for
following the "rules", that I posted earlier).

I am not sure what you mean by "point to point cables"? If you mean
the new SATA cables, they can only be used by SATA drives to SATA
controllers. PATA drive cables (the old IDE flat cables) come in two
flavors. One is 40 wires, and can only be used with slow devices
(ATA33). To use faster devices (ATA66, ATA100, etc.), you need to use
an 80 wire cable. Those 80 wire cables come with color coded
connectors on them, but they still work the same as the older 40 wire
cables, they simply have more ground wires between the signal wires. I
know that the old 40 wire cables can have either two, or three,
connectors, depending on if you have one, or two, devices on the
interface (somebody decided to save a few cents, and somebody else
made a lot of money, selling three connector cables, to replace the
two connector ones). I haven't seen, or even heard of, a 2 connector
80 wire, cable.

Hope this helps...
--
From the eComStation 1.2 of Doug Bissett
doug dot bissett at attglobal dot net
(Please make the obvious changes, to e-mail me)

On Thu, 24 Nov 2005 07:03:49 UTC, johnsuth@nospam.com.au wrote:

I don't know if you've solved your problem or not, but if your
config.sys has a statement like this

BASEDEV=DANIATAP.FLT

then you might want to check that DANIATAP.FLT in your \os2\boot\
directory isn't called DANIATAPI.FLT. (Note the "I"). I've seen setups
with the exact opposite as well. Either will give you the OS2CDROM.DMD
problem that you are experiencing.

FYI, some versions of the driver are labled slightly differently. The
"I" was dropped to fit on a floppy disk.

--
__________________________________________________ ___________________


-= B e n D r a g o n =-

BDragon@self-wrighting.net

__________________________________________________ ___________________
__________________________________________________ ___________________

Sir:

johnsuth@nospam.com.au wrote:
<snip>

I read somewhere that the wires are paired and they use differential
signaling. The electrical field away from the wire pairs has a net of
zero voltage, and thus no radiation.
--
Bill
Thanks a Million!