Re: GS + Apple 3.5 non-functional

[Lockar <lockar@nospam.com>]

  Donald,

    Well that's good to hear. Second huh?  I guess us collectors can't
have enough of them.. I think I have 4 of them (1 ROM 03, and 3 ROM
01).

      -Lockar


 In article <Od2xb.37016$R13.1171087@ursa-nb00s0.nbnet.nb.ca>, Donald
Bailey <dbailey@nospam.inherentsys.ca> wrote:

> The drives are fine.  They both booted a Mac.  I've since purchased a 
> second IIGS and they boot Copy ][+ and AppleWorks without incident.
> 
> Donald
> 
> Lockar wrote:
> >    Donald,
> > 
> >       Are you sure that your 3 1/2 disks haven't gone bad.   You said
> > your 5 1/4 disk drives work.  Do you have Copy II Plus or some other
> > ProDOS utils on a 5 1/4 disk?  If so boot from them and try to format a
> > 31/2 disk and put ProDOS and some other programs on it.  If it boots
> > then, I would say your 3 1/2 disks went bad on you.
> > 
> >     -Lockar
> > 
> > 
> > In article <1065268678.761416@nala.inherentsys.net>, Donald Bailey
> > <dbailey@inherentsys.ca> wrote:
> > 
> > 
> >>The 3.5"s are first, 5.25s second.  The drives have not be hotplugged.  If
> >>they were Disk ][s the first thing I'd look for is a 74LS161 with a hole in
> >>it (been there a few times with offset connectors 10-15 years ago) alas the
> >>GS doesn't have that problem.
> >>
> >>The control panel was double checked before posting, that slot 5 is set to
> >>SmartPort, and it is also set to boot from slot 5 FIRST to make sure the GS
> >>was in fact going to attempt that.  No 5.25s are currently connected - just
> >>a single 3.5.  No luck booting.  When only a 5.25 is connected and the GS is
> >>set to boot from 6, the 5.25 boots the disk fine.  Again, I tested the cable
> >>from one of the 3.5" drives from the drive side of the cable through to the
> >>underside of the GS board and was fine.
> >>
> >>It is entirely possible that both drives are dead. It's been my experience
> >>in the repair business that if there is something in common between two
> >>problems it's probably the common device that's the problem.
> > 
> > 
>