| Click here to select a new forum. |
| MacOS 7.7 Prototype Drive Imaging |
Posted by: jajan547 on 2022-06-15 08:42:43
I’d love a copy. Using DiskCopy in my opinion is the best way to make it easily accessible on its target machine. Using dd, raw images and all that won’t make it easy to open on a System 7.x Mac. @Johnnya101 if you’ve booted do you see what I mean about the strange debugger at boot that’s followed by the Mac OS typical boot screen? |
Posted by: CC_333 on 2022-06-15 09:07:30 Using dd wouldn't make the resulting image very (real or emulated) Mac friendly, but it would capture numerous low level details of the disk that Disk Copy misses, like the drivers and partition structure, so it might be worth making a raw dd image after the DC image is made?
c |
Posted by: Johnnya101 on 2022-06-15 11:57:51 I don't have time just this second to complete the rest of the page, but its uploaded at least. DiskCopy 6 image stuffed with Stuffit on OS 9.2.2. Maybe someone would be kind enough to try it out to make sure it is a good image?
Pre-release Mac OS 7.7.x – Mac OS 8.x Codenamed: Tempo. Once Mac OS 7.6.1 had gone gold, initial alpha & beta versions of the Mac OS released from developers to testers, were labelled "Mac OS 7.7" under the code name "Tempo".
macintoshgarden.org
|
Posted by: jajan547 on 2022-06-15 11:59:50
I don't have time just this second to complete the rest of the page, but its uploaded at least. DiskCopy 6 image stuffed with Stuffit on OS 9.2.2. Maybe someone would be kind enough to try it out to make sure it is a good image?
Pre-release Mac OS 7.7.x – Mac OS 8.x Codenamed: Tempo. Once Mac OS 7.6.1 had gone gold, initial alpha & beta versions of the Mac OS released from developers to testers, were labelled "Mac OS 7.7" under the code name "Tempo".
macintoshgarden.org
I’ll try it later today. |
Posted by: jajan547 on 2022-06-15 15:20:37
I’ll try it later today. Ok so it does work but it’s be cool if we had a .hda to just boot it outright, I know that takes time but to answer your question basically yes it works and all files look to be present. |
Posted by: Johnnya101 on 2022-06-15 18:26:28 If I could get someone to walk me through step by step using a Mac (dd command), I would gladly do that. I haven't done any command line hard drive work before really on anything sensitive like this. There's some info online about it, but I'd prefer someone on here to post instructions.
Good to know it works otherwise though. |
Posted by: jajan547 on 2022-06-15 18:34:55
If I could get someone to walk me through step by step using a Mac (dd command), I would gladly do that. I haven't done any command line hard drive work before really on anything sensitive like this. There's some info online about it, but I'd prefer someone on here to post instructions.
Good to know it works otherwise though. @CC_333 probably knows the best seems they know DD well. |
Posted by: CC_333 on 2022-06-15 19:14:21
probably knows the best seems they know DD well. I don't know DD that well, really. I basically just know enough to be dangerous 😉
c |
Posted by: jajan547 on 2022-06-15 19:15:26
I don't know DD that well, really. I basically just know enough to be dangerous 😉
c Dangerous can help though haha any tips? |
Posted by: Johnnya101 on 2022-06-15 19:30:41 Maybe dangerous enough to accidentally deleted a drive? Lol, that's probably how I'd be |
Posted by: CC_333 on 2022-06-15 19:51:51
Dangerous can help though haha any tips? I can't really think of anything relevant, other than typical boilerplate stuff: be careful to get the drive IDs right, and don't confuse your if's and of's (input files and output files).
Maybe dangerous enough to accidentally deleted a drive? Lol, that's probably how I'd be I'm as bit better than that, thankfully (I've learned the hard way: from past experience).
As a result, all the files that I made back when I first got my Tangerine iMacs and iBook have pretty much been lost to time, although I do think I have some that are still on an old, broken hard drive (I actually managed to get an exact replacement for the controller board of that drive, but the heads wouldn't seek when I tried it, which means the information on that drive is effectively lost for now. I'm still keeping that drive, in case somehow I can get my stuff off of it.)
c |
Posted by: Compgeke on 2022-06-16 06:10:29 I'd recommend going with ddrescue over straight dd. Not only does it provide a progress bar, it also does retries on bad sectors and makes a list of any parts of the disk it can't read. No need to deal with if and of either.
ddrescue -d -c 400 -b 512 -r 3 /dev/whateverthedriveis os77.img os77.map |
Posted by: jajan547 on 2022-06-17 17:13:09 Hey there how's things going? |
Posted by: Johnnya101 on 2022-06-17 18:49:46 Was not able to get to trying the ddrescue, but will definitely have a go tomorrow. Sorry to drag this out been really busy and don't want to rush something like this. |
Posted by: jajan547 on 2022-06-17 18:58:38
Was not able to get to trying the ddrescue, but will definitely have a go tomorrow. Sorry to drag this out been really busy and don't want to rush something like this. No rush time is important with stuff like this. |
Posted by: Johnnya101 on 2022-06-18 14:50:37 Anyone able to provide step by step instructions for dd to do an exact image using a modern Mac? That's the easiest/quickest computer I have available for this at the moment. DDrescue looks like its for linux. |
Posted by: demik on 2022-06-18 16:26:25 It's relatively easy.
I'm assuming you are using an IDE to USB enclosure. Just plug it to your Mac, then find it using diskutil:
> sudo diskutil list
After you have find it (let's assume it's disk3), just dd it:
> sudo dd if=/dev/rdisk3 of=ide77.img bs=512
if you are unsure, paste the output of diskutil list here.
Note: using rdisk3 instead of disk3 is recommended |
Posted by: Johnnya101 on 2022-06-18 16:36:21 Got it, thank you! Will try right now. Yes, USB to IDE. |
Posted by: Johnnya101 on 2022-06-18 16:44:37 Have the output of three disks, two are for the internal Mac drive, and the last, disk 3 (/dev/disk2) is the disk in question. Where do I put the path in your above command @demik ? I'd think the ide77.img is the output file name. Would I replace the first part with if=/dev/rdisk2? Or is rdisk3 an actual part of that? |
Posted by: demik on 2022-06-18 17:27:43 You are correct, you need to use if=/dev/rdisk2. The ide77.img is indeed the file name and dd will write in the current directory (if you didn't change anything your terminal should be in your home directory). You can also specify a full path here, example:
sudo dd if=/dev/rdisk2 of=/Users/Johnnya101/Downloads/ide77.img bs=512 |
| < 2 > |