Search results

Yeah I've noticed that too.  Salvaged one for the 3400c I think, but not for the Kanga.  So it's not recurring corrosion from that in this case.  Look I don't know.  Hopefully yours comes out fine, but I don't think it's worth the risk - particularly since who really cares about PRAM batteries...

I asked an admin to remove a note I'd made to where someone currently works.  I'd then noted that while disparate bits of public information are, of course, public, and thus not subject to a tort action under revelation of private facts, that at least in NJ pulling together bits of public info...

Oh okay.  GSOS can't copy to ProDOS; for whatever reason I assumed that extended to ProDOS.  I tried formatting a disk in DOS 3.3 and failed earlier so I'll try another disk (like physically another disk) later.  Let's see if I can get that far.  I appreciate the help!

But Elfen my goal is to copy files from ProDOS archives to DOS 3.3 disks.  Remember your point was that none of the CPM disks will work if not in DOS 3.3, but the images they're in are all ProDOS archives.  So what you're saying appears to suggest I have no options, lol, right?

No I understand.  My damage wasn't immediately under the battery on the 3400c.  Is it possible that corrosion can travel along wires or traces - which would also explain why the wire from the battery to the power distribution board (all along that wire) is often corroded.  I mean on the 3400c...

Initially I thought I could read 5.25" ProDOS disks on DOS 3.3.  But I'm now guessing you can't.  So how can I transfer the files from their ProDOS format disks to an Apple DOS 3.3 disk?  GSOS cannot format or write to the latter.  DOS 3.3 cannot read the former (lol) as best I can tell.  I feel...

Yep. That's a relist of the one I posted. Let me know when it destroys your machines, but keep in mind it didn't take very long for me. And it didn't drop. It just corroded with the irregular charge/discharge schedule. I suppose perhaps I had some very obscure problem, but I would take the...

it's the replacement PRAM batteries I recommended in another thread.  They've caused serious corrosion in the Kanga and a 3400c over only a few months.  The 3400c still seems fine.  The Kanga gets past the RAM test and to the screen on-mouse, but that's it.  I haven't tried the SCSI yet.  I'll...

eh... http://apple2.org.za/gswv/a2zine/faqs/Csa2FDRIVE.html#009 well wait i mean i can't really picture what you're saying about boot but i assume you mean that it doesn't seem to be scanning the drives normally.  i can't imagine that link will help but does anything in that seem ballpark...

And this is the "Apple 3.5" drive?"  https://en.wikipedia.org/wiki/Macintosh_External_Disk_Drive#Apple_3.5.22_Drive.  Had these specific drives worked with this IIgs before? Also does it still seek the 5.25" drive on boot if you chain it through the 3.5" drive?

I mean... I don't... but when you say doesn't recognize, do you mean it doesn't appear to read them on boot or it doesn't recognize in some system (I'm thinking specifically GSOS where you might have to expressly install the drivers).  [And I don't think DOS 3.3, to continue this line, can read...

I also had to do the two contacts on the bottom and the contacts on the top-side of the board (like where the two metal prongs on the bottom come up).  The picture you posted, I think, just shows the three pads on the bottom but that didn't work by itself for me [like at all; I found I had to...

The relevant part of the manual says this: "1 Verify that adjacent computer equipment is properly grounded. Move electrical devices away from monitor. Temporarily shut off all fluorescent lights in area. 2 Check that all ground cables are secure. 3 Disconnect internal hard drive and floppy...

I've had mixed luck with this.

Hmm. I was thinking solder joints. Since it seems nobody here knows, I'll do a little research when I have time.

I already found his email and sent it to K55. He actually works at /location/.

Oh, okay so the dd command is not a workaround.

Isn't that interrupt/blank prompt a resource fork issue?  You had a bad image (or one that you corrupted on your end), I think.

No, it still flickers seemingly at random.  This time on power on it started out a bit magenta and then reverted to normal.  But as noted it'll basically sort of flicker at random - not often; not enough to be really bothersome.  But enough to be a little annoying.

(that's a really good point; i'd never tried that!)