Found it; was RE: [ale] Zip-drive headaches

Tue Jul 27 19:17:35 EDT 1999

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01BED886.377800C2
Content-Type: text/plain;
	charset="ISO-8859-1"

Earlier I foolishly typed:
JMM> Having some problems with Zip-100's under
JMM> RH6.0/Hedwig [2.2.5 kernel]

Not knowing quite the cause, I apparently stumbled on the cure: I rebooted
to a kernel I had built after installing RH6.0, and lo-and-behold the Zip
disk came back to life. I suppose the original kernel couldn't use, or
wouldn't use, the new module, else was looking for a no-longer-extant
module. Naturally, a software problem that my drive balled up.

"Even a blind pig finds the occasional acorn."
					-Traditional Wisdom
  John Mills, Sr. Software Engineer
  TGA Technologies, Inc.
  100 Pinnacle Way, Suite 140
  Norcross, GA 30071-3633
  e-mail: jmills at tga.com
  Phone: 770-441-2100 ext.124 (voice)
         770-449-7740 (FAX)

-----Original Message-----
 From: John Mills [mailto:Jmills at TGA.com]
Sent: Tuesday, July 27, 1999 11:53 AM
To: 'ALE'
Cc: John Mills
Subject: [ale] Zip-drive headaches

:

1) mounting a DOS-formatted zip-diskette and writing a *.bz2 or *.gz, the
directory shows a file of the same size on the Zip, but it no longer appears
a file of the same type to either 'file' or the appropriate *unzip. It now
differs ('diff') from its original. Copied back to the hard disk, results
are the same: the file seems to have been corrupted.

2) making an ext2fs on the diskette, large numbers of inodes are erroneous.
Presistently typing 'y' through 'fsck' eventually results in a disk with
lots of nodes in lost+found, and I cannot delete them.

3) making a dosfs on the diskette and returning to a WinNT box, diskette
fails diagnostics because data cannot be written to it.

4) swap to a new drive, then swap to the other IDE interface similarly
failed to change this.

If I still had Win95 on that box, I could boot and try the drive in place,
but unfortunately I don't! ;^)

Suggestions?

  John Mills, Sr. Software Engineer
  TGA Technologies, Inc.
  100 Pinnacle Way, Suite 140
  Norcross, GA 30071-3633
  e-mail: jmills at tga.com
  Phone: 770-441-2100 ext.124 (voice)
         770-449-7740 (FAX)

------_=_NextPart_001_01BED886.377800C2
Content-Type: text/html;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
</pre>
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DISO-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2232.0">
<TITLE>Found it; was RE: [ale] Zip-drive headaches</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Earlier I foolishly typed:</FONT>
<BR><FONT SIZE=3D2>JMM> Having some problems with Zip-100's =
under</FONT>
<BR><FONT SIZE=3D2>JMM> RH6.0/Hedwig [2.2.5 kernel]</FONT>
</P>

Not knowing quite the cause, I apparently stumbled on =
the cure: I rebooted to a kernel I had built after installing RH6.0, =
and lo-and-behold the Zip disk came back to life. I suppose the =
original kernel couldn't use, or wouldn't use, the new module, else was =
looking for a no-longer-extant module. Naturally, a software problem =
that my drive balled up.

<P><FONT SIZE=3D2>&quot;Even a blind pig finds the occasional =
acorn.&quot;</FONT>
<BR>        =
            =
        <FONT SIZE=3D2>-Traditional =
Wisdom</FONT></P>

John Mills, Sr. Software Engineer
 TGA Technologies, Inc.
 100 Pinnacle Way, Suite 140
 Norcross, GA 30071-3633
 e-mail: jmills at tga.com
 Phone: 770-441-2100 ext.124 (voice)
 =
770-449-7740 (FAX)

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: John Mills [<A =
HREF=3D"mailto:Jmills at TGA.com">mailto:Jmills at TGA.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Tuesday, July 27, 1999 11:53 AM</FONT>
<BR><FONT SIZE=3D2>To: 'ALE'</FONT>
<BR><FONT SIZE=3D2>Cc: John Mills</FONT>
<BR><FONT SIZE=3D2>Subject: [ale] Zip-drive headaches</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>:</FONT>
</P>

1) mounting a DOS-formatted zip-diskette and writing =
a *.bz2 or *.gz, the
 directory shows a file of the same size on the Zip, =
but it no longer appears
 a file of the same type to either 'file' or the =
appropriate *unzip. It now
 differs ('diff') from its original. Copied back to =
the hard disk, results
 are the same: the file seems to have been =
corrupted.

<P><FONT SIZE=3D2>2) making an ext2fs on the diskette, large numbers of =
inodes are erroneous.</FONT>
<BR><FONT SIZE=3D2>Presistently typing 'y' through 'fsck' eventually =
results in a disk with</FONT>
<BR><FONT SIZE=3D2>lots of nodes in lost+found, and I cannot delete =
them.</FONT>
</P>

<P><FONT SIZE=3D2>3) making a dosfs on the diskette and returning to a =
WinNT box, diskette</FONT>
<BR><FONT SIZE=3D2>fails diagnostics because data cannot be written to =
it.</FONT>
</P>

<P><FONT SIZE=3D2>4) swap to a new drive, then swap to the other IDE =
interface similarly</FONT>
<BR><FONT SIZE=3D2>failed to change this.</FONT>
</P>

If I still had Win95 on that box, I could boot and =
try the drive in place,
 but unfortunately I don't! ;^)

<P><FONT SIZE=3D2>Suggestions?</FONT>
</P>

John Mills, Sr. Software Engineer
 TGA Technologies, Inc.
 100 Pinnacle Way, Suite 140
 Norcross, GA 30071-3633
 e-mail: jmills at tga.com
 Phone: 770-441-2100 ext.124 (voice)
 =
770-449-7740 (FAX)

</BODY>
</HTML>
<pre>
------_=_NextPart_001_01BED886.377800C2--