Access or read contents of OLD Sun flopy diskimage

Hello Darren. I am not certain there if theres filessytem or not. Old floppies from Sparc I think. Program on them is old, 1995 or so. I dont have Sparc to put in to access, so I hoped to view them in Linux. I see few filename but all gibberish then. I think gibberish is the executables maybe. I was hoping by posting raw bytes someone may see signature for filessytem or recognize there is none. Is there anything I can post from floppy which may help? If they are executables on floppy, any method to pull them off?Thank you. Kind regards, Vincent

vinnievincenta at 2007-7-8 22:29:20 >

Hello Darren. Thank you kindly for your help. I have copy of flopydisks using dd. file command against these comes back as "data". I have identify four files on one floppy I think. These filenames are ASCII and I see in hexviewer. I think I see permissions for each file too. But the file content is not human understandable, clear text. Its binary and I dont know starting and ending offset for files. Id like to copy each file from flopyimage , but I must determine start and end offset for each file. Here is raw information, does this help?

file1

00001ff: 0020 2020 2036 3434 0020 3332 3435 3620 .644. 32456

000020f: 0020 2020 2033 3720 0020 2020 2020 2020 .37 .

000021f: 3430 3737 2020 3533 3533 3633 3331 3534 4077 5353633154

000022f: 2020 2035 3730 3600 2036 3636 3332 00005706. 66632..

000023f: 0030 0000 0000 0000 0000 0000 0000 0000 .0..............

000024f: 0000 0000 002e 2f52 4541 444d 4500 0000 ....../README...

file2

0000e0f: 2020 2020 3735 3500 2033 3234 3536 2000755. 32456 .

0000e1f: 2020 2020 3337 2000 2020 2020 3137 333037 .1730

0000e2f: 3331 3020 2035 3335 3336 3333 3533 3720 310 5353633537

0000e3f: 2031 3035 3432 0020 3337 3737 3737 363710542. 37777767

0000e4f: 3037 3000 0000 0000 0000 0000 0000 0000 070.............

0000e5f: 0000 0000 2e2f 6269 6e2e 7375 6e34 582f ...../bin.sun4X/

0000e6f: 7069 6377 696e 0000 0000 0000 0000 0000 rodump..........

file3

007ca65: 3037 3535 0020 2020 2020 3020 0020 2020 0755.0 .

007ca75: 2031 3220 0020 2020 2020 2020 2020 203012 . 0

007ca85: 2020 3533 3533 3633 3337 3135 2020 203653536337156

007ca95: 3035 3000 2033 3737 3737 3733 3737 3637 050. 37777737767

007caa5: 0000 0000 0000 0000 0000 0000 0000 0000 ................

007cab5: 002e 2f6c 6962../lib

file4

007cc65: 2036 3434 0020 3332 3435 3620 0020 2020644. 32456 .

007cc75: 2033 3720 0020 2020 2020 2020 2031 363137 .161

007cc85: 2020 3533 3437 3731 3532 3533 2020 31305347715253 10

007cc95: 3537 3600 2033 3737 3737 3734 3030 3032 576. 37777740002

007cca5: 0000 0000 0000 0000 0000 0000 0000 0000 ................

007ccb5: 002e 2f6c 6962 2f70 6963 7769 6e5f 7369 ../lib/rodump_si

007ccc5: 7465 te

I think permissions for each file is 644 and 755 you see above And then time for file is 10 bytes and then filenames.

But where do I find size for files to copy them from flopyimage? If these floppies were for sparc, is not that big endian and would this affect my viewing on Linux little endian?

I am researching now how to find file size in this raw format but without knowing file system I don't know so its all trial and error.

kind regards,

Vincent

vinnievincenta at 2007-7-8 22:29:20 >

It's possible, but unlikely. Just copying the files wouldn't record the metadata (filenames, perms)

It could also be some sort of archive format (tar, bar, cpio, dump). But I would have expected 'file' to recognize any common format.

The only other thing that could be happening is that most SPARC formats would be big-endian, while your linux machine is probably on a x86 little-endian architecture. It's possible that using 'dd' to byteswap the data could help. But that's just a shot in the dark.

Otherwise, I don't have a clue as to how this data is recorded/encoded.

Darren_Dunhama at 2007-7-8 22:29:20 >