Forum unknown
· Hardware
#hard disk installation
11 messages in this thread
We have just announced our controllers for the 2000 and 500 at a suggested
retail of $199.95. With normal dealer margins (meaning room to discount).
Can Perry compete in that price range?
Also we have a new driver which will be posted here soon that will (using
Piskperfa or the Amizing composite `real-world' tests) move our unit's
speed better that the competition's DMA drive, without in- curring the
penalties of using DMA.
I'm real curious…what would happen if I tried my HD with your driver? I
presume they wouldn't work together…but I'm not brave enought to destroy
all the data on the disk to find out…even with a backup. Have you by any
chance tried anything like that?
All drivers for AutoConfig Devices are Device Specific in that they call
the Amiga `FindConfigDevice' routine to find out where the device is in the
memory map. The call to find the device requires the use of the `Hardware
Manufacturer's Code Number' provided by Commodore to all hardware
developers. Without this code number (ours is 1004) you can't tell where
our SCSI Host is, but using it precludes using our driver with other SCSI
Host/Controllers.
BTW, we have several `beta' sites up-and-running with our new multi-user
software. Still a few bugs, but all reports have been very favorable. One
application is using five (5) Amigas on a 150 MEG Micropolis. This system
is used by five 1-800 operators taking orders from incoming telephone calls
and logging them on a database, the guy says the system operates
substantially faster than when all entries were made to the individual
Amiga floppies and that the 5 units don't seem to slwo down the system
access time at all. The guy also reports two to three crashes a week,
requring rebooting of the system, but has incurred NO data loss resulting
from the crashes. The next revision of our driver will fix that problem
(we know what's causing it) and speed up the system even more.
All drivers for AutoConfig Devices are Device Specific in that they call
the Amiga `FindConfigDevice' routine to find out where the device is in the
memory map. The call to find the device requires the use of the `Hardware
Manufacturer's Code Number' provided by Commodore to all hardware
developers. Without this code number (ours is 1004) you can't tell where
our SCSI Host is, but using it precludes using our driver with other SCSI
Host/Controllers.
BTW, we have several `beta' sites up-and-running with our new multi-user
software. Still a few bugs, but all reports have been very favorable. One
application is using five (5) Amigas on a 150 MEG Micropolis. This system
is used by five 1-800 operators taking orders from incoming telephone calls
and logging them on a database, the guy says the system operates
substantially faster than when all entries were made to the individual
Amiga floppies and that the 5 units don't seem to slwo down the system
access time at all. The guy also reports two to three crashes a week,
requring rebooting of the system, but has incurred NO data loss resulting
from the crashes. The next revision of our driver will fix that problem
(we know what's causing it) and speed up the system even more.
I'm real curious…what would happen if I tried my HD with your driver? I
presume they wouldn't work together…but I'm not brave enought to destroy
all the data on the disk to find out…even with a backup. Have you by any
chance tried anything like that?
Penalties of DMA? If you are talking a price penalty, I can understand,
but am having difficulty figuring out what else you might mean. Could you
clarify?
Yes Price is the major penalty, but there are some other more
subtle prices to pay when DMA is used. Most notably in our case, our
SCSInet would be virtually imopssible to implement on a DMA basis. (This is
per the programmer of same, I will check further to see if he means
`impossible' or just a lot more work that he's willing to exert.)
Yes Price is the major penalty, but there are some other more
subtle prices to pay when DMA is used. Most notably in our case, our
SCSInet would be virtually imopssible to implement on a DMA basis. (This is
per the programmer of same, I will check further to see if he means
`impossible' or just a lot more work that he's willing to exert.)
Penalties of DMA? If you are talking a price penalty, I can understand,
but am having difficulty figuring out what else you might mean. Could you
clarify?
Ed, your query “Can Perry compete in that price range?'' belies an
important misconception that you have about ASDG. We are not interested in
competing with anyone in low end market. In fact, we are not even IN the
low end market.
People who purchase from ASDG have their reasons. They usually dismiss low
end product lines, such as yours, out of hand for reasons of incompatible
needs versus capabilities. This is not to say that ASDG products are right
for everyone. Nor am I saying C Ltd products are wrong for everyone.
Simply, that our two company's are not competitors at the present time.
Perry S. Kivolowitz – ASDG Incorporated – (201) 563/0529
Ed, your query “Can Perry compete in that price range?'' belies an
important misconception that you have about ASDG. We are not interested in
competing with anyone in low end market. In fact, we are not even IN the
low end market.
People who purchase from ASDG have their reasons. They usually dismiss low
end product lines, such as yours, out of hand for reasons of incompatible
needs versus capabilities. This is not to say that ASDG products are right
for everyone. Nor am I saying C Ltd products are wrong for everyone.
Simply, that our two company's are not competitors at the present time.
Perry S. Kivolowitz – ASDG Incorporated – (201) 563/0529