I have used both a 416 and a 1616 with Win 95 and SCSI. I have also had
problems using the 1542 series of adapters with the Pictors and Win 95. Your
first statement is only partially correct: some SCSI installations on Win95/98
are not possible and some are possible.

What is particularly disappointing about the 1542 series is that, as you note,
it works under DOS drivers and Win 3.1. I believe that the problem is an
inconsistency in the drivers between DOS mode and Win 95 drivers for this
device. The fact that the 1460A (which is reported to use the same chip set as
the 1542 series) does work and the fact that several other Adaptec drivers do
work indicate that there is some type of inconsistency in the drivers for Win
95. This is no solace for those with the 1542 series but you cannot extrapolate
to all SCSI interfaces from this one class. By the way, the problem seems to be
in how the device is initially seen by the operating system. In my case, EZSCSI
did not see it under Win 95 although it was seen by the BIOS in bootup and with
DOS drivers. One of the tests I did was to have the Pictor system powered down
and a second SCSI device (I used a JAZ drive) powered up and set to unit 4 (my
unit number for the Pictor), and power up the computer, After the operating
system was up, I powered off the JAZ drive and powered up the Pictor system, and
voila, Pictorview worked with a 1542.

I do not think the problem is in the PictorView software per se. I think it is
a combination of the SCSI driver logic and perhaps the Flash code in the Pictor
interface box.


Perhaps if Adaptec would release its software perhaps some of us could fix their
bugs.


Ralph Pass




Renato wrote:

> Well done Chris, this is a nice initiative, although SCSI installations on
> win 95/98 are not possible. On my system 486DX66 with 16MB RAM and a Adaptec
> 1542CP SCSI controller with the newest drivers my Pictor 416 is seen by
> ASPI4DOS and there is SCSI Connect on the LCD display but continuing booting
> win95 it changes into a *ABORT* SCSI CONNECT message. SHOWSCSI doesn't
> detect the camera neither does PictorView 6.43 or 6.44b1. As far I can tell
> SCSI works only with WIN 3.11 and is slower than a serial connection if you
> put enough delays in not to lock up every couple (American "couple"
> {multiple} not Australian {2}).
> So far I am VERY DISSATISFIED with the PICTOR 416XT it's firmware and the
> PictorView software. The product should have not be released in first place
> and I'm sorry that I bought it!
>
> Maybe if MEADE releases the source code some of us can fix the bugs, but
> this might be a little to much pride to swollow.
>
> Renato Langersek
>
> -----Original Message-----
> Heapy Chris CG
> Sent: Wednesday, 12 May 1999 19:28
> Subject: [M]: 416XT - Idiot's guide
>
> I'm pulling together a simple guide for setting up and using the 416XT CCD
> camera. It's not yet finished, but enough of it I think for a new user to
> test their setup. Would appreciate feedback on errors, ommisions and even
> contributions! (I know the connection diagram is not yet working)
>
> It's here:
> http://easyweb.easynet.co.uk/~chrish/416_ig.htm
>
> Chris Heapy

View index by [date] [author] [subject]
Previous message: [M]: RE: RE: 416XT - Idiot's guide, Heapy Chris CG
Next message: RE: [M]: RE: 416XT - Idiot's guide, =?iso-8859-1?B?SvZyZyBKb2hhbm4gTfxsbGVy?=
Next message in thread: RE: [M]: RE: 416XT - Idiot's guide, =?iso-8859-1?B?SvZyZyBKb2hhbm4gTfxsbGVy?=
Previous message in thread: [M]: RE: RE: 416XT - Idiot's guide, Heapy Chris CG