• Hello MLAers! We've re-enabled auto-approval for accounts. If you are still waiting on account approval, please check this thread for more information.

Of stuffit and resource forks

Ok...
I either need a premade .hda file for my BlueSCSI that has some tools in it (like stuff it expander), or I need to know what the file type is for a SEA file so I can edit with ResEdit and get my stuff it .sea file working.

I've got a bunch of .sit files ready to go....
 
By default, Finder should treat anything with a filetype of APPL as an application and attempt to launch it if double clicked. Self extracting archives should NOT have a resource fork by design.

EDIT: Nevermind, doesn't work.

Most of the time these files are wrapped in BinHEX or MacBinary wrappers to preserve the resource fork. Someone here posted in the past that ClarisWorks could decode one of these, which is handy because it was usually preinstalled on most Macs.
 
Last edited:
Ok... I managed to get stuffit 4 installed.
And I have just about every disk image utility known to Apple installed...

I'm thinking the .dsk file at this link is funky:

That has the drivers for the card in my SE, but NOTHING recognises it. I'm even unzipping it ON the SE itself with stuffit.

I'm doing this from a modern MacBook. Downloading the file directly to the BlueSCSI SD card.
 
Ok so that is helpful...but what exactly are you trying to achieve? Which stuffit files? Which .sea? Do you have any intermediate Macs, like a G4 or something? On that, you can open the .hda directly on the desktop as a mounted disk image to easily transfer your files. How are you currently transferring the files between the modern MacBook and the .hda file?
 
Ok so that is helpful...but what exactly are you trying to achieve? Which stuffit files? Which .sea? Do you have any intermediate Macs, like a G4 or something? On that, you can open the .hda directly on the desktop as a mounted disk image to easily transfer your files. How are you currently transferring the files between the modern MacBook and the .hda file?
Copying them via the BlueSCSI toolbox on the SE itself.
 
Ok... I managed to get stuffit 4 installed.
And I have just about every disk image utility known to Apple installed...

I'm thinking the .dsk file at this link is funky:

That has the drivers for the card in my SE, but NOTHING recognises it. I'm even unzipping it ON the SE itself with stuffit.

I'm doing this from a modern MacBook. Downloading the file directly to the BlueSCSI SD card.
Odd, I made the image using diskcopy 4.2, I will do a check when I get home.
 
I've got an intel iMac.
And for me, this seems the least painful?

Download the files I want directly to the SD card, and then manipulate everything in the destination environment
Yes. This is much easier if you have a machine with an OS capable of mounting HFS disk images. That is your biggest issue here.
 
Well, I figured it out...
For some reason, when I unzip the file with stuffit, the file types are wrong. ResEdit to dImg and dCpy fixes it.
Odd, I thought I had made a .dsk.bin to maintain the resource fork. Will re-do and reupload. Do you have one of the New Life accelerators?
 
Odd, I thought I had made a .dsk.bin to maintain the resource fork. Will re-do and reupload. Do you have one of the New Life accelerators?
I do!
It's installed in my "SE Faux 30"

An SE motherboard, with the NewLife 16mhz 68030 W/ FPU card, in an SE/30 case (because this has the good screen)
 
I do!
It's installed in my "SE Faux 30"

An SE motherboard, with the NewLife 16mhz 68030 W/ FPU card, in an SE/30 case (because this has the good screen)
Meaning a G4 or something that can mount the SD card, mount the .hda on the desktop, and just copy the files straight out that way.
 
The image works fine, just the filetype and creator need to be set and Disk Copy opens it up. Unzip the .dsk file and copy it to your BlueSCSI image. Using ResEdit, set the filetype to 'dImg' and creator to 'dCpy'
 
The image works fine, just the filetype and creator need to be set and Disk Copy opens it up. Unzip the .dsk file and copy it to your BlueSCSI image. Using ResEdit, set the filetype to 'dImg' and creator to 'dCpy'
Yup! Figured that out a few hours ago. Sadly it looks like the NewLife board is... Funky. I suspect bad RAM.
 
Back
Top