Unable to scan multiple pages when using PaperPort Problem: When using an ADF (automatic document feeder) scanner in PaperPort, it may not be possible to scan multiple pages at a time without user intervention. I have tried to setup scanning on 2 identical computers running Win 10, so I know its not a OS issue on the first machine. The odd thing is that the default Windows Scan works, but obviously there is no PDF option.
Problem Trying to restore mac, used disk utility to make backup image.dmg, now won't create 'imagescan' to boot from it. I heard online that Mac will make a.dmg backup, but will not boot from an external 2.0 hard drive (even though it has been formatted for mac.).
Apple may provide or recommend responses as a possible solution based on the information provided; every potential issue may involve several factors not detailed in the conversations captured in an electronic forum and Apple can therefore provide no guarantee as to the efficacy of any proposed solutions on the community forums.
The easiest for me has always been to use a dedicated external harddrive, and just format it as Mac OSX only. Sure its annoying not to be able to swop files with a PC but i think the drive you put your disk image on shouldn't be used for general storage, it should be stashed safely in a safe. Use another drive for copying files etc.
Most tutorial suggest to make a bootable USB starting by the installer InstallESD.dmg, found in installer.app. I would like instead to run the.dmg directly. So I have three 'propedeutic' questions: can I just mount and run the.dmg without making a bootable drive? I do have backup, a TimeCapsule one to be precise.
Run Apple Software Restore from the command line | 7 comments | Create New Account
Click here to return to the 'Run Apple Software Restore from the command line' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
I still have not been able to get the hdiutil command to convert a read/write disk image into a read-only or compressed image, and have the resulting image mount! Since you need a read-only or compressed image for 'asr' to do its magical checksumming, I am stuck. I have tried running hdiutil from the command line and running Disk Copy and doing the conversion there. All result in an error 'no mountable volumes'! Until I get past that, I am unable to use 'asr' from the command line, as 'asr' tries to mount the compressed image after computing its checksums.
Thanks for the pointer on ASR, that'll come in handy when I upgrade a lab of 60 iMacs to 10.2.X As for invictus' problem: A little while back I combined various hints and wrote a shell script that created a compressed disk image from a folder. I used something like this to convert the r/w image into a ro-compressed image: hdiutil convert original.dmg -format UDZO -o compressed.dmg I just tested this again with a a couple of small images (from 1-100MB) and it still seems to work in jaguar. Let me know if this works for you, I haven't tested with a full image of a system, so maybe there's an issue there.
I have prepared images and compressed them or converted them to read-only, mounting them successfully afterwards. Several different sizes, including a 2 gigabyte one that was almost completely full. No problems. It looks like it is just system images (perhaps the boot block info?) that have the problem.
I decided to skip the conversion step and simply go from a disk partition to a compressed image and see what 'asr' could do with that. Here is the sequence I got with the latest one: There are several things going on, after some reading. A compressed image can still be mounted so that checksums can be computed for many of the files and folders. Once these are done, the image is 'unflattened', i.e., made multipart so that the checksums can be appended. Something seems to be going wrong with these steps.
Well, I think I have got it, but it will take a few more hours of testing to confirm. I wanted to let you know that I surmounted one of the hurdles. Since 'asr' cannot seem to 'unflatten' the image, its image scanning function fails. So, I unflattened the image for it: hdiutil unflatten macosx10.1.5a.dmg sudo asr -imagescan macosx10.1.5a.dmg It worked! (or at least, no error messages, which is really not the same thing at all) So, progress at least.
When I try to use my iBook (OSX 10.2.1) Software Restore CD's on my G3 Firewire PowerBook I get the message '...this disc cannot be used on this model...'. Any idea how to get around this?
After a lot of trial and error, mostly error, I got 'asr' to work.
There were two bugs/limitations in Apple software that I had to deal with, that clouded much of the issue.
Disk Copy 10.2.2 supports disk images larger than 2 Gigabytes, essential to imaging a 10.2.2 release. However, when you create the disk image, you cannot use the sparseimage format. You must create a disk image of the appropriate size (perhaps 10% larger than the files you are going to copy to allow for the block size issue), and then do the copy.
asr can only work on compressed or read-only disk images, that have been unflattened.
What this means in practice
I originally tried to use Carbon Copy Cloner 2 to create the image from a prepared partition on the computer. However, CCC creates a sparseimage format image which led subsequently to all of my headaches in later stages. Once I figured out that creating the image beforehand was essential, everything started to work. You can still use CCC to do all of the useful stuff.
The final steps in the sequence are to unflatten the read-only image, do an image scan, and flatten the image again. After that, you can use asr to prepare all of your disks. Thus:
I'm trying to maintain my sanity here. I've gone through all of the messages I can find on this but I'm still having issues with ASR. The really frustrating thing is that I'm not getting error messages, just the help screen from ASR. I'm sure that I'm using the correct syntax, I've tried it with flattened and unflattened, and compressed image files but it's the same resuly. I'd really like to benefit from the wisdom of the group - any insight as to what might be missing? Thanks.
This is an introductory tutorial on using InstaDMG, a OSX package and image maker, to create clean never booted disk images of OSX 10.8 Mountain Lion.
Previous tutorials on InstaDMG and OSX 10.7 has three parts, base image, base image + user, base image + user and system modifications.
For those not familiar InstaDMG is a powerful command line tool application used to produce clean never booted OS X images, these images can include OSX incremental upgrades as well as 3rd party software and scripts.
This guide is for getting a clean never booted up to OSX 10.8.4 Mountain Lion Image. You will need the OSX 10.8 installer which is named the InstallESD.dmg
Get InstaDMG
Navigate to your home and create a directory name ‘instadmg’ and change directory to it.
Download InstaDMG.
Updating InstaDMG
As new OSX updates are made available the InstaDMG code is changed to include the new upgrades, to update InstaDMG, move into the directory it is installed in and run the svn update command:
Preparing the Base OS X 10.8 Image
After the InstaDMG is downloaded the next step is to make a base installation image of OS X 10.8 Extract the InstallESD.dmg from the Lion.app after it is downloaded from the App Store and before it is installed, as when it is installed the app is then deleted – this guide shows how to reveal the InstallESD.dmg and also a guide to burn a generic copy of 10.8 to disk.
Move the InstallESD.dmg file from Mountain Lion in the path below in your InstaDMG location and move onto the next section:
Using the Catalog File
The catalog file is the all important file that contains the installer build numbers plus all the incremental OSX updates, the latest version of InstaDMG now has an OSX Mountain Lion 10.8 catalog file as at version revision 480.
– The OSX 10.8 Build number for the initial build is at the top, 12A269, 12B19, 12C54, 12D78, 12E55
– Below are the OSX incremental updates in the format of name, download link and SHA1 encryption key – these are tab separated on one line per item (grab shows them soft wrapped).
– If you don’t want to include a certain update in the build just add a comment (#) to the beginning of the line.
If you only have an older install build you can add the latest OSX 10.8.4 combo, by adding in the update in the OS Updates section just paste in the line below.
Make The OSX Image
Move into the InstaDMG location and to build the image you run the all important instaUp2Date command with sudo.
Unable To Scan Installesd.dmg Function Not Implemented
The .catalog extension does not need to be added in running the command. The command will take a while to run depending on your RAM and processor power. The OS X incremental updates are downloaded and stored on your local drive, future builds will only pull down new updates.
The disk image is spat out in the directory – “~/InstaDMG/OutputFiles” named “10.8 Vanilla.dmg” which is the all-encompassing new master image. The final output at the tail of the command in the Terminal will be like this:
And there you have it one OSX 10.8 image ready for deployment, which can be used in any deployment method including ASR, DeployStudio or as a NetBoot image.
You may get errors when running the command above such as:
But you do have the installer disc filed in the right place! – just reboot and try again.
Restoring via ASR
You could push this image to another drive using ASR – this will erase your target Volume:
Part 2 of this InstaDMG tutorial takes you through setting up a local user account on the images and adding files that allow you to bypass registration process.