Message-ID: <000401c0982b$a9610f60$7cbfabd4@whitedragon>
From: "White Dragon" <white DOT dragon AT tin DOT it>
To: <opendos AT delorie DOT com>
References: <01FD6EC775C6D4119CDF0090273F74A4021F6D AT emwatent02 DOT meters DOT com DOT au>
Subject: Re: OTI9xx IDE controller chip (was chs pin)
Date: Fri, 16 Feb 2001 12:53:33 +0100
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Reply-To: opendos AT delorie DOT com

> Now, regarding your driver - make sure it is for that
> particular drive, not another drive using the same
> controller chip! I know I tried a few different drivers,
> all written by Oak for various drive manufacturers,
> all using the same IDE controller chip, yet only
> the driver from NEC (written by Oak) worked with
> this drive! These days it's not such a problem,
> because all drives _should_ now conform to the
> ATAPI standard, but for older drives, you really
> must use the correct driver!

> Joe.

I used the driver shipped with the cdrom drive.
ops! I forgot that under dos it worked perfectly.
The problems began when i tryed to access the drive
using 32 bit drivers (eg. like under linux or windows 95b)
Now i have a dvd Pioneer 105s 16x 40x which is IMHO a great
piece of hardware (plus, i belive it is a first release drive
because i can unlock it easly. My friend has the next firmware
release and it is difficult to rip copy protected tracks
and scrambled files), and a Philips CDD 3610 R-RW Eide.
I have no probs with them.

there is a way to discover if the cd reader does audio interpolation
while reads? I suspect this because audio reading is locked to 12x.
Should i proceed with checksum comparation? (i dont think it is an
affidable way)

BTW I want to advice anyone who intends to buy or use Audioactive production
studio.
It is an Rip/encoding audio suit that uses Fraunhofer IIS mp3 encoder. After
installation the program suggests to install a CDFS driver. The first time i
didn't noticed it and i skipped the installation. After several days, I
reinstalled the suite and i decided to try it. Well... That driver makes a
mess with windoze ones. So after rebooting i had two removable drives
instead of two cdroms...
Ilarious isn't it? I had to reinstall windows. Infact, even removing the
driver manually with all of its registry entries, replacing system.dat with
a backup copy, the problem remained.

White D