CD Trouble (because I meddled)

[Hyperspeed]

Hrrrm, AmiCDFS is pretty simple to mess with unlike AsimCDFS.

I'm curious as to why you needed to change the unit number for your
CompactFlash drive though.

The A4000's scsi.device is the IDE isn't it? I thought it was only the
A3000 that had REAL SCSI on scsi.device...

If MakeCD is accessing the drive though you must have the Unit numbers
correct as if there was a conflict then both would shoot themselves
clean off the radar.

:-)

You'll have to do a bit of elimination work. Try getting Phase5's
UnitControl v2.17 - this will assure you that no two devices are using
the same Unit number and are active on the chain.

You have L:AmiCDFS there as well as CD0: and CD1: in Devs/DosDrivers ?

[Hyperspeed]

Yes, very unusual.

You don't have one of those CompactFlash adaptors being discussed on
another thread - the ones that play havoc with Amigas?

:-)

Anything on the internal IDE header shouldn't affect SCSI one bit, IDE
can only have one unit number unless you have a Powerflyer or
Master/Slave.

Is the SCSI terminated fully?

Also those CF adaptors aren't hot-swappable so for it to be recognised
as a drive you need to put it in and boot, only removing when the
machine is off. If you try to hot swap it might confuse the OS.

It was really daft naming the IDE controller scsi.device, that was
bound to create confusion, but then I suppose it's related to the
A3000. Better if they had made an ide.device and a scsi.device though.

:-)

What do you mean "format zips", I thought ZIP was a PC archive system
like LHA? The only trouble you'll get is truncation to 8.3 character
filenames. The Tools/Commodities/CrossDos program shouldn't have the
text filter gadgets clicked either if you are putting ZIPs to disk as
this might alter their binary (causing CRC errors maybe).

As for your Compact Flash thing, personally I would go for a 6-in-1
internal 3.5" SCSI multi-card reader. Not only is it externally
accessible, can have 2x cards active simultaneously and has all the
benefits of SCSI... but you are also keeping your internal IDE pins
free for a backup drive. Maybe even a SiliconTech 800mb flash-drive!

:-)


----------------------

EDIT:

Oh sorry, Iomega ZiP drive disks...   DOH!

;-)

Yeah, they can play hell with the OS if you don't have a patch from
Aminet. As do Jazz and Syquest.

[Hyperspeed]

@Piru

I've always been confused...   ;-)

What I meant was older version of CrossDos (Pre v7) would truncate all
filenames down to 8.3 with capital letters if you were to transfer via
a disk format such as ZiP disks.

@X-Ray

Does a device need to be labelled as Master if there is no Slave? Or
do you just park the jumper at Master and it'll know it doesn't have
another drive?

I've heard discussions on 2nd.scsi.device before but I can't remember
what was said. Are you sure that Unit 0 is not the controller's ID?

A SCSI controller has to steal it's own ID in the chain, the Phase5
SCSI-IV kit has a SCSI ID of 7. This means you can only use 0-6, which
still leaves you with seven devices.

Do some SCSI controller interfaces have Unit 0, others Unit 7?

You didn't alter the LUN did you? Logical Unit Number is an old
standard for allowing you to use 7x SCSI devices on 7x SCSI
controllers (49 devices!!!) but it's so complex I doubt anyone uses
it.

Keep LUN to 0.

You might want to check on Reselection as that has a habit of messing
up setups that aren't totally compatible with it.

Also, you aren't being limited by the <4.2Gb limit are you? When you
stray over this the older AmigaOS would start back from the first few
bytes of the drive. I doubt this is the case though as your problem
involves multiple drives.

CD0: has the tooltype C:Mount in it's icon right?

:-)