On Friday 26 November 2004 12:55, Rikard Johnels wrote:

What filesystem? dunno, I would assume fat since it was used by a windows user

Are the partitioning intact? Can't read the disc, so I don't know. Should be only one partition though(?).

-- Kind regards Hans du Plooy Newington Consulting Services hansdp at newingtoncs dot co dot za

Out of curiosity... what is a 'stiffy' ? On Sat, 27 Nov 2004 00:58:17 +1100, Graham Smith wrote:

On Fri, 26 Nov 2004 18:22, Hans du Plooy wrote:

...

Hi all,

I'm just wondering, what do you guys use to get data off damaged stiffies? It's one of those cases where I can mount the disc (slow) but nothing is listed on it. Windows reckons the disc isn't formatted.

I don't know if this will help but there is a package called ddrescue on the SuSE distribution.

I used it to get some data off a floppy disk which failed in a number of computers because of faulty sectors. Worked like a charm, although it sounded like it was mashing the floppy in the process.

-- Regards,

Graham Smith ---------------------------------------------------------

-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

-- Andrew Betts Jasp Computer Services Ltd

On Friday 26 November 2004 9:12 am, Andrew Betts wrote:

Out of curiosity... what is a 'stiffy' ?

(storage, jargon) stiffy - (University of Lowell, Massachusetts) A 3.5-inch microfloppy, so called because their jackets are more rigid than those of the 5.25-inch and the (obsolete) 8-inch floppy disk. Elsewhere this might be called a "firmy". -- POPFile, the OpenSource EMail Classifier http://popfile.sourceforge.net/ Linux 2.6.5-7.111-default x86_64

On Friday 26 November 2004 12:11 pm, James Knott wrote:

Scott Leighton wrote:

...

On Friday 26 November 2004 9:12 am, Andrew Betts wrote:

...

Out of curiosity... what is a 'stiffy' ?

(storage, jargon) stiffy - (University of Lowell, Massachusetts) A 3.5-inch microfloppy, so called because their jackets are more rigid than those of the 5.25-inch and the (obsolete) 8-inch floppy disk. Elsewhere this might be called a "firmy".

If that's the way people talk, in Massachusetts, it's no wonder John Kerry lost. No one could understand him.

Must be something in the beans. ;-)

In Greater Chicago goloshes were ALWAYS called RubberZ even when you meant just one. PeterB

* James Knott [11-26-04 14:44]:

Rubber? I thought in Chicago, they were made with cement. ;-)

Broookllin -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos

Peter B Van Campen wrote:

On Friday 26 November 2004 1:44 pm, James Knott wrote:

...

Peter B Van Campen wrote:

...

In Greater Chicago goloshes were ALWAYS called RubberZ even when you meant just one.

Rubber? I thought in Chicago, they were made with cement. ;-)

Hi,

Patric is right, east coast gangsters favor cement shoes and salt water.

Oddly, the Great Lakes seem to **preserve** things sunk in them. CAF folks are still recovering Navy fighters and bombers that sunk in Lake Michigan during WWII. Most WWII Navy flyers did carrier t/o and landing training on Lake Michigan. There are several now flying at air showa all over. Local news did a story about the restorers finding the Navy trainee who sunk their plane. They got him in the cockpit and he said "This plane was never this clean when I flew it!"

Chicage hit men are reputed to favor putting the body in a car, crushing the car into a "Scrap-Iron Cube" and personally delivering the cube to the blast furnace.

Perhaps we should chang the subject to '"Stiff" recovery tools'. ;-)

Rikard, On Saturday 27 November 2004 04:44, Rikard Johnels wrote:

...

As i stated earlier, what filessystem is it supposed to be. Fat? Sometimes the FAT table dies. Minix? No idea on how they set the FAT up, Gooogle for that i suppose...

Try a dd if=/dev/<what device it is> of=~/image_of_disc.img bs=512 Let it run for ages :) (Sometimes it fails if the disk has damaged clusters) But its a start. Then try to look at the image with a regular text or Hexeditor. Is it anything in there at all?

The "file" command can identify file systems resident on special files if you give it the "-s" or "--special" option. Here's what it did for the first floppy I grabbed: % file -s /dev/fd0 /dev/fd0: x86 boot sector, code offset 0x4c, OEM-ID "*WFJ*IHC", root entries 224, sectors 2880 (volumes <=32 MB) , sectors/FAT 9, dos < 4.0 BootSector (0x0)

         /Rikard

Randall Schulz

On Mon, 29 Nov 2004 22:54, Hans du Plooy wrote:

On Friday 26 November 2004 15:58, Graham Smith wrote:

...

I don't know if this will help but there is a package called ddrescue on the SuSE distribution.

I thought of that, but didn't know if that would help. How did you do this?

I used it to retreive a file off a floppy. The command I used was the same as I would use for cp. dd_rescue /media/floppy/<filename> ./ It appears to change the blocksize down to where it is can retreive data from the source. I believe it can act the same a dd and copy a whole image at once although I haven't tried using that function. ddrescue - Data Copying in the Presence of I/O Errors Dd_rescue helps when nobody else will: your disk has crashed and you try to copy it over to another one. While standard Unix tools like cp, cat, and dd wail "abort" on every I/O error, dd_rescue will not. The following is the output of dd_rescue without any options given ====================================================== dd_rescue Version 1.10, garloff@suse.de, GNU GPL ($Id: dd_rescue.c,v 1.46 2004/08/28 21:45:09 garloff Exp $) dd_rescue copies data from one file (or block device) to another USAGE: dd_rescue [options] infile outfile Options: -s ipos start position in input file (default=0), -S opos start position in output file (def=ipos); -b softbs block size for copy operation (def=65536), -B hardbs fallback block size in case of errs (def=512); -e maxerr exit after maxerr errors (def=0=infinite); -m maxxfer maximum amount of data to be transfered (def=0=inf); -l logfdile name of a file to log errors and summary to (def=""); -r reverse direction copy (def=forward); -t truncate output file (def=no); -d/D use O_DIRECT for input/output (def=no); -w abort on Write errors (def=no); -a spArse file writing (def=no), -A Always write blocks, zeroed if err (def=no); -i interactive: ask before overwriting data (def=no); -f force: skip some sanity checks (def=no); -p preserve: preserve ownership / perms (def=no) -q quiet operation, -v verbose operation; -V display version and exit; -h display this help and exit. Note: Sizes may be given in units b(=512), k(=1024), M(=1024^2) or G(1024^3) bytes This program is useful to rescue data in case of I/O errors, because it does not necessarily abort or truncate the output. ========================================================== Just install it and give it a try. -- Regards, Graham Smith ---------------------------------------------------------