- How can i get HD (master) to work with CDROM (slave) on
A4000 - both IDE drives. CDrom is LG 52X. i can also put
in TEAC drive...
- Must I use SCSI controller card with SCSI cdrom??? (last
resort)
- Is / Was there something wrong with my A4000 when that
happened? Should that hard disk never boot? (it does
mount when booting from my 2nd HD though which has IDE
FIX)...
If you could provide any info how to get a 2nd drive (CDROM
IDE) to work with A4000 that would help...
thanks in advance for any help.
Make sure the HD is bootable - check&correct with the WB's
HDInstall-tool and "install".
Use the boot-menu (hold down both mousebuttons during boot) to check
which drives have been recognized. Try disabling all others except the
HD. If it boots, then there's a boot priority problem. Set the boot
priority with HDInstall.
> I took 2nd hd and installed WB again.
> Now it boots. I installed IDE FIX from aminet. It won't
> mount my cdrom...(even though its connected) i'm getting
> really tired and must go to work tomorrow :-(
I might be wrong, but maybe the internal IDE controller only supports 2
devices max.
>
> - How can i get HD (master) to work with CDROM (slave) on
> A4000 - both IDE drives. CDrom is LG 52X. i can also put
> in TEAC drive...
Did you set the master/slave jumpers correctly on these drives?
>
> - Must I use SCSI controller card with SCSI cdrom??? (last
> resort)
Unless you have a A4000T there's no SCSI-controller onboard. Before you
buy a SCSI controller consider a USB card like Algor-Z2 or
Mediator/Spider-PCI, and a USB-connected CDROM.
For the CDROM you need a filesystem software (i.e. L:XyzCDFS) and a
mountlist for it.
OS3.9 has CacheCDFS bundled, but you can also use AmiCDFS from Aminet.
The mountlist should come with the CDFS and look like this:
Device = scsi.device
Unit = 2
FileSystem = L:AmiCDFS
Flags = 0
BlocksPerTrack = 32
BlockSize = 2048
Reserved = 0
LowCyl = 0
HighCyl = 11000
Surfaces = 1
Buffers = 64
BufMemType = 1
Mask = 0x7fffffff
GlobVec = -1
Priority = 10
DosType = 0x43444653
StackSize = 600
Mount = 1
Normally a file named "CD0" under Devs:DOSDrivers with "C:Mount" as
tooltype. It should be installed by the CDFS installer.
Make sure that the "Unit" parameter is the correct one for your CDROM.
The device would be scsi.device when using the normal internal IDE
controller (it emulates SCSI) without 3rd party IDE drivers.
Once you doubleclick on the Mountlist, you might still have to type
"diskchange cd0:" or reinsert the cdrom, then it should appear on the
desktop.
If scsi.device doesn't work, try the atapi-device installation from
IDEfix
in the mountlist of AmiCDFS (or CacheCDFS).
Could think of only 2 possibilities for it not working under OS3.9 but
OS3.1:
1. one of the required files is different: the Mountlist, the
L:CacheCDFS-file or the IDEfix-atapi.device
2. a version conflict of the identical files from OS3.1 with some OS3.9
changes
If 1. is the case, copying all the required files identically from the
working OS3.1 installation to OS3.9 should work.
If 2. is the case, maybe you should use the CacheCDFS from the
OS3.9-CD,
it's a little different version.
With the error "cannot open atapi.device": Did you install IDEfix under
OS3.9?
Is the file Devs:atapi.device file installed? try reinstalling it.
You can test the atapi.device by changing the HDToolBox-Tooltype
"SCSI_DEVICE_NAME" from "scsi.device" to "atapi.device". The CDROM
should appear (check if Unit=1 is correct), if not, the problem is
probably with the IDEfix/atapi.device.
1. a version conflict with something from OS3.9 (new devices,libraries
etc.)
2. something of the CacheCDFS/IDEFix/Mountlist-installation was
overwritten during the OS3.9-install, i.e. it's not the identical same
files anymore like under OS3.1
If it's 2., make sure all the files from the OS3.1 installation are
identically under OS3.9: L:CacheCDFS, devs:atapi.device,
DEVS:CD0(Mountlist)
If it's 1., try using the CacheCDFS from the OS3.9-CD (should be enough
to replace L:CacheCDFS). It's a slightly different version than
IDEfix97
You can also try to put "atapi.device" in the Tooltype of HDInstall
instead of "scsi.device". It should still work if IDEfix is correctly
installed. If not, maybe reinstall IDEfix. Also make sure Unit=1 is
correct.
Hi,
Here's what i did... I installed WB 3.1 on partition HD0.
Installed AMICDFS and IDEFIX97. CDROM works great.
Now i Install OS 3.9 and on HD1.
I got that message. I will try things tonite.
Does OS 3.9 not take care of CDROM IDEs??? ( I assume not b/c i got nothing
going on it as far as CDROM ide). Installing CDROM driver did not help.
What about CACHECDFS (i copied it to HD0 and will try things on HD1).
Googling did not help... i guess everyone is using SCSI on A4000???
CacheCDFS is preferred as I hope not to get this annoying 10 yr old msg
about registering... At least with OS 3.9 it's best I use CacheCDFS ???
(latest/newest vs idefix97)
3.9 can handle IDE CDRom devices also with scsi.device; with 3.1 you
needed atapi.device or compatible. Just check CD0 mount file in
Devs/Dosdrivers with a text editor, set your device to scsi.device,1 if
you have just two in your chain and CDRom as slave. It should as well
work as atapi.device. But check your versions so you haven't mixed
IdeFix and OS 3.9 files.
IdeFix works just with atapi.device.
Thus wrote c64du...@nospamyahoo.com:
> > 2. something of the CacheCDFS/IDEFix/Mountlist-installation was
> > overwritten during the OS3.9-install, i.e. it's not the identical same
> > files anymore like under OS3.1
>
> Hi,
> Here's what i did... I installed WB 3.1 on partition HD0.
> Installed AMICDFS and IDEFIX97. CDROM works great.
> Now i Install OS 3.9 and on HD1.
Now if I'm not misunderstanding you, this is where your problem happens.
By installing OS3.9 on HD1 instead of on HD0, over the top of OS3.1 as it
was meant to be done, you effectively end up with no CD driver on your
boot partition. Likewise, if you have the p5 processor libraries installed
under OS3.1 - if you have a CSPPC or similar - those can obviously only
remain functional when residing on the boot partition.
To be more exact: you boot OS3.1 and install AmiCDFS. All is well now, CD
should be working - or you wouldn't be able to access the OS3.9 installer.
Then you say you install OS3.9 on HD1, which, up to this point, is assumed
to be void of any data at all. When next you boot OS3.9, HD1: becomes your
Sys: partition, which at that time contains absolutely no CD driver. After
all, you yourself have installed that successfully onto HD0. Ergo: CD is
not being tied to the system via its mountlist and 'driver', therefore it
is not there.
You can cure this by:
either -
copy HD0:#? HD1: all quiet clone
and then proceeding to install OS3.9 onto HD1...
or -
just install OS3.9 onto your present boot partition, which is HD0:
as that can see the CD, and then boot from that one.
> I got that message. I will try things tonite.
> Does OS 3.9 not take care of CDROM IDEs??? ( I assume not b/c i got nothing
> going on it as far as CDROM ide). Installing CDROM driver did not help.
> What about CACHECDFS (i copied it to HD0 and will try things on HD1).
> Googling did not help... i guess everyone is using SCSI on A4000???
My CD-RW does sit on SCSI, but I once had another A4000 with the CD
sitting on the IDE port. Same thing, really, as to the OS they are both
on scsi.device...
In any case, when you install OS3.9, it will look at what's already there
and installed, it will then add to that and update your CD0 mountfile in
"Devs:DOSDrivers/" to reflect CacheCDFS. OS3.9 was actually meant to be
installed over the top of OS3.1 - there might even be some files missing
if it weren't.
C'ya,
--
Paul :..................: strandedUFO : http://www.sufo.estates.co.uk :.: